How to run a quarterly business review (QBR)

A QBR exists to align on business outcomes with the people who control the budget. It is not product training, not a support status update, and not a feature roadmap presentation — those are all legitimate meetings with different names and different audiences.

The distinction matters because it determines the content. If the meeting is about outcomes, then the slides report progress against goals the customer stated, measured in the customer's own metrics. Tickets closed, features shipped, and logins recorded are vendor activity, and reporting them signals that you have not connected your work to anything the customer cares about.

The single best test: could your contact forward this deck to their CFO to defend the renewal? If not, rebuild it.

Open by restating the goals agreed last quarter, in the customer's words. This frames everything that follows and immediately surfaces any drift in what they are trying to achieve.

Report progress against each goal using their metrics, not yours. If they said they wanted to cut onboarding time, show onboarding time — not your product's adoption rate.

Name what did not go well before they raise it. Counterintuitively this is the highest-credibility moment in the meeting, and it makes everything else you say more believable.

Surface open risks and blockers explicitly, including ones on their side. Then agree two or three priorities for next quarter with named owners and dates on both sides. Close by asking who else internally should see this — that question is how you build the multi-threading that protects the account.

The economic buyer or an executive sponsor. Without them, you are having an operational check-in with someone who cannot authorize a renewal or an expansion, and who probably already knows everything you plan to say.

If you cannot get an executive to attend, treat that as a significant risk signal rather than a scheduling inconvenience. It usually means your value has not reached the level where it registers as strategic — which is exactly the condition under which budgets get cut.

Bring your own executive occasionally, particularly for large or strategic accounts. Peer-level presence changes what gets said and creates a relationship that survives your own role change.

Ask a CSM where QBR prep time goes and the answer is rarely "analysis". It is reconstruction: digging through email threads, meeting notes, tickets, and CRM records to rebuild what happened over three months. The analytical work — deciding what it means and what to recommend — is the smaller part.

That reconstruction is the automatable part, and the difference between preparing from a maintained account record versus reassembling one each quarter is measured in hours per account. At thirty accounts, that is the difference between QBRs happening and QBRs slipping.

Send materials 48 hours in advance. It converts the meeting from a presentation into a discussion, and the discussion is where you learn things — including the objections that would otherwise surface for the first time during the renewal.

QBRs are expensive. They only repay the effort where contract value or strategic importance justifies it. Running them across an entire long-tail book is a common way for a CS team to become fully occupied producing decks that customers skim.

For lower-touch segments, an asynchronous value summary or a five-minute recorded update usually delivers most of the benefit at a fraction of the cost — and many customers actively prefer it to another hour-long meeting. Reserve live QBRs for accounts where the executive relationship genuinely needs building.