How to run a QBR that proves customer value

"Last quarter, you told us getting the new team fully onboarded was the priority. Usage looks healthy, so we seem to be on track."

The customer pauses.

"Actually, the new team still hasn’t adopted it. We talked about this on our last 2 calls."

Now you’re catching up in the middle of the QBR.

The usage number was accurate. It just missed what the customer had been saying for 2 months. Somewhere across the calls, CRM updates, and follow-ups, that context got lost.

Walk into the same meeting with the quarter’s conversations in front of you, and you can say:

"You told us getting the new team onboarded was the priority. Overall usage is up, but that team is still behind. You raised the onboarding issue in April and again in May, and we haven’t closed it yet. I think we should make that our first priority this quarter."

That's the kind of conversation a QBR should create. You know what the customer wanted, what changed during the quarter, what’s still unresolved, and what both sides need to do next.

Building the slides is usually the easy part. Reconstructing 3 months of customer history is where the work piles up.

By the end of this guide, you’ll know how to turn scattered customer data and conversations into a QBR built around the 7 things that matter.

What should be included in a QBR?

If you have a QBR this week and need the shape of it before anything else, here it is. Seven things to include in a QBR, in order:

1. Goals the customer agreed to last quarter
2. Progress against those goals
3. Value and outcomes achieved
4. Risks and unresolved issues
5. Changes in the customer's priorities
6. Next-quarter goals
7. Actions, owners, and deadlines

That's the whole shape. Everything past this point is how to fill in each part, run the meeting itself, and follow through after it, including a fill-in template later in this guide you can copy directly into a doc.

What is a QBR (quarterly business review)?

A QBR, short for quarterly business review, is a structured meeting between a vendor's team and a customer's team to review the past quarter and plan for the next. "Quarterly" describes a default cadence, not a rule. A complex account might need one every three months, a small one every six.

It isn't a status update. A status update lists what happened. A QBR connects what happened to whether the customer is closer to the outcome they came for.

QBR vs. EBR: what's the difference?

"QBR" and "EBR" (executive business review) get used almost interchangeably, but they're not the same meeting.

If a QBR keeps drifting toward budget and multi-year strategy, that's usually a sign the account needs an EBR too, not that the QBR agenda is wrong.

In ChurnZero's 2025 Customer Revenue Leadership Study, 74% of respondents said most of their company's revenue comes from existing customers. The same research found companies with CSMs reported 98% NRR, compared with 90% at companies without them. That's correlation rather than proof that adding a CSM produces an 8-point lift, but it shows how closely post-sale work sits next to recurring revenue.

A QBR is one of the places that work becomes visible: what the customer wanted, what changed, where they're stuck, and what both sides agreed to do next.

What QBR metrics should you track?

The right QBR metrics depend on what the customer wanted to achieve. Start with the goals agreed on last quarter, then choose the metrics that show what changed and whether those goals moved.

For a customer success QBR, those might include:

A number needs context before it belongs in the QBR. “Adoption increased from 62% to 74%” tells you what changed. The 7-part QBR structure gives that number a job.

Say the customer agreed to reach 80% adoption last quarter. Here's how the account might look by the time you prepare the review:

You won't have a metric for every part. A change in priorities might come from something the customer said on a call. An unresolved risk might show up as a stakeholder who stopped attending meetings before it appears in the usage numbers.

That's why QBR metrics work best alongside the quarter's customer conversations. Together, they give you the evidence to fill each part of the review and decide what happens next.

How to prepare for a QBR

A QBR works as a loop. You collect what happened with the customer, check whether you're making progress on what they care about, bring the right people together, and agree on what happens next.

We call this the QBR Value Loop: Capture → Prove → Convene → Commit.

The commitments you make in one QBR become the things you check in the next one. That's how each review picks up where the last one left off.

1. Gather what the customer said this quarter

Start with the conversations since your last QBR.

You're looking for what the customer asked for, what they were worried about, whether their priorities changed, and what your team promised to do.

Say a customer mentioned low adoption in March. They brought it up again in April, then again in May. You want to connect those comments before you walk into the QBR.

This is usually the slowest part of prep. The information might be spread across call recordings, notes, CRM fields, Slack messages, and the memories of 3 different people.

With Avoma, you can ask a question across the account's conversations, such as:

"What concerns did this customer raise this quarter?"

The answer comes from the meeting transcripts, and you can go back to the calls where each concern came up.

2. Check what you promised last quarter

Pull up the commitments from your last QBR.

Maybe your team promised another onboarding session. Maybe the customer agreed to roll the product out to a second department. Check what got done, what stalled, and what's still open.

You don't want to hear, "What happened to that training you said you'd schedule?" and have to search your memory in front of the customer.

