Stop Running QBRs Like Reporting Sessions
A quick test. Think about the last QBR your team ran. If the customer had skipped it and read the slides afterward, would they have missed anything?
If not, that wasn't a business review. It was a report with a calendar invite.
I've sat through a lot of QBRs, and most follow the same script: usage charts, a roadmap preview, a support ticket summary, a thank-you slide. The customer nods, the CSM feels productive, nothing changes. And the executive sponsor you worked hard to get in the room quietly decides not to come next time.
Changing how my team runs these meetings has been one of the most useful things we've done. This is what we changed.
Open with their business
A reporting session starts with your product: what they used, how often, which features. A real business review starts with the customer's business. What are they trying to hit this year? What's changed since the last meeting? What's their leadership worried about?
It sounds like a small change, but it flips the meeting. Your product becomes evidence in their story instead of the subject of yours. Usage data still matters, but only as proof you're helping them reach their goals, which is the whole argument for measuring outcomes instead of logins.
Bring one thing they don't know
The fastest way to lose an executive is to tell them something they already know. They can see their own usage. What they can't easily see is a pattern across their industry, a trend in their data they missed, or how peers are handling the same problem.
My rule is that every review needs at least one genuine insight the customer didn't have walking in. It's a high bar and it changes how CSMs prepare: less time formatting charts, more time thinking about what the data means.
Tell it as a story
Executives don't act on a pile of metrics. They act on a story they believe. The reviews that land follow a simple arc: where you were, what happened, what it means, what we should do next. That structure turns numbers into a decision, and a meeting that ends in a decision is one executives come back to. I go deeper on the craft in stories with data.
Make a recommendation
A reporting session ends with "any questions?" A business review ends with an agreement on what happens next. A new team to roll out to, a goal to commit to, a project to start, and sometimes an expansion conversation.
A lot of CSMs get uneasy here because it feels like selling. If you've done the earlier work, it isn't. The recommendation is just where the story naturally lands. You're advising, not pitching, and it's often where expansion signals turn into a real conversation.
Prepare like it's your own board meeting
None of this works if the deck gets built the night before. Talk to your champion ahead of time and find out what the executive cares about. Read up on their business: earnings calls, press releases, what their leaders are posting. Write the story before you build a single slide; if you can't explain it in three sentences, the deck won't save you. And decide what you want them to agree to before you walk in.
What it changed for us
Once the meetings were worth their time, getting executives to attend got easier. Conversations moved from "how's it going?" to "what should we do next?" Expansion came up on its own instead of being forced. And CSMs started seeing themselves as advisors, which is how customers started seeing them too.
You only get a few hours a year with a customer's leadership. Don't spend them reading a report out loud.
If you want a starting point, I've put together a free business review template with an agenda, slide outline, discovery questions and a follow-up email.
If you want a second set of eyes on your team's review format, send me a note.
