QBR template — generate a custom one in seconds
A QBR that just recaps usage numbers reads as a status update, not a business review. Below is the structure that ties usage back to value and earns the next quarter, not just reports on the last one.
The eight slides
Built for a recurring meeting with someone who already knows your product — every slide should connect back to a goal the customer actually set, not just what you tracked.
- 01
Recap: goals from last quarter
Restate the goals the customer set last time, in their words. This slide is what makes everything after it a review rather than a report.
- 02
Usage and adoption
How the product was actually used this quarter — active users, key workflows, adoption against the plan. Contextualise every number against the goals from slide one, not in isolation.
- 03
Value delivered
Translate usage into outcomes the customer cares about — time saved, cost avoided, revenue influenced. This is the slide that justifies the spend; if you can't fill it with real numbers, that's the actual problem to solve before the meeting.
- 04
Wins and highlights
One or two specific moments this quarter — a successful rollout, a team that adopted fast, a problem solved quickly. Concrete stories land harder than aggregate metrics.
- 05
Challenges and blockers
What got in the way this quarter, named honestly, with what's being done about it. Raising this yourself before the customer does is what makes the rest of the deck credible.
- 06
What's next from us
Relevant roadmap items — only the ones that matter to this customer's use case, not the full release calendar.
- 07
Goals for next quarter
Set the goals that next quarter's review will open with. Written together with the customer in the room, not delivered to them, whenever possible.
- 08
Open discussion
A deliberate slide, not a fallback — the specific questions or asks you want input on. Ending here signals the meeting is a conversation, not a presentation.
Why this order works
- Opening on last quarter's goals, restated in the customer's own words, turns the rest of the deck into a review of a shared plan rather than a vendor status update.
- Value delivered gets its own slide, separate from usage — the two get conflated constantly, and a customer renewing on usage stats alone rarely renews twice.
- Challenges are raised before the customer has to ask, which is what makes the wins slide believable rather than curated.
- It ends on discussion, not a thank-you — the QBR's real job is setting up next quarter, not closing this one.
Common mistakes
The deck reports usage numbers without ever connecting them to a goal the customer actually set.
Open every usage slide by restating the relevant goal from last quarter, so the number has context instead of floating on its own.
Value delivered is skipped or folded into usage, so the customer is left to calculate ROI themselves.
Give value delivered its own slide with a real number — time, cost, or revenue — even if it's an estimate stated as one.
Challenges are omitted entirely, leaving the customer to raise them cold, which puts the vendor on the back foot.
Name the real blockers first, with a plan attached. It reads as more credible than a quarter with no visible friction.
The meeting ends on a roadmap slide with no space for the customer's own questions.
Add a dedicated discussion slide after the roadmap, and actually leave time for it.
See it filled in
Four versions of this structure, generated with different brand kits, so you can see how the layout holds up with real colours and a logo in it.
QBR deck generated with a neutral brand kit — screenshot pending
QBR deck generated with a bold accent-colour brand kit — screenshot pending
QBR deck generated with a logo-forward brand kit — screenshot pending
QBR deck generated with a dark-theme brand kit — screenshot pending
Frequently asked questions
The questions people ask before building this deck.
Who should present a QBR — the account manager or the customer success lead?
Whoever owns the relationship and has the most direct knowledge of the account's usage and goals. What matters more than the presenter's title is that value delivered and challenges are backed by real, specific detail rather than generic talking points.
What if usage was down this quarter?
Say so directly on the usage slide, and use the challenges slide to explain why and what's changing. A QBR that quietly reframes a bad quarter as a good one is usually the last QBR before a churn conversation.
How do I show value delivered without hard ROI numbers?
Use the best proxy available — hours saved based on typical usage patterns, or a comparable customer's measured outcome — and label it clearly as an estimate. An honest estimate is more useful than an empty slide.
Should goals for next quarter be set before or during the meeting?
Draft them beforehand as a starting point, but treat the meeting as where they get finalised with the customer. Goals delivered as a fait accompli tend to get less real buy-in than ones shaped together in the room.
Ready to generate one?
One prompt, already written for this structure. Edit it or send it as is.