Last month, you promised three things. This month, your investor update opens with a new list of wins.
What happened to the three things?
A polished update can still leave the reader doing the hardest work: reconstructing what changed. This template starts with that missing connection. It pairs a short monthly email with three working tables for commitments, metric definitions and requests for help.
Use the email to explain the month. Use the tables to keep one month from erasing the last.
Below: two real company updates, a current investor perspective, and a copyable template. The worked rewrites are clearly labeled fictional; the sourced company examples are not.
Download the editable worksheet · Free Markdown file; no signup.
Two real updates worth opening
Coverflex, Q2 2025: put the miss beside the number
Coverflex reported €14.2M in cARR—and 92% of its year-to-date target. Its opening explanation linked the shortfall to softer usage revenue. Growth and a missed target appeared together, rather than letting the impressive absolute number tell the whole story. Read Coverflex’s public Q2 2025 update.
Borrow this: actual → target → explanation. Keep the source’s metric label: cARR is what Coverflex reports; we are not relabeling it as recognized revenue. This is a growth-stage company’s historical, self-reported update, not a benchmark for a seed-stage startup.
There is useful nuance in founder Miguel Santo Amaro’s accompanying post: he says the broad shareholder update omitted a dedicated lowlights section, while board materials were more explicit. Our takeaway: choose the right audience for sensitive detail, but do not make the material problem disappear.
Cap, May 2024: describe the cost of a wrong turn
Cap’s public update has an explicit lowlights section. It reports hosting downtime, slow responses and an AI-infrastructure redesign that delayed development. The company acknowledges that some technical choices led to dead ends after substantial work. Its closing request asks for software/AI engineering and frontend candidates. Read the original Cap update, pages 2 and 4.
Borrow this: name the constraint and its operational consequence. Then sharpen the request. Cap’s actual hiring ask is broad; the document does not establish that it solved the infrastructure issue or produced hires. A stronger hypothetical version would specify the relevant expertise and the next decision it should help resolve.
Treat this as a historical example of communication, not a report on Cap’s current business.
What didn’t work is where the ask begins
A wins-only update leaves investors to guess where help would matter. A candid setback supplies context: what changed, why it matters, what the team has tried, and what remains unresolved.
Read Trace Cohen’s post on sharing bad news with investors
In a September 2026 essay, investor Jessica Lynch describes a founder who kept communicating through cofounder changes and fundraising trouble. She says she would back that founder again despite losing money. That is one investor’s stated judgment, not evidence that candid updates guarantee another cheque. Her advice is to separate the facts from your assessment and ask for specific help. FoundersEdge: updates when things go wrong.
Use this sequence to turn a setback into a request:
- Miss: What did you expect, and what actually happened?
- Diagnosis: What does the evidence suggest? What is still unknown?
- Response: What are you doing, stopping or testing? Who owns it?
- Ask: What person, experience or introduction would help with that response—and by when?
Do not invent a tidy root cause to look in control. “We do not know yet; here is the test” can be the accurate answer. An ask should help the team execute or decide, not transfer responsibility for the problem to investors.
Read Shruti Gandhi’s post on asking investors for help
Three ways to make the ask actionable
These are original hypothetical rewrites, not quotes from the companies above.
| What didn’t work | Useful ask |
|---|---|
| Three pilots slipped at data import | One engineer with [specific system] migration experience to review our sample import by [date] |
| Two late-stage deals chose a competitor | A sales leader in [buyer segment] to review our loss notes in one 30-minute session |
| Five candidates declined the same role | A founder who filled that role at our stage to review scope and compensation assumptions |
Add what you have already tried and a small, shareable packet: an anonymized example, a one-page problem statement or the relevant decision. Make the first useful action possible without a meeting to explain the request.
Not every setback needs an ask. If the team has the evidence and capacity to resolve it, report the response and next checkpoint. Do not manufacture an introduction request just to fill a section. If the issue materially changes the company’s position, contact the relevant investors promptly rather than saving it for the next monthly email.
Copy the monthly investor update template
Replace every bracket. Remove sections that do not fit your business. Keep unknowns visible rather than filling them with plausible numbers.
Subject: [Company] investor update | [Month YYYY] | [material change]
Hi everyone,
This month, [most important outcome]. It matters because [effect].
Our biggest unresolved issue is [specific issue]. Next we will [action].
LAST MONTH'S COMMITMENTS
- [Promise]: [met / missed / changed]. Actual: [evidence].
Next action: [owner and date].
NUMBERS
- [Metric]: [current] vs [prior], for [comparable periods].
Definition: [link or short description]. Driver: [supported explanation].
- Cash: [amount and as-of date, from reconciled records].
- [Other operating measure appropriate to your stage].
Definition changes or missing inputs: [explain, or none].
WHAT DID NOT WORK
We expected [target]; actual was [result]. The consequence is [impact].
Evidence suggests [assessment]; we still do not know [uncertainty].
[Owner] is [action or test] by [date].
WHAT CHANGED OUR THINKING
Because of [evidence], we are [changing / stopping / continuing] [decision].
HELP NEEDED
To unblock [specific response above], we need [expertise or introduction]
by [date]. We have already tried [action].
The easiest next step is [action]; here is [shareable context/link].
Last month's ask: [resolved / still open / withdrawn], [outcome].
NEXT COMMITMENTS
- [Owner] will [observable result] by [date].
- [Owner] will [observable result] by [date].
Thanks,
[Founder]
These are established practices: Yonder’s investor-authored template covers candid lows, specific requests and prior-update continuity; Visible’s guide emphasizes consistency. The downloadable kit turns them into working records for commitments, metric definitions, asks and unresolved setbacks.
A worked example: the miss belongs near the top
Imagine a fictional company building onboarding software. In August, it committed to launching three pilots during September. Two launched; the third is waiting on an integration. These are invented teaching details, not Cerrito results.
The vague version reads:
A strong month for customer momentum. We made progress on pilots and expanded our integration capabilities.
That gives the reader no way to check the previous promise. A more useful version reads:
Two of the three planned pilots launched. The third is blocked on its data import. Maya owns a test import by October 8; we will confirm a revised launch date after that test. We have isolated the failure in a synthetic sample. Can you introduce one engineer experienced with [source system] imports who could review that sample before October 8?
The second version supplies a result, a miss, a dependency and a place to help. It does not guarantee a launch date the team cannot yet support.
Keep the underlying commitment in a table:
| Promised | Actual | Status | Next check |
|---|---|---|---|
| Launch three pilots in September | Two launched; one blocked on import | Missed | Maya: test import by October 8 |
Changing a plan may be the right decision. Silently deleting the old plan prevents readers from understanding that decision.
The number went up. Did the definition change?
Consider another fictional update: “Active teams increased from 80 to 120.” That appears to be 50% growth.
Now reveal the definitions. Last month counted teams completing the core workflow. This month counted any team that logged in.
The arithmetic is correct. The comparison is not.
Before reporting a trend, either recalculate both periods under one definition or label the values non-comparable. If the older data cannot support a recalculation, say so. Do not manufacture a clean history.
| Working field | What to record |
|---|---|
| Metric | The exact name used in the email |
| Definition | Qualifying event; numerator and denominator where relevant |
| Period | Start/end dates and timezone |
| Source | System or report that produced the value |
| Exclusions | Test accounts, duplicates or other excluded records |
| Change log | What changed, when and whether older periods were restated |
Keep this record with the person preparing the numbers. The email needs the material change and its implication, not every implementation detail.
Before revenue: report evidence of progress
Pick measures that answer your current operating question. For a pilot-stage product, that could be pilots started, pilots completed and teams repeating a defined core action. Interviews, signups and paid customers are different categories; preserve those distinctions. The paid pilot directory uses the same split: a paid test, a conversation, and a rollout are not one event. When the update is doing the work of a fundraise, the pitch-deck examples show which claims need a receipt. Program applications that ask for this kind of progress are listed in the accelerator directory.
For a technical milestone, state the acceptance condition and whether it passed. “Completed five tests” is activity. “Passed the agreed latency threshold on four of five test cases; the largest case remains unresolved” makes the remaining work visible.
After revenue: keep unlike numbers apart
Use definitions consistent with your business records. Separate recurring revenue, one-time receipts and pipeline. Explain changes in customer counts or retention cohorts instead of presenting whichever version looks best that month.
This template does not prescribe accounting treatment. Financial figures should come from the company’s reviewed records. If you include a runway estimate, identify its assumptions and date rather than treating it as a fixed deadline.
Give each request an ending
“We need help with sales” is hard to act on. A request for an introduction to a specific buyer profile, with relevant context and a forwardable explanation, gives the reader a next step.
The next update should also tell them what happened.
| Request | Founder owner | Needed by | Status | Outcome |
|---|---|---|---|---|
| [Specific expertise or introduction] | [Name] | [Date] | [Open / answered / withdrawn] | [Result or next step] |
Keep private contact details outside a broadly circulated update. Confirm what may be forwarded, and thank helpers for the actual contribution rather than implying an introduction produced a result that has not happened.
A short review before sending
Read last month’s update beside this one. Every earlier commitment should have an outcome or an explanation. Every comparison should use compatible periods and definitions. Every request should be clear enough for a recipient to act without a second briefing.
If AI helps draft the email, supply the prior update and source records. Require placeholders for missing evidence. Check the output against those records; fluent language is not verification.
An update can be brief without concealing uncertainty. “Not measured yet” is more useful than a number nobody can reproduce.
The other kind of investor update
Clara Gold’s “Investors update” is a WhatsApp exchange: GiGi ranked above Tinder, a ladder emoji in reply, then “Coming to your country babyyyy,” “Let’s make America date again,” and a reaction GIF. No formal memo—just a milestone and some very informal excitement.
Read Clara Gold’s humorous investor update post
Verdict
Report the miss while it is still useful to know. Explain what you think happened, what you do not know, and what the team is doing. Then ask for the smallest specific contribution that could change the next decision.
Use the copyable email and maintain the working tables privately. In the next update, close the loop on both the problem and the help you received.
The point is not to make the business look different every month. It is to make the actual changes understandable.
Sources and method
Reviewed October 2, 2026: Yonder’s investor-authored template and Visible’s investor reporting guide. Both cover established reporting practices; Visible also sells reporting software. We do not use its fundraising association as causal evidence.
The Coverflex Q2 2025 update was read directly through its public Notion page; the founder’s accompanying LinkedIn post provides audience context. Cap’s May 2024 PDF was read directly. These are company-reported historical examples, not independently audited outcomes. Jessica Lynch’s September 8, 2026 essay is an attributed investor perspective.
The template, tables and explicitly hypothetical rewrites are original Cerrito synthesis. No investor response study or fundraising experiment was conducted. Adapt the format to existing reporting commitments and the information appropriate for its recipients.
The three X posts are embedded from their original authors: Trace Cohen (September 23, 2026), Shruti Gandhi (August 12, 2026) and Clara Gold (July 22, 2024). Their views and humor illustrate the discussion; they are not research findings. Source links remain available if embeds do not load.
