Generates structured, narrative-driven board and investor update decks by synthesizing C-suite perspectives into a standardized 11-section format. It ensures each section follows a Headline-Data-Narrative-Ask framework and provides specific guidance on delivering bad news and avoiding common presentation errors.
Say it in your own words; the assistant finds this recipe by itself. Examples:
Use this skill when preparing for quarterly board meetings, investor updates, or fundraising narratives that require a comprehensive overview of company performance. It is ideal for structuring complex financial and operational data into a coherent story that highlights key metrics, risks, and strategic asks. It is particularly useful when the user needs to frame difficult news or align multiple departmental updates into a single executive narrative.
Build board decks that tell a story — not just show data. Every section has an owner, a narrative, and a "so what."
board deck, investor update, board meeting, board pack, investor relations, quarterly review, board presentation, fundraising deck, investor deck, board narrative, QBR, quarterly business review
Ask for a board deck in natural language, naming cadence and stage:
"Build a quarterly board deck — we're Series A." "Draft a fundraising board deck for a seed-stage company."
Provide available metrics. The builder fills gaps with explicit placeholders — never invents numbers.
Every section follows: Headline → Data → Narrative → Ask/Next
3 sentences. No more. - Sentence 1: State of the business (where we are) - Sentence 2: Biggest thing that happened this period - Sentence 3: Where we're going next quarter
Bad: "We had a good quarter with lots of progress across all areas." Good: "We closed Q3 at $2.4M ARR (+22% QoQ), signed our largest enterprise contract, and enter Q4 with 14-month runway. The strategic shift to mid-market is working — ACV up 40% and sales cycle down 3 weeks. Q4 priority: close the $3M Series A and hit $2.8M ARR."
6-8 metrics max. Use a table.
| Metric | This Period | Last Period | Target | Status |
|---|---|---|---|---|
| ARR | $2.4M | $1.97M | $2.3M | ✅ |
| MoM growth | 8.1% | 7.2% | 7.5% | ✅ |
| Burn multiple | 1.8x | 2.1x | <2x | ✅ |
| NRR | 112% | 108% | >110% | ✅ |
| CAC payback | 11 months | 14 months | <12 months | ✅ |
| Headcount | 24 | 21 | 25 | 🟡 |
Pick metrics the board actually tracks. Swap out anything they've said they don't care about.
One sentence on each variance. Boards hate "revenue was below target" with no explanation. Say why.
The forecast must have a confidence level. "We expect $2.8M" is weak. "High confidence $2.6M, upside to $2.9M if two late-stage deals close" is useful.
No feature lists. Only features with evidence of user impact.
Keep this short unless there's a material issue. Boards don't need sprint details.
The "asks" slide is the most important. Be specific. "We'd like 3 warm introductions to CFOs at Series B companies" beats "any help would be appreciated."
Boards see 10+ decks per quarter. Yours needs a through-line.
The 4-Act Structure: 1. Where we said we'd be (last quarter's targets) 2. Where we actually are (honest assessment) 3. Why the gap exists (one cause per variance, not excuses) 4. What we're doing about it (specific, dated actions)
This works for good news AND bad news. It's credible because it acknowledges reality.
Opening frame: Start with the one thing that matters most — the board should know the key message by slide 3, not slide 30.
Never bury it. Boards find out eventually. Finding out late makes it worse.
Framework: 1. State it plainly — "We missed Q3 ARR target by $300K (12% gap)" 2. Own the cause — "Primary driver was longer-than-expected sales cycle in enterprise segment" 3. Show you understand it — "We analyzed 8 lost/stalled deals; the pattern is X" 4. Present the fix — "We've made 3 changes: [specific, dated changes]" 5. Update the forecast — "Revised Q4 target is $2.6M; here's the bottom-up build"
What NOT to do: - Don't lead with good news to soften bad news — boards notice and distrust the framing - Don't explain without owning — "market conditions" is not a cause, it's a context - Don't present a fix without data behind it - Don't show a revised forecast without showing your assumptions
| Mistake | Fix |
|---|---|
| Too many slides (>25) | Cut ruthlessly — if you can't explain it in the room, the slide is wrong |
| Metrics without targets | Every metric needs a target and a status |
| No narrative | Data without story forces boards to draw their own conclusions |
| Burying bad news | Lead with it, own it, fix it |
| Vague asks | Specific, actionable, person-assigned asks only |
| No variance explanation | Every gap from target needs one-sentence cause |
| Stale appendix | Appendix is only useful if it's current |
| Designing for the reader, not the room | Decks are presented — they must work spoken aloud |
Quarterly (standard): Full deck, all sections, 20-30 slides. Sent 48 hours in advance.
Monthly (for early-stage): Condensed — metrics dashboard, financials, pipeline, top risks. 8-12 slides.
Fundraising: Opens with market/vision, closes with ask. See references/deck-frameworks.md for Sequoia format.
references/deck-frameworks.md — SaaS board pack format, Sequoia structure, investor tailoringtemplates/board-deck-template.md — fill-in template for complete board decksLICENSESKILL.mdreferences/deck-frameworks.mdtemplates/board-deck-template.mdVendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path c-level-advisor/skills/board-deck-builder, licence MIT. The upstream licence file ships inside the skill.