3. Check progress against the customer's goals

Go back to what the customer said they wanted to achieve.

Then find evidence that shows how far you've moved.

Say their goal was to get new employees productive within 10 days. "Usage increased 30%" doesn't tell them whether you got there.

"You wanted new employees productive within 10 days. We went from 14 days to 8" gives them an answer they can use.

4. Find problems that are still open

Look for concerns that came up during the quarter and never got resolved.

Maybe adoption is low in one department. A support issue keeps coming back. Your champion hasn't joined the last 3 calls. The customer asked for an integration update 6 weeks ago and is still waiting.

Put those issues on the agenda yourself. You should already know about a problem the customer has reported to your team.

5. Decide who needs to attend

Look at what you need to discuss and decide who needs to be there.

On the customer's side, that usually means your day-to-day champion and, when the conversation calls for it, someone involved in budget or business decisions.

Do the same on your side. If a technical issue is likely to take up 20 minutes of the QBR, bring someone who can answer it.

6. Send the agenda before the meeting

Use everything you've found to build the agenda.

Send it 2 to 3 days before the QBR and ask the customer what they'd like to add. They get time to prepare, and you get an early warning if you missed something important.

How to prepare for a QBR in 30 minutes

If you've only got 30 minutes, start with the customer's conversations from this quarter.

Look for a concern that came up more than once. Check the commitments from the last QBR. Find one measurable result tied to a goal the customer set. Then send a short agenda covering progress, open issues, and what you need to decide together.

You'll walk in knowing what deserves a conversation.

How to run a QBR meeting

Start by telling the customer where you think the account stands.

For example:

"Last quarter, we agreed to get the operations team to 80% adoption. We're at 74%. The original team is doing well, but the new department is still at 48%, so I'd like to spend some time on what's getting in their way."

Now everyone knows why they're in the room.

1. Review progress against the goals

Take the goals from the last QBR one at a time.

Show where each one started, where it is now, and what happened along the way. Tie the numbers back to something the customer wanted.

If the goal was faster onboarding, talk about onboarding time. If the goal was adoption in a new department, show adoption there.

2. Bring up open problems yourself

If the customer raised the same problem twice this quarter, bring it up.

You might say:

"Reporting came up on our April and May calls, and we haven't closed that issue yet. Here's where it stands."

That tells the customer you heard them and remembered.

3. Ask what's changed

You know what happened in the conversations you've already had. The QBR is also your chance to find out what hasn't made it into those conversations yet.

Ask:

"What's changed on your end since we last spoke that we should know about?"

Maybe there's a new executive. Budgets changed. A team is being reorganized. A goal that mattered 3 months ago has dropped down the list.

You need that information before setting the next quarter's goals.

4. Agree on what happens next

End with specific outcomes you can check later.

"Improve adoption" is hard to check.

"Get the operations team from 48% to 70% adoption by October 31" sets a target for both sides.

Then decide who owns the work required to get there.

What to do after a QBR

The meeting created a new set of promises. Write them down while everyone still remembers what they agreed to.

1. Give every action an owner and a date

"Schedule another onboarding session" can sit untouched for 3 weeks.

"Sarah will schedule the operations onboarding session by August 21" gives you something you can follow up on.

Do this for commitments on both sides.

2. Update the account record

Put the decisions, risks, goals, and commitments somewhere the rest of the account team can find them.

This matters 3 months from now. It matters even more if the account changes hands and a new CSM needs to understand why a decision was made.

Avoma can pull action items from the QBR and carry them into the account record. The commitments made in the meeting are recorded so that no one has to reconstruct them afterward.

3. Schedule the next QBR

Get the next review on the calendar before the current one disappears into everyone's meeting history.

Now you have a date when today's commitments will be checked again.

4. Carry the commitments into the next quarter

This closes the QBR Value Loop.

The goals and commitments you just agreed on become the starting point for the next quarter. When the next QBR comes around, you can pull them up and ask: What did we agree to do? What happened? What changed? What still needs work?

Then the loop starts again.

QBR example: Finding an adoption risk hidden by healthy usage

Say you have a customer with 2 departments using your product.

The first department has been using it for 10 months, and adoption is healthy. The second came on 4 months ago and barely uses it.

Your overall account health still shows green because the first department's usage is high enough to pull up the average.

Then you check the customer conversations.

2 months ago, the second department's lead said:

“We haven't really had time to get everyone set up properly yet.”

The issue never got followed up.

Now you have something useful to bring into the QBR. You can say:

“Overall usage looks healthy, but the second department is still behind. You mentioned getting everyone set up was difficult 2 months ago, and we haven't closed that gap. I'd like to schedule a 30-minute onboarding session within the next 2 weeks and check adoption again 30 days later.”

