ingridleiria Investor Update
Investors read updates for two things: the trajectory of the numbers and the judgement of the person writing them. The failure this prevents is the update that quietly destroys both. It arrives late, or not at all in the months that were difficult. Its sections move around, so no reader can lay three of them side by side. Its metrics change definition without notice, so the series that looked like growth turns out to be a measurement change. And the bad news is either absent or arrives four months after it was known.
The cost is not embarrassment. It is that the update is the only instrument a founder has for converting shareholders into a source of help, and help arrives on the basis of trust accumulated in advance. A founder who has sent eleven honest updates can send the twelfth saying the quarter was bad and get three useful introductions inside a week. A founder who went quiet for two quarters and then asks for help gets a meeting request instead, because the shareholders now have to reassess the company before they can act. Silence is read as trouble, and the reading is usually worse than the truth.
When to use this, and when not to
Use it for any periodic written communication to people who have put money into the company: monthly notes to angels and seed funds, quarterly letters to a wider shareholder base, updates to a syndicate lead, notes to investors who did not join the last round, and the short progress note sent during a raise.
Do not use it for material going to the board. board-deck builds the pack that reports to directors and asks them to decide things; this update reports to people who are not deciding anything and should not repeat the pack. Do not use it for the relationship work around directors, which is board-and-investor-management.
Do not use it to assemble what an investor will demand in diligence. That is fundraise-readiness, and it will check these updates against the metrics pack, so anything defined loosely here becomes a question there. Do not use it to make the argument for a new commitment, which is pitch-deck; an update reports, and a deck persuades, and mixing them makes the update unreadable and the deck unbelievable.
What you need before starting
Closed numbers with written definitions. Missing: use the last closed period, say so, and label anything provisional. Do not switch to whatever number is available, because the series is the point.
The previous update. It sets the sections, the order, the definitions and the promises made. Missing: reconstruct the metric set from the accounts and state in this one that the format is now fixed.
Cash balance, net monthly burn, and runway. Missing: do not send. Every other section can be estimated; this one is why several readers open the email.
The asks. Two to four things a reader can act on. Missing: ask the leadership team what is blocked, and if the honest answer is nothing, write "no asks this month" rather than inventing filler.
The bad news, if any. The miss, the departure, the customer that left, the delayed launch. Missing: ask directly, because it is usually known and not volunteered. An update where nothing went wrong in a month is not an update, it is marketing.
The recipient list and its confidentiality constraints. Who is on it, whether any recipient is a competitor's investor, and which customer names may be used. Missing: use descriptors rather than names, and resolve the list before the next send.
The method
Fix the send date and hold it. The same working day each month. Late updates signal something is wrong even when nothing is, and a founder who slips twice will slip permanently.
Pull the metrics from one source. The same source as the board pack and the model. Where they disagree, resolve the disagreement before sending rather than choosing the better number.
Write the headline with the worst fact in it, if there is one. Two or three sentences: the primary metric against last period and plan, the most important thing that happened, the cash position. Judgement rule: if a reader would be annoyed to discover a fact in paragraph six, it belongs in paragraph one.
Build the metric table unchanged. The same six to ten metrics, in the same order, with this period, last period, the same period last year, and plan. Footnote each definition once. If a definition has to change, show both bases for at least two periods and say why.
Write wins with a number or a name attached. "Signed a 40-seat contract with a regional logistics group, our largest to date" is a win. "Great momentum in enterprise" is a mood.
Write misses with a cause and a dated corrective action. State the miss, the best current understanding of why, what is being done, and when it will be visible. This is the section readers judge the rest of the update by, and the one most often softened into meaninglessness.
State cash factually. Balance, net burn, runway in months at current burn, and any planned change. If raising, give the status in facts: conversations opened, terms received, expected close. No adjectives near a fundraising sentence.
Write two to four asks, each forwardable. A named company for an introduction, a specific role, a specific decision you want a view on. Test each one by asking whether a reader could act on it inside ten minutes without replying to ask what you mean.
Name who helped and what they did. One or two lines. This is the mechanism by which the next month's asks get answered.
Check it against the last two updates before sending. Same sections, same order, same definitions, and a status on anything you said you would do. An update that quietly drops last month's commitment is training its readers not to rely on it.
Consistency, and what it buys
The value of this document accrues across periods, not within one. A reader who can paste twelve updates into a spreadsheet and get a clean series will do exactly that, and will form a view of the business from the shape of the lines rather than from the prose. That is the outcome to design for.
Three rules protect it. Definitions are footnoted and never change silently. Rounding is consistent, and the period is stated on every figure. Every metric that appears once appears every month thereafter, including in the months it is unflattering, because a metric that disappears is more conspicuous than a bad number.
Length is a constraint, not a target: under 800 words plus the table. Beyond that the founder has started explaining rather than reporting, and explanation in an update reads as defence.
Worked example
Situation. A subscription software company, 22 people, eighteen months after a seed round, sending monthly updates to nine angels and two funds. In the month reported, revenue grew 4 percent against a plan of 9 percent, and two customers representing 11 percent of recurring revenue gave notice within the same fortnight, both citing a missing integration that had been on the roadmap for three quarters. Cash was 9 months.
Task. The monthly update, due in two days, with a founder who wanted to lead with a strong pipeline month and put the churn in the misses section.
Action. The first draft did exactly that: headline on pipeline, churn at paragraph five described as "two logos transitioned". It was abandoned on a simple test, which is worth keeping as a habit: read the update as though you were the recipient who had introduced one of the departing customers. That reader would reach paragraph five, recognise the customer, and conclude that the founder had tried to bury it.
The rewrite led with the churn, stated at 11 percent of recurring revenue, named the cause as the missing integration, and gave the corrective action with a date: the integration scoped and committed for delivery in nine weeks, with the two remaining customers on the same dependency identified by name internally and contacted by the chief executive that week.
A second decision was harder. The founder wanted to add a paragraph arguing that the churn was not representative because both customers had been early, discounted and poorly qualified. That was true. It was cut anyway, because a reader who has just been told about an 11 percent loss and immediately reads a paragraph explaining why it does not count will discount everything else in the document. The argument was moved to a single clause in the miss: both were early customers on legacy pricing, which is context rather than defence.
The asks changed too. The generic ask, introductions to mid-market prospects, was replaced with two specific ones: an introduction to anyone running operations at a company using a named workflow platform, since that integration was now the priority, and a referral for a contract integrations engineer for a three month engagement.
Result. Two of the eleven recipients replied within a day with introductions to the platform's partnerships team, which shortened the integration work by an estimated three weeks. One angel introduced a contract engineer who started nine days later. At the following round, one of the funds cited the churn update in their memo as a reason for confidence, on the basis that the company had reported the problem before being asked about it. The founder's assumption had been that reporting it would cost them that fund.
A second scenario, where it goes differently
The same company, a year later, three weeks into a priced round with a term sheet signed but not closed.
The structure holds, but three things change. Forward-looking statements come out entirely: no expected close date, no valuation, no characterisation of investor interest, because a shareholder base includes people who will repeat what they read. Fundraising status shrinks to one factual line agreed with counsel. And the asks change from commercial help to nothing at all, because asking a shareholder for help during a round invites them to ask about the round.
What did not change is the metric table and the misses section. The temptation during a raise is to make the update glossier, and it is the wrong instinct: the updates sent during a raise are the ones most likely to be read again afterwards, alongside the data room.
Output
One email, plain text or lightly formatted, under 800 words plus the table.
[Company] investor update, [month year] Sent [fixed day]
HEADLINE
[Two or three sentences. Primary metric against last period and plan, the single
most important event, cash position. The worst fact of the month appears here.]
METRICS
| Metric | This period | Last period | Same period last year | Plan | Note |
| Recurring revenue (1) | | | | | |
| Growth, month on month | | | | | |
| Gross margin (2) | | | | | |
| Net revenue retention (3) | | | | | |
| Customers | | | | | |
| New pipeline created | | | | | |
| Net burn | | | | | |
| Cash | | | | | |
| Runway, months | | | | | |
(1) definition (2) definition (3) definition Definitions unchanged since [date].
WINS
[Three to five, each with a number or a name.]
MISSES, AND WHAT WE ARE DOING
[Each: the miss, the cause, the action, the date it becomes visible.]
PRODUCT AND TEAM
[What shipped, what is next, key hires and departures. Short.]
CASH AND FUNDRAISING
[Balance, net burn, runway. If raising: factual status only.]
ASKS
1. [Specific enough to forward without a reply.]
2.
3.
THANK YOU
[Who helped since the last update, and what they did.]
The quarterly variant adds a short paragraph on what changed in the company's thinking and why, and a twelve-month outlook with its assumptions listed.
Failure modes
The month that does not get sent. Recognise it as a gap in the archive, always in a difficult month. Send a short one instead of a good one; three paragraphs on time beats a full update three weeks late.
Definitions that drift. Recognise it when a metric improves in the month a system changed. Show both bases for two periods and footnote the change.
Misses written in the passive voice. "Churn was elevated" has no cause, no owner and no date. Rewrite with all three.
Asks that cannot be forwarded. "Any introductions appreciated" gets nothing. Name the company, the role or the decision.
The defensive paragraph. Recognise it as an explanation of why a bad number does not count, appearing immediately after the bad number. Cut it to a clause of context inside the miss.
Repeating the board pack. Recognise it by length and by charts. Shareholders who are not directors need the trajectory and the asks, not the governance material.
Edge cases
A month with genuinely nothing to report. Send four paragraphs and the table. Consistency is the product; skipping a quiet month breaks the habit for both sides.
Very bad news, such as a large loss or a departure of a founder. Do not let the update be the first anyone hears. Call the largest holders and anyone with a board seat first, then send the written version the same day so everyone else has the same facts.
Recipients who are also investors in a competitor. Keep customer names out, keep pipeline detail general, and consider a two-tier distribution with a fuller version to the lead and a shorter one to the wider list. Say that a tiered list exists rather than concealing it.
During a live financing. Remove forward-looking statements, keep fundraising status to an agreed factual line, and take a view with counsel on what may be said. Keep sending; stopping mid-raise is conspicuous.
A company that has never sent one. Do not begin with an apology or a retrospective. Start with the current month, state the format and the send date, and let the series build from there.
Quality bar
- A reader can build a clean twelve-period series from the emails alone, with no definition changes.
- The worst fact of the period appears in the headline or the misses section, never later.
- Every miss carries a cause, an action and a date.
- Every ask could be forwarded to a third party without further explanation.
- Cash balance, net burn and runway appear in every update.
- The tone is identical in the good months and the bad ones.
- It went out on the fixed day, under 800 words plus the table.
Adapting this to your context
The monthly send, the metric set and the 800-word limit come from venture-backed software companies at seed to Series B with ten to thirty shareholders. Defaults, not a standard.
- Monthly. A month is meaningful at seed and Series A. Later stage or slow-moving businesses do better quarterly, with a short monthly line on cash. Move to monthly during a raise whatever the normal rhythm is.
- The metric table. Recurring revenue, net retention, gross margin and pipeline is a subscription software set. A services firm reports backlog, utilisation and realised day rate; a hardware business reports units, margin per unit and inventory.
- Two to four asks. This assumes shareholders who can act. Where the register is passive or institutional, one ask or none is honest, and "no asks this month" beats invented filler.
- Cash, burn and runway every time. Written for a company not yet profitable. A profitable one substitutes cash generation and the covenant position, and still reports it every time.
- What not to change. The worst fact of the period appears in the headline or the misses and never later, and the update goes out on the fixed day, including in the months it is difficult.
Related skills
board-deck reports the same quarter to directors in far more detail, and the two must agree on every shared number. board-and-investor-management runs the relationship this update maintains, including the calls that must precede it when the news is bad. financial-model-builder and revenue-forecast produce the plan column in the metric table. fundraise-readiness reuses this series as evidence and will surface any definition that moved, so fix it here first. pitch-deck makes the argument for a new commitment, which this document deliberately does not attempt. crisis-and-incident-comms handles the notification that must precede an update carrying very bad news.