The Business Review Customers Actually Want to Attend
There's a particular kind of meeting preparation that most CSMs know well. The slide deck gets assembled. The usage data goes in. The renewal date is highlighted. A list of features coming soon is added for good measure. The CSM rehearses how to walk through the stats without the customer's eyes glazing over. And then the meeting happens, and nobody on the customer's side is quite as engaged as the vendor team hoped, and the "how can we do better?" question at the end generates a polite non-answer.
This is the QBR most CS teams run. And the reason it lands flat has nothing to do with presentation skills.
It lands flat because it's designed around what the vendor wants to communicate (we are valuable, here is the evidence) rather than around what the customer needs from the meeting. Those are different things. And until the meeting is designed around the second question, it will continue to feel to the customer like a renewal-justification exercise dressed in business review clothes.
What customers actually want from a business review
The answer varies by customer, which is part of the problem. Most QBR formats assume that a standard template works across the book: same slide structure, same sections, same approximate running order for every account.
But different customer stakeholders are in a business review for different reasons. The economic buyer (the person who owns the renewal budget) wants to understand whether the investment is delivering a return. That is a financial question, and it deserves a financial answer, which is different from a usage report.
The operational lead (the person who uses the product day-to-day) wants to understand whether the things that are frustrating them are on the roadmap, and whether the vendor has noticed the workarounds they've had to build. That's a product conversation.
The executive sponsor (when there is one) is usually there to calibrate the relationship. Are the two organisations aligned at a strategic level? Is this the kind of vendor they should be deepening a commitment to, or is this a product conversation that belongs further down the organisation?
A business review that serves all three needs with the same slide deck is not serving any of them well.
The practical fix
The most consistently effective shift in business review design is moving from a presentation format to a conversation format.
The presentation format is the standard QBR: the vendor walks through their prepared content, the customer asks questions at the end, the meeting wraps with action items that are usually minor. The dynamic is vendor-to-customer: here is what we've done and what's coming.
The conversation format starts from a different question: what is the most valuable thing this customer could take away from 60 minutes with us? The answer to that question should shape the agenda, and it should be agreed with the customer before the meeting, not decided unilaterally by the vendor.
That means a different kind of pre-meeting prep. Rather than asking "when works for the QBR?", the CSM asks something like: "We're planning our next business review. What are the two or three questions that would be most useful for us to come prepared to answer?" The answers to that question become the agenda. The standard data goes in as supporting context, not as the main event.
This shift has several effects. The customer arrives with a different expectation: they're not attending a presentation, they're coming to a conversation where their agenda is being addressed. The CSM prepares differently, because they're building toward specific answers rather than a standard deck. And the meeting is shorter, because it's not carrying sections that aren't relevant to this particular customer.
What the agenda should contain
Even in a conversation format, some structural consistency is useful. A business review that works tends to cover three things.
Business outcomes, not usage. The value section of the meeting should be anchored in the customer's business outcomes (what they came for when they bought), not in product metrics. Usage data is supporting evidence for an outcome story; it is not the story. "You ran 400 reports this quarter" is a usage statement. "The 400 reports replaced a manual process that was taking your finance team two hours a week" is an outcome statement. One of those is meaningful to the economic buyer; the other isn't.
The honest status check. A business review where the vendor only presents positive signals is a business review the customer doesn't trust. Every account has things that haven't gone well: a feature that's proved harder to use than expected, a promise that's been slow to materialise, a workflow that doesn't quite fit. Acknowledging these honestly, and having a clear response to them, builds more credibility than a highlight reel. Customers who feel that the vendor is being straight with them are more likely to renew than customers who feel they're being managed.
A genuine forward agenda. What are the one or two things that, if they happen in the next quarter, would make the most difference to the customer's use of the product? This is a forward question, not a backward one. The best business reviews end with a specific and agreed next step (something that the customer and the CSM have committed to together), not an open-ended "we'll be in touch."
The prep the customer does
One thing that distinguishes the business reviews that work from the ones that don't is whether the customer arrives having done any preparation.
If the meeting is a vendor presentation, there's nothing for the customer to prepare. They turn up and watch. If the meeting is a business conversation, the customer can prepare by thinking about the questions they want answered, the things they want to flag, and the priorities that have shifted since the last review.
Getting the customer to that preparation state requires giving them something concrete to prepare against: the pre-meeting question ("what are the two or three things you want to address?"), sent far enough in advance that they have time to think about it, ideally going to the right people in the customer organisation rather than just to the primary contact.
A customer who has thought about the meeting before arriving is a different conversation than one who is encountering the agenda for the first time. The first customer is an active participant; the second is an audience.
The CS Ops layer
Business review design is a place where CS Ops can make a structural contribution without overcomplicating the motion.
A standard pre-meeting process (what the CSM sends, when, to whom, with what framing) ensures the preparation step actually happens consistently across the team. Meeting note templates (structured summaries of the outcome of each review) ensure that what was discussed and committed to doesn't disappear into the CRM as a freetext note. And a post-review follow-up sequence ensures that the actions agreed in the meeting are tracked.
None of this is elaborate. But without it, the quality of business reviews varies dramatically by CSM, and the CS leader has no reliable picture of what the meetings are actually covering.
Questions worth sitting with
When was the last time a customer told you, unprompted, that they found a business review useful? What made it work?
If you could see the feedback your customers gave each other after leaving your last QBR, what do you think they'd say?
What question, if the customer arrived at the meeting prepared to answer it, would give you the most useful information for managing their account over the next quarter?
The short version
The standard QBR is designed around what the vendor wants to communicate, not what the customer needs from the meeting. The shift from presentation to conversation (with the customer's agenda agreed in advance) changes both the dynamic and the outcome.
A useful business review covers business outcomes (not usage), an honest status check, and a genuine forward agenda with specific commitments. CS Ops provides the pre-meeting process, the structured note template, and the follow-up tracking.
Where Pivotal Path comes in
Pivotal Path helps CS teams redesign their business review motion from the ground up, from pre-meeting prep to agenda structure to follow-up. If your QBRs are generating politeness rather than genuine engagement, that's something worth fixing. We can help.
Working on this in your business?
We help UK SMEs and scale-ups turn this kind of thinking into action.
