How to build a QBR deck (slide by slide)

A quarterly business review deck is a 10 to 15 slide presentation that proves the value an account received last quarter and asks the customer for a specific decision about the next one. It is not a status update, and it is not a design exercise. It is a renewal argument.

Most QBR decks fail for one reason: the person building it spends four hours hunting for data across the CRM, the product analytics tool, the support desk and last quarter's email threads, then has forty minutes left to actually think. The slides end up describing activity instead of proving outcomes.

This guide walks through the 10 slides that carry a QBR, what belongs on each one, and, more usefully, which system each slide's data comes from. Here is how to build it.

What is a QBR deck?

A QBR deck is the slide document that structures a quarterly business review, the recurring strategic meeting between a vendor's account team and a customer's decision makers. It covers what was delivered, what it was worth in the customer's own numbers, what went wrong, and what happens next.

QBR stands for quarterly business review. The meeting usually runs 45 to 60 minutes and involves the customer's economic buyer, the day to day users, and often an executive sponsor. The deck exists to keep that conversation anchored in evidence rather than impressions.

Three things it is not:

• A check-in. Weekly and monthly calls handle operations. The QBR is strategic and quarterly.
• A product demo. If the customer still needs a demo, they are too early in adoption for a QBR.
• A renewal pitch. By the time you pitch renewal, the decision is largely made. The QBR is where the case gets built, quarter after quarter.

QBR vs EBR vs monthly review

The three formats get confused constantly, mostly because they share content. They differ on audience, cadence and altitude.

The practical rule: if the most senior person in the room owns the budget, you are running an executive business review, and the deck should lose half its operational detail. If the most senior person owns the workflow, it is a standard customer QBR.

Who actually reads your QBR presentation

Nobody reads all of it. The economic buyer opens the file five minutes before the call and skims four slides. The exec sponsor reads the cover and the asks. Designing for the power user, who already believes in you, is the most common structural mistake in QBR presentations.

This matters because it changes what goes where. If the value realization number is on slide 9, the person who signs the renewal will never see it. Front-load the proof, put the detail in an appendix, and accept that a well built deck has to work at speed-read pace before it works at presentation pace.

There is a trust dimension too. Research from Oracle found that 72% of senior decision makers say information overload, or mistrust in the data itself, delays their decisions. A dense dashboard screenshot does not read as rigor to an executive. It reads as a reason to postpone.

The bar is also higher than it used to be. Salesforce's State of Sales research found that 87% of business buyers expect the people selling to them to act as trusted advisors rather than vendors. A quarterly review is where that expectation gets tested in public, in front of the person who controls the budget. QBR slides that only report what your product did, without interpreting what it meant for the account, fail that test quietly.

The 10 slides that carry a QBR deck

Below is the core structure, in order. Ten slides carry the meeting; anything else belongs in an appendix you may never present. For each slide, the difference between the weak version and the strong version is almost always the same: the weak version reports activity, the strong version reports outcomes with a number attached.

Anything that does not earn a place in those ten goes into an appendix: full dashboards, the complete roadmap, integration architecture, SLA detail. You may never present it, and that is the point. It exists so that the one executive who asks a detailed question gets an answer in the room instead of a follow-up email three days later.

Four of these ten do most of the work.

Slide 3, value realization

This is the slide the economic buyer reads. Three or four metrics, each tied to a dollar figure or a percentage their own CFO could repeat in a budget meeting. Volume metrics belong in the appendix. "We processed 14 million API calls" is your number. "The consolidation removed 1.5 FTE from the operations team" is theirs. Lead with theirs.

Slide 4, adoption trend

Adoption is the leading indicator of renewal, so this slide needs a quarter over quarter shape, not a single figure. And it needs a causal sentence next to the chart. Seat utilization moving from 62% to 87% means nothing on its own. Seat utilization moving from 62% to 87% after the procurement team onboarded in April is an argument.

Slide 6, what did not go well

Covered in detail below, because it is the slide most teams delete and the one that buys the most credibility.

Slide 10, the asks

Two or three decisions, each with a named owner and a date. Without this slide, the meeting is a status update with better graphics. With it, the meeting produces something. Read each ask out loud at the end and get a verbal yes or a clear next step before anyone leaves the call.

Where each slide's data actually comes from

This is the part most QBR guides skip, and it is the part that consumes the hours. Every slide in the deck is downstream of a system your team already uses. Knowing the mapping turns deck building from a research project into an assembly job.

