Skip to main content
EcoutezNew from the Gitmore team: Ecoutez — in-product feedback at the exact moment it matters →
Template • 7 sections

Monthly Investor Update Template for Startups (2026)

A regular investor update is one of the highest-leverage habits a founder can build. It keeps investors informed without meetings, makes your asks (intros, hires, advice) reach people who want to help, and creates a written track record that makes the next fundraise much easier. The format that has become standard among early-stage startups is short and consistent: a few headline numbers, highlights, lowlights, product progress, asks, and runway. The hard part is not the format, it is doing it every month, including the bad months. This template gives you an email-ready structure you can fill in under an hour, with a product-progress section designed to be filled from what engineering actually shipped. Variations cover the monthly email, a quarterly update, and a short pre-seed version.

2-minute setup • No credit card required

When to use this template

Send monthly, in the first week of the month, covering the previous month. Send to all investors (including angels) and optionally to close advisors and prospective investors you are building a relationship with. Switch to quarterly once the company is larger and month-to-month changes are less meaningful, but do not stop sending in a bad month; that is when silence is most noticed.

7 sections

Template Variations

Pick the format that fits your context.

Subject Line & TL;DR

Investors receive many updates. A consistent subject line and a three-line summary at the top get yours read.

Template
Subject: [Company] — [Month 2026] investor update

Hi all,

**TL;DR:** [MRR / key metric] is [$N] ([+N]% MoM). [Biggest win in one clause]. [Biggest challenge in one clause]. **Ask:** [one-line ask].
Use the identical subject format every month so investors can search their inbox for the full historyPut the most important number in the TL;DR, even if it went downWrite the TL;DR last

Key Metrics

The same 3–6 numbers every month, with month-over-month change. Consistency matters more than which metrics you pick.

Template
## Key metrics

| Metric | [Month] | [Previous month] | MoM |
|--------|---------|------------------|-----|
| MRR / revenue | [$N] | [$N] | [+N%] |
| Paying customers | [N] | [N] | [+N] |
| [Activation / usage metric] | [N] | [N] | [+N%] |
| Net burn | [$N] | [$N] | [—] |
| Cash in bank | [$N] | [$N] | [—] |
| Runway | [N months] | [N months] | [—] |
Do not change metric definitions between months; if you must, say so and restate the previous monthPre-revenue? Replace revenue with the leading indicator you are optimising (active users, pilots, waitlist conversions)Add a one-line explanation under any metric that moved sharply in either direction

Highlights

The 3–5 most important good things that happened. Outcomes, not activity.

Template
## Highlights

1. **[Win]** — [Why it matters, e.g. 'Signed [customer type] on an annual contract; our first customer over $10k ACV']
2. **[Win]** — [e.g. 'Launched [feature]; [N] customers used it in the first two weeks']
3. **[Win]** — [e.g. 'Hired [role], who previously [relevant background]']
Each highlight should answer 'so what?' in the same lineName customers only if you have permission; otherwise describe them by segment and sizeThree strong highlights beat eight minor ones

Lowlights

What went wrong or worse than expected, and what you are doing about it. Investors trust founders who report bad news early.

Template
## Lowlights

1. **[Challenge]** — [What happened and its impact]. **What we're doing:** [Action]
2. **[Challenge]** — [e.g. 'Lost two pilot customers to [reason]']. **What we're doing:** [Action]
Never skip this section. An update with no lowlights reads as incomplete, not as a great monthPair every lowlight with a response, even if the response is 'still investigating'If a lowlight from last month is resolved, say so

Product Progress

What the product team shipped and what it means for customers. Written so it can be filled from merged pull requests and closed tickets, then translated into outcomes.

Template
## Product

**Shipped in [Month]:**
- **[Feature / improvement]** — [Customer outcome, e.g. 'Teams can now invite colleagues without admin approval, which was the top request in onboarding calls']
- **[Feature / improvement]** — [Customer outcome]
- **[Reliability / infrastructure]** — [Outcome, e.g. 'Cut page load time on the dashboard by roughly half']

**By the numbers:** [N] releases · [N] customer-requested items shipped · [N] of [N] planned roadmap items completed

**Next month:** [1–3 product priorities and why]
Start from the list of merged pull requests and closed tickets for the month, then group them into 3–5 customer outcomesCompare planned vs. shipped against last month's 'Next month' list; investors notice when priorities silently changeLeave out internal refactors unless they unlock something investors care about (speed, cost, security, a big customer)An investor-audience client portal (for example in Gitmore) can turn a month of GitHub, GitLab, or Bitbucket activity into a plain-language draft of this section

Asks

Specific, easy-to-act-on requests. This is where investors can create the most value for you.

Template
## Asks

1. **Intro:** [e.g. 'Head of Finance at mid-market SaaS companies (100–500 employees) for customer discovery']
2. **Hiring:** [e.g. 'Senior backend engineer, remote EU, Go or Rust experience — [job link]']
3. **Advice:** [e.g. 'Anyone who has priced usage-based plans for developer tools']
Be specific enough that an investor can think of one name immediatelyLimit to three asks; long lists get ignoredNext month, thank the people who helped with last month's asks by name

Team & Runway

Headcount changes and a clear statement of cash position.

Template
## Team
- Joined: [Name, role]
- Left: [Role] (if any)
- Headcount: [N] ([N] engineering)
- Hiring for: [roles]

## Runway
- Cash: [$N] · Net burn: [$N]/month (3-month average: [$N])
- Runway: [N] months, to [Month Year]
- Fundraising: [Not raising / planning to raise in Qx / currently raising]

Thanks for your support,
[Founder name]
Use a 3-month average burn to smooth out lumpy months, and say that you doIf runway drops below about 12 months, say what you plan to do about it before investors askMention departures briefly and factually
Pro Tips

Expert advice

1

Send on the same day each month. Founders who send consistently report that investors start replying with help unprompted

2

Keep a running doc during the month and paste wins, losses, and shipped items as they happen; writing the update then takes minutes

3

Never change the metric set to hide a bad number. Investors compare against previous emails

4

For the product section, start from the month's merged pull requests and closed tickets rather than memory, then rewrite each group as a customer outcome

5

BCC investors or use a mailing tool so replies come only to you

6

Save every update in one shared folder; it becomes a ready-made data room narrative for the next round

FAQ

Common questions

What should a startup investor update include?

The common format is: a short TL;DR, key metrics with month-over-month change, highlights, lowlights, product progress, asks, team changes, and cash and runway. Keep the structure and metrics the same every month so investors can compare.

How long should a monthly investor update be?

Short enough to read in two to three minutes, usually 300–600 words. Investors read many updates; a tight TL;DR and a consistent layout matter more than detail. Link to longer documents if needed.

What is the YC investor update format?

Y Combinator has long encouraged founders to send short, regular updates covering key metrics, highlights, lowlights, and specific asks. There is no single official template; the structure in this template follows that widely used format.

Should I send an investor update in a bad month?

Yes. Skipping a month is a signal in itself. A clear explanation of what went wrong and what you are doing about it builds more trust than silence, and it gives investors a chance to help.

How do I write the product section without it becoming a changelog?

Start from what engineering shipped (merged PRs, closed tickets), group it into three to five themes, and write each theme as a customer outcome with a reason it matters. Drop internal work unless it changes speed, cost, security, or a key customer relationship. Tools like Gitmore can produce a plain-language draft from Git activity that you then edit.

Automate Your Git Reporting

Stop filling in templates manually. Connect your git provider and let Gitmore generate reports automatically — daily, weekly, or on demand.

Get Started Free

No credit card • No sales call • Reports in 2 minutes