Your Champion Just Left the Company. Here's the Next Seven Days.

You do not find out in a meeting. You find out because LinkedIn tells you, on a Tuesday, that Sarah has started a new position at some company you have never heard of. And the deal you had at commit, or the renewal you had marked green, just lost the only person who was going to fight for it.

I have had this happen on deals I was counting on to make a quarter. The first reaction is always the same and always wrong: you assume the deal is fine because the need is still real. The need is still real. Nobody owns it anymore. Those are different problems and only one of them is yours to solve.

What follows is what I actually do, day by day, starting the hour I find out. It is not elegant. Most of it is phone calls that feel awkward to make.

Day 1: Get the departing champion on the phone before their access is cut

There is a window here and it closes fast. Somewhere between their last day and a week after, IT kills the email, the Slack, the CRM login, and the calendar. Once that happens your champion becomes a stranger with a personal Gmail and no reason to help you. Before that happens, they are still connected, still have context, and — this is the part people miss — they often feel a little guilty about leaving a project half-finished.

So call. Not email. Call the mobile if you have it, and if you have been doing your job you have it. If you only have the work line, call it anyway, because they may still be serving out notice.

What I say, more or less verbatim:

"Sarah, I saw the news. Congratulations, genuinely. I am not calling about the deal — I am calling because I do not want to be the vendor who keeps emailing a dead inbox for three weeks. Two things. Who is picking up the project, and what should I know about them?"

That framing matters. If you open with "what does this mean for our timeline," you sound like a rep protecting a forecast, and they will give you the polite version. If you open by admitting you are trying not to be annoying, you usually get the truth.

The truth you are hunting for is three things.

First, the name. Who inherits it. Sometimes it is a peer, sometimes a manager who is going to hold it temporarily, sometimes genuinely nobody and it goes into a queue. "Nobody yet" is the most dangerous answer and the most common one.

Second, the honest read. Ask it directly: "If you were still there, what were the odds this got signed this quarter? And what were the odds it dies now that you are not?" People who are leaving will answer that question honestly in a way they never would while employed. I have had champions tell me on their way out that the budget was never as approved as they had implied. Painful, useful, and better to know in week one than week nine.

Third, the introduction. Ask for it while they still have the email account. "Would you send one note from your work address introducing me to whoever is picking this up? Three lines is plenty. I will draft it for you." Then actually draft it. Send it within the hour, written in their voice, short, with the business reason for the project in it rather than a description of your product. An introduction that comes from a departing employee's work email carries institutional weight. The same person forwarding from Gmail four days later carries none.

If they say yes and then do not send it, follow up once the next morning and then let it go. They are moving house, professionally speaking.

Day 2: Write down everything only your champion knew

Spend an hour on this. Open a blank document and reconstruct the deal without them in it.

What was the original trigger? Who complained loud enough to start this? What number did the CFO care about? Which team hated the incumbent tool and why? What was the internal politics — who was quietly against it? What did procurement say the process was? Which of those facts exists anywhere other than in your head and your champion's memory?

Almost every rep I have watched discovers, doing this exercise, that the business case was never written down anywhere the customer could see. It lived in a deck you presented once and in a champion's head. Both of those are now gone. The document you are writing is the thing you will need on Day 4, so make it real.

Also pull your call notes and find every other name that has ever appeared on a meeting invite, a forwarded email, a security review, or a trial account. Those are your remaining threads whether you cultivated them or not. Rank them by how much they personally suffered from the problem you solve. The person who feels the pain daily is worth more than the person who is senior.

Day 3: Work the second and third threads, and be blunt about why

Call the other names. Do not be coy about the reason.

"Mark, you and I met on the security review back in March. Sarah's left and I do not want this to fall through a crack. Do you know who has picked it up? And separately — is the problem you described to me still a problem?"

That second question is the whole call. You are not selling. You are checking whether the pain survived the person. Pain that lives in one person's head is a preference. Pain that three people describe independently is a business problem, and business problems get budget even after reorgs.

