Draft your investor update from real numbers

Seed/A CEO with 20-60 investors, no chief of staff · Assemble in ~10 min; full draft produced in one session (~20 min of back-and-forth).

Founder opsEdit flowon X◆ new (unverified) 90

step 1connector

Gather raw inputs

⚡ bring your own tool

step 2ready

Compute metrics table with MoM deltas

financial-model4 alts

step 3ready

Extract highlights, lowlights, and asks

standup2 alts

step 4ready

Draft the full investor update

investor-update10 alts

step 5partial

Wrap in a send-ready email

investor-outreach10 alts

step 6ready

Generate an attachable metrics report

finance-report3 alts

Did this recipe work for you?

What you get

▸Send-ready investor update email (subject line, opener, Metrics / Highlights / Lowlights / Asks sections)
▸Formatted metrics table with MoM deltas (exact figures, ±0.1% accuracy)
▸Narrative bullets: highlights, lowlights, ≥1 concrete ask
▸Self-contained HTML metrics report suitable as an email attachment

tools: No paid tools required — metrics source is whatever the founder already uses (Sheets, Notion, CSV)

tokens: ~$0.50-1.50 per monthly session (one batch, 6 steps, moderate context)

≈ Under $2/mo at one update per month

What stays yours

· Review the draft for tone and accuracy before sending — numbers must be spot-checked against the source data by the founder
· Personalize or approve the email opener for the full investor list (the skill targets individual outreach; list send needs a human call on warmth vs. uniformity)
· Decide what to omit — lowlights and asks involve strategic judgment about what to surface to investors; no agent should make that call autonomously

The problem

When I need to send my monthly investor update, I want one session that pulls my raw metrics and notes, computes MoM deltas, structures highlights/lowlights/asks, and drafts a send-ready email — so I stop losing two hours per month writing from a blank page.

Cybernetic layers

Memorybyo

No harvested memory artifact fits. The founder supplies last month's update as a file — that IS the continuity anchor. A local file (e.g. updates/YYYY-MM.md) naming convention is sufficient; no CRM needed.

Background-schedulingpartial

The update is monthly and batch-shaped — a one-shot session, not a loop. A calendar reminder or Claude Code cron to open the session on the 1st of each month is possible but overkill for most founders. No harvested scheduling artifact is needed.

Harnessready

Claude Code is the runtime. Install skills 317, 428, 245, 86, and 67 into ~/.claude/skills/ and invoke by name. Cowork also works for a shared-session flow with a chief of staff.

Click any step to see what fills it — and the ranked alternatives you can swap in.