The QBR nobody wants to attend

Here's a test. Think of your next QBR. Now imagine the customer emailed to say they'd like to skip it this quarter. Be honest: is your first feeling disappointment, or relief?

If it's relief, your QBR is broken, and you already know it. You're spending two or three days building a deck. The deck has usage charts the customer could see in the product, a product roadmap they didn't ask for, and a slide called "Successes" that you wrote because the template had one. The customer sends two people who spend most of the hour on their laptops. Everyone agrees it was useful. Nobody can remember a single thing from it a week later.

I did these for years. Here's what I eventually worked out.

The QBR exists for the wrong person

The standard QBR is built for the vendor. It's a chance to show value, surface expansion, and get in front of senior people. All of that is legitimate. The problem is the customer knows it, and nobody gives up an hour of their quarter to help a supplier hit their goals.

The only business review that works is one the customer would run themselves if you didn't exist. That means it has to be about their quarter, not yours. What were they trying to achieve? What happened? What's in the way? Where does your product fit into that, if at all?

If that sounds like it requires knowing what the customer is actually trying to achieve, yes. That's the job. If you can't answer that question for an account, you're not ready to run a business review with them, and a deck won't hide it.

Three slides. Maybe four.

Here's the format I ended up with. It fits on a page and takes about forty minutes.

1. What you told us mattered. One slide, in their words, from the last conversation. "You said the priority this quarter was getting the new sales team onboarded without adding to support load." If you don't have this, you have a bigger problem than the QBR.

2. What happened. Against those priorities, specifically. Not "usage went up 12%". Rather: "The new team is live, here's what they're using, here's what they're not, and here's the one thing that's been causing tickets." Include the bad news. A review with only good news is a pitch, and they'll read it as one.

3. What's next. Two or three things you'd suggest, tied back to what they said mattered. Some of them might involve your product more. Some might not. If the honest recommendation is "stop using this feature, it's not helping you", say it. Nothing builds trust faster than a vendor telling you to use less of their product.

4 (optional). What's changed on our side. Only things relevant to them. If you shipped something they've been asking for, this is where it goes. If you shipped twenty things they didn't ask for, that's a newsletter, not a slide.

That's it. No usage dashboards unless they tell a story. No roadmap tour. No "about us". No slide titled "Partnership".

Who's in the room matters more than what's on the slides

A good review with the wrong people is still a waste. The person who buys and the people who use are rarely the same, and you need both.

The users will tell you what's true. The buyer will tell you what's going to happen. If you only ever meet the users, you'll be surprised at renewal. If you only ever meet the buyer, you'll be reporting on an account you don't actually understand.

Getting the senior person into the room is the hard part. The trick is not to invite them to a QBR. Invite them to the one slide that matters to them. "I'd like fifteen minutes with Sam to walk through how the new team's onboarding went against what she asked for in July." That's a meeting a VP will take. "Quarterly business review" is a meeting a VP delegates.

When to skip it

Not every account needs a quarterly review, and pretending otherwise is why they become theatre. Small accounts, accounts in steady state, accounts where nothing has changed: a short email with the three points above does the job, and the customer will thank you for not booking an hour.

Save the real meetings for when something is actually happening. A new team coming on. A renewal within two quarters. A change in their leadership. A problem you need to get ahead of. Those are the moments where sitting down together changes the outcome. The rest is calendar filler.

The actual goal

A business review has one purpose: at the end of it, you and the customer should agree on what's true about the account and what happens next. If you walk out with that, it worked, whether it took ten minutes or an hour, whether there was a deck or not.

If you walk out with "great session, let's do it again next quarter" and nothing else, you've spent three days building a document whose main achievement was its own existence. The customer felt the same way. That's why they were on their laptops.