If two or three people confirm the pain is still there and still costing them something, you have a deal that can be rebuilt. If everyone says some version of "honestly that was Sarah's initiative," you have learned something expensive and valuable in three phone calls instead of three months.

One more thing to do on Day 3: ask each of them who they think should own it. People are surprisingly willing to nominate a colleague, and when you later call that colleague you can say "Mark suggested I speak to you," which is a hundred times better than a cold approach into a grieving org chart.

Day 4 and 5: The inheritor call, which is not a discovery call and not a demo

Here is the thing that trips people up. The person who inherits your deal did not choose you. They get no credit for a win that was already in motion, and they get all of the blame if it goes badly. Their rational incentive is to slow it down, re-evaluate, or quietly let it die and blame the transition. If you walk in acting like the deal is still at stage five, you are asking them to sign off on someone else's judgment. Nobody does that.

So the first call with the inheritor gets treated as a first call. New discovery. Their words, their priorities, their read on the problem. I open it something like:

"I have been working with Sarah since February. I could send you the whole history, but I would rather not assume any of it still applies. You have inherited a pile of things this month. Where does this one actually sit for you?"

Then shut up. What comes back is usually one of three answers, and each one has a different next move.

"It's a priority, I just need to get up to speed." Good. Your job is to make getting up to speed take twenty minutes, not two weeks. Send one page. Not the deck. One page: the problem in their organisation's language, what it costs them, the three options they considered including doing nothing, and where the process had got to. Offer to walk them through it live rather than leaving them to read it.

"I need to re-evaluate the options." Do not fight this. Fighting it makes you the vendor who is scared of comparison. Instead: "That is completely fair, and honestly I would do the same. Can I ask you to do it on a clock? If you tell me you need three weeks, I will stay out of your way for three weeks and come back with whatever you need to close it out." Then help them evaluate — including handing them the honest weaknesses of your product. An inheritor who catches you overselling on the first call will never trust the rest of it.

"I don't know that we're doing this at all." Now you are in a real conversation. Go back to the pain the other threads confirmed. "When I spoke to Mark last week he said the reconciliation work was still eating a couple of days a month from his team. Is that not a problem worth solving, or is it just not this quarter's problem?" Those are two very different objections and you need to know which one you have.

Rebuild the business case in the new person's language

The case you built with Sarah was built with Sarah's metrics, Sarah's frustrations, and Sarah's political goals. The new owner has different ones. If she came from the operations side and your case was written for finance, rewrite it. If he reports to someone who was skeptical of the project, the case now needs to answer that skeptic, not the old champion's boss.

Practically: take the one-pager and change the first line. The first line of a business case should be the thing that keeps this person up at night. Everything else in the document supports it. I have rewritten the same case three times for three different stakeholders in one account and it is not dishonest, it is translation.

And give the new owner something to own. This is the underrated move. Ask them what they would change about the plan. Scope, rollout order, pilot group, success metric, anything. Then change it and put their fingerprints in the deck. A project the inheritor has personally modified is a project they will defend. A project they inherited unchanged is a project they will abandon the moment it gets inconvenient.

Day 6: Reset the timeline honestly

Your old close date is dead. Pretending otherwise costs you credibility with your manager and, worse, makes you push the customer in a way they will resent.

Have the conversation with the new stakeholder plainly: "Sarah and I had this landing at the end of the month. Given you have picked it up two weeks ago, that feels unrealistic to me. What does a realistic date look like from where you sit?" Then take their date, add the procurement step they forgot, and forecast that.

Internally, move the deal back a stage. Not because process demands it but because it is true. You lost your champion, which means you lost your access, your internal advocate, and your read on the politics. That is a stage-two deal wearing a stage-five suit. Slip it, tell your manager why in one sentence, and go rebuild.

Day 7: Decide what this actually is now

End of week one you should be able to answer honestly: is this a deal that survived the person, or was it always a person's pet project?

Signs it survived: multiple people describe the same pain unprompted, there is a budget line that exists independently of the departed champion, and the inheritor is asking questions about implementation rather than about justification.

