Structure and asks
Audience sets the register
| Audience | Length | Register |
|---|---|---|
| Existing investors | 300 to 500 words | Candid, peer to peer |
| Full board, between meetings | 1 to 2 pages | Decision preparation; links to the next pre-read |
| Advisor | 200 to 400 words | Focused on the one ask |
| Prospective investors | One page | Evidenced, confident, hedged where honest |
| Diligence answer | Half a page to one page | Narrow, specific, authoritative |
| Year-end recap to a broad list | 600 to 800 words | Narrative arc with numbers |
Write the audience, register, and length at the top of the draft before writing a word of the body.
The headline
One sentence. If the reader stops there, they still know what matters.
| Fails | Works |
|---|---|
| "Excited to share some progress this month." | "Five design partners are onboarding, the product ships on the 7th, and the open question is the technical co-founder hire." |
| "It has been a busy quarter." | "Q1 closed at 92% of plan on new ARR, runway is 14 months, and win rate is the constraint." |
| "I want to update you on a few things." | "We missed the quarter by 18%, the cause is a pipeline gap we saw in January, and here is the plan." |
The quote-back test. When another partner asks "what is happening with that company?", the investor should have one accurate sentence to repeat. An update should create something for the investor to repeat. Not "they are doing lots of interesting things with AI" but "they doubled enterprise ARR while holding burn flat, and three of the five customers they targeted last quarter are in contracting."
One thesis. Wins, risks, and asks support one message. An update with three competing theses has none.
The body
| Section | Share of length | Content |
|---|---|---|
| Wins | About 40% | Two to four facts, ordered by importance, with names, numbers, and dates |
| Risks | About 30% | One to three risks, each followed by what is being done about it |
| Asks | About 15% | One to three specific asks, plus what happened with last time's asks |
| Forward look | About 15% | What the next period focuses on, and the date of the next update |
One idea per paragraph. Investors scan.
Asks that get answered
| Generic | Specific |
|---|---|
| "Any intros welcome." | "An introduction to a CRO at a $10M to $30M ARR company who has rebuilt a forecast process." |
| "Would love your thoughts." | "Is a 7 May ship date too aggressive for a two-engineer team? Yes or no, and why." |
| "Help with hiring." | "Two candidates for a founding account executive, ideally from a company that sold to sales leaders." |
Make introductions easy. For every introduction ask, include a three-sentence blurb the investor can forward without editing: who you are, why this person specifically, and what you are asking of them.
Close the loop. Start the asks section with last period's asks and what happened: "Thank you to A for the introduction to B; we have a pilot scoping call on the 14th." Investors who see their help land help again.
Cadence
| Stage | Cadence |
|---|---|
| Pre-seed to Series A | Monthly |
| Series A and later | Monthly metrics, quarterly narrative |
| During a raise | Every two weeks to prospective leads, kept short |
Send on the same day each period. Consistency is itself a signal of operating discipline. A missed update is read as a bad month.
Build the audience before you need it
Investors are not only capital. Kept informed, they become a distribution network for introductions, expertise, customers, and other investors. Every update gives them another reason to remember the company, make an introduction, forward it to another investor, or notice an inflection point before the formal raise begins.
Grow the list deliberately: current investors, prospective investors you have met, angels and advisors, and operators who have offered help. Keep the prospective-investor version shorter.
Prospective investors
Add prospective investors to a shorter version of the update months before a raise. When the raise begins, they have already watched several periods of promises made and kept. Execution certainty is what wins capital against competing uses, and a consistent update record is how you build it before you ask.