Quarterly Business Review

What a Quarterly Business Review Is

A Quarterly Business Review (QBR) is the meeting where a vendor sits down with a customer every 90 days, walks through what has been delivered, and quietly figures out whether the contract is going to renew. The deck has charts. The real action happens in the room.

QBRs are most common in B2B SaaS with annual or multi-year contracts, professional services engagements, and any account where retention and Net Revenue Retention drive more revenue than new logos. The Customer Success team usually runs them. The AE crashes them when expansion is in play.

How a QBR Is Structured

The standard agenda runs 60-90 minutes and follows a predictable arc:

A good QBR ends with three things on a slide: agreed outcomes, named owners, and dates. A bad QBR ends with "great chat, let's do this again next quarter" and no decisions.

Worked QBR Example

A $180,000/year SaaS contract is up for renewal in 60 days. The CSM pulls usage data: 240 of 300 licensed seats active, weekly logins up 18% quarter-over-quarter, three new use cases in pilot. The QBR deck shows the customer saved 4,200 hours of analyst time, valued at $420,000 — a 2.3x ROI.

The Economic Buyer is in the room for the first time since signing. The CSM raises a 12-seat expansion into a new department. The AE — invited because expansion is on the table — quotes $24,000 in additional ARR. The customer agrees in the meeting. The renewal goes from "at risk" to expanded and signed early.

That outcome is the entire reason QBRs exist.

When Sales Orgs Use QBRs

Customer Success owns the cadence; they schedule the meetings and build the decks. The AE shows up when expansion or Land and Expand motion is active. RevOps cares because QBR completion rates correlate with Gross Revenue Retention — accounts that get four QBRs a year churn meaningfully less than accounts that get one or zero.

VPs of Sales watch QBR attendance from the customer side. When the Champion stops showing up, that is a leading indicator the renewal is in trouble. When a new executive shows up — especially one who did not sign the original contract — the deal is being re-evaluated whether the vendor knows it or not.

Common QBR Failure Patterns

The feature parade. The CSM presents the product roadmap for 45 minutes. The customer wanted to talk about an open support ticket. Nobody talks about the open support ticket.

The vanity metrics deck. Logins are up. Seats are activated. Nobody mapped any of this to the customer's original business case, so the executive in the room is wondering why she is there.

The single-thread QBR. Only the day-to-day user attends. The Economic Buyer has never been to one. When budget season hits and the user gets reassigned, the vendor has no relationship above her and the contract gets cut.

The QBR-as-bill-of-health. The CSM presents only good news to keep the relationship warm. Three months later the renewal slips and the CRO asks why nobody flagged it. The QBR was the place to flag it.