AGENT SKILL

board-deck-builder

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
所属仓库
ASoudy/AGS
最近更新
2026-05-23
Stars
★ 0
Forks
0

01 前言 Front Matter

name
board-deck-builder
license
MIT
metadata
{ "author": "Alireza Rezvani", "domain": "board-governance", "updated": 1772668800000, "version": "1.0.0", "category": "c-level", "frameworks": "deck-frameworks, board-deck-template" }
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.

02 资源文件 2

03 SKILL.md 正文

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.

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

04 同仓库更多 Skills

ASoudy
ASoudy/AGS

web-typography

Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", or "typographic scale". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.

★ 0
ASoudy
ASoudy/AGS

ux-heuristics

Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "UX review", "users are confused", "heuristic evaluation", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "usability testing". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.

★ 0
ASoudy
ASoudy/AGS

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "Entrepreneurial Operating System", or "business operating system". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.

★ 0
ASoudy
ASoudy/AGS

top-design

Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "premium website", "portfolio site", "scroll animations", "Awwwards quality", "brand experience", "cinematic web design", "parallax storytelling", or "agency-quality site". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.

★ 0
ASoudy
ASoudy/AGS

system-design

Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.

★ 0
ASoudy
ASoudy/AGS

storybrand-messaging

Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "messaging isnt resonating", "brand script", "StoryBrand framework", or "customer as hero". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.

★ 0