New to Claude Skills? Learn how to install them →

alirezarezvani on GitHub

Board Deck Builder

Free

Craft compelling board and investor update decks.

Get this skill

Free · Opens the source repo

What Board Deck Builder does

The Board Deck Builder is designed to streamline the process of creating comprehensive board decks that effectively communicate important business updates. This skill focuses on assembling presentations that not only present data but also tell a cohesive story, ensuring that each section has a clear owner, narrative, and actionable insights. It is particularly useful for executives and teams preparing for board meetings, investor updates, or quarterly business reviews, where clarity and engagement are paramount.

Users can quickly generate a structured board deck by simply providing a natural language request, specifying the cadence and stage of the company. The skill guides users through a standardized deck structure that includes essential sections such as the Executive Summary, Key Metrics Dashboard, Financial Update, and more. Each section is meticulously crafted to ensure that it includes the right data and narrative, making it easier for stakeholders to grasp the company's current status and future direction.

One of the key features of this skill is its emphasis on narrative frameworks, which help users present both good and bad news effectively. By following a structured approach to storytelling, users can communicate variances and corrective actions transparently, fostering trust and understanding among board members. Additionally, the skill provides guidance on common mistakes to avoid, helping users refine their presentations and focus on what matters most to their audience.

Overall, the Board Deck Builder is an invaluable tool for C-suite executives and their teams, enabling them to create impactful presentations that drive informed discussions and decision-making during critical meetings.

When to use it

Use this skill when preparing for board meetings, investor updates, or quarterly business reviews to create a compelling narrative around your data.

When not to use it

This skill may not be suitable for informal presentations or situations where a detailed narrative is not required.

What you can build with it

Quarterly Business Review Preparation

Use the skill to assemble a quarterly business review deck that clearly outlines performance metrics and strategic direction.

Investor Update Deck Creation

Quickly generate an investor update deck that communicates key developments and financial metrics to stakeholders.

Fundraising Narrative Development

Leverage the skill to craft a compelling fundraising deck that articulates your business's value proposition and growth potential.

How to install Board Deck Builder

View source

1. Install with the skills CLI

npx skills add alirezarezvani/claude-skills/board-deck-builder --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by alirezarezvani

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.

MetricThis PeriodLast PeriodTargetStatus
ARR$2.4M$1.97M$2.3M
MoM growth8.1%7.2%7.5%
Burn multiple1.8x2.1x<2x
NRR112%108%>110%
CAC payback11 months14 months<12 months
Headcount242125🟡

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

MistakeFix
Too many slides (>25)Cut ruthlessly — if you can't explain it in the room, the slide is wrong
Metrics without targetsEvery metric needs a target and a status
No narrativeData without story forces boards to draw their own conclusions
Burying bad newsLead with it, own it, fix it
Vague asksSpecific, actionable, person-assigned asks only
No variance explanationEvery gap from target needs one-sentence cause
Stale appendixAppendix is only useful if it's current
Designing for the reader, not the roomDecks 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

Frequently asked questions about Board Deck Builder

Similar skills