QBR (Quarterly Business Review) Structure
Designing and running QBRs that the customer's executive sponsor actually wants to attend — and that produce expansion and renewal confidence as the byproduct.
A is the most leveraged 60–90 minutes an has on the calendar each quarter. Done well, it re-anchors the relationship to outcomes, surfaces risks before they become urgent, validates the value narrative the will use internally, and naturally creates the conditions for expansion. Done badly, it is a status update the stops attending and the AM stops investing in.
The single biggest mistake AMs make with QBRs is treating them as something they have to deliver to the customer. The right framing is that a is something the customer's executives should be excited to attend because it gives them strategic information about their own organization that they cannot easily get from anywhere else.
Purpose of QBRs in customer success
A has three jobs, in order priority:
- Confirm and quantify value delivered. The is where the value narrative the customer will use internally — and the will use commercially — gets built and validated. If the QBR does not produce a defensible value statement, the QBR has failed regardless how it felt in the room.
- Re-align on the customer's evolving strategy. Customer priorities change quarterly. The is the structured forum where the updates their understanding what matters to the customer's executive in the *next* quarter, not the last one.
- Surface and resolve risks; identify expansion paths. The is the natural venue to escalate unresolved issues to the right level and to introduce strategic next-step conversations once the value foundation has been confirmed.
Notice what is *not* on this list: product roadmap walkthroughs, feature demos, and deep technical dives. Those belong elsewhere. A that becomes a roadmap deck has stopped being a QBR.
Structuring a QBR — the canonical agenda
A repeatable, executive-grade structure that scales across accounts:
- Outcomes against the original (10 min) — what was promised, what was delivered, with numbers. If the customer cannot defend the numbers internally, the has not done the prep.
- Leading indicators (10 min) — depth, breadth across teams, engagement with the right capabilities. This is the early-warning section that justifies the rest the conversation.
- Customer's strategic context update (10 min) — what has changed in the customer's priorities, organization, or market since last quarter. Often the most valuable section *for the *; the usually surfaces strategic information here that reshapes the next quarter's plan.
- Joint roadmap and joint plan for the next 90 days (15 min) — specific commitments on both sides, with named owners and dates. Not a vendor roadmap pitch — a *joint* plan.
- Risks and unresolved issues (10 min) — items that need executive on either side. This builds trust by showing the is willing to surface what is not working.
- Forward-looking strategic conversation (10 min) — usually expansion, multi-year structure, or executive program inclusion. Only credible if steps 1–2 produced a defensible value story.
Keep the visible at the top the deck. Executive attendees should be able to see at a glance that the meeting is about *their* outcomes and *their* strategy, not the vendor's product.
Aligning with executive stakeholders
The 's presence is what makes a a QBR. Without them it is a check-in. Three operational disciplines:
- Pre-meeting alignment with the . The should see the deck 5–7 days before the , with explicit space to flag anything that would surprise their executive. Surprises in the room are a Champion failure as much as an failure; the prep loop prevents both.
- Pre-meeting brief with your own . If you are bringing your VP or , they should walk in knowing the customer's priorities, the value narrative you intend to confirm, and the one strategic ask you want made executive-to-executive in the room.
- Tailoring to the executive's lens. A emphasizes financial outcome, risk, and predictability. A COO QBR emphasizes operational efficiency and breadth. A CTO QBR emphasizes platform reliability and strategic fit. Same underlying account, three different framings.
The test executive engagement is simple: did the executive speak more than 30% of the time, and did they leave the meeting with one specific action they personally agreed to? If both answers are yes, the was effective. If either answer is no, the QBR was a presentation, not a review.
Using QBRs to drive expansion and renewal confidence
Expansion conversations belong in the second half a — never as the headline. The that works:
- The first half the establishes the value foundation (outcomes delivered, leading indicators positive).
- The strategic context update reveals an emerging customer priority.
- The forward-looking section connects that priority to a natural in the customer's journey with the platform.
- The ask is positioned as a recommendation, not a pitch — and is owned by the in the room as a strategic decision, not by as a commercial one.
For renewals: a strong is the most reliable predictor a clean renewal. Customers who have attended four well-run QBRs in the year before their renewal almost always renew at parity or expansion. Customers who have attended one or zero QBRs are the bulk of the unexpected pool. The QBR itself is a of renewal outcome — and worth treating as such in the .
Common mistakes
- Too tactical. A full ticket counts, training schedules, and roadmap dates is a status report. Executives do not attend status reports twice. Push the tactical content into a separate operating review with the day-to-day team.
- Not outcome-focused. Slides full activity (workshops run, users trained, features released) without slides on outcome (revenue impact, cost saved, time recovered) signal that the is measuring effort, not impact. Customers notice.
- Vendor-centric . A that opens with the vendor's company update and product roadmap loses the room in the first ten minutes. Open with the customer's outcomes; the vendor update earns at most one slide late in the meeting if at all.
- No pre-alignment with the . Surprises in the room damage the as much as the . Always pre-walk the deck.
- No clear forward commitments. A that ends with 'great discussion, we'll follow up' produces no momentum. The closing slide should list 3–5 specific commitments, owners, and dates.
- Same deck every quarter. A templated deck signals the is not actually inspecting this account; they are running a process. Each QBR should have at least one section that is fresh because the customer's situation has changed.
- Skipping QBRs when the relationship feels comfortable. Comfortable accounts are exactly the ones where Champions move, executive sponsors disengage, and the renewal arrives without warning. The is the immune system; do not turn it off because the patient feels well.
Real-world example
An running a $900K account had run quarterly QBRs for two years that were heavily tactical: tickets resolved, training delivered, roadmap items shipped. Executive attendance had quietly dropped from the customer's VP to a director, then to no one above the day-to-day . The AM rebuilt the around outcomes: opened with a quantified statement ($6.4M operational savings attributable to the platform), included a strategic context discussion driven by questions to the executive, and closed with a forward plan tied to the customer's stated annual priority of cost optimization. The first redesigned QBR had the customer's COO attend; the second produced an introduction to the and a 3x expansion thesis; the third closed a $1.8M multi-year expansion. Same account, same product, materially different outcome — entirely from changing what the QBR was *for* and how it was structured.