How to Build a Quarterly Business Review Deck People Actually Read

Picture a 43-slide QBR deck. By slide 12 the VP is answering email. By slide 30 someone asks “wait, are we ahead or behind on the thing we started with?” Nobody remembers slide 3.

That is the problem with many quarterly business review decks. They try to document everything and end up communicating nothing. My opinion is that a good one has the same bones: five sections, twelve slides at most, and one number that survives the meeting.

Here is the structure I recommend.

Start With the Number, Not the Agenda

Slide one is not an agenda. It’s the single number that matters this quarter, big, alone, on the slide.

Not three numbers. Not a KPI dashboard with 14 tiles. One number: revenue growth, churn rate, active users, whatever the quarter actually turned on. If the room only remembers one thing when they leave, this is it.

Pick the number before you build anything else. If you can’t pick one, you don’t understand the quarter yet, and no deck will fix that.

What Changed (2-3 Slides)

This section is facts, not narrative. What moved, up or down, since last quarter. Cap yourself at 3 metrics total across these slides. That feels stingy after a whole quarter of work. It is stingy on purpose.

A chart with 9 lines on it is not information, it’s wallpaper. Pick the 3 metrics that connect to the headline number and show them clearly. Everything else goes in an appendix nobody opens during the meeting but everybody can find later.

For a B2B SaaS quarter, that’s usually: the headline number, one leading indicator (trials started, demos booked), and one lagging cost (CAC, support ticket volume). Three numbers, three slides, done.

What We Learned (2-3 Slides)

This is where most decks either go soft (“great progress, lots of momentum!”) or go into denial. Neither works. State what surprised you. State what you got wrong.

Write this section as if you are explaining it to yourself three months ago. What would you tell that version of you? Make it specific. Two made-up examples: “the pricing page redesign didn’t move conversion, the checkout flow did” or “the feature we thought was the differentiator, customers didn’t mention it once in 40 calls.”

One slide per lesson. If you have more than 3 real lessons, you had a chaotic quarter and that’s fine, say so. If you have zero lessons, you weren’t paying attention.

What We Do About It (2-3 Slides)

Learnings without actions are just complaints with better formatting. Each lesson from the previous section gets a corresponding action here, or it doesn’t belong in the deck.

Be concrete. “Improve onboarding” is not an action, it’s a wish. “Cut the signup form from 7 fields to 3, ship by end of next month” is an action. The room should be able to check this slide again next quarter and know immediately whether it happened.

A vague action can repeat quarter after quarter. Nobody calls it out when it sits buried in slide 27.

The Ask (1-2 Slides)

Close with what you need. Budget, headcount, a decision, a green light on something risky. Not “questions?” Not a thank-you slide. An actual ask, stated as a sentence you could put in an email.

If you don’t have an ask, you probably didn’t need the meeting, an email would have done the job. That’s a real possibility and it’s fine to notice it.

Twelve Slides Is a Discipline, Not a Suggestion

Add it up: 1 headline + 3 for changes + 3 for learnings + 3 for actions + 2 for the ask, and you’re at 12. That’s the ceiling, not a target to fill.

The discipline isn’t about slide count for its own sake. It’s that every slide you add past 12 is competing with the headline number for the room’s attention, and in my experience of watching decks, attention drops as the count rises. Cutting hard is how you protect the one thing you actually wanted people to remember.

Write the QBR as a plain text file first, with the five headings above, before you touch a slide tool. I build Slaide, which keeps a deck as a plain-text source file. You can commit the QBR text to git and diff Q2 against Q3 like any other change. It is not a fit for every team’s workflow. But for one person tracking the same five sections quarter over quarter, the diff of “what we learned” can be worth more than the deck itself.

Whatever tool you use, the sequence matters more than the software: pick the number first, write the text, then build slides around it, not the other way around. The deck people remember is the one where the sentence still makes sense a week later, without the deck.