Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@opsdesk

Board update drafter

@opsdesk/board-update-drafter

Draft a monthly investor update or quarterly board memo from your numbers and notes: headline, metrics against plan and last period, highlights, lowlights told straight, and specific asks. Never invents a number.

SkillFinancev1.0.0 (latest)
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1---
  2. 2name: board-update-drafter
  3. 3description: Draft a monthly investor update email or a quarterly board memo from the user's own numbers and notes, with metrics against plan, honest lowlights, and specific asks. Use when a founder or COO says "write the investor update", "draft the board memo", "turn these numbers into our monthly update", or "help me tell the board about this miss".
  4. 4license: MIT
  5. 5---
  6. 6
  7. 7# Board and investor update drafter
  8. 8
  9. 9Investors and board members read many updates. The good ones lead with the truth in one line, show the same metrics every time against plan, tell bad news early and plainly, and end with asks a reader can act on in five minutes. This kit drafts that from the user's numbers. It never makes numbers up.
  10. 10
  11. 11## Inputs
  12. 12
  13. 13Ask for what is missing, in one message:
  14. 14
  15. 151. **Audience and format:** monthly investor email (short, about 400 words) or quarterly board memo (longer, sent before the meeting as a pre-read).
  16. 162. **Numbers** for this period, last period, and plan. Default set for a SaaS company: ARR or MRR, net new ARR, gross and net revenue retention, net burn, cash, runway in months, headcount. Use whatever the company already reports; keep the same set every time.
  17. 173. **What happened:** wins, misses, launches, hires and departures (by role), customer news.
  18. 184. **Asks:** intros, hires, advice, decisions the board must make.
  19. 195. **Last update**, if one exists in `board/`. Read it so metrics and promises carry over.
  20. 20
  21. 21Save the inputs to `board/<yyyy-mm>/inputs.md` (see `examples/inputs-2026-10.md`).
  22. 22
  23. 23## Steps
  24. 24
  25. 251. **Check the numbers.** Compute change vs last period and vs plan. Runway = cash / average net burn of the last 3 months, rounded down. Show your math in a short note under the draft. If a number is missing, write `[TK: net burn]` and list it; never estimate it.
  26. 262. **Follow up on last time.** Anything the last update promised ("we will close X", "hiring a VP Sales") gets a one-line status, even if the news is bad.
  27. 273. **Write the headline:** one or two sentences a reader could repeat. Lead with the most important truth, good or bad. "ARR $2.41M, up 5% but 2% under plan; two enterprise deals slipped to Q1, and SSO shipped to unblock them."
  28. 284. **Highlights:** at most four, each with a number or a concrete outcome.
  29. 295. **Lowlights:** at most four, each with what happened, why, and what you are doing about it. Do not bury them below the asks or soften them into "learnings".
  30. 306. **Asks:** specific and easy to act on. "Intros to security leaders at mid-size fintech companies" beats "customer intros".
  31. 317. **For a board memo**, add: decisions needed at the meeting (with the recommendation), a plan vs actual table for the quarter, and the next quarter's three priorities.
  32. 328. **Write the draft** to `board/<yyyy-mm>/update.md`, show it, and list every `[TK]` and anything you were unsure about.
  33. 33
  34. 34## Output format (monthly email)
  35. 35
  36. 36```markdown
  37. 37Subject: <Company> update, October 2026: <headline in a few words>
  38. 38
  39. 39**Headline:** <one or two sentences>
  40. 40
  41. 41| Metric | Oct | Sep | Plan | vs plan |
  42. 42| ------ | --- | --- | ---- | ------- |
  43. 43| ARR | $2.41M | $2.30M | $2.45M | -2% |
  44. 44| Net burn | $310k | $295k | $320k | -3% |
  45. 45| Runway | 20 months | | | |
  46. 46
  47. 47**Highlights**
  48. 48- ...
  49. 49
  50. 50**Lowlights**
  51. 51- ...
  52. 52
  53. 53**Last month we said:** <promise>: <status>
  54. 54
  55. 55**Asks**
  56. 561. ...
  57. 57
  58. 58Thanks, <name>
  59. 59```
  60. 60
  61. 61## Guardrails
  62. 62
  63. 63- Never invent, round in your favor, or change the definition of a metric. If the user wants to change a definition, say so in the update.
  64. 64- Board and investor numbers are confidential. Keep files in `board/`; never paste them anywhere else. The user sends the update themselves.
  65. 65- Mention people by role, not name, for departures or performance. Keep anything that may need legal review (litigation, layoffs, fundraising terms) as a `[CHECK WITH COUNSEL]` note for the user.
  66. 66- This is a writing aid, not legal, accounting, or investment advice.
Sign in to comment on a line