Teardown: The First Call After Your Champion Left the Company

Your champion leaves. You find out from a bounced email, or from LinkedIn, or from an out-of-office that says "I am no longer with the company, please contact Priya."

And then you have to call Priya.

This is the call almost every rep gets wrong, and they get it wrong in the same direction every time: they treat the new person as the continuation of the old person. They are not. They are a new buyer who has inherited a filing cabinet, and your deal is one folder in it.

Below is a teardown of that call. The specifics are a composite of calls I have listened to and calls I have made badly myself, but the shape is exact. Renewal three weeks out. A six-figure expansion the previous champion had already half-sold internally. A replacement who had been in the seat for eleven days.

The setup

Dana was the champion. Director of operations. She had run the pilot, built the internal business case, walked it past finance twice, and told the rep in November that the expansion would land "probably January, once budget resets."

In December Dana left. No handover call. The rep found out on the fifteenth.

The replacement is Priya, promoted internally from a sibling team. She did not run the pilot. She did not build the business case. She has, at most, seen the vendor's name on a spreadsheet of contracts that expire in Q1.

The rep books twenty-five minutes with her. Here is roughly how it opened.

The open, as it happened

Rep: "Hi Priya, thanks for making time. So I worked really closely with Dana over the last eight months — sorry to see her go, she was great. I wanted to get you up to speed on where we landed, because we'd actually agreed to move forward on the expansion in January and I know your renewal is coming up on the thirty-first. Do you want me to walk you through the history?"

Priya: "Sure, go ahead."

That "sure, go ahead" is the sound of a deal dying politely.

The rep then spent nine minutes on history. Pilot scope. Which teams used it. What Dana's business case said. The pricing that had been "agreed." Priya said "mm-hm" eleven times and asked one question, near the end, which was: "And when does the current contract expire again?"

That is not a buying question. That is a person establishing how much time they have before they need to have an opinion.

Where it went wrong, precisely

Second one: naming the predecessor first

The first noun out of the rep's mouth was Dana. Not Priya's team, not Priya's problem, not even the product. A person who no longer works there.

Think about what that does to someone eleven days into a new job. Priya is not nostalgic about Dana. Depending on how the transition happened, Priya may have been handed this role because something wasn't working, or because Dana was leaving anyway and someone had to hold the bag. Either way, Dana is the past and Priya is being measured on the future.

When you open by establishing your relationship with the previous person, you are telling the new person that your relevance to them is inherited rather than earned. You have volunteered to be filed under "things Dana was doing."

That file has a well-known fate.

Second twenty: "we'd agreed"

"We'd agreed to move forward" is the single most expensive phrase in this call.

The rep means it as a status update. Priya hears it as a claim on her budget made by someone who no longer works there, on her behalf, without her.

And she is right to hear it that way. Nothing was agreed with Priya. Dana's commitment was real, but it was personal capital, and personal capital does not transfer with the job title. The org chart moved. The commitment did not move with it.

Worse: "we'd agreed" quietly asks Priya to ratify a decision she wasn't part of. New leaders almost never do that in their first month. Ratifying your predecessor's half-finished deal is all downside. If it works, it was Dana's win. If it fails, it is Priya's failure, on a project she never chose. The rational move for her is to slow it down until she understands it, and "slow it down" three weeks from renewal means an auto-renew at current terms or a lapse.

Minutes one through nine: the history dump

The rep believed the history was an asset. Eight months of work, a pilot with real usage, a business case that already exists. Why would you not lead with that?

Because context you did not earn the right to give is just noise. Priya has no framework to hang it on. She does not yet know whether this problem matters to her, so nine minutes of detail about how the problem was scoped last spring is nine minutes of somebody else's meeting.

And here is the real cost. Those nine minutes were the only window in the call where Priya was fully present and undecided. That is when you learn what she has been told to do. Instead the rep spent them talking.

The mental filing moment

If I had to mark one point where the deal became a renewal problem instead of an expansion opportunity, it is around the four-minute mark, when the rep said the words "Dana's business case."

Up to then, Priya was neutral. After that, the vendor is attached to a named predecessor and a document Priya has not read. She stops evaluating and starts triaging. The internal note she writes after the call says something like: legacy tool, Dana's project, contract up end of month, need to understand what it does before committing to anything.

Every word of that is fatal three weeks out.

What the rep should have known before dialling

Before this call, two things were knowable and neither required Priya.

The first is why Dana left, or at least the shape of it. Promoted out, poached, restructured, pushed. Ask the other people you know in the account. Ask on the pilot Slack channel if you had one. Look at whether anyone else on that team moved in the same month, because if three people left, this is a reorg and your buying committee no longer exists.

The second is what Priya was hired or promoted to do. Her LinkedIn headline changed recently. The internal announcement, if you can get someone to paste it to you, will usually contain a phrase like "will focus on" or "tasked with." That phrase is your opening line.

The rep did neither. He had eleven days of warning and used them to prepare a recap.

The rewrite

Here is the same call, opened differently.

"Priya, congratulations on the new role. Before I say anything about us — you've been in the seat under two weeks and I assume someone handed you a list of things to fix. What's actually on that list? I want to know whether we're on it, and honestly whether we should be."

Then stop talking.

