Data as of Aug 25, 2026 · Based on 334 AI responses from ChatGPT Search and Google AI Mode · See how Parse measures this
Brands AI recommends here
Named in 18% of answers
Named in 12% of answers
Named in 10% of answers
Named in 10% of answers
The best QBRs feel **less like a presentation and more like a strategic working session**. The CSM’s job is not to prove that their company has been busy; it’s to help the customer answer three questions: 1. **What did we accomplish?** 2. **What value did we get from the partnership?**
The best QBRs feel less like a presentation and more like a strategic working session. The CSM’s job is not to prove that their company has been busy; it’s to help the customer answer three questions:
That customer-outcome focus is consistently emphasized in modern QBR guidance.
For a 60-minute QBR, I’d use this agenda:
| Time | Topic | Purpose |
|---|---|---|
| 5 min | Opening & priorities | Confirm what the customer wants from the meeting |
| 10 min | Business context | What has changed in their business since last quarter? |
| 15 min | Results & value delivered | Demonstrate outcomes, not just product usage |
| 10 min | Challenges & risks | Surface gaps, blockers, and concerns |
| 10 min | Strategic opportunities | Discuss ways to improve or expand the partnership |
| 8 min | Next-quarter goals | Agree on 3–5 measurable priorities |
| 2 min | Recap & commitments | Confirm owners and dates |
The exact timing can vary, but keeping the meeting to roughly an hour is a good discipline.
This is probably the biggest difference between an average QBR and a great one.
A week or two beforehand, talk to your champion and ask:
Then build the QBR around those answers.
Don't simply pull your standard QBR deck out of a template and replace the logo. The structure can be standardized, but the insights should be highly personalized.
A weak opening:
"Here are all the things that happened in our platform this quarter." A stronger opening:
"Last quarter you told us your priorities were reducing processing time, increasing adoption across the sales team, and improving reporting for leadership. Today we'd like to look at how we're tracking against those outcomes and agree on what matters most for the next 90 days." That immediately establishes the QBR as their meeting.
Don't confuse activity with value.
For example:
Weak:
Better:
Usage metrics are useful when they explain business outcomes. Modern QBR guidance specifically recommends tying KPIs and product usage back to the customer's objectives and ROI.
A useful formula is:
Customer goal → What they did → What changed → Business impact
This creates accountability and makes QBRs cumulative rather than repetitive.
For example:
| Goal | Last Quarter | This Quarter | Status |
|---|---|---|---|
| Deploy to Sales | 60% | 92% | 🟢 |
| Reduce processing time | -10% | -24% | 🟢 |
| Train managers | 15/30 | 26/30 | 🟡 |
| Launch new workflow | Not started | In progress | 🟡 |
Don't hide the red items.
If something isn't going well, say:
"We didn't hit this target. Here's what happened, what we've learned, and what I recommend we do differently next quarter." Transparency builds considerably more credibility than pretending everything is green.
One of the biggest QBR mistakes is allowing the CSM to talk for 45 minutes.
Ask questions such as:
The CSM should be facilitating a business conversation, not delivering a lecture.
Don't spend 20 minutes discussing a support ticket during an executive QBR.
If someone raises:
"We're still having trouble with the API integration." Acknowledge it, establish ownership, and move it to the appropriate follow-up:
"That's important. Let's make sure we capture it as an action item and have our technical team work through the details with you separately. For today's discussion, let's focus on the broader impact that integration is having on your business goal." QBRs should remain strategic rather than becoming support or implementation meetings.
This is subtle.
The CSM should absolutely identify opportunities such as:
But don't make the customer sit through:
"And now here's our new premium package..." Instead:
"You mentioned that expanding this process to the European team is a priority next quarter. Based on what we've seen with your U.S. team, I think there may be a strong opportunity to apply the same workflow there. Would it be useful if we mapped out what that would require?" Solve a customer problem first. Commercial opportunity follows naturally.
The most important slide may be the last one.
End with 3–5 concrete goals:
| Next-quarter objective | Customer owner | CSM owner | Due |
|---|---|---|---|
| Launch workflow for EMEA | Jane | Mike | Oct 15 |
| Train 30 new users | Carlos | Sarah | Oct 30 |
| Reduce processing time another 10% | Jane | Mike | Nov 15 |
Then ask:
"Are these the right three priorities for the next 90 days?" Get explicit agreement.
A good QBR should produce clear goals, owners, and timelines—not merely a nice conversation.
Keep it to roughly 8–10 slides:
Gainsight's current QBR framework similarly emphasizes executive summary, KPIs, ROI, prior goals, benchmarking/health, and clear next steps.
I'd boil the whole thing down to this:
Don't ask: "What do I need to show the customer?"
Ask: "What does this customer need to understand, decide, or accomplish because of this meeting?"
A great QBR leaves the customer thinking:
"They understand our business, they can prove the value they're delivering, they know where we're going, and they have a plan to help us get there." That's what turns a QBR from a quarterly presentation into a trusted-advisor conversation.
"Are these the right three priorities for the next 90 days?" Get explicit agreement.
A good QBR should produce clear goals, owners, and timelines—not merely a nice conversation.
Keep it to roughly 8–10 slides:
Running a high-impact Quarterly Business Review (QBR) means shifting the conversation away from a boring status update and turning it into a strategic alignment session. Here is the best framework for a Customer Success Manager to run a QBR that drives retention and expansion: - Data Gathering: Pull usage metrics, ROI…
Running a high-impact Quarterly Business Review (QBR) means shifting the conversation away from a boring status update and turning it into a strategic alignment session.
Here is the best framework for a Customer Success Manager to run a QBR that drives retention and expansion:
Data Gathering: Pull usage metrics, ROI data, adoption rates, and support ticket trends.
Stakeholder Alignment: Schedule the meeting with the economic buyer and key champions. Confirm the agenda beforehand so there are no surprises.
Executive Summary: Build a short, punchy slide deck focusing strictly on the client's goals, not just your product's features.
Welcome & Objective: State clearly that the goal is to review their strategic goals, measure mutual success, and map out the next quarter.
Executive Check-in: Ask if their high-level company priorities have shifted since your last conversation.
Data Presentation: Show them the hard numbers. Highlight how your tool saved them time, reduced costs, or drove revenue ($ROI=V a l u e G a i n e d−C o s t).
Benchmark Comparison: Compare their usage and adoption against industry peers or their own internal benchmarks.
Success Stories: Briefly share a relevant win or milestone they achieved using the platform.
Gap Analysis: Address any low adoption areas or roadblocks transparently without placing blame.
Client Feedback: Ask open-ended questions like, "What is your biggest bottleneck right now?" or "Where is the team still feeling friction?"
Strategic Preview: Share upcoming product features or service upgrades that specifically solve their current pain points.
Mutual Success Plan: Co-create a forward-looking action plan for the next 90 days with shared accountability and clear owners.
Action Items Recap: Clearly state who is doing what and by when.
Executive Summary Delivery: Send a polished recap deck and recording to all attendees within 24 hours.
Would you like me to provide a slide-by-slide QBR agenda template or help you draft an invitation email to get the client to actually show up?
No sources cited
Running a stellar Quarterly Business Review (QBR)—or Executive Business Review (EBR)—is your golden ticket to proving ROI, solidifying stakeholder alignment, and locking in renewal confidence. Here is a step-by-step playbook to run a QBR that feels like a high-value strategy session rather than a boring status update.…
Running a stellar Quarterly Business Review (QBR)—or Executive Business Review (EBR)—is your golden ticket to proving ROI, solidifying stakeholder alignment, and locking in renewal confidence.
Here is a step-by-step playbook to run a QBR that feels like a high-value strategy session rather than a boring status update.
Phase 1: Pre-Meeting Preparation (2-3 Weeks Out)
Phase 2: The Meeting Agenda (45-60 Minutes)
Structure your time like a strategic consulting engagement:
Phase 3: Golden Rules for Success
Phase 4: Post-Meeting Follow-Up (Within 24 Hours)
Would you like me to share a slide-by-slide deck outline or some exact conversational scripts for handling a client who isn't seeing the ROI they expected?
No sources cited
The best QBRs feel less like a **presentation from the CSM** and more like a **strategic working session with the customer**. The core question should be: > **“Given what you wanted to accomplish when you bought our product, what happened this quarter, what did we learn, and what should we accomplish together next?”**
The best QBRs feel less like a presentation from the CSM and more like a strategic working session with the customer.
The core question should be:
“Given what you wanted to accomplish when you bought our product, what happened this quarter, what did we learn, and what should we accomplish together next?” That keeps the conversation centered on the customer's business rather than your product. This is consistent with current CS guidance emphasizing customer outcomes, ROI, executive alignment, and clear next steps.
Don't start by opening the QBR template. Start with the customer's goals.
Review:
Then have a 15–30 minute pre-QBR conversation with your champion.
Ask things like:
This prevents the classic mistake of preparing the QBR in isolation.
Ideally, include:
For strategic accounts, executive participation can elevate the conversation from operational details to business strategy.
Don't invite six people from your company just because they're involved internally.
A good 60-minute QBR might look like:
| Time | Topic |
|---|---|
| 5 min | Welcome + objectives |
| 10 min | Customer priorities/business changes |
| 15 min | Results and outcomes from last quarter |
| 10 min | Challenges, risks, and lessons |
| 10 min | Recommendations/strategic opportunities |
| 10 min | Next-quarter goals + action plan |
I'd actually put the customer priorities near the beginning, rather than spending 20 minutes presenting your slides before asking how they're doing.
Don't say:
“Today we're going to walk through your usage statistics.” Instead:
“Our goal today is to look at the outcomes we agreed on last quarter, understand what's changed in your business, and leave with a clear plan for the next 90 days.” Then ask:
“Before we jump in, what's changed for you since we last met?”
This can completely change the QBR if the customer's priorities have shifted.
This is probably the single most important principle.
Bad QBR:
Users increased 18%. Feature X adoption increased 12%. You opened 14 support tickets. Here's what's new in our product. Better QBR:
Your objective was to reduce manual reporting time by 30%. You reduced it by 42%, which represents approximately 180 hours saved per quarter. Here's what drove that improvement, and here's what we recommend doing next. Usage metrics are useful only when they explain business value.
Current QBR guidance similarly recommends connecting KPIs such as adoption and utilization to the customer's actual business objectives and ROI.
A very effective QBR structure is:
What was the customer trying to accomplish?
What changed?
Show:
What should happen over the next 90 days?
This makes the QBR feel like a strategic narrative rather than a collection of dashboards.
A QBR shouldn't be a victory lap.
If adoption dropped 20%, say so.
If an implementation milestone slipped, explain why.
If the customer isn't getting expected value, acknowledge it and propose a recovery plan.
The key is to move from:
“Here's a problem.”
to:
“Here's what happened, here's what we learned, and here's our plan to fix it.”
Customers generally don't expect perfection. They do expect their CSM to understand the problems and have a plan.
This is where a CSM can differentiate themselves as a strategic advisor.
Don't merely say:
“Feature adoption is low.” Say:
“We noticed that your highest-performing teams use X and Y together, while the teams struggling to achieve their targets aren't using Y. I'd recommend we focus the next quarter's enablement around that workflow.” You're transforming data → insight → recommendation.
That's much more valuable than reporting.
A QBR where the CSM talks for 55 minutes is usually a bad QBR.
Use questions such as:
The objective is not to get through the deck.
The objective is to learn something that changes your plan.
This is an especially important CSM discipline.
If you've established:
Customer goal → achieved outcome → new opportunity → business case
then expansion can naturally emerge from the conversation.
But:
“And now here's our new product…” after 45 minutes of reviewing metrics makes the QBR feel like a sales call.
The customer's reaction should be:
“They understand our business and have ideas for how we can get further.”
—not—
“They used our quarterly meeting to sell us something.”
Never end with:
“Great meeting. We'll follow up.” Instead, agree on 3–5 concrete priorities.
For example:
| Priority | Success measure | Owner | Due |
|---|---|---|---|
| Increase adoption of X | 80% of target users active | Customer + CSM | Oct 15 |
| Launch workflow Y | Production by Nov 1 | Customer | Nov 1 |
| Executive dashboard | Monthly reporting live | CSM | Sep 15 |
The best QBRs finish with a shared understanding of what happens next, who owns it, and what success looks like.
Within 24 hours, send:
Then update your internal customer record/health assessment and make sure the account team knows about important changes.
I'd keep the deck to roughly 8–12 substantive slides, not 40.
The exact slides should vary by customer. A consistent framework is useful, but generic, outdated content undermines the purpose of a QBR.
Think of the QBR as:
Not: “Let me show you everything we've done.”
But: “Let me demonstrate the business value we've created, understand where your business is going, and help you decide what we should accomplish together next.”
A great QBR should leave the customer thinking:
“They understand our business, they know whether we're succeeding, they know where we're struggling, and they have a credible plan to help us move forward.” That's when the QBR becomes a genuine customer-success and executive-alignment mechanism, rather than just another quarterly meeting.
“Feature adoption is low.” Say:
“We noticed that your highest-performing teams use X and Y together, while the teams struggling to achieve their targets aren't using Y. I'd recommend we focus the next quarter's enablement around that workflow.” You're transforming data → insight → recommendation.
That's much more valuable than reporting.
A QBR where the CSM talks for 55 minutes is usually a bad QBR.
Use questions such as:
The objective is not to get through the deck.
The objective is to learn something that changes your plan.
This is an especially important CSM discipline.
If you've established:
Customer goal → achieved outcome → new opportunity → business case
then expansion can naturally emerge from the conversation.
But:
“And now here's our new product…” after 45 minutes of reviewing metrics makes the QBR feel like a sales call.
The customer's reaction should be:
“They understand our business and have ideas for how we can get further.”
—not—
“They used our quarterly meeting to sell us something.”
Never end with:
“Great meeting. We'll follow up.” Instead, agree on 3–5 concrete priorities.
For example:
| Priority | Success measure | Owner | Due |
|---|---|---|---|
| Increase adoption of X | 80% of target users active | Customer + CSM | Oct 15 |
| Launch workflow Y | Production by Nov 1 | Customer | Nov 1 |
| Executive dashboard | Monthly reporting live | CSM | Sep 15 |
The best QBRs finish with a shared understanding of what happens next, who owns it, and what success looks like.
Within 24 hours, send:
Here are top web results for exploring this topic: [](https://www.gainsight.com/essential-guide/quarterly-business-reviews-qbrs/)  Gainsight·https://www.gainsight.com The Essential Guide to **Quarterly Business Reviews** (QBRs)Standardize the…
Here are top web results for exploring this topic:
Gainsight·https://www.gainsight.com The Essential Guide to Quarterly Business Reviews (QBRs)Standardize the QBR Structure, Personalize the Insights. Adopt a core QBR template as your foundation, but tailor each meeting to reflect the customer's specific goals, recent wins, and areas of oppor
Mural·https://www.mural.co How to run QBRs that strengthen client relationships - Mural A guide to help account managers and customer success managers run strategic quarterly business reviews that boost customer retention, uncover growth opportunities, and drive success.
Reddit·https://www.reddit.com Need Help with a Customer Success QBR Assignment! - Reddit Need Help with a Customer Success QBR Assignment! Hey everyone, I'm working on a Quarterly Business Review (QBR) assignment as part of a hiring process for a Customer Success Manager role at a logisti
Workona·https://workona.com How to Run Quarterly Business Reviews (QBR ) w - Workona What is a QBR in business? Let's back up a little. QBR stands for "quarterly business review" — a quarterly meeting with your high-value customers. The goal is to check in with your · to check in with LinkedIn·https://www.linkedin.com A Day in A Life of a Customer Success Manager: Quarterly Business ...I think starting the day this way is powerful. At least, that was the feedback from my customers. 2. Be prepared to listen. You are probably familiar with Stephen Covey's concept of listening – 'You h
Skilljar·https://www.skilljar.com Scale Customer Success With Our Quarterly Business Review (QBR ...What Is a QBR? A QBR is a quarterly check-in with your customer to review the impact and improvements seen in their training efforts as a result of your product or service. Customer Success Managers w
ClientSuccess·https://www.clientsuccess.com Tips for a Successful CSM Quarterly Business Review - ClientSuccess Run a successful customer success Quarterly Business Review (QBR): prep attendees early, invite cross-functional leaders, set an agenda, and send a recap. ... procedures should change after a QBR as a
SuccessCOACHING·https://successcoaching.co Transforming QBRs into Strategic Growth Sessions Quarterly business reviews, or QBRs, are critical touchpoints for Customer Success Managers, where they sit with their customers to discuss wins, past performance, and plans for the future. But too of
Statisfy AI·https://www.statisfy.com Master the Quarterly Business Review Format for Success - Statisfy A truly great Quarterly Business Review (QBR) starts weeks in advance. The most effective Customer Success Managers (CSMs) I know treat this prep time as an intelligence-gathering mission. This founda ChurnZero·https://churnzero.com**Quarterly business reviews** (QBRs): A blueprint for success Control is offering them a choice. People hate not having options. Invite customers to influence the conversation. Build in areas they can control and comment on. Affection is affirming them through e
No sources cited
The best QBRs are **not product reviews, status meetings, or disguised sales pitches**. They are strategic conversations where the CSM helps the client answer: > **“What did we accomplish, what value did we get, what has changed, and what should we accomplish next?”** That customer-outcome focus is also what current…
The best QBRs are not product reviews, status meetings, or disguised sales pitches. They are strategic conversations where the CSM helps the client answer:
“What did we accomplish, what value did we get, what has changed, and what should we accomplish next?” That customer-outcome focus is also what current QBR guidance emphasizes: personalize the discussion, connect metrics to business outcomes/ROI, involve the right stakeholders, and leave with measurable next steps.
For a typical 60-minute QBR, I'd use this flow:
| Time | Topic | Purpose |
|---|---|---|
| 5 min | Opening & priorities | Confirm objectives and what the customer wants from the meeting |
| 10 min | Executive summary | “Here's what happened this quarter” |
| 15 min | Business outcomes & ROI | Prove the value the customer received |
| 10 min | Challenges & risks | Surface gaps, blockers, and changing priorities |
| 15 min | Next-quarter strategy | Agree on 3–5 meaningful goals |
| 5 min | Commitments & close | Confirm owners, dates, and next meeting |
A week or two before the QBR, talk to your champion.
Ask:
This prevents the classic mistake of building a beautiful QBR deck in isolation and discovering during the meeting that you're talking about things the customer doesn't care about.
Send a short agenda beforehand and get agreement on the focus.
Avoid opening with:
“Here's what's new in our platform…” Instead:
“Last quarter, we agreed that your priorities were A, B, and C. Let's look at the progress we've made against those outcomes and then decide what matters most for the next 90 days.” That immediately positions you as a strategic advisor rather than a vendor.
This is probably the most important part.
Don't just report:
Translate those numbers into customer outcomes.
For example:
“Your team increased adoption from 54% to 82%, which means approximately 120 additional employees are now using the workflow. Based on the time saved per transaction, we estimate that this has eliminated roughly 300 hours of manual work per quarter.” The question behind every metric should be:
“So what?”
Gainsight similarly recommends connecting KPIs and usage data to the customer's original business case and tangible ROI rather than presenting metrics in isolation.
A good QBR should have a narrative:
Where we started → What we accomplished → What we learned → What's getting in the way → Where we're going next
For example:
Goal: Reduce onboarding time Starting point: 14 days This quarter: 9 days Impact: ~35% faster onboarding Remaining gap: Enterprise accounts still average 12 days Next quarter: Bring enterprise onboarding below 8 days That is much more compelling than six slides of charts.
One of the biggest QBR mistakes is allowing the CSM to become the presenter for 60 minutes.
A good QBR should feel like a conversation, not a presentation.
Ask questions such as:
The goal is not to prove that you prepared a lot of slides. The goal is to learn something and make a decision.
Don't hide bad news because you're afraid it will make the account look unhealthy.
If adoption is declining, say so.
If an implementation is behind schedule, say so.
If the customer isn't getting the expected value, investigate why.
A strong CSM response is:
“We're seeing a decline here, and I don't think we should gloss over it. Here's what we believe is causing it. I'd like to get your perspective and agree on how we address it.” That builds considerably more credibility than pretending everything is green. QBR guidance also emphasizes surfacing challenges and turning them into actionable solutions rather than becoming defensive about criticism.
The QBR shouldn't primarily be a history lesson.
The most valuable part is:
Pick 3–5 concrete outcomes, not 15 initiatives.
For each one, establish:
For example:
| Outcome | Success measure | Owner | Due |
|---|---|---|---|
| Increase adoption | 85% of target users active | Customer | Oct 15 |
| Improve onboarding | Reduce average time to 7 days | CSM + Ops | Nov 1 |
| Launch new workflow | 3 teams live | Customer | Nov 15 |
This becomes your mutual success plan and gives the next QBR a natural starting point.
Ideally, you want some combination of:
The more strategic the conversation, the more important executive participation becomes. The right stakeholders can turn a QBR from an operational review into a conversation about future priorities and investment.
This is subtle but extremely important.
If the customer has just demonstrated that they're struggling to achieve their current objectives, immediately pitching additional products destroys trust.
Instead:
Customer goal → problem → insight → recommendation
If your product expansion genuinely helps solve the problem, it will emerge naturally.
The customer should leave thinking:
“They understand our business and are helping us achieve our goals.” Not:
“That was a sales pitch disguised as a QBR.”
Never finish with:
“Great discussion. We'll follow up.” Finish with:
“Let me recap what we agreed to.” Then read back:
Send the recap promptly afterward. Current QBR guidance specifically emphasizes clear owners and timelines because otherwise the next QBR ends up re-deriving everything from scratch.
Keep it to roughly 8–10 slides:
And customize it. A reusable framework is good; a generic deck isn't.
The biggest shift is this:
Weak QBR:
“Here's everything we did for you.” Good QBR:
“Here's everything you achieved with us.” Great QBR:
“Here's what you achieved, here's the business impact, here's what we've learned, and here's the plan for getting you to the next level.” If the customer walks away with clarity, evidence of value, useful insight, and a concrete plan, you've run a successful QBR.
Never finish with:
“Great discussion. We'll follow up.” Finish with:
“Let me recap what we agreed to.” Then read back:
Send the recap promptly afterward. Current QBR guidance specifically emphasizes clear owners and timelines because otherwise the next QBR ends up re-deriving everything from scratch.
Keep it to roughly 8–10 slides:
That builds considerably more credibility than pretending everything is green. QBR guidance also emphasizes surfacing challenges and turning them into actionable solutions rather than becoming defensive about criticism.
The best QBRs are **not product reviews** and not “here’s everything that happened last quarter.” They are strategic conversations where the CSM helps the client answer: > **“Are we getting the business outcomes we expected, what have we learned, and what should we do together over the next 90 days?”** That…
The best QBRs are not product reviews and not “here’s everything that happened last quarter.” They are strategic conversations where the CSM helps the client answer:
“Are we getting the business outcomes we expected, what have we learned, and what should we do together over the next 90 days?”
That customer-outcome focus is consistent with current CS guidance: effective QBRs emphasize ROI, customer goals/KPIs, challenges, and mutually agreed next steps rather than vendor-centric metrics.
For a 60-minute QBR, I'd use this:
| Time | Section | Purpose |
|---|---|---|
| 5 min | Opening & objectives | Confirm what the customer wants from the meeting |
| 10 min | Business context | What's changed in their company, priorities, or strategy? |
| 15 min | Results & outcomes | Show progress against their goals and business case |
| 10 min | Challenges & opportunities | Discuss gaps, risks, and opportunities openly |
| 15 min | Next-quarter strategy | Agree on 3–5 meaningful goals |
| 5 min | Commitments & next steps | Confirm owners, dates, and follow-up |
Before the meeting, talk to your champion and ask:
Send a concise agenda beforehand. For strategic accounts, getting the right executive/decision-maker involved can elevate the conversation beyond day-to-day product usage.
Don't open with:
“Here are all the features you used this quarter.”
Instead:
“When we started the quarter, your priorities were X, Y, and Z. Let's look at what changed, what we accomplished, and where we should focus next.”
Your product usage data should support the business story, not be the story.
For example:
Weak:
“Your users created 14,238 reports.”
Strong:
“Your operations team reduced the time spent preparing weekly reports from 6 hours to 2 hours. That's approximately 200 hours saved this quarter.”
The second one demonstrates value.
Tie your metrics back to the original reason they bought your product.
Think:
Business objective → Customer behavior → Result → Business impact
For example:
Reduce customer response time → 85% of support team adopted workflow → response time fell from 4 hours to 1.5 hours → estimated 22% improvement in SLA performance.
Gainsight similarly recommends connecting QBR metrics to the customer's strategic goals and quantifying tangible business impact rather than relying on generic usage metrics.
A great QBR isn't a sales presentation where everything is green.
If adoption is poor, say so.
“We aren't where we expected to be on adoption. Here's what we're seeing, here's why we think it's happening, and here's what I recommend we do about it.”
That actually increases credibility.
The CSM's job is to turn:
Problem → diagnosis → recommendation → action
rather than hiding the problem.
This is where many QBRs fail. They spend 50 minutes reviewing the past and five minutes saying, “Any questions?”
I'd reverse the emphasis.
Ask:
Then create 3–5 mutually agreed goals with owners and dates.
This is a subtle but important point.
If you've done the QBR correctly, expansion opportunities may naturally emerge:
“You mentioned you're planning to roll this out to the European team next quarter. Would it be useful for us to discuss what that rollout would require?”
That's much better than:
“Here's our new Enterprise Package. Would you like to buy it?”
The customer should feel that you are helping them achieve their goals, not that the meeting was designed to hit a sales target.
Never finish with “Great discussion!”
Finish with something concrete:
| Goal | Customer owner | CSM owner | Due |
|---|---|---|---|
| Increase adoption to 80% | Jane | CSM | Sept. 15 |
| Launch workflow X | Mike | CSM + Solutions | Sept. 30 |
| Executive training | Jane | CSM | Oct. 5 |
Then send the recap promptly and carry those commitments into your ongoing account management. Current QBR guidance also emphasizes assigning owners, timelines, and clear follow-through.
I'd teach a CSM to remember 5 R's:
1. Results — What did we accomplish?
2. Relevance — Why does it matter to the customer's business?
3. Risks — What's getting in the way?
4. Recommendations — What should we do about it?
5. Roadmap — What are we going to accomplish next?
If you consistently do those five things, the QBR stops being a quarterly PowerPoint exercise and becomes a strategic advisory meeting.
The customer should do more talking than the CSM.
A useful test is: if you could give the exact same QBR deck to another customer without changing much of it, it's probably too generic. The best QBRs use a consistent structure but personalize the insights, goals, data, and recommendations to that particular customer's business.
Running an effective Quarterly Business Review (QBR) transitions you from a vendor to a trusted strategic advisor. The key is shifting the focus from a status report on the past to a forward-looking strategy…
Running an effective Quarterly Business Review (QBR) transitions you from a vendor to a trusted strategic advisor. The key is shifting the focus from a status report on the past to a forward-looking strategy session.
Here is a step-by-step framework to run a high-impact QBR:
1. **Welcome & Alignment** (5 minutes): Confirm the agenda and state the ultimate goal of the meeting (optimizing their business outcomes).
1. **Value & ROI Review** (15 minutes): Showcase the concrete business results, milestones hit, and goals achieved using your solution over the past quarter.
1. **Usage & Adoption Insights** (10 minutes): Highlight areas where they are thriving and address any adoption gaps or training needs constructively.
1. **Industry Benchmarks / Insights** (10 minutes): Share peer insights or market trends showing how their performance compares to industry standards.
1. **Future Roadmap & Strategic Alignment** (15 minutes): Map your upcoming product roadmap directly to their goals for the next quarter.
1. **Action Items & Next Steps** (5 minutes): Summarize commitments, owners, and dates for the upcoming quarter.[[1]](https://interview.norahq.com/interview-guides/boston-consulting-group-summer-associate-interview-guide-2026)[[2]](https://interview.norahq.com/interview-guides/procter-and-gamble-sales-interview-guide-2026)[[3]](https://www.planhat.com/customer-success/renewals)[[4]](https://www.velaris.io/articles/quarterly-business-review-examples)[[5]](https://www.distribute.so/templates/qbr-template)
If you'd like, tell me:
I can give you a tailored slide outline or specific questions to ask during the session.
The best QBRs are **not presentations about your company or a review of product usage**. They are strategic conversations about **the client’s business outcomes, the value you’ve helped create, what has changed, and what you should accomplish together next quarter**. That customer-centric, data-driven approach is…
The best QBRs are not presentations about your company or a review of product usage. They are strategic conversations about the client’s business outcomes, the value you’ve helped create, what has changed, and what you should accomplish together next quarter. That customer-centric, data-driven approach is consistently emphasized in modern CS guidance. www.gainsight.comwww.gainsight.com
1. Prepare around the customer's goals — not your agenda
Before the meeting, know:
Ideally, talk to your champion beforehand and ask: “What would make this QBR valuable for you?” Modern QBR guidance recommends collaborating with customer stakeholders rather than preparing the review entirely in isolation.
2. Send a short agenda in advance
A good 45–60 minute agenda might be:
| Time | Topic |
|---|---|
| 5 min | Business priorities & agenda |
| 10 min | Last quarter's goals and outcomes |
| 10 min | Business impact / ROI |
| 10 min | Challenges, risks & opportunities |
| 10 min | Next-quarter priorities |
| 5 min | Decisions, owners & next steps |
Keep the deck relatively short. The meeting should be a conversation, not a slide-reading exercise.
3. Start with their business
Instead of:
“Today I'll walk you through your usage statistics…”
Try:
“Last quarter you identified reducing processing time and increasing adoption across the operations team as your two priorities. Let's look at what changed, what impact we've seen, and where we should focus next.”
That immediately establishes that the meeting is about their outcomes.
4. Show measurable value
This is probably the most important part of the QBR.
Connect your product/service to outcomes such as:
Don't just say:
“Usage increased 34%.”
Say:
“Usage increased 34%, primarily because the operations team adopted X. That eliminated approximately 120 hours of manual work this quarter.”
The first is a product metric. The second is business value.
QBR best practices specifically recommend connecting KPIs and ROI to the customer's own business objectives rather than relying on generic vendor metrics.
5. Be honest about what's not working
A great QBR isn't a quarterly victory lap.
If adoption is poor, a goal was missed, or there is an unresolved problem, put it on the table:
“We didn't hit the adoption target we agreed on. Here's what we believe caused it, and here's the plan I'd recommend to correct it.”
This builds credibility. A CSM becomes a trusted advisor when they are willing to surface uncomfortable information rather than simply report positive metrics.
6. Spend significant time listening
A useful rule is roughly 40% presenting / 60% discussing.
Ask questions such as:
The answers are often more valuable than anything in your deck.
7. Make the next quarter concrete
Don't finish with “We'll keep working on adoption.”
Agree on 2–4 specific outcomes.
For example:
| Priority | Success measure | Owner | Due |
|---|---|---|---|
| Increase adoption | 80% of target users active | Client + CSM | Sept. 30 |
| Automate workflow X | 50% reduction in manual processing | CSM + Client Ops | Oct. 15 |
| Launch use case Y | Production rollout | Client | Nov. 1 |
This turns the QBR into a mutual action plan, rather than a retrospective.
Keep it to roughly 7–10 slides:
This structure closely matches established QBR guidance: executive summary, meaningful KPIs, ROI, prior goals, benchmarking where useful, customer health, and explicit next steps.
Don't ask: “What do I need to present at this QBR?”
Ask:
“What does this customer need to understand, decide, or accomplish as a result of this meeting?”
That's the difference between a QBR that feels like a mandatory vendor meeting and one where the customer thinks, “That was actually useful.”
And don't make every QBR identical. A consistent framework is useful, but the content should be highly personalized to the customer's goals, current situation, and stakeholders.
Running an impactful **Quarterly Business Review (QBR)** requires shifting the focus from a standard status report to a strategic alignment session. The goal is to prove value, address roadblocks, and map out mutual success for the next quarter. Here is a step-by-step framework to run a high-impact QBR: Before the…
Running an impactful Quarterly Business Review (QBR) requires shifting the focus from a standard status report to a strategic alignment session. The goal is to prove value, address roadblocks, and map out mutual success for the next quarter.
Here is a step-by-step framework to run a high-impact QBR:
Before the Meeting (Preparation)
During the Meeting (The Agenda)
After the Meeting (Follow-Up)
If you'd like, let me know:
I can tailor a specific slide outline or customize the questions you should ask during the meeting.
No sources cited