How to Run a Customer QBR

What is a customer QBR supposed to accomplish?

A customer QBR confirms the account is getting the outcome it bought, and surfaces renewal risk while there is still time to fix it.

Two failure modes are common. The first is the product update meeting, where the vendor presents a roadmap and the customer nods. The second is the relationship check-in, where everyone agrees things are going well and nothing is written down. Neither produces information you can forecast against.

A QBR that works answers one question for the customer: are they better off than they were before they bought, in numbers they recognize. It answers a second question for you: what would have to be true for this account to renew and grow.

Which accounts should get one?

Tier the base and match the format to the tier, because preparation is the scarce resource. The override row is the one that gets ignored. A tier 3 account showing risk signals needs a real review more urgently than a healthy tier 1 account on its normal cycle.

What should the agenda be?

Sixty minutes, with the majority of it spent on their results rather than your product. Put the commercial block on the agenda from the start. Customers find a surprise pricing conversation in the last five minutes more objectionable than a scheduled one.

What data should you bring?

Bring their numbers, not your dashboard.

The QBR pack should contain the outcome metrics that were agreed when the deal was signed, measured the same way both times. If no one wrote those down at purchase, that is the first thing to fix, because a QBR without a baseline degrades into opinions about whether things feel good.

Add adoption by team so the conversation can get specific. An account at 80 percent adoption in one department and near zero in three others is a churn risk wearing a healthy aggregate number. Then bring the commitment list from the last review with a status against each item. Nothing damages a QBR faster than a customer remembering a promise the vendor has forgotten.

Which signals tell you the account is at risk before the meeting?

Support case volume is one of the most useful early signals, and it reads in both directions.

ORM data shows accounts with no support cases at all are at risk. Silence usually means nobody is using the product deeply enough to hit friction. Accounts filing seven or more cases in a year are also at risk, for the obvious reason. Accounts filing three to five ordinary tier 2 or tier 3 cases are the healthiest group, because those customers are engaged, getting help, and generally satisfied.

Three other signals belong on the pre-meeting sheet:

- The executive sponsor changed roles or left the company. - The economic buyer declined the last two review invitations. - Usage is flat or declining while the contract value is flat.

Any of those move the account into the risk override tier regardless of size.

How does the QBR feed the renewal forecast?

Every QBR ends by changing a field, not by producing a recap document.

Three outputs are mandatory. The renewal category gets set or confirmed based on what was said in the room. The renewal date is verified against the contract rather than against memory. And any expansion discussed becomes a real opportunity record with an owner, an amount, and a close date, because expansion that lives only in a QBR summary never gets forecast and never gets worked.

That discipline is what connects customer success activity to net revenue retention. Retention numbers move because specific accounts expanded or contracted, and the QBR is where you learn which way an account is heading with enough runway to change it. Renewal risk identified 90 days out is workable. Risk identified in the renewal month is a negotiation about discount.

It also improves a number most teams never measure. Renewals are usually carried as an assumption rather than inspected like new deals, and forecast accuracy follows inspection. QBR evidence is what lets you move a renewal category on something other than sentiment.

What should happen after the meeting?

A written recap inside 24 hours, with owners and dates against every commitment.

Use the same structure every quarter. List what was agreed, then list what each side owes with a name and a date against every item. Put the next review date at the bottom and send it to everyone who attended, plus the economic buyer if they missed it.

Then close the loop internally. Feed the risk signals and the outcome data into your renewal review so the account shows up in your monthly numbers rather than sitting in a customer success tool that nobody reads during forecasting. A QBR that never reaches the revenue conversation is a meeting the customer paid attention to and you did not.