The QBR that earns a seat at the table.

The first QBR I ever sat in on was bad.

It was a forty-minute slide deck. Logo on every slide. "Q3 in review." "Highlights." "Lowlights." "Looking ahead." Mostly numbers that confirmed what the customer already knew. The customer's POC listened politely. Made a small joke about it being his second meeting in a row that morning. Said "great, thanks, looks like everything's on track" at the end. The meeting closed. We added a new follow-up to the project tracker. Nothing changed.

I left that meeting thinking: this is supposed to be the high-leverage meeting of the quarter, and we just used it to read each other our metrics.

I've since run a lot more QBRs, with very different intent. Some of them have ended with the customer literally asking me to join an internal planning meeting. The difference between those QBRs and the first one is not the polish. It's the prep.

What a QBR is actually for

The clue is in the name. Quarterly. Business. Review. Not "customer-success update," not "platform metrics roundup." Business review.

The customer doesn't need a status update from you. The customer already knows whether they're getting value. They live with the product. They have their own dashboard, their own internal Slack channels, their own opinions about what's working.

What the customer wants from a QBR is a moment, once a quarter, to:

1. Step out of their day-to-day and look at the relationship from above.
2. Hear what someone outside their company sees, based on what you can observe about how they're using the platform and where it's going.
3. Surface the things they've been meaning to ask but haven't gotten around to.
4. Hear, plainly, what's coming that they should be planning for.

None of that requires a slide deck. Most of it requires that you've done your homework.

The prep is the meeting

Here's what I prepare before a QBR. This is the actual work; the meeting is just where it gets delivered.

1. Read the customer's own usage data

Not the vanity metrics. The texture. Which features are they using a lot? Which features are they paying for but not using? Where are their team's clicks concentrated? Which integrations are healthy and which are broken? Has their volume been growing, flat, or quietly declining?

I write down three or four observations. Each one is something I can defend with a specific number. Not "engagement is up" — "your team's automation builder usage tripled in March, and looking at which automations got built it looks like Karen on your team is the new champion."

2. Read their own roadmap (the parts they've shared)

If the customer has mentioned a product direction, a new market, a hiring plan — pay attention. Is what they told you a quarter ago still what they're doing? Often it's not, and that delta is the most useful data you have. You can't ask "are you still doing X?" if you don't remember they ever said X.

3. Identify one thing to give them

Every QBR I run, I show up with one piece of value the customer didn't ask for. A pattern I noticed in their data. A feature they're not using that I think they should. A connection between two of their workflows that could be tightened. A specific introduction inside the company. Something.

This is the move that earns the meeting. The customer expects to spend the hour talking about themselves. When you show up with something they didn't know they were going to get, the meeting tilts.

4. Identify one thing to ask them

A real question. Not "how's everything going." Something like:

• "Last quarter you mentioned you were considering moving the inbound lead-routing logic out of [tool] and into us. Where did that land?"
• "Are you still planning to bring the Mexico operation onto the same instance, or are you spinning up a separate one?"
• "What's the single thing about the platform that your team has stopped asking about because you assumed it couldn't be done?"

The last one is my favorite. It surfaces the iceberg.

4. Bring an honest list of risks

If something in the relationship is fragile, the QBR is the place to name it — calmly, professionally, in a way that invites a conversation. Not a slide titled "Risks" with bullet points and red dots. A short, honest mention: "One thing I want to flag — your usage of the inbound webhook feature has dropped off in the last two months. I don't know if that's a product decision on your end or whether something broke. Either way, worth a few minutes."

Customers respect the vendor who flags things before the customer has to. It is the single most under-used trust-building move I've seen.

The meeting itself

The meeting itself, with all that prep done, takes care of itself. I don't even bring slides for most of mine anymore. I bring:

• A simple shared doc with five or six bullets, mostly the observations from the data and the questions I want to ask.
• The honest piece of value I'm bringing.
• A willingness to throw the agenda away if the conversation wants to go somewhere else.

The last one matters. If the customer wants to spend forty minutes talking about a strategic question and only ten on the platform, that's a great QBR. Don't drag them back to your agenda. Their attention is the resource you're trying to earn.

The signal you ran a good one

You can tell a QBR landed by what happens in the two weeks after it.

• The customer's POC starts forwarding you internal threads. ("Hey, our team is debating whether to build this in-house or just use you guys — what would you do?")
• You get pulled into a planning call that wasn't on the calendar.
• The customer's team starts asking your opinion on things that aren't strictly platform-related.
• Renewal conversations get easier. Sometimes the renewal happens without you raising it.

If none of those things happen, the QBR didn't move the needle, and you should treat the next one as a chance to do it differently. If two or three of them happen, the relationship has graduated. You're not the vendor anymore. You're the person they think with.

What to do this quarter

If you're running QBRs and they feel like status updates: try one differently. Pick your best customer. Don't build a deck. Spend the hour before the meeting reading their usage data with curiosity. Show up with one observation, one question, and one piece of unsolicited value.

You'll feel the meeting change halfway through. The customer will too.

That's the meeting that earns you a seat at their table.

---

If you want to talk through what a really good QBR could look like for one of your specific accounts, drop me a line. I find these conversations clarifying for both sides.