Three things happen in that open that did not happen in the original.

You have not mentioned Dana. Dana will come up, and when Priya raises her you can be warm about it, but you have not made your predecessor relationship the reason you are on the phone.

You have not claimed anything was agreed. You have made the deal contingent on her priorities, which is where it actually sits whether you admit it or not.

And you have offered her the exit. "Whether we should be" is a genuine invitation to tell you this is not a priority. Most reps are terrified of that sentence because they think it gives permission to churn. It does the opposite. It is the only way to find out fast, and when someone new to a role is given an honest way out and does not take it, what they say next is worth more than an hour of pitching.

The follow-up questions that matter

Once she answers, you are running discovery, not a renewal conversation. The questions I would ask, in this order:

"What's the first thing you want to change about how this team runs?"

"When you looked at the contract list for this quarter, what was your instinct on ours before we spoke?" — this one is uncomfortable and it is the most valuable question in the call. She has an instinct. It is usually "I don't know what this is" or "someone told me it's useful" or "I was planning to cut something and this looked cuttable." You need to hear which.

"Who on your team actually touches it day to day?" — because the users are still there even though the champion is not, and they are your only remaining internal proof.

"What would make you look good ninety days from now?"

That last question is not a trick. New leaders have a ninety-day story they are trying to tell. If you can attach your product to that story, you are not Dana's project any more, you are Priya's early win. If you cannot attach it, you need to know that too, because it changes what you are playing for.

This is straight discovery, and it deserves the full structure rather than four questions bolted onto a renewal call. The twenty-five minute diagnostic I use for SaaS discovery works fine here with one change: you already have usage data, so you can test her answers against what her own team is actually doing in the product. That is a luxury you do not get on a cold first call and most reps waste it.

Reset to discovery, or hold the timeline?

This is the actual decision, and it is not a preference. It depends on two variables: how much room the renewal date has, and whether the product is embedded in daily work.

Reset to full discovery when the renewal has room, or when usage is thin. If the contract runs another quarter, take the reset. Treat Priya as a new prospect who happens to have your product already installed. Rebuild the case with her, in her language, aimed at her ninety days. The expansion goes back in the pipeline at an earlier stage and that is correct — pretending otherwise just means a slipped forecast later.

Also reset if usage is thin, regardless of dates. A new decision maker plus low adoption is not a renewal you can hold with urgency. Urgency without value reads as desperation and gives her a reason to cut.

Hold the timeline when the product is genuinely load-bearing and the date is close. Three weeks out, with real daily usage across a team Priya now owns, you do not have the luxury of a full reset. But holding the timeline does not mean pushing the expansion. It means splitting them.

Say it plainly: "There are two things on the table and I want to separate them. One is the renewal on the thirty-first, which affects the fourteen people on your ops team who log in every day. The other is the expansion Dana was scoping, which I'd like to park until you've decided whether you want it. Can we deal with the first one today and put the second one in February?"

That sentence does more work than anything else in this teardown. You have removed the thing she feels pressured about, kept the thing she cannot afford to lose, and demonstrated that you are not trying to slip a predecessor's decision past her. Reps hate parking the expansion because it looks like shrinking the deal. It is the opposite. It is the only way the expansion survives, because a deal she chooses in February is worth more than a deal she rubber-stamps in January and resents by March.

The mechanics of protecting a renewal you no longer have an internal advocate for are the same across industries — I wrote out the version for a law firm account that has already half checked out, and the sequencing for an asset analytics account six weeks from expiry covers the harder case where procurement is already running a comparison. The through-line in both: stop selling the renewal and start selling the cost of the switch to the person who would have to manage it.

The email you send before the call

One more thing the rep got wrong, upstream of everything.

His meeting request said: "Introduction and account review ahead of January renewal."

That subject line pre-frames the entire call as administrative. Priya walked in expecting paperwork, which is exactly the frame the rep then confirmed by narrating history.

What I would send instead, short:

"Priya — you've picked up the account we work with. I don't want to assume you inherited any context, and I don't want to spend your time recapping decisions you weren't part of. Twenty minutes to hear what you've been asked to fix, and I'll tell you straight whether we're relevant to it. If we're not, I'd rather know now than in March."

No Dana. No "as agreed." No renewal date in the subject line. The date comes up in the call, from you, at the point where you separate the two decisions.

What this call is really about

A champion leaving does not kill a deal. What kills the deal is a rep who keeps selling to the person who left.

Everything in the original call was aimed at Dana. The recap was for Dana. The business case was Dana's. "What we agreed" was agreed with Dana. Priya sat through nine minutes of a conversation that was not addressed to her, and concluded, correctly, that this vendor's relationship was with a person, not with her company.

The rewrite costs nothing. Same call, same twenty-five minutes, same renewal date. The only change is whose agenda goes first.

If you want to get this right, the answer is not reading about it. It is running the open out loud until "you've been in the seat two weeks, what's on your list" comes out steady instead of apologetic, and until you can say "I'd like to park the expansion" without your voice going up at the end. That is the work I built DrillCall for — repping the awkward opens against a stakeholder who did not ask to inherit you, before you spend a real one finding out you flinch. Take the champion-departure scenario, run it six times, and notice how much of the history you stop needing to say.