Skip to content

borghei/Claude-Skills / personal-productivity/investor-update-generator

investor-update-generator

Verified

Validate a monthly investor update against a rubric of strong-update sections (transparency, decision-relevance, specific asks). Use before sending a monthly investor update or setting a fundraise communication cadence.

references/what_makes_good_updates.md

View on GitHub
# What Makes Good Investor Updates

Investors read dozens of monthly updates a month. The ones that produce help, raise reputation, and keep the cap table aligned share patterns; the ones that don't share a different set.

---

## What Good Updates Have

### Highlights AND lowlights
- 3-5 wins specific enough to be falsifiable ("closed Acme at $80k ARR" — not "great enterprise momentum")
- 2-4 lowlights — what missed, what's at risk, what's slow
- Ratio: roughly 2:1 highlights:lowlights. All-positive is a red flag.

### Hard numbers
- MRR / ARR (or revenue, or whatever your topline is)
- Growth rate (MoM or QoQ)
- Cash / runway in months
- One key product metric (DAU, weekly active, or activation rate)
- Hiring number (open / hired / lost)

### Context, not just numbers
- Why did the metric move?
- What's the next milestone you're targeting?
- What's the bet you're making?

### Specific asks
- Bad: "let us know if you can help"
- Good: "Intros to (a) VPs of Engineering at SaaS companies 100-1000 employees in NA who're hiring senior backend, (b) finance leaders we should learn from on planning, (c) anyone with regulatory experience in [your sector]"

The specificity test: could the investor act on this without further clarification?

### Forward-looking
- What's in next month?
- What gates the next 3 months?
- What decisions are coming up?

---

## What Bad Updates Have

### All-positive momentum
Updates that never have a lowlight tell investors that either (a) you're not paying attention to risks, or (b) you're managing them away from the update. Both are bad.

### Vague metrics
"Strong growth" without a number, "promising pipeline" without dollars. Investors discount what they can't quantify.

### Generic asks
"Let us know how you can help" produces no help. Specificity unlocks value.

### Inconsistent reporting
Defining MRR one way in March and another way in April erodes trust. Pick definitions; stick to them.

### Long format
2000+ word updates are skim-rate-dropping. Most investors are 5-10 minutes per read; format for that budget.

### No cadence
Quarterly updates from a Series A company are too sparse. Skipping months without explanation produces silence anxiety.

---

## Cadence

- **Pre-seed / Seed:** monthly is standard. Some weekly during a sprint.
- **Series A:** monthly for first 2 years; can move to bi-monthly once stable.
- **Later stage:** quarterly fine; supplement with significant-event updates.

---

## Distribution

**Investors only:** safer for sensitive data; minimum surface area.
**Investors + advisors:** often appropriate; advisors can act on asks.
**Extended network (helpful operators):** broader help potential; risk of leakage.

Pick a list size you can sustain. 50 names is plenty for a Series A.

---

## Format

**Email > Word doc > PDF**
- Email is read; PDFs are downloaded and forgotten.
- Use Bcc for distribution if you don't want recipients seeing each other.
- Some founders use Foundersuite, Airbase, Visible.vc, etc. — fine if it gets sent; counterproductive if the tool becomes a barrier to writing.

**Length:** target 600-800 words; 1000 if a particularly eventful month.

---

## Sensitive Information

Some founders share more, some less:
- **Always share:** topline metrics, runway, key risks, asks
- **Often share:** detailed pipeline, competitive moves, churn analysis
- **Sometimes share:** exact ARR (some prefer % growth instead), specific customer names
- **Rarely share:** salary specifics, legal-sensitive context, trade secrets

The bar: would you be comfortable if this leaked? If not, leave it out or share verbally.

---

## Recovery from Bad News

When the bad news is significant (large customer loss, key departure, missed targets, security incident):

1. Send the update **early** — same day or next day, not in the next monthly
2. Lead with the news — don't bury
3. Be specific about: what happened, impact, response, next steps
4. Be honest about what you don't yet know
5. Schedule individual calls with major investors if severity warrants

The biggest mistake: investors learn about the bad thing from someone else first.

---

## Common Mistakes

1. **Skipping months.** Once the cadence breaks, it's hard to restart.
2. **Update as PR.** Updates aren't pitches. The audience is already in.
3. **Burying the lede.** Whatever's most important — say it first.
4. **No metrics in writing.** Verbal updates don't substitute for written.
5. **Wall of text.** Use sections, bullets, bold for scan-ability.
6. **Different definitions monthly.** "MRR includes / excludes annual contracts" needs to stay constant.
7. **Asks at the end.** Asks should be early enough that they survive skim-reads.

---

## Quick Self-Test

Before sending, ask:

- [ ] Could a non-customer recognize the wins as wins (not vague claims)?
- [ ] Did I include at least 2 lowlights / risks?
- [ ] Are runway and topline visible in the first screen?
- [ ] Are my asks specific enough that an investor could act on them today?
- [ ] Is the update under 1000 words?
- [ ] Did I send it within 5 business days of month-end?

If yes to all, send. If not, fix and re-check.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall