How to Run an Account Review That Earns the Expansion Instead of Triggering a Discount Request

The default account review is a usage report, and a usage report reads like an invoice

Here is the meeting almost every rep I have watched runs. You pull the dashboard. You share your screen. You walk through logins, seats, tickets, adoption by team, maybe a nice trend line. You say "as you can see, usage is up quarter over quarter." Then you ask if there are any questions.

There is exactly one question that meeting invites, and the customer asks it every time: so what are we actually paying for?

That is not a hostile question. It is the only logical response to what you just did. You spent thirty minutes describing consumption without once describing value, so the customer's brain went where anyone's brain would go — to the line item. You showed them the meter running. Of course they want to talk about the bill.

The fix is not better slides. The fix is a different opening premise. A usage report asks are you using this? A good account review asks did the thing you bought this for actually happen? Those two questions produce completely different meetings. One ends in a procurement conversation. The other ends with the customer describing a problem they still have, which is the only door an expansion has ever walked through.

I want to lay out the structure I use, in order, with what to say. It works whether you are the AE, the CSM, or the poor soul who owns both jobs at a company that has not figured out the difference yet.

Start with the outcome their own team reported, not your data

The first thing out of your mouth should be a result, in the customer's words, about the customer's business.

Not "usage is up." Something like: "Before I get into anything, I want to read you something. Your ops lead, Marissa, told my support team in March that the reconciliation that used to take her two people a full Friday now gets done before lunch. I wanted to open with that because that is the thing you told me you were buying when we signed."

Watch what that does. It reframes the entire meeting from are you consuming enough to is this working. It puts a name from their own org on the claim, so you are not the one making it. And it hands the economic buyer something they can repeat upward without checking it with anyone, which matters more than most reps realize — your champion has their own internal review to survive.

The hard part is that you cannot say this sentence unless you went and got it. So go get it.

How to collect the outcome before the meeting

Two weeks out, email the two or three people who actually touch the product daily. Not the signer. The users. One question, and only one: "What's something this does now that you used to do another way?"

That phrasing beats "how's it going" because it forces a before-and-after. People are bad at rating satisfaction and good at describing a change in their own routine. You will get replies like "I don't have to chase the warehouse for the pick confirmation anymore" or "we stopped keeping the spreadsheet." Those are gold. The spreadsheet they stopped keeping is a story with a labor number attached to it, and you can ask the follow-up: "How long did that spreadsheet take you each week?"

If nobody replies, call them. Fifteen minutes each. I have never regretted the time. And if you genuinely cannot find a single person who will name one thing that got better, you have learned something more important than anything the review was going to tell you: this account is not renewing, and the meeting you need is a save meeting, not an expansion meeting. Do not walk into a review pretending otherwise.

Quantify the gap between where they are and what they bought it for

This is the move that separates a review from a status update, and it is the one people skip because it feels risky.

You stated the win. Now you state the shortfall — against the customer's own original goal, out loud, before they find it.

"When we signed, the goal you gave me was getting every branch onto this by end of Q2. Four of your seven branches are on it. The three that aren't are Fresno, Reno, and the one in Tulsa you opened in January. So we're better than we were and we're not where you said you wanted to be, and I want to spend most of today on why those three haven't moved."

Three things just happened. You proved you remember the original objective, which almost nobody does past the first quarter. You demonstrated you will tell them bad news, which is the entire basis of being trusted later. And you defined the gap — and a gap is a problem, and problems are the only thing anyone ever buys.

Notice that I did not say "and that's why you should add the enterprise tier." We are nowhere near that. We are just naming the distance between where they are and what they told you they wanted. Let it sit there.

The gap has to be stated in their units, not yours. Not "seat utilization is at sixty percent of provisioned." Say "four of seven branches." Not "low feature adoption in the routing module." Say "your dispatchers are still building tomorrow's routes in the old system on Sunday nights." If you cannot translate a metric into a sentence about a human doing a task, the metric does not belong in the review.

What to do when the usage number is bad

Sometimes there is no win to lead with. Adoption cratered. The champion left. The rollout stalled in September and it is now February.

Bring it up first. First thing, before anything else, with a plan already attached.

"I want to start with the uncomfortable one. Logins dropped off a cliff after Dan left in October and nobody picked up ownership. That's on me — I should have caught it in November and I didn't. Here's what I think we do about it, and then I want your read on whether it's worth doing at all."

The instinct is to bury it on slide nine and hope the meeting runs long. Do not. Everyone in that room already knows. The only variable is whether you are the person who said it or the person who was caught not saying it, and that difference determines whether you are in the room for the renewal decision or hearing about it afterward.

The "is it worth doing at all" part is not false modesty. You are genuinely asking whether the original use case still exists. Sometimes it does not — the department reorganized, the initiative got killed, the problem you solved stopped being a problem. Better to find that out in month eight than in the renewal window. And occasionally the answer surprises you: the original use case died but a different team started using it for something you did not know about, and that is your expansion, sitting there the whole time, hidden under a bad aggregate number.

A bad number handled well builds more credibility than a good number ever will. I have had accounts where the recovery conversation is the reason they expanded a year later. Nobody expands with a vendor who they suspect is managing them.

The two sentences that separate a review from a sales call

Somewhere around the twelve-minute mark, say these two things.

The first: "I'm not going to ask you for anything today."

The second: "If something isn't worth what you're paying for it, I'd rather you tell me now than at renewal."

Then stop talking.

