board-deck-builder

5
0
Source

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.

Install

mkdir -p .claude/skills/board-deck-builder && curl -L -o skill.zip "https://mcp.directory/api/skills/download/3460" && unzip -o skill.zip -d .claude/skills/board-deck-builder && rm skill.zip

Installs to .claude/skills/board-deck-builder

About this skill

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

/board-deck [quarterly|monthly|fundraising] [stage: seed|seriesA|seriesB]

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

senior-architect

alirezarezvani

Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.

170129

content-creator

alirezarezvani

Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or when user mentions content creation, brand voice, SEO optimization, social media marketing, or content strategy.

11619

cold-email

alirezarezvani

When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).

3713

content-trend-researcher

alirezarezvani

Advanced content and topic research skill that analyzes trends across Google Analytics, Google Trends, Substack, Medium, Reddit, LinkedIn, X, blogs, podcasts, and YouTube to generate data-driven article outlines based on user intent analysis

10913

ceo-advisor

alirezarezvani

Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.

8413

content-humanizer

alirezarezvani

Makes AI-generated content sound genuinely human — not just cleaned up, but alive. Use when content feels robotic, uses too many AI clichés, lacks personality, or reads like it was written by committee. Triggers: 'this sounds like AI', 'make it more human', 'add personality', 'it feels generic', 'sounds robotic', 'fix AI writing', 'inject our voice'. NOT for initial content creation (use content-production). NOT for SEO optimization (use content-production Mode 3).

359

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

643969

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

591705

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318398

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

339397

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

451339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.