investor-update
The investor-update skill generates a structured monthly or quarterly investor update formatted for early-stage and growth investors. Use it when preparing progress reports for your board, investor newsletter, or funding communications. The skill produces a complete update including metrics tables, highlights, challenges, priorities, and specific asks, following a format designed to build credibility through clear storytelling and honest problem disclosure.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/investor-update && cp -r /tmp/investor-update/plugins/pm-business/skills/investor-update ~/.claude/skills/investor-updateSKILL.md
# Investor Update Skill
This skill writes a complete investor update — structured for clarity, honest about challenges, and specific about asks. Output follows the format preferred by most early-stage and growth investors.
## Required Inputs
Ask the user for these if not provided:
- **Company name and stage** (Seed / Series A / Series B / etc.)
- **Period covered** (month or quarter)
- **Key metrics this period** (revenue, MRR, users, churn, burn, runway — whatever's relevant)
- **Biggest wins**
- **Biggest challenges or misses**
- **Specific asks from investors** (intros, advice, talent, partnerships)
- **What's coming next period**
- **Tone** (formal / conversational — most investors prefer conversational)
## Output Structure
---
**[Company Name] — [Month/Quarter] Update**
*[Date]*
---
Hi [Investor names or "all"],
[One or two sentence opener — a specific highlight or honest framing of the period. Don't open with "Hope you're well." Open with the most important thing that happened.]
---
## The Numbers
| Metric | This Period | Last Period | Change |
|---|---|---|---|
| [MRR / ARR] | [Value] | [Value] | [+/- %] |
| [Active users / customers] | | | |
| [Churn rate] | | | |
| [Burn rate] | | | |
| [Runway] | | | |
| [Other key metric] | | | |
[1–2 sentences of narrative on the numbers — what's the story behind the movement? Don't just repeat the table.]
---
## Highlights
**[Highlight 1 — 4–6 word title]**
[2–4 sentences. What happened. Why it matters. Be specific — name the customer, the number, the milestone.]
**[Highlight 2]**
[2–4 sentences]
**[Highlight 3 — optional]**
---
## Challenges
[This section is what separates trustworthy updates from self-promotional ones. Investors know you have challenges. Being direct builds trust.]
**[Challenge 1]**
[2–4 sentences. What the problem is. What you've tried. What you're doing about it. Don't spin — investors see through it.]
**[Challenge 2 — if applicable]**
---
## Focus for Next [Month/Quarter]
[3–5 bullet points. What you're concentrating on next period and why. Keep it tight — not an exhaustive roadmap.]
- [Priority 1]
- [Priority 2]
- [Priority 3]
---
## Asks
[Be specific. "Let me know if you can help" is not an ask. These should be actionable items an investor can act on immediately.]
1. **[Ask type: e.g. Intro]** — [Specific request. e.g. "Looking for an intro to procurement leads at mid-market SaaS companies. Happy to share a warm intro note."]
2. **[Ask type: e.g. Advice]** — [Specific question you want input on]
3. **[Ask type: e.g. Talent]** — [Specific hire you're looking for — title, key requirements]
---
[Closing line — 1 sentence. Forward-looking or a genuine thanks. Not "as always, let me know if you have questions."]
[Signature]
[Name]
[Company]
[One way to reply — email / Calendly / reply to this thread]
---
## Writing Rules
- Updates should take an investor 3–4 minutes to read. If it's longer, trim it.
- Never lead with process ("This month we focused on...") — lead with outcomes
- Challenges section must be honest. A missing challenges section signals the founder isn't self-aware or isn't being transparent.
- Metrics table must include comparison to last period — a number without context is meaningless
- Asks must be specific enough that an investor knows within 5 seconds if they can help
- No jargon or buzzwords ("synergies," "crushing it," "hockey stick") — plain language only
## Quality Checks
- [ ] Opens with a specific highlight or honest framing (not a pleasantry)
- [ ] Numbers include period-over-period comparison
- [ ] Challenges section is present and honest
- [ ] Asks are specific and actionable
- [ ] Total length is skimmable in 3–4 minutes
- [ ] No spin or buzzwords
## Anti-Patterns
- [ ] Do not omit challenges or bad news — sanitised updates erode investor trust faster than bad results do
- [ ] Do not bury the lead — use BLUF structure and put the most important news in the first paragraph
- [ ] Do not send an update without a clear "Ask" section — investors who want to help need to know how
- [ ] Do not use buzzwords or spin — investors see hundreds of updates and will see through vague positive language
- [ ] Do not report metrics without a comparison baseline — numbers without context (vs. last period or target) are meaningless
## Example Trigger Phrases
- "Write an investor update for [month/quarter]"
- "Draft a monthly update for our investors based on these notes: [paste notes]"
- "Help me write a board update for Q[N]"
- "Write our Series A investor newsletter"Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.