I know how that second one reads. It reads like you just invited the discount request. It does the opposite, and here is why. The discount request is a defensive move. It comes from a customer who suspects they are being sold to and wants to establish leverage before you get to your ask. Once you remove the ask, you remove the reason to posture. They do not need leverage against a person who is not pushing.

What actually comes back, in my experience, is one of two things. Either "no, it's fine, we're getting value" — in which case you now have the economic buyer on record saying it, unprompted, which is worth more than any slide you could have built — or you get the real objection, months before it would have surfaced on its own. Both outcomes are wins. The only losing outcome is the one where they were quietly unhappy and you never heard it.

And you have to actually mean the first sentence. If you say "I'm not asking you for anything" and then ask them for something eleven minutes later, you have taught them that your framing statements are theater. That damage does not repair inside the same account. Hold the line. The ask happens in a different meeting, and I will get to how you book it.

Let the customer name the next problem

This is the part that determines whether an expansion exists.

After the gap discussion, ask a question that has nothing to do with your product:

"Forget us for a second. What's the thing your team is dreading this quarter?"

Or: "If you got two more headcount tomorrow, where would you put them?"

Or my favorite, because it is specific enough to get a specific answer: "What's still living in a spreadsheet?"

Then shut up and write down exactly what they say. Verbatim. Their nouns, not your product's nouns.

The reason this matters is that an expansion the customer names is a purchase, and an expansion you name is a pitch. Same product, same price, completely different conversion. When they say "honestly the mess right now is that every time a contractor rolls off we start the sourcing from zero," they have just written your business case for you, in language their CFO will accept, and all you have to do later is connect your thing to their sentence. That is precisely the hinge that the staffing and recruiting upsell script is built around — you are not selling a redeployment module, you are solving the sentence the client already said out loud.

The discipline is to not connect it in the moment. You will feel the pull. They named a problem you solve, the words are right there, and every instinct says say it now. Do not. Say this instead:

"Okay. That's a real one. Let me think about it and come back to you — I don't want to give you a half-answer in the last five minutes of a review."

That sentence buys you a second meeting with a stated agenda, positions you as someone who thinks before he sells, and lets you show up prepared with a scoped version instead of an improvised one. It is the highest-leverage thing you can say in the entire hour.

Hold the ask until there is a stated need to attach it to

Rule I try never to break: no expansion ask without a customer-stated need to hang it on, said in the customer's words, in a meeting where you can quote it back.

Without that, your ask is a product recommendation. With it, your ask is a response. "You said the Tulsa branch is running blind on inventory counts and it is costing you a shift a week to reconcile. Here is what that would cost to fix and here is what it would save." That is not a pitch, that is arithmetic on a problem they raised.

The difference is most visible in accounts where a bad ask does real damage. In heavy asset businesses, the plant manager who feels sold to during a review will not take the next meeting, and the manufacturing upsell script exists because the sequencing on those accounts is unforgiving — you get one shot at reading the line utilization back to them correctly, and if it lands as a pitch you have lost the operational relationship, not just the deal. Freight accounts are similar in a different way: margins are thin enough that anything resembling an unprompted upsell reads as you taking a cut, which is exactly what the freight and 3PL version is designed to route around.

If you finish a review and no need got stated, the correct outcome is no expansion ask. Not a smaller one. None. The account was not ready and you did not damage it, and you get to run this play again in ninety days with credibility intact. Reps burn accounts by treating every review as a forced conversion event. The review is not the conversion event. The review is what earns you the conversion event.

Book the expansion conversation as its own meeting, on the call

Do not follow up by email. Book it live, before you hang up, with a named agenda and the right people in the room.

"Can I take thirty minutes in two weeks to come back on the contractor sourcing thing? I'd want to bring numbers on what it would take, and I think you'd want whoever owns that process in the room — is that Priya?"

Three deliberate pieces. A short block, because thirty minutes signals a scoped conversation rather than a full pitch and makes it easy to accept. A named topic, which is their topic, so accepting the meeting does not feel like agreeing to be sold. And a request for the process owner, which quietly widens your footprint into the org and gets you in front of the person who will actually use the thing.

Then send the recap same day, and make the recap a document, not a note. Three parts: what their team said got better, the gap against the original goal with what you are each doing about it, and one line — "you raised contractor re-sourcing; we're picking that up on the 14th." Nothing else. No product literature attached. That document gets forwarded internally, and when it does, it should read like a business summary written by a partner, not marketing collateral written by a vendor.

Keep it to forty minutes and let the silence do work

An hour of you talking is a webinar. Aim for forty minutes where they talk more than you do. Open with the win, name the gap, say the two sentences, ask what they are dreading, book the follow-up. That is the whole shape.

The hardest skill in the room is silence after a question. Ask what is still in a spreadsheet and then count to seven in your head. The first answer is usually polite. The real one comes after the pause, and reps talk over it constantly because three seconds of quiet on a video call feels like a minute.

If you want to get better at this, it is a rehearsal problem, not a knowledge problem — you already know the structure now, and you will still cave on the ask when the customer names a perfect need in minute thirty-four. That is the specific thing I would drill: run the review out loud against a buyer who dangles the expansion at you and see whether you can actually say "let me come back to you on that." It is what we built DrillCall for, and it is the rep I would practice being before the next quarter's reviews land on the calendar.

Run the next one this way. Lead with what their own people said. Name the gap before they do. Promise nothing, ask for nothing, and let them tell you where it hurts. The expansion is on the other side of that conversation, not inside it.