Blog/ Email writing & templates

Monthly Investor Update Email: 9 Templates for Founders

Nafiul HasanNafiul Hasan· 17 min read
Monthly investor update email templates for startup founders, showing a structured update with metrics, highlights, lowlights, runway, and asks sections

The short answer

A monthly investor update email should include MRR and its month-over-month change, one or two highlights, honest lowlights, current runway in months, and a specific asks section with named requests. Keep it under 400 words, send on the same day every month, and lead with the numbers rather than context.

Nine monthly investor update email templates for founders: standard, bad-month, runway warning, first-raise, asks, and pre-raise warm-up.

On this page
  1. 01How often should founders send investor updates?
  2. 02What a good investor update contains
  3. 03Template 1: The standard monthly investor update
  4. 04Template 2: The first update after closing a round
  5. 05Template 3: The bad-month investor update
  6. 06Template 4: The runway-warning investor update
  7. 07Template 5: The specific-asks investor update
  8. 08Template 6: The pre-raise warm-up
  9. 09Template 7: The milestone or product-launch update
  10. 10Template 8: The quiet-month investor update
  11. 11Template 9: The pivot or major strategy-shift update
  12. 12How to write the bad-month update well
  13. 13What to do when investors do not reply to your updates
  14. 14Should you share runway with investors every month?
  15. 15Let AI Emaily draft the update

A monthly investor update email is the single most underrated investor-relations tool a founder has. It is not a pitch deck, a board presentation, or a crisis message — it is the 300-word note you send on the same day each month to tell your investors where you are, what is working, what is not, and what you need. Done consistently, it turns passive shareholders into an active network: making introductions, surfacing problems before they compound, keeping you top of mind when an opportunity lands in their inbox.

The nine templates below cover the moments founders most need: the standard monthly update, the first note after closing a round, the bad-month update, the runway-warning message, the specific-asks update, the pre-raise warm-up, a milestone announcement, a quiet month, and the pivot or major strategy-shift. Each template uses bracketed placeholders — [METRICS], [MoM CHANGE], [RUNWAY], [ASKS], [LOWLIGHTS] — to adapt and send in under ten minutes.

How often should founders send investor updates?#

Monthly is the consensus standard. Y Combinator's guidance for portfolio companies is consistent: monthly updates, sent on a fixed day within the first five days of each month. Weekly is too frequent for most stages. Quarterly is too sparse; it looks like avoidance and leaves investors guessing during stretches when they could have helped.

Pick one date — the 1st, the 3rd, or the 5th — and protect it. The specific day matters less than the consistency. Consistent timing tells investors you treat communication as a professional obligation, not a marketing exercise.

Two practical rules: send the update even in quiet months — it proves you are not only reaching out when you need something. And send it to all investors at once on a single list or bcc, not in individual threads, so every shareholder has the same information.

Block 45 minutes on the fixed date and protect it

Founders who write the best investor updates set a recurring 45-minute block on, say, the 3rd of every month. The constraint forces clarity: you have 45 minutes to write the update, which means it stays short and the numbers have to be ready. Long updates are almost always a sign the numbers are not clear yet, not a sign of thoroughness.

What a good investor update contains#

300 to 400 words plus a metrics block is enough. Completeness matters, not length — the table below maps each section to what belongs there.

SectionWhat to includeTarget length
MetricsMRR or ARR; month-over-month change; burn rate; one or two leading indicators such as trials, pipeline, or churn rate2 to 4 numbers, no narrative
HighlightsOne or two things that went measurably well since the last updateTwo to three sentences
LowlightsOne or two honest problems, risks, or misses — no spin, no buried ledeTwo to three sentences
RunwayMonths of cash at current burn; updated monthly, not quarterlyOne number; optionally one sentence on what changes it
AsksSpecific introductions, open roles, partnerships, or advice you need — each ask is one line, named where possibleThree to five line items
Product or team (optional)A shipped feature, a key hire, a departure — only if genuinely material to the businessTwo to three sentences; skip if there is nothing worth noting

The section order matters as much as the content. Metrics come first because investors scan for numbers first. Lowlights belong before asks — burying a problem after an ask reads as manipulation. Asks come last and must be specific: 'any introductions welcome' gets zero responses; 'warm intro to the Head of Partnerships at Stripe, working on embedded finance' gets a reply from the one investor who has that contact.

The nine templates follow. The first six cover the most common update types; the last three cover moments founders frequently mishandle. Replace each bracket with your real numbers and names before sending.

Diagram showing the five modular sections of a monthly investor update email: a metrics block, a highlights block, a lowlights block, a runway figure, and a specific asks list
A well-structured investor update is five modular blocks in a fixed order. Metrics first, asks last. The order is not a preference — it is what keeps investors from feeling managed.

Template 1: The standard monthly investor update#

