コンテンツへスキップ
TL;DR（要約）
QBR in business stands for Quarterly Business Review. For Customer Success teams, it is a recurring meeting with a customer to review progress against agreed goals, discuss changes or risks, and set the priorities for the next quarter.
A useful customer QBR should leave both sides with:
- a clear view of progress against the goals already agreed
- enough evidence to explain the results
- an updated picture of the customer’s priorities and risks
- specific actions, owners, and dates for the coming quarter
The preparation can take longer than the meeting itself, especially when customer context is scattered across CRM notes, product data, and months of calls. tl;dv’s AI meeting assistant for Customer Success teams keeps customer conversations searchable and can analyse information across several meetings when a CSM needs to reconstruct the quarter.
目次
What Is a QBR in Business?
Businesses generally use QBR in two contexts.
1. Customer QBR
A customer QBR is held between a vendor and a customer, usually every three months. The conversation covers the customer’s goals, results, product adoption where relevant, current risks, and the plan for the next period.
For SaaS companies, Customer Success Managers and account managers commonly own these reviews.
The customer should be able to understand how the work completed during the quarter connects to the reason they bought the product or service in the first place.
Suppose a support team bought software because it wanted to reduce average handling time from 14 minutes to 10 minutes. Reporting that workflow adoption reached 78% provides useful operational context. The business result is whether handling time actually moved toward 10 minutes.
The QBR brings those pieces together.
2. Internal QBR
An internal QBR reviews the performance of a team, department, or company.
A sales leadership team might review quota attainment, pipeline coverage, win rates, forecast accuracy, and territory performance. A CS leadership team could review retention, expansion, account health, adoption trends, and risks across the portfolio.
| QBR type | Main focus | Typical attendees | Main output |
|---|---|---|---|
| Customer QBR | Customer outcomes, value, risks, future priorities | CSM, account team, customer stakeholders | Shared plan for the next quarter |
| Internal QBR | Team or company performance | Leadership and functional teams | Decisions on priorities, performance, and resources |
The rest of this article focuses mainly on the customer-facing QBR because it is the version most commonly used in B2B Customer Success and account management.
For a wider view of how CS teams manage customer goals, retention, onboarding, and account health, tl;dv’s Customer Success guide covers the broader role.
What Should a QBR Cover?
The quarterly cadence creates a regular point where the vendor and customer can look beyond the day-to-day account activity.
1. Progress Against Goals
Start with the objectives agreed previously.
For every goal, establish:
- the original baseline
- the target
- the current result
- the change since the previous review
- the current status
A customer who agreed to increase active usage from 55% to 75% should see that comparison immediately.
Showing “68% active users” on its own forces everyone in the room to remember what the number was supposed to be
2. Business Value and Results
Usage data explains what happened inside the product. The QBR also needs to show how that relates to the customer’s operation.
Depending on the product, that could include:
- hours saved
- lower handling time
- faster onboarding
- higher conversion
- fewer manual tasks
- reduced error rates
- higher throughput
- cost avoided
- improved SLA performance
Use ROI numbers carefully. If the customer has agreed on the methodology, include them. If the calculation depends heavily on assumptions, state those assumptions.
Effective QBRs can double the likelihood of B2B customer renewal based on its research. The quality of the review is central to that claim. Gainsight specifically calls out customer collaboration, relevant success measures, and forward planning as characteristics of a stronger QBR.
3. Risks and Changes
Three months can change an account considerably.
A customer may have reorganized a team, reduced headcount, appointed a new executive, delayed a rollout, changed budget priorities, introduced a new compliance requirement, or moved an important project.
These changes affect the assumptions behind the original customer success plan.
A QBR should make the material ones visible and explain their effect on the account. If regional adoption fell behind because the customer postponed training for six weeks, show the delay, its impact, and what needs to happen next.
Serious risks should already be under discussion before the quarterly review. The QBR provides the wider account context and gives the relevant stakeholders an opportunity to agree on the response.
4. Priorities for the Next Quarter
The final part of the QBR should turn what you have learned during the review into a clear plan for the next quarter. That usually means agreeing which priorities deserve attention, what evidence will show progress, where each side has responsibility, and which dependencies could affect delivery.
For example, imagine a customer is considering an APAC rollout, while adoption and performance in EMEA are still inconsistent. The QBR might end with a decision to delay the expansion until the existing rollout is more stable. The customer could take ownership of regional enablement and internal champions, while the CS team reviews workflow usage, adoption gaps, and the operational results those workflows are expected to improve. Both sides then agree on the thresholds they want to see before revisiting expansion.
That gives the next quarter a real strategic focus and creates something concrete to review when the teams meet again.
QBR vs. EBR vs. Customer Check-In
QBR, EBR, and regular customer check-ins can overlap, and companies do not use the labels consistently.
| Meeting | Typical cadence | Main focus | Typical audience |
|---|---|---|---|
| Customer check-in | Weekly or monthly | Current work, issues, tasks, immediate blockers | Operational stakeholders |
| QBR | Quarterly | Results, customer value, risks, next-quarter priorities | Customer stakeholders and account team |
| EBR | Often biannual or annual | Business impact, long-term strategy, investment, executive alignment | Senior leaders from both organisations |
An EBR, or Executive Business Review, typically brings senior stakeholders from both companies together to discuss the longer-term direction of the relationship. The conversation is more likely to cover strategic priorities, business impact, future investment, expansion plans, and major risks.
A regular customer check-in is usually more operational. It might cover open actions, implementation progress, support issues, upcoming deadlines, or immediate blockers.
A QBR sits between those two. It reviews the previous quarter’s results and customer outcomes, then uses that information to agree on priorities for the next quarter.
The terminology varies between companies. Some SaaS teams use QBR and EBR interchangeably, particularly for strategic accounts where executives attend the quarterly review. In practice, the purpose, audience, and time horizon of the review are more useful distinctions than the name itself.
How to Prepare for a QBR in 5 Steps
Preparation should begin with the account history and the commitments made during the previous review.
1. Review the Previous QBR
Pull the goals, decisions, and actions agreed last quarter.
Give each one a status like this: Achieved | On track | At risk | Changed | Dropped.
Check what was agreed, who owned it, when it was due, what happened, and whether the underlying customer priority still exists. If the previous review recorded “complete EMEA enablement before the end of May,” find out whether it happened before you build the new deck.
2. Reconfirm Customer Priorities
Speak to the main customer contact before finalising the QBR. Ask what has changed, what leadership is focused on, which results matter most, and whether anyone has joined or left the decision-making team.
A customer that entered Q1 focused on growth may enter Q2 under a cost-reduction programme. Efficiency, utilisation, or consolidation may now deserve more attention than expansion.
3. Gather the QBR Data
Pull the evidence required to evaluate the customer’s goals. Depending on the account, that may come from product analytics, CRM records, support systems, Customer Success platforms, financial data, project-management tools, and customer conversations.
Check the methodology behind important figures. Define the comparison period for percentage changes and be able to explain any savings or ROI calculation.
4. Review Customer Conversations
Calls often contain context that dashboards miss. A customer may have discussed a delayed rollout, procurement issue, new executive priority, or feature requirement during a routine monthly conversation.
tl;dv can record and transcribe customer meetings and keep the meeting history available for later review. When preparing a QBR, look for customer-stated goals, changes in priorities, repeated blockers, commitments from each side, stakeholder changes, positive outcomes, and renewal or budget discussions.
For accounts with many meetings, Multi-Meeting AI Insights (or conversational intelligence) can surface recurring themes across the quarter.
5. Align Internally
Resolve internal uncertainty before the customer joins. Get the latest position on technical issues, product requests, support escalations, and commercial conversations. If Sales wants to discuss expansion, check whether the current rollout supports that conversation. If the customer has raised the same issue several times, know its status and ownership.
QBR Agenda Template: A 60-Minute Structure
A 60-minute QBR works well for many B2B accounts. Complex strategic accounts may need longer. The agenda should leave room for discussion. You can use the following template I created for reference.
1. Customer Priorities: 5 Minutes
Open by confirming whether anything has changed since the pre-QBR conversation.
If the customer has a new issue that materially affects the account, adjust the discussion while everyone needed in the room.
2. Previous Goals: 10 Minutes
Review the goals agreed last quarter. Show the target, actual result, status, and any material gap.
Spend more time on the goals that require a decision. A target that was met cleanly may only need a brief acknowledgement.
3. Results and KPIs: 15 Minutes
Show the evidence behind the quarter.
Use comparisons and trends.
For example: Weekly active users: 712 of 840, compared with 594 last quarter. Q2 target: 700.
Then explain what that means for the customer outcome.
If active use is concentrated in two departments and the third is barely using the platform, show the departmental split. The account-wide average could hide a problem that affects the next rollout.
4. Risks and Blockers: 10 Minutes
For each material issue, explain:
- What happened?
- Which customer goal does it affect?
- What has already been done?
- What still needs to happen?
- Who needs to be involved?
A QBR audience does not need the complete history of every support ticket. Give them enough information to understand the business impact and make the required decision.
5. Next-Quarter Plan: 15 Minutes
Agree on the few priorities that deserve focused attention over the coming quarter.
The discussion may include:
- completing an unfinished rollout
- changing the success measure
- addressing low adoption in a specific group
- preparing for expansion
- resolving a recurring product or process issue
- introducing a new use case
- improving executive engagement
- adapting the success plan to a new business priority
Document the measures that will be reviewed next time.
6. Actions and Owners: 5 Minutes
Close with a simple action table.
| アクション | 所有者 | Due date | Evidence of completion |
|---|---|---|---|
| Complete regional enablement | Customer Ops + CSM | Sept 15 | Remaining leads trained |
| Review adoption and operating trend | Joint | Oct 15 | Results reviewed against agreed thresholds |
| Reassess expansion | Executive sponsors | Oct 20 | Decision recorded |
This becomes part of the follow-up and the starting point for the next review.
What QBR Metrics and KPIs Should You Track?
The right QBR metrics depend on what the customer is trying to achieve. A support platform, recruiting product, cybersecurity tool, and revenue platform should not produce identical scorecards.
A useful scorecard combines several types of evidence.
1. Business Outcome Metrics
Start with the result the customer wanted from the product.
| Customer goal | Metrics that could show progress |
|---|---|
| Reduce support workload | Handling time, tickets per agent, resolution time |
| Speed up onboarding | Time-to-value, onboarding duration, completion rate |
| Improve productivity | Output per employee, admin time, manual tasks removed |
| Reduce operating costs | Cost per transaction, hours saved, tools consolidated |
| Improve service | SLA attainment, first-response time, escalation rate |
| Increase conversion | Conversion rate, qualified opportunities, attributed revenue where defensible |
| Reduce risk | Error rate, incidents, compliance completion, audit findings |
Show the target and previous result alongside each metric.
2. Product Adoption and Usage Metrics
Usage data can show whether the behaviors associated with the customer’s success plan are happening.
Common measures include:
- active users versus eligible users
- license utilization
- feature adoption
- workflow completion
- usage frequency
- adoption by department, role, or region
- time-to-value for new users
Segment the data when averages hide important differences.
An account may show 84% overall adoption while one business unit sits below 50%. If that unit is central to the customer’s expansion plan, the lower figure deserves attention.
Give each important metric enough context to interpret: Baseline → target → current result → trend → explanation
3. Service and Support Metrics
Service metrics belong in the review when they affect the customer’s ability to get value. These may include SLA attainment, first-response time, resolution time, unresolved escalations, recurring incidents, and support-volume trends.
Investigate the cause behind a change before presenting it. A rise in ticket volume caused by a larger rollout has a different implication from repeated tickets caused by the same integration failure.
4. Customer and Relationship Signals
Some account changes appear in conversations first. Listen for budget pressure, procurement changes, stakeholder changes, competitor mentions, expansion discussions, and repeated frustration with a workflow.
Make sure to verify any material finding against the source conversation itself before it goes into the QBR.
Internal health scores, churn risk, and renewal probability can help the team prepare. Use the underlying facts in the customer deck only when they are relevant.
QBR Deck Template
There is no right or wrong structure when it comes to QBR decks. However, it should organise the evidence and keep the conversation easy to follow. For most customer QBRs, eight slides are usually enough. Also, you can always detailed analytics in an appendix.
1. QBR Overview
Include:
- customer name
- quarter
- date
- attendees
- two or three topics requiring attention
Avoid long company introductions when the relationship is already established.
2. Previous Goals
Bring forward the outcomes agreed during the previous QBR.
A scorecard works well:
3. Executive Summary
Summarize the state of the account in a few sentences.
例えば、こんな感じです：
Average handling time reached the Q2 target. Overall workflow adoption rose to 78%, although EMEA finished 19 percentage points below target following a delay in regional enablement. The account team recommends completing that rollout and validating the operational impact before moving into APAC.
Someone joining only the executive portion of the meeting should be able to understand the account from this slide.
4. Results and Trends
Show the evidence supporting the summary.
Quarter-over-quarter trends, target comparisons, and segmented results are generally more useful than isolated current-period numbers.
Keep causal claims within what the evidence supports. If workflow adoption and handling time improved during the same period, say that. Claiming that adoption caused the full improvement requires stronger evidence.
5. Drivers and Blockers
Explain the main factors behind the results, such as delayed enablement, a stakeholder change, a process problem, implementation scope, or a technical dependency.
6. Current Customer Priorities
Capture material changes since the previous review, including budget pressure, leadership changes, headcount, a new market, compliance work, or a revised timeline.
7. Next-Quarter Plan
Present the priorities you recommend carrying forward and discuss them with the customer.
Include the measure of progress, ownership, and major dependencies.
8. Mutual Action Plan
Record the actions agreed during the meeting, with owners and dates.
Keep supporting usage reports, ticket histories, detailed implementation timelines, and roadmap material in the appendix.
10 QBR Questions to Ask Customers
Some of the most useful QBR information will come from the customer during the discussion.
Questions worth asking include:
- Have your priorities changed since our last review?
- Which result from this quarter matters most to your leadership?
- Where are you seeing less value than expected?
- What is making adoption difficult for a specific team?
- Are the outcomes we are measuring still the right ones?
- Which business priority should receive most attention over the next quarter?
- Has the decision-making team changed?
- What could stop the next phase from succeeding?
- Is there an expectation from your team that we have not addressed?
- Who else should be involved in the next phase?
Several of these questions work better before the meeting. They give the account team time to investigate the answer and bring useful evidence to the QBR.
QBR Best Practices for Customer Success Teams
A template creates consistency. B But, the quality of the review comes from the account work behind it.
1. Build the New QBR From Previous Commitments
Open the previous QBR or success plan before creating the new deck. Check the target, owner, due date, result, and current status. If a goal was vague, leave the previous quarter as recorded and define the measurement properly for the next one.
2. Reconfirm Priorities Before Finalising the Deck
Speak to the customer champion before the final version is ready.
Find out what changed, what their leadership wants to understand, and whether a new issue deserves attention.
A customer entering a cost-cutting program may care much more about utilization and efficiency than the expansion opportunities discussed three months earlier.
Your deck should reflect the customer you have today.
3. Lead With the Customer Outcome
Decide which business result each major metric helps explain. If the customer bought your platform to reduce support workload, seat utilisation alone will not establish the outcome. Show the operational measure and use product data to explain the behaviours around it.
4. Segment Data When the Average Hides the Problem
Break results down by region, team, role, use case, workflow, or implementation stage when the account-wide number conceals an important gap. This is especially useful when a weak segment affects an upcoming rollout or business target.
5. Explain Missed Targets With Specific Evidence
Avoid vague labels such as “adoption opportunity” or “room for improvement.”
State what happened.
例えば、こんな感じです：
EMEA adoption finished at 46% against the 65% Q2 target. Regional training started six weeks later than planned, and 18 team leads have yet to complete enablement.
Then cover:
- What contributed to the gap?
- What has already changed?
- What remains unresolved?
- Which decision is required?
A specific problem gives both sides something useful to work on.
6. Use Customer Conversations to Explain the Numbers
A dashboard may show a decline in usage without telling you that two regional managers left or a process changed. Meeting insights can help CSMs retrieve those themes across customer calls, while recurring AI reports can help track selected topics during the quarter.
7. Keep Supporting Detail in the Appendix
The core deck should contain the information needed to understand the account and make decisions.
Move deeper supporting material out of the main flow, including:
- feature-level usage tables
- complete ticket histories
- individual user activity
- detailed project plans
- secondary KPI charts
- lengthy roadmap material
Keep it available when a question requires it.
8. Build the Attendee List Around the Decisions
Invite the people needed for the decisions on the agenda. A regional rollout may require the customer leader who controls enablement resources; a technical dependency may require a specialist for part of the meeting.
9. Handle Roadmap and Expansion Discussions Carefully
Expansion and roadmap conversations often belong in strategic account reviews, but timing matters.
If the current rollout is underperforming, understand why before moving the meeting toward additional licenses or regions.
If a roadmap item is relevant to the customer’s future plan, clarify whether it is committed, planned, or still exploratory. A tentative item shown in a formal QBR deck can easily be remembered later as a promise.
10. Finish With a Mutual Action Plan
Reserve the final few minutes for actions, owners, dates, success measures, and dependencies. Send the agreed version after the meeting and use it as the starting point for the next QBR.
What to Do After a QBR
Send a short written recap while the decisions are fresh. Include the priorities agreed, action items, owners, dates, and open questions. Update the customer success plan and CRM so the account record reflects the final discussion.
If the QBR is recorded with tl;dv, AI meeting minutes can capture key discussion points and action items. Teams can also use the Salesforce integration or HubSpot integration to move meeting information into the systems where the account is managed.
How to Use tl;dv for QBRs
The account history behind a QBR can include onboarding sessions, success check-ins, product calls, escalations, executive conversations, and commercial discussions. tl;dv gives CS teams a searchable meeting record they can use during preparation and follow-up.
1. Before the QBR
A CSM can use conversational intelligence across multiple meetings to review the quarter without opening every recording individually.
A preparation prompt could look like this:
Review meetings with [Customer] since [date]. Identify customer-stated goals, changes in priorities, blockers, commitments from each side, stakeholder changes, positive outcomes, and discussions involving renewal, budget, or future expansion. Keep direct customer statements separate from interpretation and include the source meeting for important findings.
Then narrow the search to specific questions such as which commitments remain open, which concerns appeared more than once, and how the customer’s priorities changed during the quarter.
There is a useful example of this type of workflow in tl;dv’s Speee Customer Success case study. Speee built more than 20 purpose-specific prompts for its sales-to-CS handoff and kept the source meeting available for verification. The company reported a two-thirds reduction in handoff effort and onboarding completed 23 days faster.
2. During the QBR
Recording the QBR creates a reference for new priorities, decisions, customer concerns, action items, owners, and deadlines. tl;dv’s AI Agents for Meetings support workflows around meeting summaries, customer feedback, CRM updates, and action-item tracking.
3. After the QBR
Use the meeting record to confirm the recap and update the systems where the account is managed. tl;dv connects with CRM and workflow tools through its integration library, so the agreed actions and relevant meeting context can remain accessible during the quarter.
The next review can then begin with a cleaner record of what the customer and account team agreed previously.
FAQs About QBRs
What should you do if customers are disengaged during QBRs?
Look at the agenda first.
Customers tend to disengage when the review becomes a walkthrough of usage charts, roadmap updates, and information they could have received by email. Ask what they want from the session beforehand and spend the live meeting on decisions, risks, changed priorities, and areas where their input is actually required.
Should product roadmap updates be included in a QBR?
Only when they are relevant to the customer’s plans.
If an upcoming capability affects a rollout, dependency, or agreed goal, it belongs in the discussion. A general catalogue of upcoming features usually does not. Be clear about whether anything shown is committed, planned, or exploratory.
Can you run a QBR asynchronously?
Yes. An async QBR can work for accounts where the quarter mainly requires reporting rather than discussion.
You might send a short performance summary or recorded walkthrough covering results, risks, and proposed next steps, then schedule a live conversation only where decisions or strategic discussion are needed. Some CS teams are already experimenting with async account updates instead of compulsory quarterly meetings.
Does every customer need a QBR?
No. Live QBRs make the most sense for strategic or complex accounts where there is enough change, risk, or decision-making to justify the time. Lower-touch or stable accounts may be better served by an async review, written update, or less frequent strategic meeting.
