Why is a usage recap a weak QBR agenda?

Usage figures are already available to the customer in the product, so a meeting built around them exchanges nothing for the customer's time. It also makes usage the topic when the customer's actual question is what the spending produced.

What can a vendor provide in a QBR that the customer cannot self-serve?

An outside view is the main one — how comparable organizations approach the same problem and where this deployment sits relative to those patterns. Customers cannot generate cross-organization perspective from their own data.

Should expansion be discussed during a QBR?

Raising expansion immediately after presenting value makes the value claim read as a setup for a sale. Separating the two keeps the review credible, and expansion discussions land better when the customer raises the need.

Why most QBRs are a reporting ritual and what makes one worth the hour

Guide · customer-success · 4 min read · last verified 2026-07-21

Reviewed before publication Editorial board Independent commercial review

In shortA usage recap gives customers nothing they cannot pull from a dashboard. A QBR affects renewal only when it delivers outcomes, an outside view, decisions, and material the sponsor can carry into a budget review.

A quarterly business review earns a renewal when it gives the customer something they cannot produce for themselves — an outside view of their own position, a decision they need to make, or evidence they can carry into an internal budget conversation — rather than a recap of usage data the customer already has access to.

Why the usage recap fails

The standard QBR opens with adoption charts: seats provisioned, logins, features used, tickets resolved. Every one of those numbers is available to the customer in the product, on demand, without a meeting.

That structure creates three problems.

It offers nothing in exchange for the customer's time. A meeting whose content is retrievable from a dashboard is an imposition dressed as a service.
It invites the wrong conversation. Presenting usage numbers makes usage the topic, and usage is a metric the vendor cares about more than the customer does. The customer's question is what the spend produced.
It generates no artifact. The sponsor leaves with nothing to forward, so the meeting contributes nothing to the internal case for renewal.

The failure is sharpest when the room has changed. A new budget owner sitting through a usage recap learns that the vendor tracks logins carefully and cannot articulate what the contract bought.

What the meeting must deliver

A QBR that affects a renewal outcome supplies at least one of four things the customer cannot self-serve.

Outcomes tied to the customer's own objectives. Not what the product did, but what changed in the customer's operation as a result — work absorbed, cycle time reduced, decisions made differently. Stated in the customer's terms and, where possible, confirmed by the customer's own people.
An outside view. How this customer's approach compares to how other organizations solve the same problem, what patterns the vendor sees across its base, and where this deployment sits relative to that. This is the one category the customer structurally cannot generate alone.
Decisions that need to be made. Specific choices with owners and dates: whether to extend to a second team, whether to retire a workaround, whether to resolve a data dependency blocking a use case. A meeting that produces decisions is worth attending.
Material for the internal case. A short written record the sponsor can send upward without editing, covering what was delivered, what it displaced, and what is planned. Most renewal conversations happen in rooms the vendor is not in, and this is the only thing that travels into them.

Structuring the meeting

The order matters, because attention is highest at the start and the first topic signals what the meeting is about.

Open with the customer's objective, not the vendor's data. Restate what the customer set out to achieve, in their own words, and address it directly. If nobody in the room can state the objective, that discovery is more valuable than anything else on the agenda.

Present outcomes before activity. Activity data belongs in an appendix, used to support an outcome claim, not as the opening act.

Name what has not worked. A QBR that reports only success is read as a sales meeting. Naming a use case that stalled, with a proposal for what to do about it, establishes that the assessment is honest — which makes the positive claims credible.

Bring one thing they did not know. A pattern across similar organizations, an emerging shift in how the problem is being solved, a capability their peers use that they do not. This is what distinguishes the meeting from a report.

Close with decisions and owners. Every item that leaves the room should have a name and a date attached.

Who needs to be there

The composition of the room determines whether the meeting can do anything.

The budget owner attends the meeting where the case is made, or the case does not reach them. If they never attend, the QBR is briefing people with no authority over the outcome.
The daily users supply the dependency evidence. They know what breaks without the product, and their account is more persuasive than the vendor's.
New arrivals matter most. Anyone who joined since the purchase has no context, and the QBR is the mechanism for supplying it before a renewal forces the question.

Mapping who actually decides is the same exercise as mapping a buying committee during a sales cycle, and a renewal is a purchase decision with an incumbent.

What to stop doing

Stop running QBRs quarterly by default. Cadence should match the customer's decision rhythm. A meeting held because the calendar says so, with nothing substantive to cover, trains the sponsor to decline.
Stop leading with the roadmap. Future capability is a reason to keep paying only after present value is established. Leading with it implies the present is thin.
Stop asking for expansion in the same breath as reporting value. Blending the two makes the value claim read as a setup, and reframes a review as a sales call.
Stop treating attendance as the outcome. A well-attended meeting that produces no decision and no artifact has not moved the renewal.

The test for whether a QBR did its job is simple: after the meeting, could the sponsor defend the renewal in a budget review without the vendor present, using material the meeting produced? If not, the meeting was a status update. Renewals are decided by whether the account has an internal advocate holding evidence, and the QBR is the recurring opportunity to supply both. Accounts where that evidence exists convert more reliably at renewal and expand on the customer's own initiative, which is the mechanism that lifts net revenue retention rather than merely protecting recurring revenue already booked.