New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Assembles comprehensive board and investor update decks

Board deck builder

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

Board deck builder cover

Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives.

---
name: "board-deck-builder"
description: "Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes."
license: MIT
metadata:
  version: 1.0.0
  author: Alireza Rezvani
  category: c-level
  domain: board-governance
  updated: 2026-03-05
  frameworks: deck-frameworks, board-deck-template
---

# Board Deck Builder

Build board decks that tell a story — not just show data. Every section has an owner, a narrative, and a "so what."

## Keywords

Overview

Build board decks that tell a story — not just show data. Every section has an owner, a narrative, and a "so what."

Manual install (npx, ZIP)
Claude Codenpx skills add alirezarezvani/claude-skills --skill board-deck-builder -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \ | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/c-level-advisor/skills/board-deck-builder
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/2613d2194dad91e3fe40/board-deck-builder.zip" -OutFile "$env:TEMP\board-deck-builder.zip"; Expand-Archive "$env:TEMP\board-deck-builder.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md7.4 KB
  • references/1 file · 6.8 KB
  • templates/1 file · 5.7 KB
Read the files here
alirezarezvani/19392f73 files
SKILL.md
Show the full text185 lines

Board Deck Builder

Build board decks that tell a story — not just show data. Every section has an owner, a narrative, and a "so what."

Keywords

board deck, investor update, board meeting, board pack, investor relations, quarterly review, board presentation, fundraising deck, investor deck, board narrative, QBR, quarterly business review

Quick Start

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.

Deck Structure (Standard Order)

Every section follows: Headline → Data → Narrative → Ask/Next

1. Executive Summary (CEO)

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."

2. Key Metrics Dashboard (COO)

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.

3. Financial Update (CFO)
  • P&L summary: Revenue, COGS, Gross margin, OpEx, Net burn
  • Cash position and runway (months)
  • Burn multiple trend (3-quarter view)
  • Variance to plan (what was different and why)
  • Forecast update for next quarter

One sentence on each variance. Boards hate "revenue was below target" with no explanation. Say why.

4. Revenue & Pipeline (CRO)
  • ARR waterfall: starting → new → expansion → churn → ending
  • NRR and logo churn rates
  • Pipeline by stage (in $, not just count)
  • Forecast: next quarter with confidence level
  • Top 3 deals: name/amount/close date/risk

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.

5. Product Update (CPO)
  • Shipped this quarter: 3-5 bullets, user impact for each
  • Shipping next quarter: 3-5 bullets with target dates
  • PMF signal: NPS trend, DAU/MAU ratio, feature adoption
  • One key learning from customer research

No feature lists. Only features with evidence of user impact.

6. Growth & Marketing (CMO)
  • CAC by channel (table)
  • Pipeline contribution by channel ($)
  • Brand/awareness metrics relevant to stage (traffic, share of voice)
  • What's working, what's being cut, what's being tested
7. Engineering & Technical (CTO)
  • Delivery velocity trend (last 4 quarters)
  • Tech debt ratio and plan
  • Infrastructure: uptime, incidents, cost trend
  • Security posture (one line, flag anything pending)

Keep this short unless there's a material issue. Boards don't need sprint details.

8. Team & People (CHRO)
  • Headcount: actual vs plan
  • Hiring: offers out, pipeline, time-to-fill trend
  • Attrition: regrettable vs non-regrettable
  • Engagement: last survey score, trend
  • Key hires this quarter, key open roles
9. Risk & Security (CISO)
  • Security posture: status of critical controls
  • Compliance: certifications in progress, deadlines
  • Incidents this quarter (if any): impact, resolution, prevention
  • Top 3 risks and mitigation status
10. Strategic Outlook (CEO)
  • Next quarter priorities: 3-5 items, ranked
  • Key decisions needed from the board
  • Asks: budget, introductions, advice, votes

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."

11. Appendix
  • Detailed financial model
  • Full pipeline data
  • Cohort retention charts
  • Customer case studies
  • Detailed headcount breakdown

Narrative Framework

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.


Delivering Bad News

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

Common Board Deck Mistakes

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

Cadence Notes

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

  • references/deck-frameworks.md — SaaS board pack format, Sequoia structure, investor tailoring
  • templates/board-deck-template.md — fill-in template for complete board decks
