Investor update template

The monthly investor update is a short document with a fixed set of sections and a variable amount of substance: some months the highlights run long, some months the ask is a single line. That is why it works better as a Google Doc than a deck. The sections flow, the metrics table grows if you start tracking another number, and the pages break themselves rather than forcing you to cut a sentence to fit a slide.

The five sections that survive contact with a cap table

Strip away the variations and the structure most Series A founders converge on is short. Five sections, in this order, every month, two screens of scroll, readable on a phone in a coffee queue.

Three rules make the difference between an update that gets read and one that gets archived:

• Each highlight should be something a board member would repeat at Monday meeting. If they would not pass it on, it is not a highlight. Investors recognise padding immediately and the trust cost is high.
• Lowlights are where the network actually helps. The angel who has seen a churn cliff before will email the day they read about yours. Founders skip this section most and lose most by skipping it.
• A generic ask is no ask. “Let me know if you can help” gets ignored. “We are hiring a Head of Sales with mid-market healthcare experience” gets three referrals.

The KPI block, month over month

Stability of the metric set is itself a signal. Investors are looking for the same four to seven numbers every month so they can read the trend; a rotating dashboard reads as a founder who has not decided what matters yet.

Two worked examples

Both anonymised, both real in shape.

An early-stage AI infrastructure company

Series A, eighteen months in, $4M ARR, fifteen employees, ten months of runway. Lead VC at partner level, three follow-on funds, fifteen angels.

Highlights

• Closed a six-figure ACV deal with a top-tier model lab, the first lighthouse customer in that segment.
• Hired a Head of Engineering from a hyperscaler, closing a seat that had been open four months.
• Launched inference routing; first three customers migrated.

Lowlights

• One mid-market customer churned, citing an internal build-vs-buy decision. Not a segment signal, but tracked.
• The enterprise rollout flagged in January has slipped to April: legal review on their side.

KPIs — ARR $4.0M (+8% MoM, +35% QoQ) · 47 paying customers (3 new, 1 churned) · 10 months runway at $380k/mo burn · headcount 15 (+1)

Asks

• A senior PMM who has marketed to ML engineers. Referrals welcome.
• Two introductions to GTM leaders who have sold inference-layer infrastructure into model labs.

What’s next — March is the enterprise rollout going live and standing up the channel motion. Board meeting 28 March; pre-read the week before.

A B2B SaaS at $3M ARR

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 up to 118%, the first month above 115% in two quarters.
• Largest contract to date: a three-year commit with a portfolio company of the lead.
• Shipped the integrations release promised since November.

Lowlights

• Founder-led sales is running out of road: first month a deal that should have closed did not.
• Top SDR resigned. Search open; expect three weeks of softer pipeline coverage.

KPIs — ARR $3.0M (+5% MoM, +22% QoQ) · 92 paying customers (4 new, 1 churned) · 14 months runway at $210k/mo burn · headcount 20 (one open SDR seat)

Asks

• A VP Sales, the first sales hire above the IC layer. Especially keen to hear from anyone who hired a first VP at this stage.
• Two customer introductions in financial services, the vertical we are leaning into.

What’s next — April is the VP Sales hire and the financial-services beachhead. Board meeting 5 May.

Keep the numbers in the source, write only the judgement

Roughly half an update is figures you already hold and half is judgement nobody else can write. Keep the first half where it lives, an Airtable base or a Google Sheet with a row per month, and put the commentary in text fields beside it. The template then places both, and the update goes out on the same day whether or not anyone had time to rebuild last month’s file. The common failure is the reverse arrangement, where numbers are typed straight into the document: a figure gets corrected in one place, and a week later the board pack quietly disagrees with what your investors were told.

When to automate, and when not to

For a single update to a single investor list, this template plus a calendar reminder is the entire system. Do not build more.

The complication arrives when the cap table fragments. The lead wants deeper KPI commentary; the angels want narrative; the advisers want headlines; employees with options want runway and milestones, not the strategic asks. Same five sections, three cuts of the data. Writing one update takes ninety minutes. Writing three cuts takes four hours, and that is the cliff where the monthly update turns from a discipline into a chore that gets skipped.

Below the seam, manual is correct. Above it, generating from one source buys back the four hours a month the cuts cost. The investor update automation guide covers the architecture; the quarterly LP report is the downstream document your investors build from these.

How to start in thirty minutes

Fill in the five sections for your most recent month, without optimising. Send it to your lead and one trusted angel and ask which sections they read and which they skipped. That answer compresses six months of iteration into a Tuesday afternoon. Once the structure is stable, decide whether you have one investor class or several, and only then decide whether to automate.