A quarterly business review (QBR) is a scheduled meeting, usually 60 to 90 minutes, where a vendor and a customer review progress against the customer goals set the previous quarter, quantify the value delivered, surface what is blocked, and agree on three to five measurable goals for the next 90 days. A QBR that reviews your product roadmap instead of the customer results is not a business review. It is a demo with a nicer name.
Most QBRs fail for the same reason: they are built around the vendor. The deck opens with a company update, moves to feature releases, shows a usage chart, and closes with an upsell slide. The customer sits through 45 minutes of content that answers questions they never asked. They accept the next invitation out of politeness, then stop accepting it.
A QBR earns its place on a busy executive calendar only if the customer leaves with something they could not have produced themselves: a clear read on whether the investment is working, and a decision about what happens next.
What is a quarterly business review?
A QBR is a structured checkpoint between a vendor and a customer, held roughly every 90 days, that reviews outcomes rather than activity. It has three jobs. It proves or disproves the business case the customer used to buy. It exposes risk early enough to act on. It sets the next quarter goals, with named owners on both sides.
In customer success, the QBR is where renewal risk becomes visible while there is still time. In sales and account management, it is where expansion gets qualified honestly instead of guessed at. In professional services, it is where scope, delivery, and satisfaction get reconciled before they turn into an escalation. Same meeting, different emphasis.
What should be included in a QBR?
Six things, in this order. Everything else is optional.
- The goals the customer set last quarter, restated in their words, not yours.
- Performance against those goals, in the customer metrics: hours saved, cycle time, error rate, revenue, tickets deflected. Product usage is evidence for this, never a substitute for it.
- What got in the way, including the things your side got wrong. Owning a missed commitment buys more credibility than any green dashboard.
- Adoption and health, told as a story about who is using it, who is not, and why that matters to the outcome.
- Next quarter goals, three to five, measurable, co-created in the room rather than presented.
- Actions, with a named owner and a date on both sides.
Notice what is missing. There is no company update, no roadmap tour, and no pricing slide. Roadmap belongs in the meeting only where it unblocks a goal the customer already named.
What is a good QBR agenda?
Ninety minutes, front-loaded with the customer, back-loaded with decisions. The single most useful structural choice is to put the discussion before the deck.
| Segment | Minutes | Who leads | Output |
|---|---|---|---|
| Where we were: goals set last quarter | 5 | Vendor | Shared starting point, no surprises |
| Customer update: what changed in their business | 10 | Customer | Context that reframes everything after it |
| Results against the business case | 20 | Vendor | Agreement on what the investment returned |
| Adoption, health, and where value is blocked | 15 | Both | Named blockers with a cause, not a symptom |
| What we got wrong and what we are doing about it | 10 | Vendor | Credibility, and a plan with a date |
| Next 90 days: co-create three to five goals | 20 | Both | Measurable goals with owners |
| Actions, owners, dates | 10 | Both | A written list, read aloud before anyone leaves |
Send the agenda 24 to 48 hours ahead, along with the results section. If the numbers arrive in the room for the first time, half the meeting is spent processing them. If they arrive in advance, the meeting is spent deciding what to do about them.
How long should a QBR be?
Sixty to ninety minutes. Ninety is the practical ceiling before attention collapses, and 60 is enough for any account below a few hundred thousand dollars in annual value. If you cannot cover results, blockers, and next-quarter goals inside 60 minutes, the problem is usually that the results section is a usage dashboard rather than a business outcome, and nobody can tell what it means.
How often should you run a QBR, and for which accounts?
Not every account earns a quarterly meeting, and pretending otherwise is how customer success teams burn a third of the year building decks. Tier the cadence.
| Tier | Typical profile | Cadence | Format |
|---|---|---|---|
| Strategic | Top accounts by revenue or logo value, exec sponsor present | Quarterly, live | 90 minutes, on site or video, exec attendance both sides |
| Managed | Mid-market, named CSM, real expansion surface | Twice a year, plus a written update in the off quarters | 60 minutes, video |
| Scaled | Long tail, no named CSM | Annual, or triggered by a health score drop | Automated written review, live meeting only on risk |
The trigger row matters most. A scaled account whose health score falls two bands in a month deserves a live conversation more than a strategic account cruising at 95 percent adoption does.
What goes in a QBR deck?
Ten slides, maximum. If a slide does not change a decision, cut it.
| Slide | Content | The test it has to pass |
|---|---|---|
| 1. Agenda and attendees | Sections, timings, who owns what | Sent 48 hours early |
| 2. Last quarter goals | The three to five goals, verbatim | Quoted from their words, not paraphrased |
| 3. Scorecard | Each goal marked hit, partial, or missed | At least one honest miss, if there was one |
| 4. Business impact | The customer metric: hours, dollars, cycle time | A number their CFO would recognize |
| 5. Adoption | Who is using it, by team, over time | Explains the number on slide 4 |
| 6. Where value is blocked | Two or three blockers with root causes | Each has a named owner |
| 7. What we got wrong | Missed commitments, and the fix | Specific, dated, no hedging |
| 8. Next 90 days | Draft goals, presented as a starting point | Editable in the room |
| 9. Actions | Owner and date, both sides | Read out loud before close |
| 10. Appendix | Ticket volume, releases, raw usage | Never presented, only referenced |
Slide 4 is the one that carries the meeting. Everything else supports it. If you run a services or delivery business, the adoption and impact sections should be generated from the system where your projects and resourcing are actually tracked, rather than rebuilt by hand in slides the night before, because hand-built numbers drift from the numbers the delivery team is working to, and customers notice.
Quarterly business review examples
A software vendor selling to a mid-market operations team. Last quarter the customer set one goal: cut invoice approval time from nine days to four. The scorecard shows 5.1 days, a miss. Slide 6 explains why: two of five approvers never activated, so every invoice above $10,000 still routed through the CFO. The action is not a training webinar. It is a change to the approval matrix, owned by the customer controller, due in three weeks. Next quarter goal: 4.0 days, with a second metric for the share of invoices that clear without an exception. That is a QBR that will be attended again.
A services firm reviewing a delivery account. The goal was two campaigns shipped per month. Actual: 1.4. The blocker is that the client took an average of 11 days to approve creative. The vendor owns their half, a slow first draft, and proposes a standing 30-minute weekly review to compress the approval loop. The client leaves with a commitment of their own, which is the point.
An account heading for churn. The executive sponsor changed in month two and has never attended. Usage is flat, support volume is low, and everything looks fine, which is exactly the profile of a quiet loss. The right QBR opens by naming it: we have not met your new sponsor, and we do not know what success looks like for them. Half the meeting is spent rebuilding the business case from scratch. No results slide will save an account whose buyer left.
How do you prepare for a QBR?
Preparation is roughly three hours for a strategic account, and it is mostly not deck work.
- Pull the numbers first, then decide the story. Not the reverse. If the quarter went badly, the story is the plan, not the spin.
- Read last quarter action list. Anything you committed to and did not deliver goes on slide 7 before the customer raises it.
- Check the sponsor is still there. Sponsor turnover is the leading cause of silent churn in B2B, and it is invisible in usage data.
- Pre-align internally. Sales, support, and delivery should agree on the risks and the ask before anyone joins the call.
- Pre-share the results section. Surprise is not a presentation technique.
- Write the one-page recap before the meeting. You will only need to correct it afterwards, and it forces you to know what outcome you want.
Send the recap within 24 hours. A QBR whose actions are not written down within a day did not happen.
What should you never do in a QBR?
Open with a company update. Lead with product usage as if it were a result. Bury a missed goal in an appendix. Present next quarter goals as finished rather than co-creating them. Bring an upsell to a meeting where the customer is unhappy, which converts a recoverable account into a lost one. And never, in a review of the customer business, spend more time on your roadmap than on their outcomes.
One more: do not run a QBR without knowing the account health going in. Walking into a review blind, then discovering in the room that the sponsor is disengaged, wastes the one meeting a quarter where you had their attention.
How do you measure whether QBRs are working?
QBRs are an expensive motion, so treat them like one. Three measures tell you if they pay for themselves.
- Action completion rate. The share of QBR actions closed by their due date, tracked on both sides. Below 60 percent, your QBRs are theater.
- Health score movement. Accounts that hold a QBR should show a measurable change in health within 60 days. No movement means the meeting did not change what anyone did.
- Retention and expansion in the reviewed cohort. Compare renewal and net revenue retention for accounts that held QBRs against comparable accounts that did not. The lift, or the absence of it, is the honest answer to whether the motion deserves its headcount.
The rest of the picture comes from the metrics you already run. Renewal rate and churn rate tell you the outcome. Support metrics tell you whether the account is quietly grinding through friction between reviews. And the goals themselves should trace back to whatever the customer was trying to accomplish when they bought, which is why mapping the B2B customer journey is worth doing before you design the QBR, not after.
Run properly, the QBR is the one recurring forum where retention stops being a metric on a dashboard and becomes a conversation with the person who decides. That is the same reason it belongs at the center of a B2B retention program rather than at the edge of it.