How to Open a Renewal Call When You Already Know Adoption Is Dead

The report is flat and the call is Tuesday

You already know how this goes. You pull the usage export the Friday before, you sort by active users, and the line is the same line it was at kickoff. Maybe two logins from the admin who set it up. Maybe a burst in month two when someone ran a pilot and then nothing. The seats you sold are sitting there like unopened boxes in a garage.

And the renewal call is Tuesday.

Most reps handle this one of two ways, both bad. The first is the apology tour, where you open with how sorry you are that things did not go as planned and spend the next twenty minutes absorbing punishment you hope will convert into goodwill. It does not. The second is the deflection, where you open with a deck full of roadmap and new features and hope nobody looks at the usage tab. They will look at the usage tab. Their finance team already did.

This post is about the first ten minutes only. Not the negotiation, not the multi-year restructure, not the save plan. The first ten minutes, because that is where the call is decided. If you get those right, you are in a working session. If you get them wrong, you are in a cancellation call with extra steps.

Name it before they do

Here is the single rule that governs everything else. Whoever names the adoption problem first controls what the problem means.

If the customer says it, it means "your product did not work and we are not paying for it again." It arrives fully formed as a verdict. Your job for the rest of the call becomes arguing with a verdict, which is a losing posture no matter how good your arguments are.

If you say it, it means "here is a thing we both need to solve, and I have already been thinking about it." Same facts. Completely different room. You are not defending, you are diagnosing, and the customer is now a participant instead of a judge.

So you open with the number. Not the spin on the number. The number.

The fear is that naming it hands them the cancellation. In my experience the opposite happens. Customers who are planning to churn quietly are usually a little embarrassed about it too. Nobody enjoys telling a vendor that their team ignored the thing they signed off on. When you say it first, and say it without flinching, you take the awkwardness off the table and a surprising number of people relax into honesty.

The tone matters more than the words. You want the tone of a mechanic looking under a hood. Interested, unsurprised, slightly clinical. Not the tone of a man about to lose his commission.

Opener one: the honest audit

This is my default. Use it when the relationship is intact, the buyer is still there, and nobody has been actively hostile.

"Before we get into renewal mechanics I want to put something on the table, because I would rather we talk about the real thing. I pulled usage last week. Across the twelve months, we have four people who logged in more than once, and three of them are on your IT team. That is not a renewal conversation, that is a why-did-this-not-take conversation, and I would rather have that one. Can I walk you through what I think happened and you tell me where I am wrong?"

Four things are doing work there. You raised it, so you own the frame. You used a specific figure from their own tenant, so nobody can argue about whether it is bad. You explicitly declined to pitch, which buys more credibility than any amount of value talk. And you ended on a question that invites correction, which is the fastest way to get a real answer out of an executive.

That last part is not a rhetorical trick. Ask people to confirm a story and they nod. Ask people to correct a story and they tell you things. Half the time the correction is the whole diagnosis: "honestly it is not that people did not want it, it is that we reorganised in March and the ops group that was going to run it does not exist anymore."

The hard part of the honest audit is the silence after. You have just said something uncomfortable and true. Do not fill it. Let it sit for the full three or four seconds it takes for them to decide how honest they are going to be back. Reps blow this constantly, rushing into "but of course there is a lot we can do" and burning the moment they just paid for.

Opener two: the narrow win

Use this when the usage is not literally zero. If there is one office, one crew, one clinic, one partner group that actually used the thing, you lead with them and let the contrast do the argument for you.

"I want to start somewhere specific. Your Leeds branch has been in the system nearly every week since February. Nobody else has. I do not think that is because Leeds got a different product. I think it is because something is true about how Leeds works that is not true anywhere else, and if we can figure out what that is, we know whether this is worth renewing. Do you know what they are doing differently?"

What this does is convert the call from a referendum on your product into an investigation into their organisation. The evidence that it can work is already sitting in their own data, so you are not asking them to take your word for anything. And the question is genuinely interesting to most operations leaders, because a single team outperforming the rest is a puzzle they care about independently of you.

Be careful not to oversell the win. If you inflate a small pocket of usage into a triumph, you lose the credibility you were about to spend. Say it plainly: one team, and only one team, and that is the thing worth understanding.

The energy and utilities renewal script we put together for asset analytics accounts six weeks from expiry leans hard on this pattern, because in that world there is almost always one plant or one region that made it work while the rest of the estate did nothing.

Opener three: the sponsor reset

Use this when the person who bought is gone, or when you are talking to someone who inherited your contract like an unwanted piece of furniture.

"You did not buy this and you have no reason to be attached to it, so I am not going to talk to you like you do. Here is what I know. It was bought last March to solve a specific problem, usage never got above a handful of people, and it comes up for renewal in six weeks. I do not know whether the original problem still exists or whether it went away. That is genuinely the first thing I need to find out, because if it went away, we should not be renewing this and I will tell you that."

Saying out loud that you might recommend against renewal is the most powerful thing in this opener, and you have to actually mean it. If it is a bluff, they hear the bluff. If it is real, you have just become the only vendor in their inbox who is not obviously optimising for their own quota, and that is worth more than any concession you could offer.

When the champion has left the building

The departed champion is the most common cause of dead adoption I have seen, and it is the one reps are worst at handling, because they keep trying to reconstruct the old relationship instead of building a new one.

Do not eulogise. Do not say "Sarah was really excited about this." To the new person, Sarah is a predecessor whose decisions they are now cleaning up, and enthusiasm from Sarah is closer to a liability than an endorsement.

Instead, separate the purchase from the problem. The purchase was Sarah's. The problem might still be the organisation's. Your entire job in the first ten minutes is to find out whether the problem outlived the person.

"I am not going to defend a decision you were not part of. What I want to understand is whether the thing it was bought to fix is still a thing. When your field supervisors close out a job today, what actually happens to that paperwork?"

That second question is the important one. You are asking about their current process, not about your product. If the answer describes a mess, you have a live account. If the answer is "honestly we built something in-house and it is fine," you have a dead one, and knowing that on Tuesday is better than discovering it at the deadline. The construction and trades renewal script for saving an account after a year of dead adoption works through this exact fork, because turnover in operations roles tends to take the sponsor out at exactly the wrong point in the contract cycle.

One more thing on departed champions. Ask who else was in the room. Somebody sat in the original evaluation who is still there, and they remember the pain that drove the purchase even if they did not sign the order form. Find them before Tuesday if you can, and if you cannot, ask on the call.

Get them to say what they thought they were buying

This is the question I would keep if I could only keep one.

"When you signed this, what did you picture people doing differently on a Monday morning?"

Ask it exactly like that. Monday morning, not "what outcomes were you expecting." You want a scene, not a category. Outcomes language produces outcomes language back, all value and efficiency and visibility, and none of it tells you anything you can act on.

What you are listening for is the gap between what they pictured and what you sold. Almost every dead-adoption account I have looked at has one, and it is usually not a lie anyone told. It is a quiet mismatch that neither side noticed because both sides used the same words to mean different things.

Sometimes they pictured something the product does not do. That is worth knowing on Tuesday, because you can either fix it or stop pretending.

Sometimes they pictured a change in behaviour that nobody was ever tasked with driving. They bought a tool expecting it to produce a habit. Tools do not produce habits, managers do, and no manager was ever asked to.

Sometimes they pictured it right and the rollout just never happened, because the person who was going to run it got pulled onto something more urgent in week three and never came back.

Those three diagnoses lead to three completely different second halves of the call. You cannot pick the right one by guessing, and you certainly cannot pick it from a deck you built on Friday.

The professional services version of this call puts a lot of weight on that Monday-morning question, because in firms full of billable people, the gap between what a partner pictured and what an associate was actually told to do is usually where the whole year went.

Pivot from "why did this fail" to "what would make one team use it"

You get a short window for diagnosis. Past a certain point, the post-mortem stops producing information and starts producing gloom, and gloom is what a churn decision feels like from the inside. Watch for the moment the answers start repeating. That is your cue.

The pivot sounds like this:

"Alright. I think I understand what happened and I do not think we need to keep going over it. Let me ask a different question. Forget the whole account. If one team, the single most likely team, was going to be using this properly thirty days from now, who would that team be and what would have to be true?"

Everything about that question is chosen. One team, because the failure of the enterprise rollout is fresh and nobody wants to authorise another one. Thirty days, because it is short enough to be real and long enough to be possible. And "what would have to be true" instead of "what do you need from us", because the honest answer usually involves things only they can do, and you want them to hear themselves say it.

What comes back is your save plan, written by the customer, in their language, with their constraints already priced in. You are not going to get a better one out of an internal brainstorm.

Write down the names of the people they mention. Those are your next calls, and referencing them by name in your follow-up email is what makes this feel like a project rather than a conversation.

The exact ask, and why it is not a discount

Here is where reps panic. The instinct, when adoption is dead, is to lead with money. Take twenty off, restructure the seats, do anything to make the number smaller than the pain of the decision.

Do not do it in the first ten minutes, and ideally do not do it at all on this call. A discount offered before you have agreed on the problem tells the customer that the price was always soft, that you are frightened, and that the product's value is negotiable. You also give away your only real lever before you know whether you needed it. And the discount does not solve their actual problem, which is that nobody uses the thing. A cheaper unused tool is still an unused tool, and you will be back here next year with less margin and less credibility.

So the ask is time, not terms.

"I am not going to ask you to renew today and I am not going to open with a discount, because I do not think price is what went wrong here. What I want is this. Give me two weeks and a working session with the team you just named. I will come back with a thirty-day plan for that one team, with what we do, what you do, and what we would both expect to see at the end of it. If it works, we talk about the renewal with something real behind it. If we cannot build a plan we both believe in, I will tell you that too and we can have a much shorter conversation. Does two weeks work?"

That is a small yes. It costs them almost nothing, it does not commit them to spend, and it moves the decision from "do we keep paying for a thing nobody uses" to "do we want to try the specific thing we just designed together." The second question is far easier to win.

Get a date in the diary before you hang up. Not "I will send some times." An actual date, with the actual people, while you are still on the phone. Every day between this call and that session is a day in which somebody in their finance team runs a cost-cutting exercise and finds your line item. The healthcare version of this script is worth reading on this point specifically, because clinical documentation accounts tend to have compliance deadlines you can anchor the session to, and anchoring the date to something they care about is much stronger than anchoring it to your quarter.

And if they say no to two weeks? Then the account was gone before you dialled, and you have found out on Tuesday rather than in six weeks. That is a good outcome. It is not the one you wanted, but it is a good outcome, and it frees up the hours you were about to spend building a save plan for a customer who has already moved on.

What I would do before Tuesday

Read the usage report again and pick your opener now, not in the car. Decide which of the three you are running, write the first four sentences out longhand, and say them out loud until they sound like you and not like a script. The words are easy. The tone is the whole thing, and tone under pressure only comes from repetition.

If you want to rehearse it properly rather than practising on the actual account, that is exactly what I built DrillCall for. Load the scenario, let the customer on the other end be flat and slightly irritated the way they will be on Tuesday, and run the opening ten minutes until the silence after the honest audit stops making you want to talk. It is the cheapest place to make the mistakes.