Investor update template: what to send investors monthly

An investor update template is a fixed outline for the short monthly email a founder sends shareholders: a headline summary, key metrics against plan, cash and runway, wins, challenges, asks, hiring and product, in that order every month. It should take about three minutes to read, arrive at the same time each month after the books close, and use exactly the same metric definitions as the month before.

This is not the board deck. The quarterly startup board deck is a fuller package for directors that asks the board to discuss and approve decisions. The monthly update is a lighter email to every investor that keeps them current between meetings, and its numbers should reconcile to the deck when the quarter ends.

The template to copy

Paste this into a new email each month and fill in the brackets. Keep every heading, even when a section is short.

Subject: [Company] investor update, [Month Year]

1. Headline. Two or three sentences: the most important thing that happened, how the month compared with plan, and the one ask that matters most.
2. Key metrics vs plan. A table with the same five or six metrics every month: actual, plan and variance. One line of commentary on anything more than a small variance away from plan.
3. Cash and runway. Ending cash [$], net burn this month [$], trailing three month average net burn [$], runway [months], and the month the next raise needs to start.
4. Wins. Up to three, each specific: a named customer type, a shipped feature, a hire closed.
5. Challenges. Up to three, each with what is being done about it and who owns it.
6. Asks. One to three narrow requests: an introduction to a [role] at a [type of company], a referral for a [open role], feedback on [decision].
7. Hiring. Headcount now versus plan, roles opened and filled, any key departures.
8. Product. What shipped, what slipped and why, and what is next month's priority.

Sign off with a line inviting replies.

Key metrics vs plan: a worked example

The metrics table should be small and stable. The metric list and how to define each one are covered in the guide to SaaS metrics. The example below is for a fictional seed stage company.

Illustrative figures, not client data. Ending ARR is beginning ARR plus net new ARR (2,280 + 120 = 2,400; 2,280 + 50 = 2,330). Ending cash is 3,500 less net burn. Runway is 3,290 / 210 and 3,310 / 190, rounded down.

The commentary line is where the update earns trust. Net new ARR came in at well under half of plan while burn was lower. If a delayed sales hire caused both, the update should say so, because the revenue gap will persist next month. Runway here is calculated on a single month of burn for simplicity; the guide to burn rate and runway explains why a trailing average and forward commitments give a more reliable figure.

How long it should be, and when to send it

An update that takes more than a few minutes to read gets skimmed. Aim for a single screen of headings plus the table, with each section a few lines at most. Detail such as the full income statement belongs in the board deck or on request.

Send it at the same point every month, once the books have closed for the prior month, and keep the date predictable. A consistent rhythm matters more than an early date.

What to send in a bad month

Send it on time, and lead with the miss. The headline should state the problem plainly, say what caused it, and say what changes as a result: a revised plan, a cost reduction, or a change in the date the next raise starts. Then use the asks section for help that bears directly on the problem.

What damages trust is not the miss but the signs of hiding it: a late update, a metric that disappears from the table, a new metric that happens to look better, or a headline about a win while the challenges section carries the real news.

How investors read an update

Decipher's founder spent nearly a decade running FP&A inside private equity backed software companies, preparing the reporting investors read every month. Experienced investors read updates in sequence, not in isolation.

• They compare with last month. If last month's ending ARR does not equal this month's beginning ARR, they notice.
• They check that definitions held. A change in how ARR or burn is counted needs one sentence of explanation and a restated prior month, or the trend is meaningless.
• They go to cash and runway early. The question is always when the next raise has to start.
• They track whether challenges get resolved. The same challenge with the same explanation three months running reads as a problem nobody owns.
• They respond to specific asks. A named introduction request gets action; a general request for help rarely does.