Startup board deck: what to include for a board meeting

A startup board deck for a regular board meeting should open with a one-page summary and the decisions needed, then show KPIs against plan, financials and budget versus actual, cash and runway, pipeline and revenue, product and team, and risks, in that order every time. Keep the main deck to roughly 15 to 25 slides, put the detail in an appendix, and send it about a week ahead so the meeting is spent on discussion rather than presentation.

This playbook is for founders of seed to Series B software companies preparing a quarterly board meeting. Some boards call the same document a board pack or the startup board reporting package; the structure below applies whatever the name. Where the deck fits in the wider finance setup is covered in the guide to a fractional CFO for startups.

The section order, and what each section answers

Each section exists to answer a question a director would otherwise ask in the meeting. The order puts the asks and the cash position early, because directors look for those first.

A director who reads only the first and last pages should still know the state of the company and what is being asked.

Showing numbers against plan

Every financial and KPI page should show three things side by side: actual, plan, and the variance, plus last quarter for trend. Without the plan column, a director cannot tell whether a number is good. The monthly mechanics of building that comparison and writing the commentary are in the guide to budget vs actual analysis; the deck carries the quarterly result and the explanation.

The example below shows a KPI page for a fictional Series A company, and why the columns matter.

Illustrative figures, not client data. Monthly net burn is 350 on plan (1,050 / 3) and 320 actual (960 / 3); runway is 5,400 / 350 and 5,490 / 320, rounded down.

Read alone, the burn line looks like good news: spending under plan and two more months of runway. Read with the ARR line, it tells a different story. If the underspend came from two sales hires starting late, it is the same cause as the net new ARR miss, and it will reappear as a revenue shortfall next quarter. A good deck says that in the commentary before a director has to ask.

How long the deck should be, and when to send it

For a regular meeting at this stage, roughly 15 to 25 slides in the main deck is usually enough. Anything a director might want to check but does not need to discuss goes in an appendix: the full income statement, balance sheet, the ARR waterfall, cohort detail and the hiring plan line by line.

Send the deck about a week before the meeting, and never later than a few days. Directors who have read it arrive with questions, and the meeting becomes a discussion of the decisions rather than a walk through slides. A pre-read also gives directors a chance to raise a concern privately before the meeting, which is better than a surprise in front of the full board.

Keep metric definitions the same every quarter

The most common way a board deck loses credibility is a quiet change in how a metric is calculated. If ARR included services revenue last quarter and excludes it this quarter, the trend line is wrong even if each number is correct on its own terms.

A definitions slide in the appendix fixes this. It lists each KPI with its formula and what is in and out, using the same definitions as the SaaS metrics the company reports elsewhere. When a definition genuinely needs to change, say so on the KPI page, give the reason, and restate prior quarters on the new basis. That is the same discipline the SEC expects of public companies reporting key performance indicators: a clear definition and calculation, and disclosure of any change in method, its reasons and its effects, with prior periods recast where the change is significant.

How a board member reads your deck

Decipher's founder spent nearly a decade running FP&A inside private equity backed software companies, preparing the board packages investors read. Directors tend to read a deck in a predictable order, and it is rarely front to back.

• The summary and asks first. If the asks are vague or missing, the director assumes the meeting will be a presentation.
• Cash and runway next. The question is when the next raise has to start, so runway under a downside case matters more than the base case. The mechanics are covered in burn rate and runway.
• The full-year forecast column. Directors care less about the quarter than about whether the year is still on track, and whether the forecast moved since the last meeting.
• The previous deck, side by side. Experienced directors compare this quarter's figures with what was shown last quarter. A restated number with no explanation draws more attention than a miss that is explained.
• Whether commentary leads to action. A variance explained the same way two quarters running, with no change in plan, reads as a problem nobody owns.