Use this eleven months out of twelve. The goal is a complete, honest picture of the business in the time it takes to read one page. Do not add context the numbers do not need.

Standard monthly investor update
Subject[Month] update — [Company]
Hi [Investor First Name],
Here is where we are.
MetricsMRR: [METRICS] ([MoM CHANGE] from last month). Burn: [BURN]/month. Runway: [RUNWAY] months at current burn.
Highlights[1 to 2 things that went measurably well — e.g. 'Signed [Company] as our first enterprise customer at $[ARR] ARR.']
Lowlights[1 to 2 honest misses or risks — e.g. 'Churn ticked up to [X]% this month, concentrated in the [segment] cohort. We believe the cause is [short explanation] and are testing [specific change] this week.']
Runway[RUNWAY] months. [Optional: 'That extends to [N] months if we close [pipeline deal] before [date].']
Asks1. Intro to [specific person or role] at [company] — working on [specific thing]. 2. Referral to a [specific role] who has done [specific thing] at an early-stage SaaS company. 3. [Third ask, one line.]
Happy to jump on a call if any of this raises a question. Next update: [Date].

Template 2: The first update after closing a round#

The first update after a close sets expectations for every update that follows. It is part thank-you, part cadence-setter. Use the space to name the plan and the rhythm.

First update after closing a round
SubjectFirst update from [Company] — [Month] [Year]
Hi everyone, thank you for backing [Company]. I am grateful for the trust and want to start as I intend to go on: a short, honest update on the [Nth] of every month.
Where we areWe closed [Round] at [valuation or cap], with [Amount] in the bank. Current MRR: [METRICS]. Burn: [BURN]/month. Runway: [RUNWAY] months.
The plan for this capital[Two to three specific things you will use it for, time-boxed — e.g. 'Hire a Head of Sales by Q3', 'Reach $[ARR] by year-end.' I will measure us against these commitments in every future update.]
Asks — right now1. Warm intro to [specific target: role and company]. 2. [Second ask, one line.] If you can help with either, reply and I will send a blurb.
Next update: [Date]. Thank you again for coming in.

Template 3: The bad-month investor update#

The template most founders avoid writing and most investors most want to receive. When the numbers went backwards, the instinct is to delay, bury the lowlight, or frame the miss as a temporary anomaly. Resist all three: lead with the lowlight, name the cause even if tentative, and name what you are doing about it and when you will know if it is working.

Bad-month investor update
Subject[Month] update — [Company] — [METRICS] MRR ([MoM CHANGE])
Hi [Investor First Name],
A difficult month. I want to be direct about what happened before the full numbers.
The lowlight[LOWLIGHTS] — e.g. 'We lost [N] customers in the [segment] cohort. Combined with slower new business, MRR fell [MoM CHANGE].' We believe the cause is [specific diagnosis, even if tentative]. We are doing [specific action] and expect to know by [date] whether it is working.
MetricsMRR: [METRICS] ([MoM CHANGE]). Burn: [BURN]/month. Runway: [RUNWAY] months — unchanged, because [brief reason].
Highlights[One honest highlight if one genuinely exists. Skip this section rather than stretching to find one.]
Asks1. If you know anyone who has navigated [specific situation], an introduction would be valuable right now. 2. [Second ask.]
I will give you a fuller picture of whether the fix is working in the next update. Thank you for being in this with us.

Template 4: The runway-warning investor update#

Raise the alarm at six months remaining, not three. At three months you are in a forced timeline with few options. At six you still have room to act. Name the number, the plan, and specifically what help looks like.

Runway-warning investor update
Subject[Month] update — [Company] — runway at [RUNWAY] months
Hi [Investor First Name],
The usual update, plus a heads-up I want to give you with enough time to be useful.
MetricsMRR: [METRICS] ([MoM CHANGE]). Burn: [BURN]/month. Runway: [RUNWAY] months at current burn.
Runway noteAt [RUNWAY] months, we are at the point where I want to loop you in early. Our plan: [Option A — e.g. 'reach $[MRR] by [date] and raise a [Series X] on that basis'] or [Option B — e.g. 'reduce burn to $[amount] to extend runway while we close [pipeline deal]']. I am treating [date] as the decision point.
Highlights[HIGHLIGHTS]
Lowlights[LOWLIGHTS]
Where I need help1. If you are open to a bridge or pro-rata in a near-term round, please let me know privately — useful to know before I go to market. 2. Warm intro to [specific investor type] at [stage and geography]. 3. [Third ask.]
Happy to get on a call this week if helpful. I will update you on each of these on [date of next update].

Template 5: The specific-asks investor update#

Use this when you have a concrete set of needs. The business update stays brief; each ask is specific enough for an investor to answer yes or no in thirty seconds.