Signs it died: nobody will own it, the answer to "who picked this up" keeps changing, and the pain is only ever described in the past tense by people quoting Sarah. When that is the case, say so out loud, take it out of the forecast, and put the account on a nurture cadence with a note to check back when the new org settles. The worst outcome is not losing the deal. It is spending a quarter's worth of calls on a corpse because you could not admit the sponsor was the whole reason it existed.

The renewal version of this is more dangerous

Everything above applies to new business. On a renewal it plays out differently and worse, because there is no obvious moment where anyone tells you the deal is off. It just does not renew.

Here is the pattern. Your sponsor bought the tool, drove the rollout, and then left. Usage was already soft because the original rollout never quite finished. The person who inherits the budget line looks at a contract they did not sign, for a tool their team barely logs into, and sees an easy saving. Nobody calls you to argue. They just do not respond in the last month and then send a non-renewal notice from a procurement address.

So when a sponsor leaves on a renewal account, treat it as a red account that day, not at ninety days out. Pull the usage data before you make a single call, because the first question you will get from the new owner is "who is actually using this," and if you do not know the answer before they ask it, you have already lost the conversation. Then get in front of the actual users — the people who never signed anything but who would notice if the tool disappeared on Monday. Those users are your new champions, and their testimony is worth more to a cost-cutting inheritor than any deck you can build.

The call itself has a shape to it, and the shape changes by industry. In software the fight is almost always adoption versus seat count, which is the conversation I walk through in the SaaS renewal call script. In freight and 3PL it is usually a visibility platform where a departed logistics director means nobody is defending the spend anymore, and the freight and 3PL version deals with exactly that. Carriers have their own flavour of it, where a claims platform survives on the goodwill of one operations lead, which is the situation the insurance renewal script is built for. And in professional services, where the sponsor leaving often coincides with a year the firm would rather forget, the professional services save call is the one I would rehearse.

The common thread in all of them: you are not asking the new person to renew. You are asking them to decide, with evidence, whether the thing is worth having. If it is, they will renew it and own it. If it is not, you needed to know in month nine so you could fix adoption, not in month twelve so you could beg.

Prevention: what multi-threading looks like before you need it

Everything above is emergency medicine. Here is the actual cure, and it is boring.

Multi-threading is not adding a CC line. It is having a relationship with a second person that could survive the first one leaving. The test is simple: if your champion vanished tomorrow, is there someone else at that account who would take your call and tell you the truth? If the answer is no, you have one thread, no matter how many names are on the email chain.

Three habits that get you there without being weird about it.

Ask your champion for the introduction while things are good. "You've told me the finance team will need to sign off eventually. I would rather meet them now while there is nothing to argue about than three weeks before a signature." Champions almost never refuse that, because it makes their life easier.

Go down, not just up. Sales training pushes you towards the VP. The VP moves jobs. The senior analyst who does the workaround every Friday morning does not, and she will tell you exactly how the deal is really going. On the accounts I have seen survive a sponsor change, it was usually a mid-level operator who kept the project alive.

Write the business case down where the customer can see it, and put more than one person's name on it. A shared document that three stakeholders have commented on is institutional memory. A deck sitting in your champion's downloads folder is not.

And on renewals specifically: put a standing item in every quarterly review that asks who else needs to be in this meeting. Do it when the account is green. Nobody ever added a stakeholder in a crisis and had it go well.

What I would do next

If I were you and I had just seen the LinkedIn notification, I would spend twenty minutes today rehearsing the two calls that decide this: the one to the departing champion asking for the truth and the introduction, and the first call with the inheritor where you have to sound curious rather than desperate. Both of them go badly the first time you try them live, and the first time you try them live is on an account you cannot afford to lose. That is the specific reason I built DrillCall — so reps can run the awkward version of a call ten times against an AI buyer before running it once against the person holding their number. Run the inheritor call a few times with the prospect set to skeptical and see how you sound. It is a cheaper place to be bad at it.

The champion leaving is not what kills the deal. Waiting a week to find out, and then acting like nothing changed, is what kills the deal.