What Should be in a QBR Presentation?
A Guide To Optimizing Quarterly Business Reviews
It Comes Down To Who Carries The Deck Out Of The Room
Renewal decisions are rarely made in a meeting with the vendor. They are made afterward, in a budget review or a consolidation exercise, where a champion has a few minutes to defend a line item to someone who has never used the product and is looking for things to cut.
That moment is what the presentation is for. Every slide should be judged by whether it helps the person in that room, holding a forwarded file, with no one from the vendor available to explain it. A slide that only works while someone is narrating it does not survive the trip, and the trip is where the decision happens.
Applied honestly, that test clears out a surprising amount. A roadmap preview is interesting in the meeting and indefensible in a budget conversation. A feature summary describes what the vendor did rather than what the customer got. An agenda slide consumes the one minute when attention is highest. What remains is a short list of things that can be repeated secondhand by someone who is not a product expert, which is a far more useful description of a QBR deck than any standard template.
Open With What The Customer Said They Wanted In Their Words
The first substantive slide should be the customer’s own objectives, in the customer’s own words, from whenever they last stated them: the original evaluation, the last review, the kickoff, an email from the VP who sponsored the purchase.
Doing this changes the character of everything after it. The meeting stops being a vendor reporting on itself and becomes an assessment against a standard the customer set. It also disarms the most common failure mode in these meetings, which is a room full of people quietly holding different definitions of what success was supposed to look like.
It requires that someone wrote the objectives down and kept referring to them, which is where a lot of account teams discover a gap. Objectives captured during a sales cycle tend to live in a CRM field nobody reopens, and by the third quarterly review the only version in circulation is whatever the account manager remembers. The teams that do this well treat the objectives as a maintained artifact carried forward from one review to the next, not as something reconstructed each quarter from memory.
Results Earn Slides; Activity Earns An Appendix Section
The largest section of most review decks is usage data, and usage data is not a result.
Logins, sessions, assets created, adoption percentages. All real, all worth tracking, and none of them what the customer bought. They describe consumption. A high login count in a quarter where nothing improved is evidence of a habit, not a return, and a customer under budget pressure will read it that way.
What belongs on the slide is the translation: the cycle that got shorter, the work that stopped being duplicated, the response that took three days and now takes one, the team that expanded output without expanding headcount. The underlying usage figure can sit beneath it as support, which is the correct relationship between the two. Ticket volumes, feature releases, and detailed adoption breakdowns go into a written appendix for the people who want them, and out of the presentation entirely.
Where the honest translation is thin, the better move is to say so. A review claiming transformation off a quarter of modest adoption teaches the customer to discount everything else in the document. A review that says adoption concentrated in two teams, that those two teams show a measurable change, and that next quarter is about the other four, is more persuasive. Partly because it is true, and partly because it gives the champion something specific to defend rather than a claim taken on faith.
The Contract Belongs in the Deck
The slide most often missing is the one covering the contract itself: what is in it, when it ends, what has been added, what the renewal timeline looks like, and what is under discussion.
Account teams leave it out because it feels like selling in a meeting meant to be about value. The effect is the opposite of the one intended. A champion who has to go and look up a renewal date, or who does not know that a contract feeds into a procurement review starting in six weeks, cannot advocate on a useful timeline. Putting it in the deck is not a pitch. It is the information the internal advocate needs to do their part before the decision window closes.
This is also where any expansion conversation belongs, framed against the objectives from the opening slide rather than as a separate pitch attached to the end of a review.
Build it for the Entire Buying Comittee
Account teams build these decks for the people they talk to every week, and then the meeting fills with people who have never seen the product. Executive sponsors change. Reorganizations move the relationship under a new leader. A finance business partner joins because the contract is in a review cycle. Someone forwards the invitation.
The result is a room operating at two or three different levels of context at once, and a fixed linear deck can serve only one of them, usually the wrong one, because it was built for the day-to-day contacts who need it least. Material that can be navigated handles this in a way a sequence cannot. When a new executive asks a question that belongs to slide nineteen, the answer should be a jump rather than a promise to follow up. When a finance lead wants the commercial picture and nothing else, that should be reachable without scrolling past six slides of adoption detail.
The same pressure applies after the meeting, more severely. A file emailed afterward is frozen at the moment it was sent. Its figures age, its commitments fall out of date as they are completed, and the version a champion forwards into a budget conversation in month three describes a quarter that has since ended. Meanwhile the account team has no idea whether it was opened, by whom, or which section held attention, which is why follow-up so often defaults to a generic check-in, and why the first real signal about a renewal frequently arrives too late to act on.
Three questions are worth asking of any review material. Whether it stays current after it is sent, so the champion is never defending a stale number. Whether it can be navigated by someone arriving with one specific question and no context. And whether it reports anything back, because knowing a deck was reopened twice and forwarded to someone in finance is a different situation entirely from knowing an attachment left the building.
Those three are the reason the strongest quarterly reviews have moved off the static file. Account teams running them in DIGIDECK are working from a presentation that updates after it is sent, opens to whatever section the room asks about, and shows who opened it and what held their attention once the meeting is over
Closing
Quarterly Business Reviews are a key part of most teams’ business. They support adoption, strengthen relationships, and help retain revenue by showing customers the value your team is delivering.
That’s why it’s worth putting some thought into what goes into your next QBR. Start with the customer’s own words to open the conversation and remind them why the work matters. From there, include the key results and metrics that demonstrate the value you’ve delivered. Finally, make sure your QBR works for you even when you’re not in the room. It should be easy to digest, understand, and share without you there to walk someone through it.
Follow these steps and your QBR becomes more than a meeting. It becomes a tool that reinforces your value long after the conversation ends.