The investor update you send a prospect is a different document
Prospects, diligence investors, and passed investors need different updates. One broadcast leaves round momentum on the table.
The same email, forwarded to the wrong reader
You write a good monthly update. Revenue, two wins, one challenge, the ask, a thank-you. Your existing investors love it. So when a partner you pitched last month says "keep me posted," you add them to the list and send the same email. It feels efficient. You have one update, it is honest, everyone gets it.
The problem shows up three weeks later, when nothing happens. The existing investor read your update and felt reassured, which is what they wanted. The prospect read the identical email and felt nothing, because a reassurance update is written for someone who already believes. To a prospect, "here is how the month went" reads as a status report for an audience they are not part of yet. There is no reason to lean in, no signal that the round is moving without them, no single thing that answers the question keeping them out.
An update for someone who has already wired money has one job: keep them confident and useful. An update for someone deciding whether to wire has a completely different job: move them along a path they have not yet committed to walk. Sending the first kind of email to the second kind of reader is not a small inefficiency. It is sending a customer-retention email to a cold lead and wondering why they did not convert.
What founders do, and why one update loses
The default is a single broadcast. One template, one send, the whole list in the BCC field. The reasoning is sound on its face: more updates means more maintenance, and a founder mid-raise has no spare hours. So the update gets written for the easiest audience to please, the people already in, and everyone else gets a copy.
This fails in a specific way for each group it was not written for.
The prospect who has met you once gets an update full of internal shorthand and a generic "we're raising a [round]" line that names no urgency. They cannot tell whether the round is hot or stalled, whether they are early or late, whether replying changes anything. So they do the safe thing and keep watching, which from the outside is indistinguishable from losing interest.
The investor in active diligence, the one who might lead or write a real check this quarter, gets the same broad update and not the one number their internal memo is stuck on. They asked about net revenue retention in the second meeting. The monthly update talks about logo wins. The gap between what they need and what you sent does not read as an oversight. It reads as either you do not have the number or you are avoiding it.
The investor who passed gets dropped entirely, or kept on the list out of politeness with no thought to what would make them reconsider. A pass is rarely permanent. It is usually "not at this price, not on this evidence, not yet." But a founder who treats the passed list as dead never gives them the one proof point that would have changed the answer, and never converts a soft pass into a later check or a warm referral.
One update cannot do three jobs, because the three readers are at different points in a buying decision and a status report is not a selling document.
The framework: segment by investor state, not by relationship
Stop sorting your list into "investors" and "prospects." Sort it by where each person sits in the decision, because that determines what the update has to do.
There are three states that matter during a raise, and each one has a single job the update must accomplish.
Prospect (met you, not in diligence). They are deciding whether to engage at all. The job of their update is to manufacture legitimate momentum: show the round is moving, show traction is compounding, and make replying feel like getting in before a door closes. Not hype. Evidence that things are happening without them.
Active diligence (asked real questions, considering a check). They are deciding whether to say yes. The job of their update is to remove the one blocking objection. You know what it is, because they asked. This update is narrow on purpose: it advances the specific number, reference, or risk that stands between them and a term sheet.
Passed (said no, or went quiet after diligence). They are deciding whether they were wrong. The job of their update is to make the pass look like a mistake worth revisiting, by surfacing the exact proof point their concern was about. A founder who hit the wall the investor doubted earns a reply, a re-look, or at minimum a referral to someone whose thesis now fits.
The same month of company progress gets cut three ways. The prospect sees momentum. The diligence investor sees their objection dissolving. The passed investor sees the evidence that contradicts their reason for passing. One set of facts, three framings, each aimed at the one decision that reader is making.
This is not three times the work. It is one source update and three short cuts of it, which is a layout problem, not a writing-from-scratch problem.
Same month, three updates
Take one month of real progress and watch the segmentation do the work. Assume the facts are: revenue grew from $40K to $52K MRR, you signed two mid-market logos, churn ticked up on the smallest plan, and you are halfway through the round with a lead in diligence.
The prospect update. The job is momentum.
Subject: [Company] - $52K MRR, round half-committed
Quick update since we spoke. MRR is up 30% month over month to $52K, driven by two mid-market signings ([Logo A], [Logo B]) that moved us upmarket faster than planned. On the raise: we're at roughly half of the [round size] committed, with a lead in active diligence and a target close in [month]. I'm keeping the remaining allocation for investors who can be useful on [specific: GTM, enterprise intros, etc.]. If that's still interesting, happy to send the deck and the latest metrics. No pressure if the timing's off.
Notice what it does. It sizes the momentum (30%, two logos, upmarket), it signals the round is filling (half committed, lead in diligence, a close date), and it makes replying time-sensitive without manufacturing fake scarcity. A prospect reads this and understands they are not first and not last, and that the door is real.
The active diligence update. The job is to kill the blocking objection. Say they flagged retention.
Subject: [Company] - the retention picture you asked about
Following up on the cohort question from last week. Pulling the numbers: net revenue retention on the mid-market segment (the one we're betting on) is 118% over the last two quarters, and the two logos we signed this month both expanded within 30 days. The churn we do have is concentrated in the sub-$200/mo plan, which is why we're sunsetting it in Q3. So the headline churn number overstates the risk to the segment that matters for this round. Full cohort breakdown attached. Happy to walk your team through it.
This update ignores most of the month. It does one thing: take the exact concern raised in diligence and put the contradicting evidence directly in front of it, with the breakdown attached so the investor can drop it into their memo. You are doing their work for them.
The passed investor update. The job is to make the pass reconsiderable.
Subject: [Company] - the thing you weren't sure about
No ask here, just closing a loop. When we talked, the open question was whether we could land mid-market without a full sales team. Update: we signed [Logo A] and [Logo B] this month through the founder-led motion, MRR is up 30% to $52K, and net retention on that segment is 118%. I know the timing wasn't right for you, and that's completely fine. If it becomes relevant again, or if there's someone in your network whose thesis fits this better now, I'd welcome the intro.
It names their stated reason for passing, shows the evidence that reverses it, takes the pressure off, and leaves two open doors: a re-look or a referral. A passed investor who sees their own doubt answered is the warmest cold contact you have.
Three emails, one month, fifteen extra minutes. The broadcast version would have done none of these three jobs.
The artifact: the segmented investor update kit
Keep this as one page next to your update draft. Write the source update once, then cut it into the three versions using these skeletons.
Subject lines (the most-skipped lever):
| State | Subject pattern | Why it works |
|---|---|---|
| Prospect | `[Company] - [headline metric], round [% committed]` | Signals traction and scarcity in one line |
| Active diligence | `[Company] - the [topic] you asked about` | Proves you listened; answers their open loop |
| Passed | `[Company] - the thing you weren't sure about` | Pattern-interrupt; invites a low-stakes re-look |
Prospect update skeleton:
1. One-line momentum headline (metric + direction + cause) 2. Round state: % committed, lead status, target close 3. What you're optimizing the remaining allocation for 4. Soft, specific invitation (deck / metrics / call)
Active diligence update skeleton:
1. Reference the exact question they raised 2. The number or evidence that answers it 3. The honest caveat, framed against the segment that matters 4. Attach the breakdown; offer to walk their team through it
Passed investor update skeleton:
1. "No ask, closing a loop" 2. Name their stated reason for passing 3. The proof point that now contradicts it 4. Two open doors: re-look if relevant, or a referral
Common mistakes, by state:
| Mistake | Where it shows up | Fix |
|---|---|---|
| One broadcast to everyone | All three | Cut the source update three ways |
| No round state or close date | Prospect | Always show % committed + timing |
| Answering questions they didn't ask | Diligence | Lead with their exact objection |
| Dropping passed investors silently | Passed | Send one proof-point note per quarter |
| Manufactured urgency / fake scarcity | Prospect | Only claim momentum you can show |
| Same subject line for all | All three | Match subject to the reader's decision |
Where this gets hard at scale, and where RoundOS fits
The segmentation is simple to understand and tedious to maintain. By the time you have forty investors across the pipeline, you are tracking who is a prospect, who asked what in diligence, who passed and why, and which proof point each of them is waiting on. That state lives scattered across your inbox, your meeting notes, and your memory, which means the cut-three-ways move collapses back into one broadcast under time pressure.
This is the work RoundOS is built to carry. It pulls the round from where it already lives, your email, calendar, meeting notes, and investor list, and tracks each investor's state and the open question they last raised. When you write the month's source update, it drafts the three cuts against that context: the momentum version for prospects, the objection-killing version for each investor in diligence using the actual question they asked, and the proof-point version for the people who passed, anchored to their stated reason. You review and send. The segmentation holds even when you are too busy to remember who needed what.
Try this on your next update
Open the last investor update you sent. Pull up your list and sort it into three columns: prospect, active diligence, passed. For each person in diligence, write the one question they last asked you. For each person who passed, write the one reason they gave. You will likely find that your last update answered none of those questions for anyone outside the people already in. That gap is the round momentum you are leaving on the table, and it is fifteen minutes of cutting away.
Cut the next update by investor state.
Sort the list into prospects, active diligence, and passed investors before the next send. Keep each investor state, last objection, and pass reason attached to the record so the monthly source update becomes the right cut for each reader, not one broadcast to everyone.