How to Build a Quarterly Business Review Deck People Actually Read

I sat through a 43-slide QBR deck last quarter. By slide 12 the client’s VP was answering email. By slide 30 someone asked “wait, are we ahead or behind on the thing we started with?” Nobody remembered slide 3.

That’s the problem with most quarterly business review decks. They try to document everything and end up communicating nothing. After 15 years of consulting for companies like L’Oreal and BASF, I’ve built more QBR decks than I want to admit, and the good ones all share the same bones. Five sections. Twelve slides, maximum. One number that survives the meeting.

Here’s the structure I use now, every time.

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. I know that feels stingy after a whole quarter of work. It’s 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.

I write this section as if I’m explaining it to myself three months ago. What would I tell that version of me? Usually it’s something specific: “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.

I’ve watched teams present the exact same “we’re improving onboarding” action three quarters running. Nobody called it out because it was buried in slide 27 the first time and nobody remembered it existed.

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 it usually wins that fight for about 90 seconds before everyone tunes out anyway. Cutting ruthlessly is how you protect the one thing you actually wanted people to remember.

I write these QBRs as plain text files first, structured with the five headings above, before I touch a slide tool. I build the actual deck in Slaide, which keeps decks as markdown-like source files, so I can commit the QBR text to git and diff Q2 against Q3 like I’d diff any other change. It’s not a fit for every team’s workflow, but for a solo consultant tracking the same five sections quarter over quarter, seeing the literal diff of what changed in “what we learned” is worth more than the deck itself some quarters.

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.