Monthly investor update template (with examples for Series A founders)
A monthly investor update template Series A founders actually use: five sections, two examples, and where automation helps when investor classes diverge.
A founder I know hit publish on her seventh monthly investor update at 11pm on a Sunday. She had forty-two investors across the cap table — lead, two follow-ons, a strategic, eighteen angels from her angel round, and twenty employees with notes that she’d promised quarterly visibility to. The update went to all of them in one email. Her lead VC’s partner emailed back at 8am: “loved this, but the runway slide isn’t quite the cut I’d want for the partnership — can you send me the deeper version?”
The deeper version didn’t exist. She’d been writing one update for everyone, sanding off the edges to make it readable to everyone, and ending up with something nobody quite needed. The partner wanted KPI commentary at a level her angels would skim past. The angels wanted a narrative; the partner wanted the numbers. Same data, different cut.
That’s the framing this piece runs on. The template below is the structure most Series A founders end up converging on — five sections, email-friendly, two screens of scroll. The harder problem, which we’ll address at the end, is what to do when one update has to become two or three. The longer architectural treatment lives on the investor update automation.
The five-section investor update template
Strip away the variations and the structure that works is short. Five sections, in order, every month.
1. Highlights
Three to five bullets. The things you want investors to remember if they only read the first screen. New logo wins, a hire that closes a known gap, a product milestone, a partnership signed, a press hit if it actually moved something. Resist the urge to inflate — investors recognise highlight padding immediately and the trust cost is high.
The rule of thumb: each highlight should be something a board member would proudly mention to their partners at Monday meeting. If you wouldn’t pass it on, it’s not a highlight.
2. Lowlights
Two or three bullets. The things that aren’t going to plan, framed honestly, framed as the founder seeing them clearly. A churned account and the reason. A hire that fell through. A roadmap miss. A metric that moved the wrong way.
Founders avoid this section the most and lose the most by avoiding it. Investors who see only highlights stop trusting the document. Lowlights are also where pattern-matching investors notice their pattern — the angel who’s seen a churn cliff before will reach out the day they read about yours.
3. KPIs
A short block of numbers, the same numbers every month. The minimum honest set:
- Revenue — MRR or ARR, depending on the business; with growth from prior month and prior quarter.
- Customers — total, net new, churned. Or active accounts if that’s the unit.
- Runway — months at current burn, with a note if burn is changing.
- Headcount — total, with hires and departures.
For most B2B SaaS, add NRR, gross margin, and CAC payback as they stabilise. For marketplaces, GMV and take rate. For infra, paying-customer count and ARR per customer. The principle: investors are looking for the same metrics month over month, not a new dashboard each cycle. Stability of the metric set is itself a signal.
4. Asks
Two or three specific things investors can do. Hires the network can refer. Customers the network can introduce. Press the network can pitch. A specific question — “we’re debating Series B timing, would value perspective from anyone who’s done this in our segment” — that an engaged investor can answer in five minutes.
The asks section is where founders most under-extract value from their cap table. Investors want to help; they need a specific lane. Generic “let me know if you can help” is the same as no ask. Specific “we’re hiring a Head of Sales, ideally with experience selling to mid-market healthcare” is an ask the network can act on.
5. What’s next
A short forward-look. The next month’s milestones. The board meeting if there is one. The fundraise if there is one and it’s appropriate to flag. Two or three sentences, not a roadmap document.
That’s the template. Two screens. Sendable as plain email. Readable on a phone in a coffee queue.
Two anonymised examples
To make the template concrete, here are two real-shape examples — anonymised, with descriptions of the companies rather than names.
Example A: an early-stage AI infra company
Company shape: Series A, eighteen months in, $4M ARR, fifteen employees, ten months of runway. Lead VC at the partner level, three follow-on funds, fifteen angels.
Highlights:
- Closed a six-figure ACV deal with a top-tier model lab; first lighthouse customer in that segment.
- Hired a Head of Eng from a hyperscaler; closed an open seat that had been vacant for four months.
- Launched the inference-routing feature; first three customers migrated.
Lowlights:
- One mid-market customer churned in February, citing internal infra build vs buy. Won’t sway the rest of the segment but is a signal we’re tracking.
- The enterprise rollout we’d flagged in January has slipped to April; legal review on their side, not ours.
KPIs:
- ARR: $4.0M (+8% MoM, +35% QoQ)
- Customers: 47 paying (3 new, 1 churned)
- Runway: 10 months at current burn ($380k/mo)
- Headcount: 15 (+1 this month)
Asks:
- Hiring a senior PMM with experience marketing to ML engineers — referrals welcome.
- Two introductions this month: any GTM leader who’s sold inference-layer infra into the model labs.
What’s next:
- March focus is the enterprise rollout going live and standing up the channel motion.
- Board meeting March 28; will share the pre-read the week before.
Example B: a B2B SaaS at $3M ARR
Company shape: Series A, two and a half years in, $3M ARR, twenty employees, fourteen months of runway. Lead VC, one follow-on, twelve angels, thirty employees with options.
Highlights:
- NRR ticked up to 118% — first month above 115% in two quarters.
- Closed our largest contract to date, three-year commit with the Series A lead’s portfolio company.
- Shipped the integrations release we’d been promising since November.
Lowlights:
- A founder-led sales motion is running out of road; first month where I personally couldn’t close a deal that should have closed.
- Our top SDR resigned. Replacement search is open; expect three weeks of softer pipeline coverage.
KPIs:
- ARR: $3.0M (+5% MoM, +22% QoQ)
- Customers: 92 paying (4 new, 1 expansion-by-merger, 1 churned)
- Runway: 14 months at current burn ($210k/mo)
- Headcount: 20 (flat; one open SDR seat)
Asks:
- Looking for a VP Sales — first sales hire above the IC layer. Network referrals especially welcome from anyone who’s hired a first VP at our stage.
- Two customer introductions this month, both in the financial-services vertical we’re starting to lean into.
What’s next:
- April focus is the VP Sales hire and the financial-services beachhead.
- Board meeting May 5.
Both fit on a phone screen. Both lead with the things that matter. Both close with a specific ask the cap table can actually act on.
Where automation helps — and where it doesn’t
For a single update to a single investor list, the template above plus a calendar reminder is the entire system you need. Don’t build more.
The complication arrives when the cap table fragments. The lead wants the deeper KPI commentary. The angels want the narrative. The advisors want the headlines. The employees with notes want runway and milestones, not the strategic asks. Same five sections, three different cuts of the data.
The pattern Series A founders end up using:
The KPIs and headcount data live in one place — usually an Airtable base or a Google Sheet the founder updates monthly. The narrative sections — highlights, lowlights, asks, what’s next — get written once. The output is generated three ways: a deeper version with full KPI commentary, a lighter version with the headline numbers, and a shorter version for the employee channel. Same source, three artefacts.
This is the seam where investor update automation starts paying back. Below the seam — under thirty people on the cap table, single update — manual is correct. Above the seam — multiple investor classes, recurring asks, growing volume — automation buys back the four hours a month that the cuts cost.
A note on quarterly LP updates
For founders who’ve raised from funds that themselves report to LPs, the monthly update is the input to the fund’s quarterly LP update. Your monthly is helping your investor write theirs. That’s not a constraint — it’s a clue. The KPIs your investors include in their LP reports are the KPIs they want to see in your monthly. Ask them which ones. The signal is unsubtle.
For the LP-side companion piece — what your investors are doing with these updates downstream — see the LP reporting quarterly template.
How to actually start
A 30-minute exercise:
Open the template above in a doc. Fill in the five sections for your most recent month. Don’t optimise. Send it to your lead VC and one trusted angel and ask which sections they actually read and which they skipped. The answer compresses six months of iteration into a Tuesday afternoon.
Once the structure is stable, decide whether you have one investor class or several. If one, keep writing it manually — the discipline is the value. If several, that’s when the investor update automation becomes the relevant read, and the production pipeline is the next step.