1---
2name: "board-deck-builder"
3description: "Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes."
4license: MIT
5metadata:
6 version: 1.0.0
7 author: Alireza Rezvani
8 category: c-level
9 domain: board-governance
10 updated: 2026-03-05
11 frameworks: deck-frameworks, board-deck-template
12---
13 
14# Board Deck Builder
15 
16Build board decks that tell a story — not just show data. Every section has an owner, a narrative, and a "so what."
17 
18## Keywords
19board deck, investor update, board meeting, board pack, investor relations, quarterly review, board presentation, fundraising deck, investor deck, board narrative, QBR, quarterly business review
20 
21## Quick Start
22 
23Ask for a board deck in natural language, naming cadence and stage:
24 
25> "Build a quarterly board deck — we're Series A."
26> "Draft a fundraising board deck for a seed-stage company."
27 
28Provide available metrics. The builder fills gaps with explicit placeholders — never invents numbers.
29 
30## Deck Structure (Standard Order)
31 
32Every section follows: **Headline → Data → Narrative → Ask/Next**
33 
34### 1. Executive Summary (CEO)
35**3 sentences. No more.**
36- Sentence 1: State of the business (where we are)
37- Sentence 2: Biggest thing that happened this period
38- Sentence 3: Where we're going next quarter
39 
40*Bad:* "We had a good quarter with lots of progress across all areas."
41*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."
42 
43### 2. Key Metrics Dashboard (COO)
44**6-8 metrics max. Use a table.**
45 
46| Metric | This Period | Last Period | Target | Status |
47|--------|-------------|-------------|--------|--------|
48| ARR | $2.4M | $1.97M | $2.3M | ✅ |
49| MoM growth | 8.1% | 7.2% | 7.5% | ✅ |
50| Burn multiple | 1.8x | 2.1x | <2x | ✅ |
51| NRR | 112% | 108% | >110% | ✅ |
52| CAC payback | 11 months | 14 months | <12 months | ✅ |
53| Headcount | 24 | 21 | 25 | 🟡 |
54 
55Pick metrics the board actually tracks. Swap out anything they've said they don't care about.
56 
57### 3. Financial Update (CFO)
58- P&L summary: Revenue, COGS, Gross margin, OpEx, Net burn
59- Cash position and runway (months)
60- Burn multiple trend (3-quarter view)
61- Variance to plan (what was different and why)
62- Forecast update for next quarter
63 
64**One sentence on each variance.** Boards hate "revenue was below target" with no explanation. Say why.
65 
66### 4. Revenue & Pipeline (CRO)
67- ARR waterfall: starting → new → expansion → churn → ending
68- NRR and logo churn rates
69- Pipeline by stage (in $, not just count)
70- Forecast: next quarter with confidence level
71- Top 3 deals: name/amount/close date/risk
72 
73**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.
74 
75### 5. Product Update (CPO)
76- Shipped this quarter: 3-5 bullets, user impact for each
77- Shipping next quarter: 3-5 bullets with target dates
78- PMF signal: NPS trend, DAU/MAU ratio, feature adoption
79- One key learning from customer research
80 
81**No feature lists.** Only features with evidence of user impact.
82 
83### 6. Growth & Marketing (CMO)
84- CAC by channel (table)
85- Pipeline contribution by channel ($)
86- Brand/awareness metrics relevant to stage (traffic, share of voice)
87- What's working, what's being cut, what's being tested
88 
89### 7. Engineering & Technical (CTO)
90- Delivery velocity trend (last 4 quarters)
91- Tech debt ratio and plan
92- Infrastructure: uptime, incidents, cost trend
93- Security posture (one line, flag anything pending)
94 
95**Keep this short unless there's a material issue.** Boards don't need sprint details.
96 
97### 8. Team & People (CHRO)
98- Headcount: actual vs plan
99- Hiring: offers out, pipeline, time-to-fill trend
100- Attrition: regrettable vs non-regrettable
101- Engagement: last survey score, trend
102- Key hires this quarter, key open roles
103 
104### 9. Risk & Security (CISO)
105- Security posture: status of critical controls
106- Compliance: certifications in progress, deadlines
107- Incidents this quarter (if any): impact, resolution, prevention
108- Top 3 risks and mitigation status
109 
110### 10. Strategic Outlook (CEO)
111- Next quarter priorities: 3-5 items, ranked
112- Key decisions needed from the board
113- Asks: budget, introductions, advice, votes
114 
115**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."
116 
117### 11. Appendix
118- Detailed financial model
119- Full pipeline data
120- Cohort retention charts
121- Customer case studies
122- Detailed headcount breakdown
123 
124---
125 
126## Narrative Framework
127 
128Boards see 10+ decks per quarter. Yours needs a through-line.
129 
130**The 4-Act Structure:**
1311. **Where we said we'd be** (last quarter's targets)
1322. **Where we actually are** (honest assessment)
1333. **Why the gap exists** (one cause per variance, not excuses)
1344. **What we're doing about it** (specific, dated actions)
135 
136This works for good news AND bad news. It's credible because it acknowledges reality.
137 
138**Opening frame:** Start with the one thing that matters most — the board should know the key message by slide 3, not slide 30.
139 
140---
141 
142## Delivering Bad News
143 
144Never bury it. Boards find out eventually. Finding out late makes it worse.
145 
146**Framework:**
1471. **State it plainly** — "We missed Q3 ARR target by $300K (12% gap)"
1482. **Own the cause** — "Primary driver was longer-than-expected sales cycle in enterprise segment"
1493. **Show you understand it** — "We analyzed 8 lost/stalled deals; the pattern is X"
1504. **Present the fix** — "We've made 3 changes: [specific, dated changes]"
1515. **Update the forecast** — "Revised Q4 target is $2.6M; here's the bottom-up build"
152 
153**What NOT to do:**
154- Don't lead with good news to soften bad news — boards notice and distrust the framing
155- Don't explain without owning — "market conditions" is not a cause, it's a context
156- Don't present a fix without data behind it
157- Don't show a revised forecast without showing your assumptions
158 
159---
160 
161## Common Board Deck Mistakes
162 
163| Mistake | Fix |
164|---------|-----|
165| Too many slides (>25) | Cut ruthlessly — if you can't explain it in the room, the slide is wrong |
166| Metrics without targets | Every metric needs a target and a status |
167| No narrative | Data without story forces boards to draw their own conclusions |
168| Burying bad news | Lead with it, own it, fix it |
169| Vague asks | Specific, actionable, person-assigned asks only |
170| No variance explanation | Every gap from target needs one-sentence cause |
171| Stale appendix | Appendix is only useful if it's current |
172| Designing for the reader, not the room | Decks are presented — they must work spoken aloud |
173 
174---
175 
176## Cadence Notes
177 
178**Quarterly (standard):** Full deck, all sections, 20-30 slides. Sent 48 hours in advance.
179**Monthly (for early-stage):** Condensed — metrics dashboard, financials, pipeline, top risks. 8-12 slides.
180**Fundraising:** Opens with market/vision, closes with ask. See `references/deck-frameworks.md` for Sequoia format.
181 
182## References
183- `references/deck-frameworks.md` — SaaS board pack format, Sequoia structure, investor tailoring
184- `templates/board-deck-template.md` — fill-in template for complete board decks
185 
View all files on GitHub →

