Board Revenue Update Template: The Six Slides a CRO Should Bring Every Quarter

What should the board update contain?

Six slides, each ending in a decision or a change in belief. Anything that does not sit in those six goes in an appendix. Directors read appendices when they care, and slides that exist only to demonstrate effort dilute the ones that matter.

What belongs on the forecast slide?

The three sources the period's revenue will come from, sized separately. A single forecast number produces a conversation about whether the CRO is optimistic. A decomposed forecast produces a conversation about mechanics, which is a conversation the CRO can win.

The decomposition:

1. Carry-over deals already in pipeline on day one that are expected to close this period. 2. In-period business that does not exist yet, and will be created, qualified, and closed inside the period. 3. Pull-forward deals from future periods that may close early, usually with a discount or a future-period tradeoff.

Most teams over-trust the visible pipeline and under-model the invisible portion. They inspect the deals sitting in CRM closely and barely forecast how much revenue has to be created and closed inside the period. They also understate what pulling future deals forward costs the next quarter, which is exactly the sort of tradeoff a board should be told about before it happens rather than after.

Show the pull-forward line explicitly even when it is small. A board that sees it every quarter will notice when it grows, and that growth is one of the earliest signs a team is borrowing from the future.

How should retention be shown?

As a monthly reconciling waterfall where beginning ARR always equals the prior month's ending ARR. ORM structures it this way: Gross revenue retention and net revenue retention sit on the same chart, calculated from the lines above rather than reported as standalone figures. The reconciliation is what makes the slide credible. Every dollar of movement lands in a named bucket, so a director who asks where $400K went gets an answer from the chart rather than a follow-up.

How should pipeline be presented?

With composition on the same slide as the ratio, never the ratio alone. Total pipeline coverage without context is the metric that generates the most noise in an executive setting. It makes people feel informed while masking the actual risk.

A company can hold 4x coverage and still miss badly when the pipeline is low quality, concentrated in the wrong stage, dependent on a few large deals, inflated by stale opportunities, or built on close dates that keep moving. A company can start thin and outperform on a strong in-period motion. The ratio distinguishes neither case.

Across ORM's customer base, coverage runs from roughly 1.4x to 5x with most customers near 3.5x, which is why the 3x coverage rule holds up so poorly as a board-level assurance. Two additional facts belong on the slide. More than 10% of pipeline in a typical customer base has not been touched in twelve months. And of the pipeline carrying in-period close dates on day one, roughly 20% actually closes in that period, leaving 80% of the visible value unrealized.

Present coverage with segment mix, stage distribution, age profile, and the share of the number sitting in the top five deals. That is a slide a board can reason about.

What do you do about numbers you cannot trace?

Take them off the deck. The first question after any surprising figure is where it came from, and an answer that requires two days of reconstruction costs more credibility than the slide ever gained.

This is the practical limit on using a language model to assemble board material. If you ask an LLM to build slides, validating the numbers takes about as long as building the deck yourself, which erases the time saving. The gap is trust and traceability. The tooling has to point back to the point of truth that produced each figure. ORM built Radar, its MCP and in-app AI, around that requirement, carrying the semantic and analytics layer that raw data lacks so numbers can be queried and traced from whichever model you connect.

Set the rule before the deck gets built: any number on a board slide must resolve to a system of record on request, in one step.

What should you leave out?

Rep names, activity metrics, and any chart with no decision attached.

Individual rep performance is a management topic, not a governance one, and naming reps in a board deck tends to produce direction from people three levels removed from the account. Activity metrics belong in the operating cadence. A board cares whether the revenue motion works, not how many calls were logged.

The harder cut is the chart that everyone likes and nothing depends on. Ask of each slide what changes if the number is worse than expected. When the answer is nothing, move it to the appendix and give the time back to the forecast decomposition, where the real argument about the year is going to happen.