QBR structure for customer-success managers
How to run a Quarterly Business Review that actually drives renewal and expansion
Most QBRs are status meetings dressed up as strategic conversations — slide 1 'last quarter's usage,' slide 2 'product updates,' slide 3 'roadmap,' slide 4 'questions.' The customer leaves with the same impression of your product they walked in with. A QBR that actually drives renewal and expansion has a different structure: it's organized around the customer's outcomes, not your product's features. This page lays out a 60-minute QBR agenda template that has worked across mid-market and enterprise B2B SaaS, names the specific questions that surface expansion opportunities, and covers the structural mistakes that turn QBRs into product-update meetings.
The 60-minute QBR agenda that works
Five sections, with time-box discipline. (1) 5 min — open with the customer's stated business goals (not your product's). 'When you signed last cycle, the goal was X. Where are you on X today?' This sets the conversation as customer-outcome-driven from minute one. (2) 15 min — value-realization metrics. Show the specific numbers tied to the goals: tickets resolved, revenue influenced, time saved, NPS lift. Per-customer-specific, not aggregate. (3) 15 min — expansion opportunities. 'Here are 3 use cases adjacent to what you're doing today that other customers like you have layered on.' Concrete examples; ask which resonates. (4) 10 min — friction surfacing. 'What's not working that I haven't seen?' Open question; let them name the silent pain. (5) 15 min — next-quarter alignment. Specific commitments both sides will make in the next 90 days, captured in writing during the call. The structural rule: cut your product-roadmap slides from this meeting entirely. They belong in a separate enablement session, not in the QBR.
Value-realization metrics that actually move buyers
The metric that moves the buyer is the one tied to THEIR business outcome, not yours. Your dashboard might show 'feature adoption,' 'monthly active users,' 'integration count.' The buyer cares about: dollar impact (revenue influenced, cost saved), time impact (hours per week saved per user, days off the cycle time), quality impact (NPS, customer satisfaction, error rate reduction), and capability impact (things the team can do now that they couldn't before). Translate every product metric into the buyer's outcome metric. 'Your team made 200 calls per rep this quarter' is a product metric; 'your team's per-rep talk time increased 18% which correlates with the 12% pipeline lift you reported' is the buyer's metric. The translation is the work; without it, the QBR is a feature-adoption review, not a value-realization conversation.
Expansion: position 3 specific use cases, not 1 generic upsell
The expansion ask in a QBR should be 3 specific use cases adjacent to the customer's current usage, anchored to other customers who succeeded with each. 'Other customers in your tier who started where you are layered on use cases A, B, and C; A and B feel most relevant to your team's stated goals — which one would you want to explore first?' This frames expansion as 'what other customers like you do' rather than 'we want to upsell you,' and the comparison set is concrete (named customers, specific outcomes) rather than generic. Where this fails: when the CSM hasn't done the customer-research work to know which 3 use cases are actually relevant. The QBR opens the door; the discovery work happens in the weeks before, not during the call.
Friction surfacing — the question that saves renewals
'What's not working that I haven't seen?' is the highest-leverage question in a QBR. Most customers don't proactively raise minor frustrations because they don't want to seem demanding; they raise them at renewal time as reasons not to renew. The QBR is the chance to surface them earlier. The follow-up that matters: when they do name something, ask 'how often does this happen, and what's the workaround you're using today?' This converts the abstract complaint into a quantified pain you can either fix in product, route to support, or build into the next-quarter commitment list. The mistake to avoid: getting defensive when the customer surfaces friction. Defensive response = fewer issues raised = bigger renewal-cycle surprise.
Next-quarter alignment as a written artifact
Every QBR should produce a 1-page written artifact: customer's stated business goals for next quarter, value-realization metrics they'll measure success against, expansion paths they want to explore (with timelines), and the specific commitments your team is making in the next 90 days. Both sides walk away with the same document; it becomes the agenda for the next QBR. Without this artifact, the QBR is a one-time conversation with no continuity; with it, you've built a quarterly accountability rhythm where both sides remember what was committed. HearQA's per-call session summary auto-generates the first draft of this artifact from the call transcript; the CSM edits and sends within 24 hours.
Checklist
- ☐Open with the customer's business goals, not product usage stats — sets customer-outcome-driven framing from minute one
- ☐Translate every product metric into a buyer-outcome metric (dollar / time / quality / capability) before the meeting starts
- ☐Prepare 3 specific expansion use cases anchored to comparable customers, not 1 generic upsell pitch
- ☐Ask 'what's not working that I haven't seen?' and let the silence work — the answer surfaces the frustration most likely to threaten renewal
- ☐Cut your product-roadmap slides from the QBR — they belong in a separate enablement session
- ☐End with a written next-quarter artifact — customer's goals, metrics, expansion exploration paths, your team's specific commitments — sent within 24 hours
- ☐Calendar the next QBR before this one ends — quarterly rhythm only works if it's actually quarterly
How HearQA Helps
- Upload the customer's account brief, prior QBR slides, ticket history, value-realization metrics, comparable-customer case studies, and your team's expansion playbook into the document library
- Practice → Sales Roleplay before a hard renewal-anchor QBR — the AI plays the customer's economic buyer raising the friction concerns you'd normally surface in 'what's not working' — by the live call, your response framework is muscle memory
- Live AI surfaces value-anchor recall during the call (specific dollar / time figures from prior QBRs), expansion case-study fluency (the comparable customer who succeeded with use case A, with their specific outcomes), and friction-handling response patterns when the customer names something difficult
- Per-call session summary auto-captures the customer's stated business goals, the metrics agreed on, the expansion paths surfaced, and your team's commitments — generates the first draft of the next-quarter written artifact
FAQ
Should QBRs be virtual or in-person?
Virtual works for most cadences; in-person earns its way in for renewal-anchor QBRs (the one before the renewal decision) and at-risk-account QBRs (where the relationship needs reinforcement). The cost of in-person is real (travel, logistics, calendar friction); the value is the relationship signal it sends ('we flew to see you'). For mid-market accounts ($25-100k ARR), virtual every quarter; for enterprise ($250k+ ARR), virtual most quarters with 1 in-person per year aligned to renewal cycle.
How is a QBR different from a regular check-in?
A check-in is tactical — open tickets, recent issues, near-term roadmap. A QBR is strategic — business goals, value realization, expansion. Different cadences, different stakeholder sets, different artifacts. Many CS teams confuse the two by stuffing tactical issues into the QBR; the QBR loses strategic punch and the customer's executive sponsor stops attending. Run check-ins monthly with the operational team; run QBRs quarterly with the executive sponsor + economic buyer + champion.
Who should be on the customer's side of a QBR?
Three roles, ideally: economic buyer (the person who signs the contract; usually CFO / COO / VP-level), executive sponsor (the person whose org-level outcomes the product is tied to; often a director or VP), and champion (the day-to-day product user advocate). If only the champion shows up, the QBR's strategic value is reduced — you're back to a tactical check-in. Renewal-anchor QBRs especially need the economic buyer in the room.
What's the worst QBR mistake you see?
Spending 30 of the 60 minutes on product-roadmap slides. The roadmap belongs in an enablement webinar, not in the QBR — most customers don't care about features they haven't asked for, and the time crowds out the conversations that actually drive renewal. The customer's strategic time is too expensive to spend on your team's update. Cut the roadmap section entirely; reference it once at the end ('here's a 1-page roadmap summary; let me know if any of these affect your planning') and move on.
How do I handle a QBR where the customer is at-risk?
Restructure. Skip the value-realization stats (they'll be defensive); skip the expansion ask (it'll feel tone-deaf). Spend 40 of the 60 minutes on the friction-surfacing question + their stated reasons for considering not renewing. Get specific on what's not working, what the workarounds are, what would need to change for them to stay. The remaining 20 minutes is your team's specific commitment to address what surfaced, with timelines. The renewal conversation is downstream of whether you can credibly commit to fixing the friction; the at-risk QBR is where the credibility is built or lost.