Key Takeaways
- The monthly investor update is your highest-leverage 60 minutes. It's your only consistent touchpoint with people who can intro, hire, and re-fund you.
- The 4-section structure: TL;DR (3 bullets) · Metrics (table) · What changed (3-5 bullets) · Asks (1-3 specific).
- Length: 400-600 words. Under 200 = lazy. Over 800 = unread.
- Cadence: monthly, same day every month. First Monday is the canonical choice.
- Tone: honest. Spin destroys trust faster than missed numbers. Investors back people, not graphs.
How to write an investor update matters more than most founders realise. The monthly investor email is your single most consistent touchpoint with the people who can introduce you to your next 10 customers, write the next round, and unstick the operational problem you've been wrestling with for weeks. A good update gets responses; a bad update gets opened, skimmed, and ignored.
Why investor updates matter
The investors who introduced you to your seed round will also introduce you to your Series A. The investor update is how you stay top-of-mind without having to ask explicitly every month. Treat it as the single highest-leverage 60 minutes you spend each month.
The 4-section structure
| Section | Length | Goal | If they only read this |
|---|---|---|---|
| 1. TL;DR | 3 bullets · 80 words | Set the frame | They know momentum, risk, and ask |
| 2. Metrics | 5-7 numbers · 60 words | Show direction | They know if you're growing |
| 3. What changed | 3-5 bullets · 200 words | Show progress | They know what shipped |
| 4. Asks | 1-3 items · 60 words | Make the help-loop possible | They know how to help |
Section 1: TL;DR (3 bullets)
One sentence on momentum, one on the biggest risk, one specific ask. If the investor only reads this section, they should know how you're doing and what you need.
• Momentum: MRR up 18% MoM to $42K, closed 2 enterprise pilots.
• Risk: Engineering bottleneck — backend hire didn't work out, restarting search.
• Ask: Intros to senior Rails engineers with multi-tenant experience.
Section 2: Metrics
MRR, customer count, runway, and one product/channel metric specific to your stage. Show month-over-month; don't bury the trend in a chart they have to squint at.
| Metric | Last month | This month | Δ |
|---|---|---|---|
| MRR | $35,500 | $42,000 | +18.3% |
| Paying customers | 78 | 94 | +20.5% |
| Logo churn | 2.6% | 1.8% | -31% |
| Runway (months) | 14 | 13 | -1 |
| North star: weekly API calls | 184K | 240K | +30.4% |
Skip metric definitions ("MRR is monthly recurring revenue..."). Your investors already know. Skip vanity metrics (Twitter follower count, blog page views). Show what moves the business.
Section 3: What changed this month
3-5 bullets: product shipped, customers landed, learnings from churn, key hire made. Concrete, not vague.
| Vague (skip) | Specific (use) |
|---|---|
| "We made progress on the product roadmap." | "Shipped multi-workspace support — now blocks 3 churns and unlocked 2 enterprise pilots." |
| "We had some great customer conversations." | "Closed Acme ($1.2K MRR) + 2 mid-market pilots after the v2 redesign." |
| "We learned about churn." | "Top churn driver: missing Salesforce integration. Started building it Monday." |
| "Team is doing great." | "Hired senior backend engineer (ex-Stripe). Replacing my 30 hrs/week of API work." |
Section 4: Asks (the section that produces replies)
1-3 specific requests. Specific wins; vague gets ignored.
1. Named intros: "Intro to <person> at <company> for <reason>." 3 out of 5 investors reply with the intro.
2. Hiring asks: "Looking for senior backend engineer with marketplace experience; please forward." Often the easiest win for investors.
3. Scoped strategic questions: "How have you seen Series A pre-money valuations move in fintech the last 6 months?" Gets actual data.
Length, cadence, and tone
| Dimension | Goldilocks | Why |
|---|---|---|
| Length | 400-600 words | Below 200 looks lazy; above 800 reads like a report nobody asked for |
| Cadence | Monthly, same day each month | First Monday is the canonical choice. Predictability builds the habit. |
| Tone | Honest, not corporate | "Missed MRR target 20% — two enterprise deals slipped" beats "we're optimising the pipeline" |
| Format | Plain email or markdown | Designed PDFs are over-engineered; the email gets opened on mobile |
| Distribution | BCC list or Loops/Visible | BCC for under 20 recipients; tooling above |
Full sample update (copy-paste)
"Acme — June update — MRR $42K, +18%"
Body:
Hi team — June update from Acme:
TL;DR
- MRR $42K (+18% MoM); closed 2 enterprise pilots
- Biggest risk: engineering bottleneck — last hire didn't work out
- Ask: intros to senior Rails engineers with multi-tenant experience
Metrics (vs May)
- MRR $42,000 (+18%)
- Paying customers: 94 (+20%)
- Logo churn: 1.8% (down from 2.6%)
- Weekly API calls (north star): 240K (+30%)
- Runway: 13 months
What changed this month
- Shipped multi-workspace support — unblocked 2 enterprise pilots and stopped 3 likely churns
- Closed Acme Corp ($1.2K MRR) + 2 mid-market pilots
- Built Salesforce integration after surfacing it as the #1 churn driver
- Lost a senior backend hire — they took a counter-offer at week 2. Restarting search.
Asks
- Senior Rails engineers (multi-tenant exp): please reply with names or forward
- If anyone has a strong relationship with [target VP] at [target customer], a warm intro would be huge
- How are you seeing Series A pre-money valuations in vertical SaaS the last 60 days?
Thanks all — onward.
<Founder name>
What to skip in every investor update
1. Generic appreciation ("thanks for your continued support") — every paragraph that doesn't carry new information loses attention.
2. Restating the company mission — they know.
3. Detailed roadmap discussions — belong in a separate doc the interested investors can read.
4. Metric definitions — your investors know what MRR is.
5. Excuses without learnings — "we missed because X" without "and here's what we're changing" reads as defensive.
Frequently asked questions
How to prepare for a seed round · Bootstrapping vs raising · Founder glossary · Founder templates