Most QBRs are glorified status updates.

You spend two weeks building a deck. You walk through adoption metrics, support tickets, and a roadmap slide the customer has seen before. You ask if they have questions. They say no. You schedule the next one.

And you leave without a commitment.

That's not a business review. That's a reporting exercise. And it's costing you renewals and expansion opportunities every single quarter.

The QBR is one of the most underutilized commercial tools in a CSM's arsenal. When run correctly, it's not a recap of the past, it's a forward-looking commercial conversation that builds urgency, surfaces expansion signals, and walks you out of the room with a verbal commitment.

Here's how to run one that actually closes business.

Most QBRs are structured like this:

This structure is broken.

It positions you as a vendor reporting in. Not a partner driving outcomes. The economic buyer in the room doesn't care about your feature releases or your NPS score. They care about one thing: Are we getting the return we expected on this investment?

The shift is simple but powerful.

Old QBR structure: Past → Present → Future (eventually)

Revenue-driven QBR structure: Goals → Gap → Growth

Every section of your QBR should ladder back up to that framework. What were we trying to achieve? Where do we stand against it? What do we do next to close the gap or accelerate the gains?

Open by restating the customer's goals in their language. Not your success metrics. Their business outcomes.

Before the meeting, pull your notes from the original sale, your onboarding kickoff, and your last business review. What did they say they were trying to achieve? What was the problem that made them buy?

Start the meeting like this:

"When we started working together, you told us you were trying to [reduce ramp time for new reps / cut manual reporting overhead / improve customer retention]. Before we jump in, has that priority shifted? Is that still the number one thing we're solving for?"

Two things happen here. First, you signal that you've been paying attention. Second, you create space to discover if their priorities have changed, which is intelligence you need for the commercial conversation ahead.

This is where most QBRs fall apart.

CSMs report on product usage. Logins. Feature adoption. Sessions per user. The problem is that none of those metrics mean anything to a VP or CFO. They're internal success metrics. They're not business outcomes.

The translation framework is three steps:

What they did → What changed → What that's worth

Example: "Your team automated the pipeline reporting workflow in month two. That eliminated roughly 4 hours of manual work per rep per week. Across your 12-person team, that's nearly 2,500 hours recaptured this year, time that's been redirected to customer-facing activity and a savings of $xyz"

Now you're speaking CFO. Now you're building a renewal case that doesn't need you in the room to hold it together.

If you can't translate your customer's usage data into a business outcome narrative before the meeting, you're not ready to present yet.

Every account has a gap. The space between where they are and where they want to be. Most CSMs avoid naming it directly because it feels uncomfortable.

That's backwards.

The gap is your commercial leverage. It's the reason they should keep investing, and invest more.

Name it directly:

"You're at about 60% of where you said you wanted to be on [goal]. Here's what's blocking the other 40%, and here's what we'd need to do to close it."

Then stop talking.

Let them respond to the gap. That response tells you everything about where the expansion conversation goes next. If they lean in, you have urgency. If they push back, you have an objection to handle. Either way, you're in a commercial conversation, not a status update.

Also remind them of what the real commercial value is for them to close that gap. Remind them of what the real pain was when they started and get them back into that place of why this was an urgent issue to solve from the start. 

This is the most neglected part of every QBR.

The meeting ends. Someone says "great conversation." You promise to send a follow-up email. The momentum dies.

Every QBR needs to end with a specific, time-bound commitment from the customer, not a vague "let's explore this further."

It doesn't have to be a signature. It can be:

The commitment is the close. If you leave without one, you haven't finished the meeting.

The QBR doesn't start when the Zoom opens. It starts two weeks before.

1. Interview your champion. Before building a single slide, get 30 minutes with your champion and ask: "What does leadership care most about heading into this quarter?" Build your narrative around their answer. If your deck doesn't map to what the room cares about, it doesn't matter how good the data looks.

2. Pre-wire the expansion conversation. Identify one specific growth opportunity before you walk in. A team that isn't using the product yet. A use case you know they have. An adjacent problem you've seen come up. Come in with a hypothesis, not a pitch.

3. Set the agenda as a shared document. Send the agenda 48 hours in advance and ask them to confirm it's the right focus. This does two things: it shows professionalism, and it creates implicit buy-in for the outcomes you're walking them toward.

QBRs feel transactional when CSMs treat them as reporting obligations.

They become commercial conversations when CSMs treat them as the most important meeting in the customer relationship.

Here's the reframe:

The QBR isn't a meeting where you report on the past. It's a meeting where you earn the right to shape the future.

That means you come in with a point of view. You have a thesis about where this customer should go next. You've done the prep to back it up. And you close by directing them toward a next step, not waiting to be asked.

That's not selling. That's advising. As CSM’s we must be strategic advisors and consultants for our customers. 

And customers who are advised well don't just renew. They expand.

The QBR is yours to own. Use it.

If this reframe hit home, forward it to one CS leader on your team who's running QBRs that feel like status updates.

And reply and tell me: what's the hardest part of your QBR right now? The prep, the room, or the close? I read every reply.

Onwards,

Mark