How to write a founder update investors read
An investor update is the cheapest trust a founder can build, and the most commonly wasted. Done well, it takes thirty minutes a month and keeps your network primed to help. Done badly, it trains your most useful readers to archive you. This guide shows a weak and a strong update, then the three-part structure that separates them.
Why do founder updates go unread?
An investor scans an update for exactly two things: is this company alive and learning, and is there anything I can do. Most updates answer neither. They open with pleasantries, report “momentum” without numbers, hide the problem in paragraph four, and end without an ask. The reader cannot help, so they archive.
Worse, vagueness is itself a signal. Investors assume that hidden numbers are bad numbers. A foggy update does not protect you; it starts the very speculation you were trying to avoid.
What does a weak update look like?
Subject: Update
Hi everyone,
Hope you’re all doing well. It’s been a busy couple of months over here. The team has been heads-down on a bunch of exciting things — we shipped some big improvements to onboarding, started conversations with a couple of really interesting potential partners (can’t share names yet, but fingers crossed), and we attended two conferences that generated a lot of buzz.
On the growth side, things are moving. We’re seeing encouraging engagement and some really positive feedback from users. Churn has been a bit of a challenge, but we have some ideas there. Hiring is ongoing — it’s a tough market.
There’s a lot more I could share, so if anyone wants to grab coffee, I’m always happy to chat. Thanks as always for your support.
Cheers, Alex
No numbers anywhere. “Encouraging engagement” is not a metric, and “a bit of a challenge” is a problem wearing makeup. The subject line says nothing, the only ask is coffee, and the one fact that matters — churn — is hand-waved in a subordinate clause.
What does a strong update look like?
Subject: Acme — May: MRR $41.2k (+9%), churn down, one ask
Headline: MRR $41,200, up 9% month over month. Churn 6.1%, down from 7.4% after the onboarding rework. The hard news: our lead engineer resigned. An offer is out to a replacement; zero runway impact, roughly three weeks of velocity lost.
What we learned:
- Annual-first pricing works. 40% of May upgrades chose annual once we reordered the pricing page.
- Outbound does not, yet. 200 cold emails produced one demo. We are pausing it for partner referrals, which closed five of our last eight deals.
What we need: two or three intros to heads of operations at mid-size logistics firms. Reply “intro” and I’ll send a one-paragraph blurb you can forward.
— Alex
The metric sits in the subject line. The bad news sits in the first paragraph, attached to a plan. Every lesson carries a number. The ask is specific and forwardable — a reader can act on it in ninety seconds.
What structure makes the difference?
- Headline metric. The one number you steer by, with its direction and last period’s value. If you would not put it in the subject line, it is not the headline.
- What we learned. Two or three items, each a claim plus a number. Early investors are not funding this month’s revenue; they are funding a team that learns fast, and this section is the proof.
- What we need. One specific, forwardable ask. “Intros to operations leads at logistics companies” gets replies. “Let me know if you can help with anything” gets archived.
How often should you send it, and how honest should you be?
Pick a cadence you can hold — monthly is the common default — and never skip one. A missed update reads as a bad month even when it was merely a busy one. The discipline signals more than the interval does.
On honesty: bad news goes early. First paragraph, never the postscript, never omitted. Investors expect problems; what they punish is surprise. The ones who learn early can open their networks to help. The ones who find out late stop believing your good news too.
Save these rules as a playbook
The skeleton of a strong update never changes; only the numbers do. Save it as a playbook in ILURA and train it by correcting a draft or two — version history keeps every refinement, so your update voice compounds the way the company does. It all runs on your iPhone, no account required.
Turn this message into an agent rule
Do not treat the answer as a one-off rewrite. Save the repeatable behavior behind it so your ILURA agent can apply the same judgment next time.
- What situation triggered the message?
- What tone, boundary or decision should repeat?
- What should the agent avoid doing again?
Problems this guide helps with
The same rule appears in real user searches.
Do it now
Draft this in ILURA right now.
Open ILURA, paste your message, and get help with "write founder update" — in your voice, on device, free. It quietly saves the rule (Metric, lesson, risk, ask.), so the next time is one tap.
Free to start · No account · Data Not CollectedQuick answers
- How often should I send a founder update?
- Monthly is the default for most early-stage companies. Pick a cadence you can hold for a year, because a skipped update reads as a bad month even when it was not.
- Should I tell investors bad news?
- Yes, and early — in the first paragraph, attached to a plan. Investors expect problems; what they punish is surprise. Those who know early can actually help.
- How long should a founder update be?
- Under 300 words for the core update. If a topic needs depth, append it below the ask so the scannable version stays intact for busy readers.