Utilization charts answer a question your customer never asked. A method for building the review around what they have already committed money to instead.
Most quarterly business reviews open with a utilization chart. Seats provisioned, seats active, month-over-month adoption. Everyone nods. Nothing changes. Six months later the renewal is contested and nobody on the customer side can articulate what the platform did for them.
The problem is not that the chart is inaccurate. It is that it answers a question the customer never asked. Utilization measures whether people logged in. The executive in the room is trying to decide whether a line item survives the next budget cycle, and login counts do not speak to that.
This is a method for building the other kind of review. It uses AI to do the correlation work that nobody has time to do by hand, but the AI is not the interesting part. The interesting part is changing what goes in.
Start with three sources, and notice that only one of them belongs to you.
The customer's stated objectives. Whatever they told you during the sale, in the kickoff, or in any executive conversation since. Their words, not your summary of them. If you cannot find these written down anywhere, that is your first finding.
What they have said in public since. Every company publishes a running account of what it believes it lacks. Open roles are the most legible version — a job posting is dated, specific, and costs real money to place, so nobody does it casually.1Job postings are public, dated, and specific, which makes them the rare customer signal you can act on without asking anyone's permission or waiting on a data request. But it is not the only one. An earnings call, a risk factor in an annual filing, a market they just entered, a reorganization, a named executive hire, a published roadmap, an open RFP: each is a dated, public statement that some problem is worth money to them.
Pick the signal your platform actually bears on. If what you sell makes people better at something, open roles are usually the right read, because a requisition is a company saying in public that it cannot do a thing with the people it has. If you sell infrastructure, the signal is more often a commitment they have announced and now have to deliver against. The test is the same either way: public, dated, and expensive enough that they meant it.
Your platform data. Last, and used only as evidence for a claim you have already formed from the first two.
The order matters. If you start with your own data you will end up narrating it, and narrated data is a utilization chart with better adjectives.
Here is the question the whole method turns on:
Of the things this customer has already committed money to fixing, which ones are they paying for twice?
That question puts your platform inside a decision the customer is already making, with a budget already attached, at a price they have already accepted.
Here is one instance of it, with a skills platform reading the hiring signal. Take the shape, not the signal.
Meridian Freight, a logistics company, 4,200 employees, three years into a platform agreement. Fictional, but the shape is taken from real accounts.
The finding writes itself. Meridian is paying to recruit a skill that 340 of their existing people have already demonstrated, and the recruiting is happening around a department that has a retention problem. That is not an adoption story. That is a claim about money they are already spending, and it lands with a VP of Operations in a way that "adoption is up twelve percent" never will.
Swap the signal and the shape holds. A security platform reads a compliance regime the customer has publicly committed to meeting, and asks which of those controls they already own and have not deployed. A data platform reads an announced expansion into a new market, and asks which of the pipelines that expansion requires already exist. The evidence changes. The question does not.
Note what made it work. The finding is about their business. Your platform appears in it, but it is not the subject of the sentence.
Once you have the correlation, the economics follow a shape the customer already understands, because it is the same shape they use for every other spending decision.
Against whatever they are already funding, you have three quantities the customer can supply and verify themselves:
You do not need precision here. You need the order of magnitude to be obviously in one direction, and you need the customer to recognize their own numbers.
One hard rule: the person running the review does not produce pricing. Not a number, not a range, not a hint. What their current approach costs is the customer's number. Contract value is the renewal owner's number.
The single biggest structural improvement you can make is to stop trying to do this in one session.
The pre-call deck presents hypotheses. Here is what we think your objectives are. Here is what your public signals suggest you are short on. Here is where we think your existing capability sits. Every one of these is framed as a question, and the entire ask of the meeting is: which of these is right?
The post-call deck presents the plan. Now the objectives are confirmed in the customer's own words, the gaps are ones they agreed exist, and the ninety-day plan addresses gaps they named rather than gaps you inferred.
This costs you an extra meeting and it is worth it every time. A plan built on confirmed premises survives a change in sponsor. A plan built on your inference does not.
Two practical notes. The decks need to land close together, within a week or two, or the customer loses the thread and you burn the goodwill the first meeting generated. And the pre-call deck should be visibly incomplete.
Any AI-assisted version of this will confidently produce a well-formatted answer built on nothing, because that is the failure mode of the technology. In customer-facing work that is not a small error. It is the thing that gets someone embarrassed in front of an executive who knows their own business better than you do.
Three rules, all of which make the output more useful by making it narrower.
The confirmed objectives from the post-call deck are the most valuable thing this process produces, and they are almost always lost. They live in a deck in someone's drive and never make it into the system of record, so the next person to touch the account starts from zero.
Whatever your process produces at the end, make it map cleanly onto the fields your CRM or success platform actually has. Objective, outcome type, KPI target, current measure, evaluation period, due date. If the output requires a human to reinterpret it before it can be entered, it will not get entered.
This is the least glamorous step and it is the one that determines whether the work compounds or evaporates.
The reframe is not a presentation trick. Starting from what the customer has said in public rather than from your own usage data forces you to know something about their business that they did not tell you, and to be useful about it. That is the whole job. The AI just makes it fast enough to do for every account instead of the three you were already worried about.
If you try one thing from this, pick a single account and find one thing they have publicly committed money to this year. Put it next to what your platform says they already have, and see what the gap tells you. It usually takes twenty minutes and it usually changes what the meeting is about.