Expansion Managers: Running a Utilization Review That Produces Decisions

A utilization review exists to help the customer make an operating decision. It does not exist to turn a login count or a transaction total into a case for more seats. When an expansion manager walks into this meeting with a dashboard and a growth target, the customer notices within the first two minutes, and the rest of the hour becomes a negotiation instead of a working session. Run it well and the same data builds the trust you need for the next conversation about scope.

Why This Conversation Goes Wrong

Most utilization reviews fail for one of two reasons. The manager reads low adoption as a verdict on the customer's team and opens with something close to a complaint, or the manager reads high adoption as proof the account is ready to grow and opens with something close to a pitch. Both moves put the customer on the defensive before you have said anything useful. In financial services accounts this problem is sharper than usual. Usage data often sits next to audit trails and compliance reporting, so a customer who senses a promotional spin on the numbers starts to wonder what else you are spinning. Once that doubt sets in, the rest of the relationship gets harder to manage, not just this one meeting.

The other common failure is vaguer but just as damaging. The manager presents a chart, waits for a reaction, and has no plan for what happens next. Without a decision to work toward, the meeting drifts into commentary. Everyone nods, nothing gets assigned, and the same numbers come back unchanged at the next quarterly check.

How to Prepare

Verify every number before you bring it into the room. Confirm the time window the report covers, confirm what counts as an active user, and confirm whether the count includes service accounts, shared logins, or only named individuals. A number that turns out to be wrong in front of the customer costs you more credibility than a weak insight ever will. Financial services customers are used to defending their own numbers to regulators, so they will test yours the same way.

Next, write down the objective the customer stated when they bought or renewed, not the objective you wish they had stated. If a usage pattern does not connect to something the customer actually asked to accomplish, do not present it as a finding. Present it as a question you want to ask them directly.

Decide in advance what a good outcome looks like. A utilization review has three honest endings. Someone gets named to own a workflow review, someone schedules training, or someone documents a requirement for a later release. If you cannot picture the meeting closing on one of those three, you are not ready to run it yet.

Two things are worth doing before you sit down. Read how to identify who actually sponsors a workflow before you propose changing it, covered in Expansion Managers Build a Workflow Sponsor Map Before Proposing More Scope. And if the meeting involves pulling evidence from the customer's own systems, look at how to request that evidence without sounding like you are building a case against them, in Fintech SDR Discovery Audit Evidence Requests Without the Fear Pitch.

What to Say

Open with the customer's stated goal, not the chart. Something like, "You told us the goal for this case queue was cutting the time it takes support to close a ticket. Here is what we are seeing after three months."

State the finding plainly and name its limits before anyone reacts to it. "Support opens close to forty cases a week through the queue. Finance opens almost none. I do not want to guess why. Does that match what you are seeing on your side?"

The finance lead pushes back, as customers often do when a number sounds like a criticism. "That number does not tell the whole story. My team still runs a daily report instead of using the queue."

Resist the urge to defend the tool. Ask a decision question instead. "What does that report give your team that the queue does not?"

The finance lead explains that the report includes a reference number the queue does not capture, something their auditors ask for every month. Now you have something real to work with. "That is useful. That is either a product gap, a training gap, or something we need to treat as out of scope for now. Which one do you think it is?"

Close on an action, not a summary. "Here is what I will do. I will document the reference number as a requirement and bring it to my product team this week. Can you get me thirty minutes with your analyst so I can see exactly where that number needs to sit in their report?"

Mistakes to Avoid

A few habits sink this meeting more often than anything else.

1. Leading with low adoption as though it reflects poorly on the customer's team, rather than as a shared question to answer.
2. Treating high usage as automatic grounds for a conversation about more seats or a higher tier, before the customer has asked for one.
3. Bringing a number you have not personally verified, including counting service accounts as human users or misreading the time window.
4. Letting the meeting end in agreement without a specific action and a named owner attached to it.
5. Skipping the check for whether your data matches the customer's lived experience before you draw a conclusion from it.

Any one of these turns a working session into a sales moment, and financial services customers tend to disengage fast once they sense that shift.

How to Practice and Score It

Run this meeting once before you run it for real. Have a colleague, or an AI counterpart, play a finance lead who pushes back with a line like the one above, that the number does not tell the whole story, and pay attention to your first instinct. If your first instinct is to defend the report, you need more reps before the live meeting. If your first instinct is to ask what would make the number useful, you are ready.

DealSpeak's financial services scenarios are built around this exact exchange, and they score three things after the role play ends. Did you open with the customer's stated objective instead of the data? Did you ask a decision question after presenting evidence instead of defending it? Did the meeting close with a named action and an owner, not just a shared understanding? Run the scenario as many times as it takes to make the decision question your default reaction instead of a line you remember to say under pressure.

If you want more of these scenarios across other roles in the same industry, the full set of Financial Services practice conversations covers discovery calls, renewal conversations, and scope discussions built around the same kind of realistic pushback.

Where This Leaves the Relationship

A utilization review that ends in a real decision does more for the account than any pitch could. It tells the customer you are willing to sit with a number that does not flatter your product and work through it with them instead of around them. Keep the data in service of their operating question, and the conversation about expanding scope will come up on its own, when it is actually true.