Start the business review with the customer's priorities.

Listen before presenting the evidence

I open with the customer's priorities and the progress against them. I use the customer's own language where possible, because the meeting should be organized around the outcomes they care about.

That opening gives the evidence a purpose. Instead of walking through product activity and hoping its importance is obvious, I connect what happened to the stated priority.

I distinguish outcomes from usage. Time saved, a process improved or a risk reduced belongs in the main conversation when there is evidence to support it. If quantitative outcome data is not available, I use a clear qualitative comparison of what the customer did before and what has changed. I do not turn missing evidence into a confident claim.

Make room for what is not working

I put blockers and risks into the review itself. For each issue, I describe the impact on the customer, the cause as it is currently understood and the recommended next step.

I also leave room for discovery. Account context changes between routine check-ins, and a business review is an opportunity to understand those changes:

• What is ahead for the business?
• What is changing in the organization?
• What is difficult right now?
• What is missing?

I use the answers to test the recommendations I brought into the meeting. A recommendation that no longer fits the customer's priorities needs to change.

Keep recommendations connected to the discussion

I bring a small set of specific recommendations, each connected to a priority the customer has stated. The recommendation should explain the next action and why it matters in that customer's business.

I include expansion only when the evidence supports it. Strong value evidence and expressed interest can justify a growth conversation. If either is missing, I focus on the existing commitments and the work needed to make the current relationship successful.

I close by documenting the commitments from both sides, with owners and dates. I also make space for a direct discussion about anything that could prevent the relationship from continuing. That is a chance to surface a concern while there is still time to address it.

Give the customer credit for the result

When I present an outcome, I attribute the customer's contribution first. The people who changed a workflow, drove adoption or coordinated implementation deserve recognition for that work.

I describe what the champion and their colleagues did, then explain how the product enabled it. That makes the value evidence useful to the champion in front of their executive sponsor.

I want the review to reinforce a real achievement the customer can explain internally. Credit should follow the evidence, with the customer's work visible in the account of what changed.

Keep the detail available without letting it lead

I keep granular usage and adoption data, relevant roadmap information, approved customer quotes and the renewal timeline available as supporting material. These details are useful when the discussion calls for them.

The main sequence stays simple: priorities, value evidence, blockers, business context, recommendations and agreed next steps. That gives the customer room to contribute to the meeting.

I set the review cadence from the account relationship. A strategic account may need a quarterly discussion with an executive sponsor, champion, CSM and CS leader. A less intensive relationship may need a semiannual review or a concise written snapshot. The format should support a meaningful exchange, with ownership and follow-through afterward.

The playbook connects that cadence to segmentation and renewal preparation. The KPI hierarchy helps distinguish supporting activity from the business outcome being discussed.