How to write an investor update people read
Guide · Founder · 5 min read · last verified 2026-07-27
An investor update is a short written report a founder sends to current investors on a fixed rhythm — usually monthly — covering the numbers that matter, what changed since the last one, what went wrong, and the one thing the company needs. It is not a pitch and it is not a diary. A good update works like a pulse reading: quick to take, honest by construction, and meaningful mostly in sequence. One reading tells an investor a little; a year of readings in a row tells them almost everything about how the company is actually doing.
Why most updates go unread
Updates tend to fail for predictable reasons. The first is that they read like marketing. An update that contains only wins carries almost no information, and experienced readers tend to treat it accordingly — skimmed, filed, forgotten. The second is inconsistency: when every month has a different shape, the reader has to relearn the document each time, and busy people tend to stop doing that work. The third is length without hierarchy. A long update can be fine; a long update with no fixed sections, no defined numbers, and no ask forces the reader to do the summarising themselves, and many readers quietly decline.
None of these failures are moral failures. They are formatting problems, and formatting problems have formatting solutions.
The candor format
The format has four rules, and everything else in this article is elaboration on them.
- Numbers come with their basis. Every metric you report is defined: what was counted, over what window, and whether the counting method changed.
- Bad news goes first. The problem section sits near the top, before the wins.
- There is exactly one ask. Specific, answerable, and easy to forward.
- The structure repeats. Same sections, same order, every month.
A founder who follows these rules will usually produce an update that takes a few minutes to read and leaves the reader knowing more than they did before. That is the entire job. Everything ornamental — mission restatements, press-style prose, screenshots of praise — competes with that job and generally loses.
Numbers need a basis
A number without its definition is an invitation to misread. "Active users" can mean anyone who logged in, anyone who completed a core action, or anyone who paid; investors who have seen many updates tend to assume the flattering interpretation was chosen, unless you show your work. So state the basis every time, even when it feels repetitive: what the metric counts, the time window, and any change to how you measure it since last month. If a number moved because you redefined it, say so before the reader wonders.
The same discipline applies to market evidence. If your update claims that buyer interest is building, say where that reading comes from — which questions buyers are asking, in which forums and channels you looked, and when. Evidence-first platforms such as Magrios exist to keep that kind of record continuously, but even a dated folder of notes beats recollection. What matters is that the claim has a source the reader could inspect.
Bad news travels first
Putting problems at the top feels unnatural and may be the single highest-leverage habit in investor communication. The logic is simple: investors tend to find out about serious problems eventually, and the founder who surfaced the problem early tends to be trusted on everything else. Candor is not confession; it is a credibility instrument. A problem stated plainly — what happened, what you think caused it, what you are doing — often reads as competence, while a problem discovered later through omission tends to read as either blindness or concealment, and neither is recoverable cheaply.
There is a practical bonus. Investors can usually only help with problems they know about. The bad-news section is where introductions, warnings, and pattern-matching from their other companies tend to show up — but only if you give them something true to react to.
One ask, clearly stated
Many updates ask for nothing, which trains readers that nothing is needed from them. Others ask for everything — intros, feedback, hiring help, advice — which is the same as asking for nothing, because a vague list is hard to act on. The candor format allows one ask per update. Make it specific enough to forward: a kind of introduction, a named role you are hiring, a decision you want a second opinion on. If the ask is answerable in one reply, some readers will answer it.
Keep the same skeleton every month
Repetition is what turns a document into an instrument. When the sections arrive in the same order every month, readers learn where to look, and change becomes visible without commentary. The rhythm itself carries signal: updates that arrive on schedule suggest a company that runs on schedule, and a silent month tends to be read as a message even when none was intended.
A workable skeleton: metrics with basis, the bad news, the good news, learnings, the ask, and a short closing on what next month should show. Your internal weekly review is the natural source material — see How to run a weekly growth review — and your experiment log supplies the learnings section, as covered in How to document growth experiments. If something went genuinely wrong during the month, the written account you produce for a marketing postmortem can be summarised here rather than rewritten.
The update is not the board meeting
Founders sometimes merge the two, and both suffer. The board meeting is a decision forum: it exists so that governance can happen, with materials built for discussion — that craft is covered in How to present market research to your board. The written monthly update is a record: it exists so that everyone with a stake holds the same honest picture at the same time, whether or not they attend anything. The meeting persuades in the room; the update compounds on paper. Write the update as if it will be reread in a year to check what you knew and when — because occasionally it will be, and updates written under that assumption tend to age well.