Guide

If you do one thing after a raise, send a short monthly email to every investor (and often to serious angels who asked to be on the list). Consistency beats polish. Partners see dozens of companies; a predictable format trains them to skim and respond.

Concept

Information rights in a financing often legally entitle major investors to regular financials and inspection rights (see control terms). The monthly update is the cultural version of the same idea: you reduce surprise risk for people who cannot see your Slack. Treat the email as part of governance, not marketing.

The big idea

Subject: [Company] update — Mar 2026

1. Highlight (3–5 bullets)
2. Metrics (table or tight list vs last month / plan)
3. Lowlights / risks (honest)
4. Asks (specific, actionable)
5. Appendix (optional links: dashboard, deck)

Highlights. Ship, customers, hires, revenue wins — facts, not adjectives.

Metrics. Pick a stable set and do not rotate the scoreboard to flatter the month. For SaaS, a typical set: MRR/ARR, MoM growth, gross churn or NRR, burn, runway, cash. Consumer or marketplace companies substitute the north-star that actually runs the business. See SaaS metrics and burn and runway.

Lowlights. This section is the trust engine. Missed hire, churned logo, delayed launch, pipeline slip — name it and say what you are doing. Investors forgive bad months; they do not forgive discovering them in diligence for the next round or from Twitter.

Asks. Specificity wins: "Intro to VP Eng at companies like X/Y for our enterprise pilot" beats "intros welcome!" Include a one-line blurb they can forward.

Cadence: monthly is the default for venture-backed startups. Weekly is usually noise unless you are in a crisis or an active fundraise. Quarterly-only is too sparse once you have institutional investors.

Default distribution: every preferred investor, every SAFE holder who asked for updates, and board observers. Do not send the full investor update to the whole company — numbers and asks leak — but do share a cleaned metrics snapshot in all-hands so internal and external stories match.

Length: half a page to two pages. Attach a live dashboard link only if it stays accurate; a stale Looker link destroys credibility faster than no link.

Walking through a lowlight

Frame: fact → impact → action → ask (if any).

"Enterprise churn: lost 2 logos ($18k MRR). Cause: onboarding debt on SSO. Fix: dedicated CSM + SSO checklist shipping Friday. Ask: intros to security reviewers at similar logos."

That is usable. "Challenging month but we remain excited about the opportunity" is not.

Same pattern for hiring asks. Bad: "Let us know if you can help with hiring." Good: "We are hiring a founding AE (NYC or remote East Coast), $OTE $180k, selling to VPs of Ops at $20–100M retailers. Forwardable JD attached — warm intros to operators who have hired AEs appreciated this month."

Common mistakes

  • Rotating metrics to make the month look good. Partners notice.
  • No lowlights. Trust dies when the miss shows up in the next raise.
  • Vague asks. "Intros welcome" is not an ask.
  • BCC-ing the whole company on the investor email.

Check yourself

Your update has highlights and a dashboard link, no lowlights, and "intros welcome." What is missing?

An honest miss with a fix, and a specific forwardable ask. The dashboard link only helps if it is current.

Who should get the full email vs a cleaned all-hands snapshot?

Investors and observers get the full note. The company gets metrics that match the story, not the asks and legal detail.

Key takeaways

  • Monthly: highlights, stable metrics, lowlights, specific asks.
  • Lowlights are the trust engine; frame fact → impact → action → ask.
  • Make asks forwardable. Track who actually helps.
  • Internal all-hands numbers should match the investor story.

Further learning

Next, the formal version of the same honesty: running board meetings.