The Investor Update Template Nobody Writes for Founders Outside the US

A good investor update is a headline metric with a trend, two or three specific wins, one honest miss, a cash-and-runway line, and a single clear ask — sent on the same schedule every month, in under 500 words. Every template on the first page of search results gives you that structure. None of them tell you what to do when half your investors read cash flow in dollars and the other half in riyals, dirhams, or naira, and that gap is where most non-US founders actually get stuck.

The structure isn't the hard part. Every accelerator hands out a version of it — Y Combinator's, Techstars', a dozen VC blogs with the same five headers reordered. The hard part is the mechanics underneath it: which currency you lead with, how you keep the numbers honest when they come from three different sources, and who actually belongs on the list. That's the part this article covers.

The structure, once, so it's out of the way

Five sections, in this order, because investors read top to bottom and stop when they've seen enough:

1. Headline metric. Your one north-star number — MRR, active users, gross transaction volume, whatever you'd say first on a call — with the trend direction next to it. Not a table. One number, one arrow.
2. Wins. Two or three specific things that happened, with numbers attached. "Closed our first enterprise contract" is weaker than "closed a $40K/year contract with [customer type], our largest to date."
3. The miss. One real challenge, stated plainly. Investors who've operated companies respect this more than a highlight reel with no shadows, and it's the line that makes the rest of the email credible.
4. Cash and runway. Current cash, monthly burn, months of runway at current burn. Three numbers, no more.
5. The ask. One specific thing you need — an introduction to a named type of person, feedback on a decision, a warm intro to a customer segment. Vague asks ("let us know if you can help") get ignored because they require the investor to do the thinking you should have done.

That's the whole template. If you've read a "how to write an investor update" article before, none of this is new. What's missing from every version of it is what happens once your cap table has investors in more than one country, which describes most Seed-to-Series-B companies outside the US by the time they've closed a second round.

Where the generic template breaks

The currency problem. If you're operating in Saudi riyals, UAE dirhams, Nigerian naira, or Indonesian rupiah, and your investor base includes both local and international funds, "cash: 450,000" means nothing without a currency and a conversion. The fix isn't to run two versions of the update — it's one email, with your operating currency as the primary number and a parenthetical conversion at the rate on the date you're sending, stated explicitly: "SAR 1,650,000 (~$440,000 at 3.75)." State the rate. An investor doing quick mental math with the wrong exchange rate in their head will misjudge your runway, and they won't tell you that's what happened — they'll just quietly recalculate your risk.

The timezone problem. "Send it Wednesday morning" assumes a fund and a founder in the same three time zones. If your cap table spans Riyadh, London, and San Francisco, no single send time lands as "morning" for everyone. Pick the timezone where most of your check size sits, send there, and stop optimizing further.

The sourcing problem. This one damages trust, and it has nothing to do with geography. Most founders build the update from three places — a bank statement, a spreadsheet cap table, and memory of last month's grants and closes — reconciled by hand at 11pm the night before it ships. That reconciliation is where errors happen: a SAFE that closed but never got added to the spreadsheet, an option grant that vested but wasn't logged, a runway number calculated against last month's burn instead of this month's. None of that is bad faith. It's what happens when the update and the source of truth live in different files.

Write the update from the ledger, not from memory

The fix isn't a better template — every template says the same five things. The fix is where the numbers come from. If your cap table, SAFE overhang, and burn tracking live in the same system you're sending the update from, the headline numbers in section four are already correct before you start writing, because they're not being re-typed from a spreadsheet that's a week stale. You're writing the narrative around numbers that are already right, instead of writing the narrative and then scrambling to verify the numbers match what's actually true.

This also sharpens the ask in section five. "We're looking for an intro to enterprise buyers in the Gulf" is a fine ask. "We're 8 months from closing our next round, our SAFE overhang is 12%, and we need two more soft circles before we go to term sheet" is a better one — and you can only write that second version confidently if the overhang number is live, not calculated from three PDFs the week the email goes out. If you're not sure your current SAFE math is right, check before your next update — we've walked through the mechanics of multiple SAFEs stacking and diluting founders separately.

