board-deck-builder
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseBoard Deck Builder
Board Deck 制作工具
Build board decks that tell a story — not just show data. Every section has an owner, a narrative, and a "so what."
制作能够讲述故事的Board Deck——而非单纯展示数据。每个板块都有负责人、叙事逻辑以及对应的“意义所在”。
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 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.
/board-deck [quarterly|monthly|fundraising] [stage: seed|seriesA|seriesB]提供可用指标。工具会用明确的占位符填补空白——绝不会编造数据。
Deck Structure (Standard Order)
演示文稿结构（标准顺序）
Every section follows: Headline → Data → Narrative → Ask/Next
每个板块遵循：标题 → 数据 → 叙事 → 请求/下一步行动
1. Executive Summary (CEO)
1. 执行摘要（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."
最多3句话。
- 第1句：业务现状（我们所处的位置）
- 第2句：本周期内发生的最重要事件
- 第3句：下一季度的发展方向
反面示例： “我们度过了不错的一个季度，各方面都取得了诸多进展。”
正面示例： “我们以240万美元ARR（环比增长22%）结束Q3，签下了最大的企业客户，进入Q4时拥有14个月的现金流储备。向中端市场转型的战略已见成效——ACV提升40%，销售周期缩短3周。Q4优先级：完成300万美元A轮融资，达成280万美元ARR目标。”
2. Key Metrics Dashboard (COO)
2. 核心指标仪表盘（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.
最多6-8个指标。采用表格形式。
| 指标 | 本周期 | 上一周期 | 目标 | 状态 |
|---|---|---|---|---|
| ARR | $2.4M | $1.97M | $2.3M | ✅ |
| 月环比增长率 | 8.1% | 7.2% | 7.5% | ✅ |
| 消耗倍数 | 1.8x | 2.1x | <2x | ✅ |
| NRR | 112% | 108% | >110% | ✅ |
| CAC回收期 | 11个月 | 14个月 | <12个月 | ✅ |
| 员工人数 | 24 | 21 | 25 | 🟡 |
选择董事会实际关注的指标。替换掉他们明确表示不关心的内容。
3. Financial Update (CFO)
3. 财务更新（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.
- 损益表摘要：收入、销货成本、毛利率、运营费用、净消耗
- 现金状况及现金流储备（月数）
- 消耗倍数趋势（近3个季度）
- 与计划的差异（差异内容及原因）
- 下一季度的预测更新
每个差异用一句话说明。 董事会讨厌只说“收入未达目标”却不解释原因。务必说明理由。
4. Revenue & Pipeline (CRO)
4. 收入与销售 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.
- ARR瀑布图：初始值 → 新增 → 扩张 → 流失 → 最终值
- NRR及客户流失率
- 各阶段Pipeline金额（以美元计，而非仅数量）
- 预测：下一季度目标及置信度
- 前3大交易：名称/金额/预计关闭日期/风险
预测必须包含置信度。 “我们预计达成280万美元”不够明确。“高置信度达成260万美元，若两笔后期交易完成则有望达到290万美元”才更有价值。
5. Product Update (CPO)
5. 产品更新（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.
- 本季度已上线功能：3-5个要点，每个要点说明用户影响
- 下一季度计划上线功能：3-5个要点及目标日期
- PMF信号：NPS趋势、DAU/MAU比值、功能采用率
- 从客户调研中得出的一个关键结论
不要罗列功能。 只展示有用户影响证据的功能。
6. Growth & Marketing (CMO)
6. 增长与营销（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
- 各渠道CAC（表格形式）
- 各渠道贡献的Pipeline金额（美元）
- 与阶段匹配的品牌/知名度指标（流量、市场份额）
- 有效策略、拟终止策略及测试中策略
7. Engineering & Technical (CTO)
7. 工程与技术（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.
- 交付速度趋势（近4个季度）
- 技术债务占比及解决计划
- 基础设施：正常运行时间、事故、成本趋势
- 安全状况（一句话说明，标记待处理事项）
内容尽量简短，除非存在重大问题。 董事会不需要了解冲刺细节。
8. Team & People (CHRO)
8. 团队与人力（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
- 员工人数：实际vs计划
- 招聘：已发出offer、招聘 pipeline、招聘周期趋势
- 离职情况：遗憾离职vs非遗憾离职
- 员工参与度：最近调研得分及趋势
- 本季度关键招聘、重点空缺岗位
9. Risk & Security (CISO)
9. 风险与安全（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
- 安全状况：关键控制措施状态
- 合规性：正在进行的认证及截止日期
- 本季度事故（如有）：影响、解决方案、预防措施
- 前3大风险及缓解状态
10. Strategic Outlook (CEO)
10. 战略展望（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."
- 下一季度优先级：3-5项，按重要性排序
- 需要董事会做出的关键决策
- 请求：预算、引荐、建议、投票
“请求”幻灯片是最重要的。 务必具体。“希望获得3个向B轮公司CFO的暖引荐”远胜于“任何帮助都将不胜感激”。
11. Appendix
11. 附录
- Detailed financial model
- Full pipeline data
- Cohort retention charts
- Customer case studies
- Detailed headcount breakdown
- 详细财务模型
- 完整Pipeline数据
- 用户留存 cohort图表
- 客户案例研究
- 详细员工人数 breakdown
Narrative Framework
叙事框架
Boards see 10+ decks per quarter. Yours needs a through-line.
The 4-Act Structure:
- Where we said we'd be (last quarter's targets)
- Where we actually are (honest assessment)
- Why the gap exists (one cause per variance, not excuses)
- 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.
董事会每季度要审阅10份以上的演示文稿。你的文稿需要有一条贯穿始终的主线。
四幕结构：
- 我们曾承诺的目标（上一季度的目标）
- 实际达成的状况（坦诚评估）
- 差异原因（每个差异对应一个原因，而非借口）
- 解决方案（具体、有时间节点的行动）
这一结构适用于好消息和坏消息。它因承认现实而更具可信度。
开场框架： 从最重要的信息切入——董事会应在第3页幻灯片前了解核心信息，而非第30页。
Delivering Bad News
坏消息传达方式
Never bury it. Boards find out eventually. Finding out late makes it worse.
Framework:
- State it plainly — "We missed Q3 ARR target by $300K (12% gap)"
- Own the cause — "Primary driver was longer-than-expected sales cycle in enterprise segment"
- Show you understand it — "We analyzed 8 lost/stalled deals; the pattern is X"
- Present the fix — "We've made 3 changes: [specific, dated changes]"
- 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
绝不能隐瞒。董事会迟早会知道。晚知道只会让情况更糟。
框架：
- 直白陈述 —— “我们Q3 ARR目标未达成，缺口为30万美元（12%）”
- 承担责任 —— “主要原因是企业客户销售周期长于预期”
- 展示认知深度 —— “我们分析了8笔流失/停滞的交易，发现共性问题为X”
- 提出解决方案 —— “我们已做出3项调整：[具体、有时间节点的调整措施]”
- 更新预测 —— “修订后的Q4目标为260万美元；以下是自下而上的推导依据”
切勿做这些事：
- 不要先用好消息铺垫坏消息——董事会会注意到并质疑这种框架
- 不要只解释不承担责任——“市场环境”是背景，而非原因
- 不要提出无数据支撑的解决方案
- 不要展示修订后的预测却不说明假设前提
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 |
| 误区 | 解决方案 |
|---|---|
| 幻灯片过多（超过25页） | 果断删减——如果无法在现场解释清楚，说明幻灯片设计有误 |
| 指标无目标 | 每个指标都需要对应目标和状态 |
| 缺乏叙事逻辑 | 无故事的数据会迫使董事会自行得出结论 |
| 隐瞒坏消息 | 主动提出、承担责任、解决问题 |
| 请求模糊 | 只提出具体、可执行、明确责任人的请求 |
| 不解释差异原因 | 每个与目标的缺口都需要用一句话说明原因 |
| 附录内容过时 | 附录只有内容最新时才有价值 |
| 为读者而非现场展示设计 | 演示文稿是用来讲解的——必须适合口头陈述 |
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 for Sequoia format.
references/deck-frameworks.md季度版（标准）： 完整演示文稿，包含所有板块，20-30页。提前48小时发送。
月度版（适用于早期阶段）： 精简版——核心指标仪表盘、财务状况、Pipeline、主要风险。8-12页。
融资版： 以市场/愿景开篇，以请求收尾。参考中的红杉资本格式。
references/deck-frameworks.mdReferences
参考资料
- — SaaS board pack format, Sequoia structure, investor tailoring
references/deck-frameworks.md - — fill-in template for complete board decks
templates/board-deck-template.md
- —— SaaS董事会资料格式、红杉资本结构、投资者定制指南
references/deck-frameworks.md - —— 完整Board Deck的填充式模板
templates/board-deck-template.md