Your Champion Just Left. Here Are the First Three Calls You Make.

Nobody kills your deal. It just goes quiet.

The most common way a live opportunity dies is not a competitor. It is not price. It is not the security review. It is that the one person inside the account who actually wanted this thing to happen took a job somewhere else, and nobody told you.

You find out from a LinkedIn notification, or a bounced email, or an out-of-office that says "I am no longer with the company, please contact..." and then a name you have never heard of. And in that moment the deal you had at ninety percent is closer to zero than you want to admit, because everything that made it real lived in one person's head. The internal politics. The reason this project got funded instead of the other one. The favor they called in with security. The fact that the CFO hates three-year terms but will sign one if you call it something else.

All of that walked out the door with a cardboard box.

I have watched this happen on my own deals and I have watched it happen to reps I have worked alongside. The reps who save these accounts are not smarter. They are just faster and less polite about it. They pick up the phone inside a couple of days instead of sending a careful email and waiting a week for a reply that never comes.

So here is the triage. Three calls, a 72-hour clock, and what to actually say on each one.

Why 72 hours

The clock is not arbitrary. It is tied to three things that decay fast.

The first is the laptop. Your champion's access gets cut, sometimes on their last day, sometimes the week after. Once IT wipes them, the deck you built together, the internal business case, the Slack thread where four people agreed this was a priority — that is all gone from their reach. They can still remember it. They cannot forward it to you.

The second is goodwill. On the day someone resigns, they feel generous and slightly guilty. They know they are leaving people in the lurch. If you call in that window, they will help you. Give it three weeks and they are deep into onboarding at the new company, your project is somebody else's problem, and your call feels like an imposition.

The third is the vacuum. When a seat empties, the work gets reassigned within days. Somebody picks up the open items. If you are not one of the open items with a name and a next step attached, you are not on the list at all. You become a line in a tool nobody logs into.

So: three days. Not a nurture sequence. Three phone calls.

Call one: the departing champion, before the laptop dies

Call the person who is leaving. Their cell, not their work line. If you have been working together for months and you do not have their mobile, that is a separate lesson for later, but LinkedIn messages work and so does a text to whatever number they once called you from.

Open by congratulating them, and mean it. This is not a tactic. Somebody just improved their own life and you are on the short list of people who noticed. Then be direct about why you are calling, because they know why you are calling and pretending otherwise insults both of you.

"Congrats, seriously. Selfishly I have got a favor to ask before your access gets shut off — can I have ten minutes?"

Almost nobody says no to that.

The four things you need out of this call

Who inherits it. Not "who is your backfill," because the backfill may not exist for two months. Ask who is picking up the work in the interim. Those are different people and the interim one is the one who matters right now. Get a name, a title, and how they feel about the project.

Where the project actually stood. Not where it stood in your CRM. Where it stood internally. Was the budget approved or just discussed? Was it in the plan for this quarter or was your champion trying to pull it forward? Was there anyone quietly against it? I have found out on this call that the deal I thought was in legal review had never made it past a verbal from a director who was about to be reorganized out. Better to know.

Who else already cares. Every project has more than one person who benefits from it. Your champion knows who they are because they were the ones your champion leaned on. Ask: "Besides you, who was most annoyed by this problem?" That question gets you names you never met on the deal.

A warm intro you can cash. This is the ask. Do not settle for "sure, mention my name." Mentioning someone's name is worth nothing. Ask for a specific, written handoff: an email from their work address, before it goes dark, to the successor and to you, saying what the project is, why it mattered, and that you are the person to talk to.

Give them the language. People are busy and they will send whatever you draft.

"If it is easier, I will write it and you just hit forward. Something like: 'Before I go — the visibility project with Tim's team. We scoped it in the spring, budget is in the ops line, the whole reason we started was the Friday morning fire drill. Tim has all the context. Worth ten minutes.'"

