board-deck-builder
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Covers deck structure, narrative frameworks, bad news delivery, section-by-section guidance, and common mistakes. Use when preparing board meetings, investor updates, quarterly business reviews, fundraising narratives, or when user mentions board deck, investor update, board pack, board presentation, quarterly review, fundraising deck, or investor deck.
What this skill does
# 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." Boards see 10+ decks per quarter -- yours needs a through-line. ## 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, board report, metrics dashboard, bad news delivery, variance explanation --- ## Deck Types and Structure ### Deck Type Selection | Type | When | Slide Count | Sent in Advance | Key Section | |------|------|-------------|-----------------|-------------| | Quarterly Board Deck | Standard board meeting | 20-30 slides | 48 hours ahead | Full deck below | | Monthly Update | Early-stage boards | 8-12 slides | 24 hours ahead | Metrics + risks | | Fundraising Deck | Active fundraise | 12-15 slides | During meeting | Vision + traction | | Emergency/Ad-hoc | Crisis or major decision | 5-8 slides | Depends | Situation + options | --- ## Standard Board Deck (Section by Section) ### Section 1: Executive Summary (CEO) Three sentences. No more. No less. | Sentence | Purpose | Example | |----------|---------|---------| | 1 | State of the business | "We closed Q3 at $2.4M ARR, up 22% QoQ" | | 2 | Biggest development this period | "Signed our largest enterprise contract ($180K ACV)" | | 3 | Forward-looking priority | "Q4 priority: close Series A and hit $2.8M ARR" | **Anti-pattern**: "We had a good quarter with lots of progress across all areas." **Why it fails**: Says nothing. Board learns nothing. Time wasted. ### Section 2: Key Metrics Dashboard (COO) 6-8 metrics maximum. Every metric needs a target and a status. | Metric | This Period | Last Period | Target | Status | Trend | |--------|-------------|-------------|--------|--------|-------| | ARR | $2.4M | $1.97M | $2.3M | [G] | Up | | MoM Growth | 8.1% | 7.2% | 7.5% | [G] | Up | | Burn Multiple | 1.8x | 2.1x | < 2x | [G] | Improving | | NRR | 112% | 108% | > 110% | [G] | Up | | CAC Payback | 11 mo | 14 mo | < 12 mo | [G] | Improving | | Headcount | 24 | 21 | 25 | [Y] | Below plan | **Rule**: Only show metrics the board actually tracks. Ask what they care about. Remove anything they have said they do not care about. ### Section 3: Financial Update (CFO) | Component | Include | Format | |-----------|---------|--------| | P&L Summary | Revenue, COGS, Gross Margin, OpEx, Net Burn | Table with variance column | | Cash Position | Current balance + runway in months | Single number, bold | | Burn Multiple Trend | 3-quarter trend | Line chart | | Variance to Plan | Each line item vs. budget | Table with one-sentence explanations | | Forecast Update | Next quarter projections | Conservative, base, upside | **Rule**: Every variance needs a one-sentence explanation. "Revenue was below target" with no explanation is unacceptable. ### Section 4: Revenue and Pipeline (CRO) | Component | Include | Format | |-----------|---------|--------| | ARR Waterfall | Opening -> New -> Expansion -> Contraction -> Churn -> Closing | Waterfall chart | | NRR and Logo Churn | Current + 4-quarter trend | Table + trend line | | Pipeline by Stage | Dollar amounts, not just counts | Funnel visualization | | Forecast | Next quarter with confidence level | "High confidence $2.6M, upside to $2.9M" | | Top 3 Deals | Name, amount, close date, risk | Table | **Rule**: Forecast MUST include a confidence level. "We expect $2.8M" is weak. ### Section 5: Product Update (CPO) | Component | Include | Format | |-----------|---------|--------| | Shipped This Quarter | 3-5 items with user impact | Bullet list | | Shipping Next Quarter | 3-5 items with target dates | Bullet list | | PMF Signals | NPS trend, DAU/MAU, feature adoption | Metrics table | | Key Learning | One insight from customer research | Narrative paragraph | **Rule**: No feature lists. Only features with evidence of user impact. ### Section 6: Growth and Marketing (CMO) | Component | Include | |-----------|---------| | CAC by Channel | Table with efficiency trend | | Pipeline Contribution | $ by channel | | What's Working | Specific channels/campaigns with data | | What's Being Cut | Underperforming channels | | What's Being Tested | New experiments with hypothesis | ### Section 7: Engineering and Technical (CTO) | Component | Include | |-----------|---------| | Delivery Velocity | 4-quarter trend | | Tech Debt Ratio | Current + plan to address | | Infrastructure | Uptime, incidents, cost trend | | Security Posture | One line unless there is a material issue | **Rule**: Keep this short unless there is a material issue. Boards do not need sprint details. ### Section 8: Team and People (CHRO) | Component | Include | |-----------|---------| | Headcount | Actual vs. plan | | Hiring | Offers out, pipeline, time-to-fill trend | | Attrition | Regrettable vs. non-regrettable | | Engagement | Latest survey score and trend | | Notable | Key hires, key departures, key open roles | ### Section 9: Risk and Security (CISO) | Component | Include | |-----------|---------| | Security Posture | Status of critical controls | | Compliance | Certifications in progress, deadlines | | Incidents | This quarter (if any): impact, resolution, prevention | | Top 3 Risks | Risk description + mitigation status | ### Section 10: Strategic Outlook (CEO) | Component | Include | |-----------|---------| | Next Quarter Priorities | 3-5 items, ranked by importance | | Board Decisions Needed | Specific votes or approvals | | Asks | Specific, actionable requests | **Rule**: The "asks" section is the most important. "We'd like 3 warm introductions to CFOs at Series B companies" beats "any help would be appreciated." ### Section 11: Appendix Include but do not present unless asked: - Detailed financial model - Full pipeline data - Cohort retention charts - Customer case studies - Detailed headcount breakdown --- ## Narrative Framework ### The 4-Act Structure Every board deck should follow this through-line: ``` Act 1: WHERE WE SAID WE'D BE Last quarter's targets and commitments Act 2: WHERE WE ACTUALLY ARE Honest assessment -- good and bad Act 3: WHY THE GAP EXISTS One cause per variance. Not excuses -- explanations. Act 4: WHAT WE'RE DOING ABOUT IT Specific, dated, owned actions ``` This works for good news AND bad news. It is credible because it acknowledges reality. ### Opening Frame The board should know the key message by slide 3, not slide 30. | Good Opening | Bad Opening | |-------------|-------------| | "We beat ARR target by 8% and NRR hit 112%" | "Let me walk you through our quarter..." | | "We missed revenue by $300K. Here's why and the fix." | "First, some context about market conditions..." | | "We need a board vote on the acquisition opportunity" | "Before we get to the main topic, some updates..." | --- ## Delivering Bad News ### The SOUF Framework | Step | What | Example | |------|------|---------| | **S**tate | State it plainly | "We missed Q3 ARR target by $300K (12% gap)" | | **O**wn | Own the cause | "Primary driver: longer enterprise sales cycle than modeled" | | **U**nderstand | Show you understand it | "Analyzed 8 stalled deals; pattern is procurement delays" | | **F**ix | Present the fix | "Three changes: [specific, dated], revised Q4 target: $2.6M" | ### Bad News Anti-Patterns | Anti-Pattern | Why It Fails | Better Approach | |-------------|-------------|-----------------| | Leading with good news to soften | Boards notice and distrust framing | Lead with the most important thing | | "Market conditions" as cause | That is context, not a cause | Name specific, controllable causes | | Fix without data | Board does not trust unfounded fixes | Show analysis behind the fix | | Revised forecast without assumptions | Looks like guessing | Show bottom-up build | --- ## Common Board Deck Mistakes | Mistake | Fix | |---------|-----| | Too many slides (>
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.