Assign an owner to the onboarding session on both sides, and put the follow-up on the calendar.

The green health score still matters. The conversation explains what the green score missed.

A QBR template you can fill in directly

The table below is the same seven-part shape from the top of this guide, turned into the actual question you need to answer for each part.

Copy this directly and fill it in per account:

Goal: ______

Evidence of progress: ______

Business outcome: ______

Risk / blocker: ______

Customer priority that changed: ______

Next action: ______

Owner: ______

Deadline: ______

Keep internal-only fields, renewal probability, churn risk score, competitive mentions, out of the version the customer sees. Those belong in your own account review, not the customer-facing deck.

QBR best practices for customer success teams

• Send the agenda two to three days ahead, and ask the customer if anything's missing from it.
• State a point of view in the first minute, not a replay of the quarter.
• Ask a direct question at least once: "what's changed on your end we should know about?"
• Close every commitment with a name and a date, and open the next QBR by checking whether they got done.
• Keep the meeting to an hour. Past that, attention drops faster than the agenda does.

Common mistakes that turn a QBR into a wasted hour

Common mistake: building the deck from memory the night before, instead of from the quarter's actual calls and notes.

• Getting defensive when the customer raises a real concern, instead of naming it as something to fix.
• Running every account off the same generic template, regardless of what happened this quarter.
• Ending the meeting without a scheduled date for the next one.
• Letting last quarter's commitments disappear, so the next QBR starts from a deficit instead of a track record.

How Avoma helps customer success teams prepare for QBRs

The friction points called out above (finding what happened across a quarter of calls, and keeping commitments alive after the meeting ends) are where most QBR practices break down, and where Avoma is built to help.

Avoma records and transcribes customer calls, generates notes and action items from each one, and surfaces account health and risk signals from conversation data rather than a lagging CRM field, catching the kind of quiet disengagement a green health score misses.

Ask Avoma works at different levels. For a single meeting, ask a question and get an answer pulled from that transcript. At the account, deal, or pipeline level, ask questions across every meeting tied to it in plain language, without opening each recording yourself. Source selection and @ tagging let you pin the exact meetings, deals, or accounts you want as context, so the answer comes from what you pointed it at, not a blind search across everything Avoma has recorded.

If your QBR work happens outside Avoma, Avoma MCP lets you bring that meeting and account intelligence into other AI tools that support MCP. A CSM working in a tool such as Notion can use Avoma context there instead of manually copying call notes, customer concerns, and commitments from one system to another. The conversation record stays useful after you leave Avoma.

Notes Templates and Collections keep QBR notes in a consistent shape across accounts. The Meeting Agenda template lets you build the review agenda with the customer before the call starts, instead of surprising them with it when the meeting opens.

Customer-facing teams save 4+ hours a week using AI meeting assistance instead of manual note-taking and CRM updates. That figure comes from broader usage across sales and CS teams, not QBR prep on its own, but the mechanism is the same one at work here: less time rebuilding a quarter from memory, more time acting on what the customer said.

Pro tip: A starting prompt for Ask Avoma before a QBR:

"Using every call for [account name] since [last QBR date], prepare a QBR summary using only information from these conversations.

Organize the answer into:

1. Goals agreed last quarter: What did the customer say they wanted to achieve?
2. Progress against those goals: What evidence shows progress or lack of progress?
3. Value and outcomes achieved: What results has the customer said they're seeing?
4. Risks and unresolved issues: What concerns came up, especially more than once, and which are still open?
5. Changes in customer priorities: What new goals, needs, or changes did the customer mention?
6. Next-quarter goals: What goals or outcomes have been discussed for the next quarter?
7. Actions, owners, and deadlines: What commitments did either side make that are still open? Include the owner and deadline when mentioned.

For each point, include the meeting date and a short supporting quote or reference. If the conversations don't contain enough evidence for a section, say 'No evidence found' rather than making an assumption."

A good QBR should make the next quarter clearer

A customer shouldn't leave a QBR wondering why they spent an hour reviewing information they already knew.

They should leave knowing what they set out to achieve, how far they got, what's getting in the way, and what both sides agreed to do next.

That starts with having the quarter's full story in front of you. Usage numbers tell you part of it. Customer conversations fill in why those numbers moved, which concerns are still open, whether priorities changed, and which promises still need attention.

Use the 7-part structure in this guide as your starting point. Carry the commitments from one QBR into the next, and each review has a record to build from instead of starting over every 3 months.

If pulling that record together still means searching through recordings, notes, CRM fields, and Slack threads, Avoma can do that work across your customer conversations.

Start a free trial or book a demo to try it with your own accounts.