Govy's investor updates work this way by default: they compose against the same ledger that holds your cap table, so the numbers in the email are the numbers that are actually true that day, and every update sends and records permanently against that investor's activity history — with open tracking, so you know whether the update was read before your next board conversation, not after.

Who actually gets the update

Three lists, not one:

• Committed investors. Everyone who's wired money, no exceptions, no matter how small the check. A $10K angel check who gets skipped because the update list only includes "real investors" is a $10K angel who won't refer you to the next ten people they know.
• Warm passes. Anyone who took a real meeting, gave real feedback, and passed for a stage or thesis reason rather than a flat no. This list is your next round's pipeline, and a consistent update is the only thing keeping you in their peripheral vision between now and then.
• Advisors and board observers. Include them in the same update as investors, not a separate summary. A second version of the truth, written for a different audience, is where inconsistencies creep in.

Keep cold contacts and anyone who gave a hard "not a fit" out of the list entirely. An investor update that reads as a mass newsletter to people who don't remember taking your call gets marked as spam in the reader's head even if it never touches an actual spam folder.

A cadence you can actually keep

The template only works if it ships on schedule. Monthly for pre-seed and seed, tightened to every two weeks while you're actively raising, quarterly once you're past Series A and the month-to-month numbers move slower. The exact cadence matters less than never missing one — a founder who sends updates every month without fail is telling investors something about how the company is run before they've read a single metric. A founder who sends three updates then goes quiet for four months is telling them something too, and it isn't reassuring.

If your data room is already the thing investors check between updates, the update and the room should tell the same story — we've covered how to structure a data room that doesn't require you to explain what's changed on every call, which pairs directly with a monthly update that references it.

Start from numbers you don't have to double-check

The five-section structure is table stakes — copy it, it works. What separates an investor update that builds trust from one that quietly erodes it is whether the numbers inside it came from a live ledger or a reconciliation you did the night before. Govy sends investor updates from the same system that holds your cap table and SAFE overhang, with delivery and open tracking built in, so the update you send is the update you'd stand behind if an investor asked a follow-up question five minutes later. See it at govy.tech.

FAQ

How often should a startup send investor updates?

Monthly for pre-seed and seed companies, quarterly once you're past Series A and metrics move more slowly. If you're actively raising a round, tighten to every two weeks until it closes, then drop back to monthly. The frequency matters less than never skipping a cycle — investors read consistency as a signal about how you run the company, not just what's in the email.

What should be in an investor update email?

Five things, in this order — a headline metric with trend direction, two or three specific wins, one honest challenge or miss, a short financial snapshot (cash, burn, runway), and a specific ask. Skip the narrative preamble and put the metric in the first line; investors skim before they read.

Should you send updates to investors who haven't invested yet?

Yes, if they took a meeting and passed with genuine interest rather than a hard no. A prospect who declined because the round wasn't the right stage for them is a warm lead for your next round, and a running trail of updates is what turns "not now" into "let's talk" a year later. Don't add cold contacts who never took a call — that's a newsletter, not an investor update.

How do you send one investor update when investors are in different currencies?

Report your primary operating currency as the headline number and add a one-line USD (or EUR) conversion in parentheses next to cash and burn, using the rate on the date of the update, not a rounded approximation. State the rate you used. An investor in Riyadh and an investor in London should be able to read the same email and both trust the number without opening a spreadsheet.

How long should an investor update be?

250 to 500 words for a monthly update — long enough for five sections, short enough to read on a phone between meetings. Quarterly updates can run 750 to 1,500 words if you're adding a strategy section, but the monthly cadence should stay short enough that skipping it feels like an obvious gap in the investor's inbox.