Details

Updated
Aug 30, 2026
License
MIT
Stars on the repo
★ 26,349
Checked
Source
alirezarezvani/claude-skills ↗
Creator
alirezarezvani · 363 listings
View creator

Similar skills

See all →
MCP3-5 days | Agents: 6 | Gate Keepers: DevOps Automator +⚙️ Phase 2 Playbook — Foundation & Scaffoldingmsitarzewski/agency-agents · by msitarzewski> Duration: 3-5 days | Agents: 6 | Gate Keepers: DevOps Automator + Evidence Collector★ 154k GitHub starsMCPNEXUS transforms The Agency's independent AI specialists🌐 NEXUS — Network of EXperts, Unified in Strategymsitarzewski/agency-agents · by msitarzewski> NEXUS transforms The Agency's independent AI specialists into a synchronized intelligence network. This is not a prompt collection — it…★ 154k GitHub starsSkillGenerate an Ansoff Matrix analysis mapping growth strategiesphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsSkillSurvey any codebase as a senior advisorImproveshadcn/improve · by shadcnSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.★ 9.2k GitHub starsSkillTranslate skills from one industry to anotherCareer changer translatorParamchoudhary/ResumeSkills · by ParamchoudharyTranslate skills from one industry to another, identify transferable skills★ 2.4k GitHub starsSkillA collection of 37 battle-tested marketing skillsOpenClaw Marketing SkillsLeoYeAI/openclaw-marketing-skills · by LeoYeAIA collection of 37 battle-tested marketing skills for OpenClaw agents. Use when you want to install or reference any marketing skill including: CRO (page-cro, signup-flow-cro, onboarding-cro, form-cro, popup-cro, paywall-upgrade-cro), copywriting, copy-editing, cold-email, email-sequence, social-content, seo-audit, ai-seo, programmatic-seo, site-architecture, schema-markup, content-strategy, paid-ads, ad-creative, ab-test-setup, analytics-tracking, referral-program, free-tool-strategy, churn-prevention, revops, sales-enablement, launch-strategy, pricing-strategy, competitor-alternatives, marketing-ideas, marketing-psychology, lead-magnets, product-marketing-context, and data connectors (google-ads-connect, search-console-connect, meta-ads-connect, x-twitter-connect). Start with product-marketing-context to set up your product context document, then use any other skill naturally. Powered by MyClaw.ai.★ 1k GitHub stars

More from alirezarezvani

SkillResume a paused experiment/ar:ar-resume — Resume Experimentalirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub starsSkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboardalirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillStart an autonomous experiment loop with user-selected/ar:loop — Autonomous Experiment Loopalirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub starsSkillRun a single experiment iteration/ar:run — Single Experiment Iterationalirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub starsSkillSet up a new autoresearch experiment interactively/ar:setup — Create New Experimentalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub starsSkill/cs:boardroom <brief/cs:boardroom — Multi-Role Boardroom Deliberationalirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars