Follow up on what you said you’d do.
Read your last update before drafting the next one. If you said you would launch onboarding, close a pilot, or hire an engineer, say what happened. A missed target deserves a sentence too.
If the priority changed, explain why. “We delayed the reporting release by two weeks to fix the import errors affecting our three largest customers” gives the reader a reason for the change. Quietly dropping the release from the email leaves them guessing.
Write the opening after the rest.
Once you’ve written the details, pull the main result and the biggest concern into two or three sentences at the top. Someone who only reads that paragraph should understand how the month went.
“We ended September at $24,000 MRR, up 20% from August. Four smaller customers cancelled after their first month, so our focus for October is getting new teams through setup.”
There’s no need for “an exciting month” or a long thank-you before the news. You can sound like yourself and still get straight to it.
Keep the numbers comparable.
Choose a small set of metrics you can report every month. For a subscription business, that might be MRR, paying customers, cash, and net burn. Before revenue, it could be active pilots and product milestones alongside cash and runway.
Put the previous period next to the current one. “MRR: $24,000, up from $20,000 in August” is more useful than “MRR grew 20%.” It shows the size of the business as well as the growth. Use the same date range and definition each time; explain any change in how you count a metric.
State the assumption behind your runway. “12 months at September’s spending” tells the reader what the estimate means. If planned hires will shorten it, include that too. Keep a weak metric in the update even when another number looks better.
Explain what the work accomplished.
Pick the few changes that matter to the business. A list of meetings, tickets, and releases makes the reader figure out which ones were useful. Tell them what happened for a customer or what you learned.
“Shipped onboarding v2” names the work. “New teams now finish setup in three days, down from eight” explains the result. If it’s too early to measure the result, say when you’ll know. You don’t need to claim a win before you have one.
Say what went wrong and what happens next.
Name the problem, describe its effect, and explain your next step. Separate what you know from what you suspect. Three cancellation interviews can give you a reason to test a shorter setup flow; they don’t prove that setup caused every cancellation.
“Four customers cancelled in their first month. Three told us setup took too long. We’re testing a shorter checklist with October’s new customers and will report back on how many finish setup.”
If you haven’t worked out the cause, say so and describe how you’ll investigate. An honest open question gives an investor something useful to respond to.
Give someone a request they can forward.
Choose the one or two things outside help could move forward this month. For an introduction, name the role, type of company, and reason you want to talk. Include enough context that your investor can pass the request along without rewriting it.
“Do you know a head of operations at a distributor with 20–100 staff? We’re looking for three people who still manage orders in spreadsheets to try our order import flow. It’s a 20-minute call, with no preparation needed. Reply if someone comes to mind and I’ll send a short intro.”
Follow up on help from the previous month, too. If an introduction led to a pilot or an interview, let the person who made it know.
Read it once as the person receiving it.
Keep the subject easy to find later: “[Company] investor update — September 2026.” Put the update in the email body. Link to a detailed report when it helps, but keep enough context in the email that nobody has to open an attachment to understand the month.
Before sending, check:
- Can the opening stand on its own?
- Do the numbers use the same period and definitions as last time?
- Have you followed up on the targets you set in your last update?
- Does each request say who can help and what to do next?
Cut anything that repeats a point or needs a paragraph of jargon to explain. Pick a regular day to send the update, including in quiet months. If something needs an urgent conversation, have it when it happens instead of saving it for the next email.