That email is the single most valuable artifact you will get out of this entire situation. It converts a cold call into an inherited obligation. It also survives the champion's departure, which is the whole point — it sits in the successor's inbox from an internal, trusted address.

One more thing before you hang up. Ask where they are going. Not to be nosy. Your champion just became a warm lead at a new company where they have budget authority and a mandate to fix things. I have closed more business from champions who changed jobs than from most of my outbound. Put a reminder in your calendar for ninety days out, after they have stopped drinking from the fire hose.

When the champion left angry

Sometimes they did not get a better offer. Sometimes they got pushed, or they quit in frustration, and the project you were working on was part of what they were frustrated about.

You will hear it in the first thirty seconds. The tone goes flat, or worse, it gets loud.

Do not try to recruit them into the grievance. Let them vent for a minute — genuinely, do not rush them — and then get very specific: "I hear you. Setting aside how it ended, is there anyone left there who still wants this fixed, or did it die with you?"

That question does two things. It gives them permission to be honest, and honest is what you need. Sometimes the answer is "honestly, nobody, I was pushing it uphill alone." That is a gift. You just saved yourself a quarter of forecasting a dead deal. Take it out of commit, tell your manager the truth, and go work something real.

And do not ask an angry leaver for a written intro. It will read like a grenade and it will poison you with the successor. Take the intel and go in on your own.

Call two: whoever inherited the seat

Here is where most reps blow it.

The instinct is to call the new person and give them a status update. "Hi, I was working with Sarah on the visibility project, we were in final stages, just wanted to reconnect and figure out next steps." It feels efficient. You are picking up where you left off.

It is exactly wrong, and the reason is simple: the new person owes your project nothing.

They did not scope it. They were not in the room. They did not spend political capital getting it funded. From where they sit, this is an inherited commitment made by somebody who is no longer around to defend it, arriving in the same week as forty other inherited commitments. If your first move is to ask them to honor it, you have made yourself a chore.

Worse, new people in a seat are looking for things to cancel. Killing a predecessor's project is the cheapest way to look decisive in your first month. Do not hand them the opportunity.

Open as a re-diagnosis, not a status update

Treat this as a first call, because it is one. You are running discovery on a person who happens to have a signed-ish deal sitting on their desk.

"I worked with Sarah on the visibility project for the last few months. I am not calling to push you to pick that up — you have not even found the bathroom yet. What I would rather do is spend fifteen minutes on what you are walking into, and then you can tell me whether the thing we scoped still makes sense. It is entirely possible it does not."

That last sentence is the one that works. Giving them a real exit is what makes them stay on the line. You have just become the only vendor who is not demanding they inherit a decision.

Then run actual discovery. Not "what are your priorities," which gets you a recital of the org chart. Ask about the mechanics of their week. What is broken that they noticed in the first ten days. What their boss asked them to fix. What the team complains about in standup. The structure I use for a technical re-diagnosis is the same one in the cybersecurity discovery playbook — diagnose the operating reality before you go anywhere near what you sell, and let the person describe the problem in their own words so they own the conclusion.

What you are listening for is whether the pain your champion described still exists. It usually does. Problems do not resign. If the Friday morning fire drill was real, it happened again last Friday, and the new person sat through it wondering why nobody had fixed it.

When you hear it, that is your moment. "That is the exact thing Sarah brought us in for. Want me to show you what she had lined up? You can tear it apart."

Now it is their decision, not their inheritance.

When the backfill is a contractor

This happens constantly and it changes the play. A contractor or an interim manager is holding the seat while a search runs. They usually have zero signing authority and a strong incentive to make no permanent decisions.

Do not treat them as the buyer. Treat them as the best-informed friendly you have. They will tell you things a permanent employee never would, because they have no long-term political stake. Ask them directly: "Realistically, can a decision like this get made before the permanent hire lands? Who would sign it if the answer is yes?"

Then do the two things that actually help. Keep the contractor supplied with whatever makes their interim life easier — documentation, a summary of where things stood, a one-pager they can hand to the incoming hire. And work the level above, which is call three.