Specific-asks investor update
Subject[Month] update — [Company] — 3 specific asks
Hi [Investor First Name], short update this month. Numbers are [brief characterization — 'holding steady' or 'up [MoM CHANGE]' or 'a tough month, detail below']. The main thing I want from this email is three specific outcomes.
MetricsMRR: [METRICS] ([MoM CHANGE]). Burn: [BURN]/month. Runway: [RUNWAY] months.
Ask 1Intro to [Full Name or Role] at [Company]. We are trying to reach their [procurement / partnerships / engineering] team because [one sentence on why]. If you know them or know someone who does, a warm intro would move the needle significantly.
Ask 2Referral to a [specific role] with [specific experience — e.g. 'has taken a B2B SaaS product from $1M to $5M ARR']. We are hiring for this position now. Salary range: [$X to $Y]. Any names welcome.
Ask 3Advice on [specific decision — e.g. 'whether to go direct or through a channel partner in the enterprise segment']. Twenty minutes with someone who has faced this would be worth a lot. Happy to share full context.
If you can help with any of these, reply and I will send a blurb or book a call. Thank you.

Template 6: The pre-raise warm-up#

Start warming up investors two to three months before you raise, not when you open the fundraise — by then you have lost two to three months of relationship-building. Send this with metrics trending in the right direction and a clear description of the milestone you are building toward. Do not announce the raise; describe the milestone and what it unlocks.

Pre-raise warm-up investor update
Subject[Month] update — [Company] — building toward [milestone]
Hi [Investor First Name], a good month, and one I wanted to share in some detail because we are building toward a moment that matters.
MetricsMRR: [METRICS] ([MoM CHANGE]). Burn: [BURN]/month. Runway: [RUNWAY] months.
Highlights[2 to 3 highlights that show the business accelerating or de-risking — e.g. 'Closed [N] new enterprise accounts in [Month] — fastest month of new business since launch.']
The milestone we are building toOur focus for the next [N] months is reaching [specific milestone — e.g. '$500K ARR' or '10 enterprise design partners' or 'unit-level profitability in the [segment] segment']. At that milestone, we believe we will have [what it unlocks — e.g. 'a strong basis to raise a Series A on favorable terms']. Everything we are doing right now maps to that target.
Lowlights[LOWLIGHTS — be honest even in a warm-up update; investors notice when a pre-raise message has no lowlights]
Asks1. [Specific ask that helps the milestone]. 2. [Second ask.] 3. If you are open to participating in our next round, I would love to know privately ahead of time — no pressure, just useful context for planning.
Next update: [Date]. Thanks for being on this journey with us.

Template 7: The milestone or product-launch update#

Not every month warrants a milestone announcement. When one does — a first enterprise contract, a major product launch — put the milestone at the top and reorder the opening so investors know immediately why this month is different.

Milestone or product-launch investor update
Subject[Month] update — [Company] — [Milestone name]
The news[One to two sentences on the milestone, specific and concrete — e.g. 'We launched [Feature] on [Date]. In the first [N] days, [specific result: 200 new signups, 40% of existing users adopted it, three enterprise prospects moved to trial.']
Why it matters[One sentence on what this does for the trajectory — e.g. 'This changes our enterprise sales conversation: we now have a live demo of [capability] that no competing product ships yet.']
MetricsMRR: [METRICS] ([MoM CHANGE]). Burn: [BURN]/month. Runway: [RUNWAY] months.
Lowlights[LOWLIGHTS]
Asks1. [Ask directly tied to the milestone — e.g. 'Intro to enterprise procurement at [type of company]: we now have a case study to share.']. 2. [Second ask.]
Excited to show you what comes next.

Template 8: The quiet-month investor update#

Some months the metrics are flat and nothing notable shipped. Send the update anyway. Founders who go quiet on flat months train investors to associate late updates with bad news — a brief quiet-month update costs five minutes.

Quiet-month investor update
Subject[Month] update — [Company]
Hi [Investor First Name], a quieter month than I would like to report, but a complete picture.
MetricsMRR: [METRICS] ([MoM CHANGE] — flat). Burn: [BURN]/month. Runway: [RUNWAY] months.
Where the team's time went[Brief explanation — e.g. 'Most of [Month] went to fixing a reliability issue affecting [N] accounts and rebuilding our onboarding flow. Neither shows up in this month's MRR, but both clear the path for [Month+1].']
Lowlights[LOWLIGHTS — a flat month is better framed as flat than as 'a period of consolidation']
Asks1. [Specific ask.] 2. [Second ask if relevant.]
Short update this month. Back with more to show next time.

Template 9: The pivot or major strategy-shift update#

A strategic pivot is the update founders most often mishandle, usually by under-communicating. Investors do not mind a pivot; they mind finding out through the grapevine. Be explicit: name the old strategy and the new one, the evidence that prompted the change, and the signal you will use to know if the new direction is working.

