The QBR Presentation That Customers Don't Dread

By the Kinsy team · Published 27 July 2026

Ask customers what they expect from a quarterly business review and you'll hear a polite version of the truth: an hour they couldn't refuse, charts they couldn't use, and a renewal conversation wearing a lanyard. It doesn't have to be that. A QBR presentation that opens with the customer's goals and closes with a co-owned plan is a meeting people defend in their calendar. Here is that structure, slide by slide, and the discipline around it.

What should a QBR presentation include?

A QBR presentation should include, in this order: a recap of the goals you agreed last quarter, outcomes measured against those goals, the usage and adoption story behind the outcomes, unresolved issues owned honestly, the parts of your roadmap relevant to this customer, and a success plan for next quarter. The order matters because it mirrors how a customer decides whether to trust the meeting: their goals first, your evidence next, your honesty after that, and the plan you'll own together at the end.

• Goals recap. Open with the goals the customer agreed at kick-off or the last QBR, in their words, not yours. If the goals have drifted, say so and re-agree them — a review against goals nobody remembers is theatre.
• Outcomes against those goals. Not activity — outcomes. What changed in the customer's business, set directly against each goal from the previous slide, including the ones you missed.
• The usage and adoption story. The evidence layer: which teams adopted what, where usage deepened or stalled, and what that pattern means. Numbers appear here as support for a story, never as the story itself.
• Open issues, owned. Tickets, escalations and misses — raised by you before the customer has to, each with an owner and a date. Nothing rebuilds trust faster than a vendor volunteering its own punch list.
• A roadmap that's about them. Only the items that touch this customer's use cases, with rough timing. The full roadmap belongs in your all-hands deck, not here.
• Next quarter's success plan. Goals, owners on both sides, dates. This is the slide the whole meeting exists to agree — everything before it earns the right to ask.

Value realised, not a feature tour

A QBR exists to answer one question: is the customer getting the value they signed up for? That makes it a different animal from the deck that won the deal — a sales deck structure is built to persuade a prospect; a QBR is built to show a customer evidence about their own business. Confuse the two and you get the three classic failures every CS leader recognises. The renewal pitch in disguise: forty minutes of value messaging that everyone in the room correctly decodes as "please sign again", which makes the actual renewal conversation harder, not easier. The generic product roadmap: the same all-hands slide every customer sees, which tells this customer they are an audience, not a partner. And metrics without meaning: login counts and API calls read aloud with no link to anything the customer is trying to achieve — activity dressed as outcome.

The fix for all three is the same: anchor every slide to the goals on slide one. A usage chart earns its place only if it explains progress, or the lack of it, against something the customer said they wanted. A roadmap item earns its place only if it changes what this customer can do next quarter. And the renewal takes care of itself when four consecutive QBRs have shown honest evidence of value — that record is the pitch.

Thirty minutes of content for a sixty-minute meeting

The length rule for QBRs is stricter than for most decks: plan half the meeting for content and leave the other half empty on purpose. The empty half is where the value is — the operator explaining why adoption stalled in one region, the sponsor thinking out loud about next year's priorities. If your deck fills the hour, the meeting was a broadcast, and a broadcast could have been an email. In slide terms that usually means a core of eight to twelve slides with anything explanatory pushed to an appendix; the general arithmetic is covered in our guide to how many slides a presentation really needs. When a section runs long, cut from the middle — the adoption detail — never from the ends, because the goals recap and the success plan are the two slides the meeting cannot work without.

The exec and the operator read different decks

Every QBR has two audiences wearing one meeting invite. The executive sponsor wants the business story: outcomes against goals, risk, where this is heading — and will forgive missing detail but not missing candour. The day-to-day operator wants the working story: which issues are fixed, what the roadmap changes for their workflow, who owns what next. The structure above serves both if you keep the altitude honest — outcomes and open issues at exec altitude in the core, operational detail in a numbered appendix you can jump to when the question comes. If the sponsor rarely attends, borrow the pre-read habit from the boardroom — the same discipline that anchors the board deck structure directors expect — and send the deck ahead with a short note flagging what you'll ask for. A sponsor who has seen the asks coming says yes in the room.

The fortnight before: a prep rhythm that holds

1. Two weeks out — reread the record. Pull up the last QBR's success plan and your CRM notes since. Every commitment made last quarter gets a status now, because the customer remembers all of them.
2. Ten days out — turn usage data into a story. Get the adoption numbers and write the sentence each chart proves. A chart you can't caption with a claim doesn't go in the deck.
3. One week out — align the account team. Support, product and sales agree the open-issues list, the roadmap items worth showing, and the asks. The QBR is where internal disagreement goes to be discovered by customers — settle it beforehand.
4. Three days out — send the agenda. A short note to your champion: what you'll cover, what you'll ask, what you'd like them to bring. Nobody useful attends a mystery meeting.
5. Meeting day — present half, discuss half. Thirty minutes through the six sections, then let the room work. The success plan gets agreed live, not emailed after.
6. Within the week — close the loop. Send the agreed plan with owners and dates. It becomes slide one of the next QBR — which is the whole point.

Your QBR already exists in your CRM

By the time a QBR lands in your calendar, most of it is already written: the success-plan doc, the CRM call notes, the support summary, the adoption export someone circulated on Monday. The deck job isn't writing — it's compression and structure, which is exactly the part that eats a CSM's evening, multiplied by every account in the book.

That's the case for the doc-to-deck route. Upload the success-plan doc and your notes (PDF, markdown or plain text) with a one-line brief — "turn this into a ten-slide QBR: their goals first, open issues owned, success plan last" — answer a few clarifying questions about emphasis and audience, and you get back a structured draft with speaker notes on every slide, exported as a native, fully editable .pptx. The same route works when the raw material is scrappier — see our guide to turning rough notes into a presentation.

Be clear-eyed about the last step: the account data is yours. Kinsy drafts the structure, the narrative and the notes; the real adoption figures and issue statuses are yours to drop in and verify before anything reaches a customer. Which is why the export format matters — every text element opens as a real, editable object, so swapping a placeholder for the actual number is a ten-second edit in PowerPoint, not a fight with a flattened image. If you're weighing tools for this, start with the ones that pass the editability test in our roundup of AI presentation makers that export truly editable .pptx files.

Keep reading

• The best AI deck maker in 2026: the full field test
• Turning a document into a deck with Kinsy
• Kinsy pricing — plans and credits