Two sources on that list are consistently underused.

Call transcripts. The goals the customer stated in the discovery call, in their own words, are the exact framing your value realization slide should use. Most teams paraphrase those goals into vendor language and lose the resonance.

The original proposal. Whatever you promised when the deal was signed is the benchmark the customer is quietly measuring you against. Pulling the success criteria from the original proposal or RFP response and restating them on slide 2 is the single fastest way to make the deck feel like a continuation of the relationship rather than a fresh sales motion.

Pulling all of this by hand is why the average deck takes half a day. Connecting the systems directly is the alternative: Cobl reads from Salesforce, Gmail, Notion, SharePoint and Teams, and assembles the deal context before you open a slide. If your account data lives mostly in the CRM, the mechanics of pulling proposal and account data straight from your CRM apply identically to QBR material.

What to put in your QBR deck when the quarter went badly

Include the bad quarter. Explicitly, on its own slide, with the number, the cause and the correction.

This runs against a lot of published advice, which suggests steering away from negatives and leading with wins. That advice is wrong for one practical reason: your customer already knows. They filed the tickets. They sat through the outage. A deck that shows nine green slides and no acknowledgment of a March that everyone remembers as painful does not read as positive. It reads as either uninformed or evasive, and both cost you the benefit of the doubt on every other claim in the deck.

The format that works is three sentences:

1. The number. "Support response times averaged 14 hours in March against our 8 hour target."
2. The cause, stated plainly. "We lost two support engineers in February and backfilled slowly."
3. The correction and the current number. "Three engineers started in April. The June average is 6 hours."

That structure gives the customer something to defend internally when their own leadership asks about the relationship. It also makes your positive slides believable, which is the actual return on the honesty.

One caveat: this slide requires that the correction is real. A "what did not go well" slide with no corrective action underneath it is worse than omitting the topic, because it documents a problem you are not fixing.

How to build every QBR deck in under an hour

The structure above is the easy part. The hard part is producing it thirty or forty times a quarter, across a team, without the quality collapsing on the accounts that get built last on a Thursday night.

The consistency problem

Generic AI tools make this worse, not better. They widen the gap between your strongest and weakest builders: a senior CSM who prompts well gets a usable draft, a new hire gets something off-brand that needs rewriting. What account teams need is the opposite, a repeatable standard where a junior rep and a ten year veteran ship the same structure, the same brand, the same level of proof.

That is a control problem rather than a generation problem. Randstad ran into it at scale across document production and solved it with modular, purpose-built applications instead of open-ended prompting. Their innovation director, Pascal Mathieu, put it this way: "We chose Cobl for its extreme modularity which enabled us to create tailored AI applications for document creation. We now have unique, adaptable apps which are widely acclaimed by our 2000 consultants." The outcome was an 80% reduction in production time and roughly 55,000 euros saved per month. Free Pro described the same benefit from the content control angle: documents that are finally unique and controlled rather than generically assembled.

The workflow

Four steps, and the first one is the only one that takes real thought:

1. Connect the sources once. CRM, mailbox, notes, files. This is setup, not per-deck work.
2. Generate the structure. Point the tool at the account and the quarter. You want a draft that already maps to the 10 slide skeleton above, populated with real figures, not a blank template.
3. Refine in plain language. Rewrite the asks, sharpen the success story, adjust the tone for a technical versus a commercial audience. Chat-based editing is faster than slide surgery.
4. Export. PowerPoint for the meeting, PDF for the follow-up, a shareable link for the stakeholders who could not attend.

Two things to hold onto here. First, the human step is not optional. AI drafts get numbers into the right slots; a person still decides which three metrics carry the renewal argument and whether the ask is the right ask. That judgment is the job. Second, you are putting customer data into a tool, so check where it lives and what happens to it. Cobl runs on European infrastructure with no model training on your content, which is documented on the security page.

Build your next quarterly business review from the deal, not from a blank slide

The teams that run QBRs well are not better at slide design. They have removed the four hour data hunt that sits between the account and the deck, which leaves the time for the part that actually decides the renewal: choosing what to prove and what to ask for.

Cobl connects to the tools where your deal context already lives and generates the deal materials that move accounts forward, from proposals and RFP responses through to QBR decks, exported as PowerPoint, Word or PDF and on-brand by default. Try Cobl for free.