The winning board deck template
P&L + variance
Actual vs. plan on revenue, gross margin, opex, and runway. Explain the top 3 variances.
Formula
Revenue [actual / plan / variance]. GM [%]. Opex [$/mo]. Cash [$]. Runway [months at current burn].
Strong example
Q2 revenue $2.1M (plan $2.2M, -5%). GM 71% (plan 70%). Opex $780K/mo (plan $750K). Cash $9.4M. Runway 12 mo at current burn, 15 mo at plan burn. Cash-out Q2 2027. Top variances: (1) SDR salary +$60K vs. plan (start dates), (2) AWS spend +$40K (traction), (3) legal -$20K (M&A slipped).
Must have
- Runway in months at current burn, and at plan burn, both
- Top 3 variances explained in one line each
- Cash-out date on the slide, not just runway months
Avoid
- GAAP-vs-non-GAAP acrobatics in a board deck
- Runway without a cash-out date
- 'Opex slightly over plan' with no dollars
The winning board deck template
Top 3 risks
Name the three things that could break the plan, and what you're doing about each.
Formula
[Risk]: probability [low/med/high], impact [$/quarters]. Mitigation: [action]. Owner: [name].
Strong example
(1) Top-3 customer = 22% of ARR: med, impact -$460K/yr. Mitigation: expand to 3 more design partners in Q3. Owner: Jane. (2) VP Sales offer declines: med, impact -6mo on GTM plan. Backup: 2 finalists in-process. Owner: Jane. (3) AWS partnership slip: low, impact 1-quarter pipeline. Owner: Ravi.
Must have
- Impact in dollars or quarters of runway, not adjectives
- One named owner per risk
- At least one risk you'd rather not raise (customer concentration, key hire)
Avoid
- 'Competition' as a top risk (too generic)
- 'We may need to raise more' without dollars or dates
- Risks with no owner
The winning board deck template
Legal + compliance
Anything the board needs to sign, know about, or worry about, in one page.
Formula
Signatures needed: [X]. Incidents: [Y]. Litigation: [Z]. IP / trademark / privacy: [notes].
Strong example
Signatures: 409A refresh, VP Sales offer. Incidents: 1 Sev-1 (May 3, 41 min degradation, post-mortem attached). Filings: SOC 2 Type II renewed May 20. IP: Nimbus wordmark filed in EU (May 8).
Must have
- Any Sev-1 or Sev-2 incident from the quarter, with post-mortem link
- Any regulatory filing or license change
- Anything requiring a board signature this meeting
Avoid
- 'No issues to report' when there was a Sev-1 (the board hears about it later)
- Hiding a lawsuit or subpoena from the deck
- 409A refresh as a footnote instead of a signature line
The winning investor update template
Lowlights (2, honest)
The two things that didn't work, and what you're doing about each. This is the highest-trust section.
Formula
[What didn't work, one line of what happened]. Cause: [one line]. Fix: [one action, one owner, one date].
Strong example
1) SDR ramp slipped 6 weeks: two hires started 4 weeks late. Fix: pushed VP Sales start to May, restructured Q2 quota. Owner: Jane, by May 1. 2) Sev-1 incident May 3: 41 min degradation on European rails. Cause: DB failover misconfig. Fix: shipped, post-mortem attached.
Must have
- At least 2 lowlights every month (not zero)
- Named cause, not 'we underestimated the market'
- A dated fix or explicit 'still figuring this out'
Avoid
- Zero lowlights ('everything went great')
- Lowlights framed as brags ('too many inbound leads')
- No named owner or date on the fix
The winning partnership deck template
Risks (pre-empted)
Answer the 3 objections their BD lead is going to raise in the read.
Formula
Objection: [what they'll ask]. Answer: [one line].
Strong example
(1) Do you compete with Rippling EOR? No: we do not offer US EOR, and we route employees to your EOR in the 40 countries where you cover. (2) Who owns support? Tier 1 in Rippling, Tier 2 escalates via a shared Slack channel and a 4h SLA. (3) Are you exclusive? We're pursuing a preferred partnership; we're not asking for exclusivity in v1.
Must have
- The channel-conflict objection ('do you compete with our EOR?')
- The support / SLA objection ('who owns support when it breaks?')
- The exclusivity objection ('are you talking to Deel too?')
Avoid
- Pretending channel conflict doesn't exist
- 'We'd need to discuss' as the answer to support ownership
- Vague exclusivity language that a BD lead will read as evasive