When there is no successor at all

Sometimes the seat just sits empty. The work got sprayed across three people who each took a piece. In that case you are looking for the person who took the piece that touches your problem, and the honest way to find them is to ask the person above.

Call three: the exec sponsor or the finance owner

The first two calls are about the project. This one is about the money.

Budget lines are not attached to people, but they get reviewed when people leave. A departure is a natural moment for a finance team to sweep unspent allocations, and an unspent allocation with no named owner is the easiest thing in the world to sweep.

So you call the exec sponsor, or if the sponsor was your champion's boss and is also gone, the finance owner. Your goal is not to sell. Your goal is to make sure that when someone looks at that line item, a human being says "no, leave that, it is committed."

The call is short and it is respectful of the fact that this person has a lot going on.

"You have got a hole in the ops team and I am not going to pretend my project is your top problem this week. One question and I will get out of your way: the budget that was allocated for this — do you want me to hold it, or should I assume it goes back into the pot until you have hired?"

That question forces a decision that is easier to answer with "hold it" than with "kill it." Killing it means the exec has to own the decision to un-fund a thing their team said they needed. Holding it costs them nothing today.

If they say hold it, get a date. "Should I check back after the new person starts, or does that feel too soon?" Now you have a real next step tied to an event, not a soft follow-up in ninety days.

If they say the money is going back, you have still won, because you found out now instead of at the end of the quarter.

Resetting the clock when the account has been headless for two months

Everything above assumes you caught it early. Sometimes you did not. Sometimes you inherited the account, or you were heads-down elsewhere, and by the time you look up the seat has been empty for two months and the renewal is coming.

The mistake here is to run a renewal conversation. There is no relationship to renew. Nobody in that building has an emotional stake in your product, nobody can articulate what it does, and the usage data probably looks terrible because the person who drove adoption left.

What you have is a re-sell with an artificial deadline, and the deadline is the enemy. So the first move is to buy time. Ask for a short extension — a month, a quarter, whatever the contract structure allows — explicitly framed as giving the new owner a fair shot at evaluating something they did not choose. Procurement teams grant these more often than reps expect, because the alternative is forcing a decision nobody is qualified to make.

Then you run a save. Not a renewal. A save has a different shape: you go find the users who never stopped using the thing, you get one of them to tell you what would break if it went away, and you carry that to the new owner as evidence rather than as a pitch. The mechanics of that conversation, including how to open when you know the account has gone cold, are laid out in the SaaS renewal save call script, and the same structure works in relationship-heavy businesses where the departure of one partner puts everything at risk — the legal renewal script walks through that version.

One warning about extensions. Only ask for one if you are going to use the time. An extension you spend sending check-in emails just moves the loss one quarter to the right and makes it worse, because now the new owner has had another quarter of not needing you.

The part nobody does

All of this is reactive. The real fix is upstream, and it is boring: multi-thread every deal before you need to, because you cannot lose the only person who cares if there is more than one.

I know every sales book says this and I know reps nod and then do not do it, because single-threading is faster and the champion is right there being helpful. But the question I try to ask myself on any deal I actually care about is simple. If this person quit tomorrow, who would notice that we stopped talking? If the honest answer is nobody, the deal is not as healthy as the stage field says it is.

The good news is that the three calls above are learnable, and they are mostly about tone. The congratulations call has to sound genuine. The successor call has to sound like you are giving them an out. The budget call has to sound like you respect that they have bigger problems. Get the tone wrong on any of them and the words do not matter.

That is why, if I were coaching a rep through this, I would not hand them a script and wish them luck. I would have them run the successor call out loud a half dozen times against someone playing a skeptical new director who does not want to inherit anything — which is exactly what we built DrillCall for, so the first time you say "it is entirely possible this does not make sense anymore" is not on a live call with a deal on the line. Practice the awkward one. That is the one that saves the account.