Board Update Narrative

Investors expect problems. What erodes trust is silence, or worse, finding out about a bad month from someone else. This skill enforces the structure that produces trust through transparency — a TL;DR that names the headline (good or bad) in the first four bullets, a metrics table that stays consistent month after month, and a Struggles section that names at least one real challenge. Adding and removing metrics looks like hiding, and the skill won't let you do it.

The framework runs in five parts every time: Topline, Results, Updates, Struggles, Targeted Asks. Same shape, same order, every month. Investors learn where to look for what they care about, and consistency is the single thing they value most after honesty. Bad news goes near the top with a one-paragraph diagnosis and what you're doing about it — buried bad news compounds in cost the longer it stays buried.

The Targeted Asks section is where most updates fail and where most ROI from the investor relationship actually lives. "Any intros would be appreciated" is not an ask. "Looking for senior backend engineers, Go and Postgres, who've been at a Series A SaaS company in London or remote-UK" is. The skill drafts asks specific enough that an investor can act on them inside a single email reply — because that's the difference between an update that produces help and one that produces a polite read.

Length is under 500 words. Activities get replaced with outcomes — "we launched three features" becomes "we launched three features and activation went 34% to 51%." If the founder says nothing is keeping them up at night, the skill pushes back, because every startup has problems and pretending otherwise is the fastest way to lose investor confidence. A good 500-word update every month beats a perfect 1,500-word update every quarter.