How investors read your updates
Investor updates are scanned for momentum, risk, and a specific ask, not read like essays.
You spent two hours on the update. You wrote a warm intro paragraph, a recap of the quarter, a section on the team offsite, three nicely worded paragraphs about a feature launch, and at the bottom, an ask for two intros.
The investor on the other end opens it on their phone between two meetings. They do not read the warm intro. Their eyes drop to the numbers, jump to anything that looks like a risk, and look for whether you asked for something they can act on. Total time: about forty seconds. Then they either reply, forward it to a partner, file it for the next partner meeting, or close it and forget you exist for another month.
The gap between how you write the update and how it gets read is where most updates die. Not because the company is doing badly. Because the signal an investor needs is wrapped in paragraphs they will never read.
What investors actually do with an update
An update is not a newsletter. A newsletter is read for interest. An update is scanned for a decision. The investor is running a fast triage with three questions, roughly in this order:
First, is this company moving? They look for one or two numbers compared to last time. Revenue, users, pipeline, retention, cash. Direction matters more than absolute size. A clean "ARR $42k → $61k MoM" tells them more in two seconds than three paragraphs of narrative.
Second, is there a risk I need to know about? Investors are pattern-matchers on bad news. They are looking for the thing you might be hiding: a churned anchor customer, a cofounder issue, runway tightening, a missed milestone you mentioned last time. A founder who names the risk plainly reads as in control. A founder whose update is all wins reads as either lucky or evasive.
Third, is there something I should do? A specific, forwardable ask. Not "let me know if you have any ideas." A named target: "intro to a VP Eng who has scaled a 0→1 ML team" or "we're opening a $1.5M extension, room for one more $250k check."
If your update answers those three questions in the first screen, it works. If the reader has to dig for them, the update becomes background noise, and background noise does not build the momentum that makes your next round easier.
The reading pattern, drawn
Here is the eye path of an investor scanning a typical update on a phone:
[Subject line] ← decides if they open at all
↓
[First 2 lines] ← TL;DR or warm fluff? If fluff, they scan faster
↓
[Numbers / metrics] ← the real read. Direction vs last update.
↓
[Anything bold or
labelled "Risk"] ← scans for the catch
↓
[The Ask] ← can I act on this in 30 seconds?
↓
[Reply / Forward /
File / Ignore]Notice what gets skipped: the narrative connective tissue, the offsite photos, the long feature descriptions. That content is not worthless, but it is not what gets scanned, so it cannot carry your three signals. Put the signals where the eye lands.
Structure the update for the scan
Reorder the update so the reading pattern and the page agree. Five sections, in this order:
1. TL;DR (3 lines, top of the email). State the quarter in three lines: one win, one number, one ask. This is the only part you can assume gets read in full. Example:
Closed our first two enterprise pilots ($60k combined ACV). ARR $42k → $61k, net new logos 4. Ask: warm intro to Series A leads who do infra; opening a small extension.
2. Metrics (a small table, not prose). Three to six numbers, each with last period's value next to it so direction is visible without math. Never make the investor calculate the delta.
| Metric | Last update | Now | Δ |
|---|---|---|---|
| MRR | $3.5k | $5.1k | +46% |
| Active teams | 22 | 31 | +9 |
| Net revenue retention | 96% | 104% | +8pts |
| Runway (months) | 11 | 9 | −2 |
3. Wins (2–4 bullets, concrete). Not "great momentum on the product." Instead: "Shipped SSO, which unblocked the two pilots above" or "Hired Head of Sales from [type of company]." Each win should connect to a number or a milestone.
4. Risks / asks for help (named). This is the section most founders weaken or delete. Keep it. Two or three items, each a plain risk plus what you are doing about it, or a specific ask. "Runway is 9 months; we want to be at $100k MRR before raising, which is the gap we're closing." Naming the risk and the plan in the same breath is what builds trust.
5. The ask (specific, forwardable). One or two asks a reader can act on by hitting reply or forwarding to one person. The test: could the investor forward your ask to a contact without writing any context themselves? If not, it is too vague.
Everything else (team color, longer narrative, screenshots) goes below the ask, where it belongs: available for the reader who wants it, out of the way of the reader who is scanning.
The artifact: the update scan test
Before you send, run your own update through the test your investor will run on it. Score each line. If any line scores 0, fix it before sending.
Investor Update Scan Test
THE 40-SECOND TEST
Set a 40-second timer. Read only your TL;DR + metrics table.
Can a stranger tell whether the company is up or down? ......... [ ] Y [ ] N
THE THREE SIGNALS (1 point each, 0 if buried below the first screen)
[ ] Momentum: one or two numbers vs last period, direction obvious
[ ] Risk: at least one honest risk or constraint, named plainly
[ ] Ask: a specific, forwardable request (not "let me know")
THE FORWARD TEST
[ ] Could the investor forward your ask to a contact
WITHOUT writing any context of their own?
THE EVASION CHECK
[ ] Did you delete or soften a risk because it looked bad?
(If yes, put it back. All-wins updates read as evasive.)
THE MATH CHECK
[ ] Does every metric show last period's value next to it,
so no reader has to calculate the delta?
SCORE
6/6 → send it
4–5 → fix the missing signal, then send
≤3 → the update is narrative, not a momentum artifact. Rewrite.The point of the test is to stop optimizing the update for how it feels to write and start optimizing it for how it gets read. A founder who passes this every month is, without realizing it, building a paper trail of momentum that an investor can pull up when your name comes up in a partner meeting.
Before / after
Before (the opener that gets skipped):
Hi everyone, hope you're all doing well and had a great start to the quarter! It's been an incredibly busy few months for the team and we have so much to share. We kicked things off with an offsite that really helped us align on vision...
By line three, the investor has scrolled past, looking for a number.
After (the opener that gets read):
TL;DR: First two enterprise pilots closed ($60k ACV). ARR $42k → $61k. Ask below: one infra-focused Series A intro.
Details for those who want them follow.
Same quarter. One version gets scanned and filed as "moving." The other gets scanned and filed as "nothing happened."
Where this connects to RoundOS
The hard part of a good update is not the writing. It is that the inputs live in five places: revenue in Stripe or a sheet, pipeline in your notes, the risk you flagged last month in a thread you have to go find, the right ask depending on which investor is reading. Most founders rebuild that context from scratch every month, which is why updates slip and get generic.
RoundOS holds the round's operating data and conversation memory in one place, so the update assembles from what already happened: the metrics with last period's values, the risk you raised before and what changed, and an ask targeted to where each investor sits in your pipeline. You edit and send. The scan test above is the structure it drafts into.
Write for the scan, not the archive.
Run the last update through the scan test and rebuild the top so momentum, risk, and the ask are visible immediately.