Pivot or major strategy-shift investor update
Subject[Month] update — [Company] — a strategic shift I want to explain
Hi [Investor First Name], this month's update includes a significant change I want to be direct about.
The shiftWe are moving from [old strategy — specific] to [new strategy — specific]. The evidence: [two to three data points — e.g. 'Of our 40 customers, 8 are using the new approach without prompting and have measurably better retention. The other 32 are churning at twice the rate.']. We tried to make [old approach] work for [N] months. The data is clear enough that we are committing to the new direction.
What changes and what does notChanges: [specific things]. Does not change: [specific things — e.g. 'core technology, the team, the target customer segment'].
MetricsMRR: [METRICS] ([MoM CHANGE]). Burn: [BURN]/month. Runway: [RUNWAY] months.
How we will know it is working[Specific metric and timeframe — e.g. 'If the new direction is right, we expect [specific outcome] within [N] months. If we do not see it, we will tell you.']
Asks1. If you have seen a similar move work or fail, I would genuinely value a conversation. 2. [Second ask.]
I want you to hear about this from me, clearly and early. Happy to get on a call if you have questions.

How to write the bad-month update well#

Template 3 gives you the structure. The harder part is the instinct to override. When MRR drops or a key customer churns, the impulse is to wait for something good to happen first, or to write the bad news softly while detailing the highlights. Both produce the same result: an investor who reads between the lines and loses confidence in your judgment, not just your numbers.

A clear bad-month update almost always generates more engagement than a good one. 'MRR fell 12% — here is why, here is the plan' tells investors you do not hide from reality, a quality more bankable than any single month's metrics.

Three rules. First, lead with the lowlight — before the metrics block, not after paragraphs of context. A founder who buries bad news hopes the investor stops reading; they do not. Second, name the cause even if tentative: 'we believe the cause is X' is more trustworthy than vague framing. Third, name the action and timeframe: 'we are testing Y and expect to know by [date].' That converts a bad-news update into a plan update.

Silence is louder than bad news

Founders who go quiet during a difficult stretch train investors to assume the worst whenever an update is late. An investor who receives a bad-month update on time, with a clear plan, is far more likely to help than one who has been waiting three weeks. Consistency of reporting matters more than the numbers in any single month.

What to do when investors do not reply to your updates#

Most investor updates get no reply, and that is not a signal of disengagement. Measure engagement by the quality of help you receive on specific asks, not by reply rate.

A few things increase the odds of a useful response.

  1. 1

    Make the ask specific and named

    An ask like 'intro to Sarah Chen, Head of Partnerships at Stripe, working on embedded finance' gets answered; 'any fintech introductions welcome' gets ignored. The more specific the ask, the faster an investor can say yes.

  2. 2

    Ask one direct question per quarter

    End one update per quarter with a direct question: 'Has anyone seen a clean solution to this pricing problem?' or 'Is anyone open to a 20-minute call on our hiring approach?' A question is easier to respond to than an open-ended update.

  3. 3

    Follow up by phone on a single time-sensitive ask

    If one investor could help with a time-sensitive ask, a single direct follow-up call is legitimate. More than once on the same ask becomes pressure, not communication.

  4. 4

    Interpret silence as satisfaction, not neglect

    An investor who reads your update, finds nothing alarming, and moves on is doing exactly what you want. Optimize for information quality, not reply volume.

Should you share runway with investors every month?#

Yes. Runway is a risk indicator and investors are risk monitors. Withholding or softening the number does not prevent a difficult conversation — it makes it worse. An investor who has watched runway drop from 18 months to 6 across six updates has context and can help. One who finds out at four months has been handed a problem, not a number.

Report the actual number each month — months at current burn — and note what changes it. Do not round 5.5 to 'roughly six' or call 4.5 months 'a comfortable position.' Investors respect founders who report these numbers accurately.

The trigger for a runway-warning update (Template 4) is six months remaining — when you still have options. At three months you are in a forced process. The difference is almost entirely how long ago you started the conversation.

Let AI Emaily draft the update#

The blank page is the hardest part, especially in difficult months. AI Emaily is an AI-native email client that works with Gmail, Outlook, and any IMAP account. Set your communication context once — writing style, company stage, update structure — and it drafts in your voice rather than generic template language. We build AI Emaily — that is on the table.

AI Emaily works in three modes: Manual drafts for you to review; Copilot prepares the draft and waits for your one-click approval; Autopilot sends within rules you set. Every action has undo and a full audit trail. The 7-day free trial is at aiemaily.com/pricing.

Frequently asked

Nafiul Hasan

Written by

Nafiul Hasan

Nafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.

EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
More from Nafiul
Ready when you are

Draft your investor update in under 10 minutes.

AI Emaily writes the first draft in your voice, keeps the structure consistent month after month, and logs every send with undo and audit. Try it for 7 days.

  • 7-day free trial
  • Cancel anytime
  • Every provider