Write investor updates that build confidence and surface help — monthly format, board deck structure, fundraising narrative, and metrics dashboards. Use when writing investor updates, preparing board meetings, or communicating with stakeholders. Triggers on: "investor update", "board deck", "monthly update", "investor communication", "fundraising update", or any stakeholder reporting.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Write investor updates that build confidence and surface help — monthly format, board deck structure, fundraising narrative, and metrics dashboards. Use when writing investor updates, preparing board meetings, or communicating with stakeholders. Triggers on: "investor update", "board deck", "monthly update", "investor communication", "fundraising update", or any stakeholder reporting.
license
MIT
compatibility
Claude Code, Jesse, Codex, Hermes, Windsurf, OpenCode, Gemini CLI, Copilot, Zed, VS Code, Goose
Investor updates are the most underleveraged asset in a founder's toolkit.
A great update builds confidence, surfaces problems early when investors can
help, and makes fundraising conversations natural rather than desperate.
A bad update — or no update — signals that things aren't going well, even
when they are.
Send monthly. Every month. Even when (especially when) things are hard.
Jason Lemkin (SaaStr) — Board metrics: growth, burn multiple, NRR
David Skok — VC dashboard metrics (LTV:CAC, payback)
When to Use
"Write my monthly investor update"
"Create a board deck"
"Prepare for a board meeting"
"Structure an investor communication"
"What should I include in investor updates?"
"Build a fundraising narrative"
"Investor update during crisis / outage / breach"
"Board comms after bad press"
Step-by-Step Process
Phase 1: Monthly Update Structure
Every update follows this structure. Every month. Consistency builds trust.
1. Headline / TL;DR (1-2 sentences)
"Revenue grew 12% MoM to $X MRR. Churn dropped to 1.2%. Hired first AE."
2. Key Metrics
Use saas-metrics-calculator/references/metric-definitions-exit-weight.md for
formulas. Minimum investor set: MRR/ARR, NRR, GRR, logo churn, CAC payback,
magic number, burn multiple, runway.
MRR / ARR (with growth rate)
Customer count (new, churned, net new)
Churn rate (logo + revenue)
Cash / runway (months remaining)
Burn rate (monthly)
3. Wins (what went right)
3-5 bullet points. Specific, named achievements. "Closed Acme Corp ($24K ACV)"
not "made good progress on enterprise deals."
4. Challenges (what's hard)
2-3 bullet points. Be honest. "Churn spiked to 3% this month. Investigating
root cause — initial data points to onboarding gaps. Hired a CS lead to fix."
5. Asks (specific things investors can help with)
"Introduction to VP Sales at [Company A, B, C]." "Candidate referrals for
senior frontend role." "Advice on pricing model for enterprise tier."
6. Team updates
Hires, departures, open roles. Investors track team velocity.
7. Cash and runway
Current cash, monthly burn, months of runway. Always include this.
Phase 2: Writing Principles
Honesty over optimism. Investors can't help with problems they don't
know about. Bad news delivered early builds trust. Bad news hidden destroys it.
Specific over vague. "Grew 12%" beats "good growth this month."
Asks are gifts. Investors want to help. Give them specific things to do.
"Introduction to [specific person]" beats "help with hiring."
One page. Nobody reads 5-page updates. One page, clear metrics, specific
asks. If they want more detail, they'll ask.
Phase 3: Board Deck (quarterly)
For formal board meetings, expand the update:
Strategy review (are we on track?)
Financial performance (vs plan, vs prior quarter)
Product roadmap (what shipped, what's next)
GTM review (pipeline, conversion, CAC, payback)
Team update (org chart, gaps, hiring plan)
Key decisions needed (board vote items)
Risks and mitigation
Phase 4: Crisis & Incident Investor Comms
Lemkin rule: Send updates more reliably in bad months — never skip because of embarrassment. Source: Handling Bad News
Sev 3+ addendum (same day as customer holding statement, after counsel if breach):
What happened — facts only; no legal admissions without counsel
When actively fundraising, the update becomes evidence for your pitch:
The narrative arc: "Here's where we were → here's what we did → here's
the result → here's what we'll do next → here's what we need to do it."
Investors who receive consistent monthly updates are 3-5x more likely to
invest in your next round. They've watched your trajectory. They trust
your reporting. The pitch is just the latest chapter in a story they've
been reading for 12+ months.
Output Format
Monthly update template, board deck structure, and fundraising narrative
framework.
Quality Check
Headline communicates the most important thing this month
All key metrics present (MRR, churn, customers, cash, runway)
Wins are specific and quantified
Challenges are honest (not sugar-coated)
Asks are specific and actionable
Update fits on one page (or one screen)
Sent on time (first week of the month)
Common Pitfalls
Hiding problems. Investors find out anyway. Problems you communicate
early are opportunities for help. Problems you hide are trust-breakers.
No asks. Investors want to feel useful. If you never ask for anything,
they stop reading. Specific asks drive engagement.
Sending only when things are good. The months you don't want to send
an update are the months you most need to. Silence signals trouble.
Dense walls of text. Nobody reads 5-page updates. One page. Metrics
first. Narrative second. Bullet points, not paragraphs.
Inconsistent format. Different structure every month means investors
can't find what they're looking for. Same format, every month, forever.
Execution Artifacts
references/framework-notes.md — Named frameworks and reference tables
templates/output-template.md — Deliverable shell for agent output
