Your board reads the first three pages and searches for burn. Build for that.

I’ve sat in enough board meetings to tell you what most board members actually do with a monthly package:

1. They read the first page.
2. They skim the next two.
3. They ctrl-F “burn” or “runway” in the PDF.
4. They form their question.
5. They ask it.

If your package is structured so that burn, runway, and the main variance story are in the first three pages, you’ve already won a good chunk of the meeting. If they’re on page eleven, after the mission statement and the team-building slide, you’ve wasted the one behavior you can predict.

This isn’t a complaint about board members. It’s a specification.

What the first three pages should cover

Page 1 — Executive summary. Lead with the conclusion. “March landed ahead on net new ARR and behind on gross margin. Gross-margin softness is the migration we flagged in January. NRR question from last month is resolved in section 3.”

Page 2 — The metric dashboard. ARR, NRR, gross margin, burn rate, runway, burn multiple. Every figure with its formula and inputs visible. No “Gross Margin 0.0%” because the COGS mapping is incomplete — say so explicitly.

Page 3 — The variance story. The two or three material variances and what caused them. Temporary vs. structural. Budgeted vs. actual, with the reason. Cited.

Everything else — ops plan, team, product, customer, pipeline — comes after, because everything else matters less to a board that is protecting their downside.

What “build for that” actually means

Build one narrative, not two. The executive summary cannot disagree with the metric dashboard. The metric dashboard cannot disagree with the variance story. If the PDF says 72% gross margin and slide 4 of the deck says 68%, the board is going to find it in the meeting, and now you’re reconciling on the fly. The export button should refuse to enable until everything reconciles. (Ours does.)

Build once, defend everywhere. Every framing decision — “temporary investment,” not “headwind”; Rule of 40 operating-margin variant; NRR excluding services — should be captured as a signal the first time the CFO confirms it. Next month, the draft lands on the same framing without you having to remember to re-apply it.

Build with memory. If a board member asked about NRR methodology last month, the next package should open on NRR methodology. If the Accel partner pushed back on the variance framing, the next variance section should address it. A well-built package cites the prior meeting the way a well-built legal argument cites prior precedent.

An honest example

An anonymised Series B SaaS client’s March package. ARR $12M, gross margin 67%, burn multiple 2.1x. The first three pages were:

That’s the whole board meeting for most boards, most months. You can tell from a well-constructed first three pages whether the founder understands their business. You can also tell when they don’t.

What this changes about your next package

Open the last one you shipped. Read just the first three pages. Ask:

• Does the executive summary have a conclusion, or just a chronology?
• Can I find burn, runway, and the main variance without scrolling?
• Is every figure traceable to a formula and a source row?
• Does any framing decision reference a prior board ask?

If the answer to any of those is “no,” you’re making the board work for the answer. They will, but you’ll pay for it — in time they don’t have to ask harder questions, and in the trust they don’t extend because they had to dig.

Build for the behavior you can predict. The board is telling you how to build the package every time they ctrl-F “burn.”