Your Champion Just Left. Here's the 10-Day Plan.

A champion leaving is not a normal loss. A normal loss you can see coming. You get the slow-walk, the reschedules, the budget language, the sudden interest in a competitor's pricing page. You have time to fight.

This one arrives as a LinkedIn notification. Or a bounced email. Or a calendar invite that quietly disappears from your week. One day you have a deal with momentum and a person inside the building who wants it to happen, and the next day you have a logo, an opportunity record, and nobody.

I have watched this kill deals that were done. Not "probably closing" — done. Verbal, security review passed, redlines back, the whole thing. And then the person who spent four months carrying it internally took a job somewhere else, and the deal sat in the pipeline for two more quarters like a body nobody wanted to move.

The reason it hurts so much is that you already paid for the revenue. You did the discovery. You built the case. You earned trust with a specific human being, and that trust does not transfer automatically to whoever sits in the chair next. It has to be rebuilt from scratch, and the window to do it is short, because the moment a champion leaves, everything they were carrying gets re-evaluated by people who did not choose it.

So here is what I do. Day by day. It is not complicated, but it is time-sensitive in a way most reps do not respect.

Why speed matters more than finesse here

When someone leaves a company, their projects go into a pile. Somebody has to sort that pile. That sorting happens fast — usually within the first few weeks — and it happens without you in the room.

Everything in that pile gets one of three labels. Keep, because there is a contract or a deadline or a boss who cares. Pause, because nobody understands it well enough to kill it. Or quietly drop, because the only person who ever advocated for it is gone and no one wants to inherit an argument.

Your job in the first ten days is to make sure your deal or your account lands in the first bucket, and to do it before anyone has settled into an opinion. Opinions are cheap to form and expensive to change. If you show up in week six with a beautifully personalized sequence, you are not competing against indifference. You are competing against a decision that already got made in a meeting you were not invited to.

So the plan is aggressive on days one through five and patient after that. Most reps do it backwards. They send a polite "sorry to hear you're moving on" note, wait for the org to sort itself out, and then start real outreach three weeks later, at exactly the moment the deal has already been reclassified.

Day 1: Find out where they went, and whether the deal goes with them

The first move is not to the account. The first move is to the person who left.

Call them. Not email — call. If you have their mobile, use it. If you do not, LinkedIn message and ask for it. This is the one moment where the goodwill you built has maximum value and a rapidly shortening shelf life, because in about a month they will be deep in a new job and you will be a name from a previous life.

What you are after in that conversation is two things, and you should be direct about both.

Where did they go, and do they have the same problem there? This is not opportunism, it is math. A champion who believed in your product enough to fight for it internally is the single best pipeline source you will find this quarter. They know the product, they know the objections, they know what the implementation actually looks like. If their new company has the same pain, you are not prospecting — you are picking up a conversation you already had, in a new building. I have had a champion leave and open two doors at the new place inside a month, which more than covered the deal I lost at the old one.

Who is picking up their work? Not who has their title. Who has their work. Those are almost never the same person in the first month, and knowing the difference is the whole game. Ask it plainly: "Before you go — who is actually going to pick up the vendor evaluations? Is it going to your manager, or is one of your peers absorbing it?"

Here is roughly how I open that call:

"Hey, saw the news. Congratulations, genuinely. Two things and I'll let you go. First, selfishly — is the same problem waiting for you at the new place? Because if it is, I'd rather have that conversation with you than with a stranger. Second, and this is me asking a favor: who's picking up the [project] internally? I don't want to cold-email the wrong person and make it weird for you on your way out."

That last framing matters. You are giving them a reason to help you that protects their reputation, not just yours. Most people who are leaving on good terms will hand you a name and sometimes an introduction, because it costs them nothing and it makes them look organized to the people they are leaving behind.

If they will send an internal handoff note before their last day, that is worth more than any sequence you could write. Ask for it. Give them the draft:

"Before I go — Timothy at [vendor] has been working with me on [project]. We got as far as [specific stage]. Worth continuing the conversation with [new person] so it doesn't fall through the cracks."

One paragraph. Two minutes of their time. It converts a cold reintroduction into a warm one, and the difference in how those two calls go is not subtle.

Days 2 to 4: Work the org for the person who inherited the work

Assume you got nothing on day one. No callback, no name, just an out-of-office. That happens plenty.

Now you are doing org archaeology, and the mistake almost every rep makes is going straight up. They find the departed champion's manager, send a long email explaining the deal, and wait. Sometimes that works. Usually it produces silence, because a director with a vacant seat on their team has forty things happening and your deal is not one of the loud ones.

The better move is sideways first. Find the peers. Look at who else was on the email threads, who else showed up to the demo, who got cc'd on the security questionnaire, who asked a question in the technical call that suggested they would be a user. Those people are the ones absorbing the work, because that is how work actually gets redistributed — it goes to whoever was already closest to it, not to whoever the org chart says owns the function.

Then work three angles at once over these three days.

The peers get a short, low-stakes note that assumes nothing and asks for direction, not a meeting. Something like: "Hi Sarah — I'd been working with Dan on [project]. I saw he's moved on. I'm not trying to restart anything, I just don't want to be the vendor who keeps emailing a dead address. Is this still live on your side, and if it's not you, who should I be talking to?"

The manager gets a different note — shorter, and framed around risk and continuity rather than the sale. Managers care about things falling through cracks on their watch. "Dan and I had gotten to [stage] on [project], with [date] as the target. I want to make sure that doesn't get lost in the transition. Happy to send a one-page summary of where it stands so whoever picks it up isn't starting from zero." Offering the summary is the ask. It is easy to say yes to and it gets you back in the record.

The users — if this is a live account rather than an open deal — are your early warning system. If people are still logging in, still asking support questions, still in your Slack channel, the value is real and the renewal has a floor under it. If usage went quiet the week your champion left, you were never selling to the company. You were selling to one person, and now you have a much bigger problem than a transition.

Three days is the right amount of time for this. Long enough to give people a chance to respond, short enough that you are still ahead of the pile-sorting.

Day 5: The reintroduction call that assumes nothing

You got a name. Now you have to run the single most-fumbled call in enterprise sales.

The fumble is always the same. The rep treats this as a continuation. They open with "so, picking up where Dan and I left off" and then walk through the deal history like a status update. It fails for a reason that should be obvious but never is: the new person did not leave off anywhere. They have no history. They inherited a folder and a calendar invite and a vague sense that some vendor is in the middle of something. Talking to them like they were in the room makes them feel behind, and people who feel behind stall.

The other fumble is the opposite — treating it as a fresh cold call and running full discovery from scratch, which wastes the equity you built and makes you look like you were never really engaged.

The right posture is somewhere in between: you have context, they do not, and you are going to hand it over without any expectation that they agree with it.

Here is how I open:

"I want to be useful and I want to be fast. Here's what I know: Dan and I had been working on [problem], we'd gotten to [stage], the target was [date]. That's what I know. What I don't know is whether any of that is still how you see it, or whether your priorities are different. So rather than me pitching you, can I ask what landed on your plate when Dan left, and where this sits in that pile?"

Then stop talking.

The answer to that question is your entire quarter. You will get one of three things. You will get "honestly, this is priority four and I haven't looked at it" — which is workable, and tells you exactly what you need to displace. You will get "actually I have opinions about this, I never thought we needed it" — which is painful but is the best possible outcome, because now you know where the fight is. Or you will get vagueness and warmth and no specifics, which is the dangerous one, and I will come back to that.

What you are also listening for is whether they inherited the problem or just the project. Someone who owns the underlying pain — the outages, the manual reporting, the compliance gap — can be rebuilt into a champion. Someone who just inherited a vendor evaluation with no ownership of the outcome will never fight for you, no matter how good the call goes. If it is the latter, your job on that call is to find out who does own the pain, and to ask for the introduction while you are still on the phone.

What to never send

Three things. I have seen all three do real damage.

Never forward the old thread. A forty-message chain with a departed employee's name all over it reads as "here is a pile of work you did not ask for." Summarize instead. One page, their language, no jargon they were not present for.

Never reference the price you already agreed to, unprompted. If your champion negotiated a number, the new person did not negotiate anything. Leading with "we'd landed on X" invites them to treat X as the ceiling and start over below it. Let them ask.

And never — this one is the most tempting — imply that their predecessor already committed. "Dan had signed off on this" sounds like leverage in your head. In their head it sounds like you are trying to bind them to a decision made by someone who is no longer accountable for it. New people in a seat need to own their first decisions. Give them room to arrive at yes themselves.

Days 6 to 8: Rebuild the business case in the new person's language

The case you built with your champion was tuned to your champion. It used their words, aimed at their metrics, solved their version of the problem. That case is now a historical document.

Rewriting it is the actual work of this ten-day plan, and it takes three days because it should. Go back to what the new person told you on day five and rebuild the argument around what they are measured on. If the old champion cared about engineering hours and the new one owns a cost line, the same product now saves money instead of saving time. Nothing about the product changed. Everything about the framing does.

Keep it to one page. Where the project stood, what problem it was solving, what the alternative to doing it is, what the next step costs. If you are re-establishing value inside a live account facing a renewal, this is the same muscle as a save call, and the sequencing I use in the SaaS renewal call script applies almost directly — the difference is that you are not defending against a competitor, you are defending against inertia and an empty chair. If your account is in logistics and the value story runs through visibility and exception handling, the freight and 3PL version of that renewal script is closer to the right language.

While you are rebuilding the case, rebuild the coalition too. A single champion is how you got into this mess. Use the transition as cover to meet two or three more people — the transition is the most legitimate reason you will ever have to ask for wider access. "Since Dan's gone, I want to make sure I'm not making assumptions about how your team actually uses this. Could I get twenty minutes with whoever's closest to the day-to-day?" That request gets said yes to constantly, and it is how you make sure the next departure does not reset you to zero.

Days 9 to 10: Re-establish the date

A deal without a date is not a deal. It is a relationship.

By day nine you should know enough to put a specific next step on a specific calendar day, and you should ask for it directly rather than hoping momentum produces one. Not "let's touch base in a few weeks." A named event with a named date: the technical review on the eleventh, the pricing conversation with finance on the eighteenth, the decision by end of month.

Ask it as a question about their constraints, not yours: "What has to be true for this to get decided this quarter, and who has to be in the room? Let's work backwards from that and get it booked."

If they can give you a real answer with real names and real dates, the deal survived the transition. If they cannot, the deal did not.

How to tell a paused deal from one that died quietly

This is the distinction that separates reps who forecast well from reps who carry ghosts in their pipeline for three quarters.

A paused deal has friction in it. The new person pushes back. They ask hard questions about pricing, about implementation, about who is going to run this internally. They give you a reason for the delay that is specific and inconvenient — a hiring freeze, a reorg, a system migration that has to finish first. Specific and inconvenient is good. It means they are thinking about it seriously enough to have real obstacles.

A dead deal is smooth. Everyone is pleasant. Emails get answered, politely and a little slowly. Nobody objects to anything. You get "this looks great, let me socialize it internally," and then nothing, and then a check-in, and then "still interested, just a lot going on." No friction at all, because nobody is pushing against anything, because nobody is pushing.

When you see that pattern, run the test. Ask for something small that costs them almost nothing but requires them to act: a fifteen-minute call with one other person, a document, an answer to a question only they can answer. If they will not spend fifteen minutes, they will not spend the budget. Then say the quiet part out loud — "It feels like this stopped being a priority when Dan left, and that's a completely reasonable outcome. I'd rather know than keep checking in. Is this still real?" — and take the answer seriously either way. A clean no on day twelve is worth more than a maybe you nurse until March.

And when a deal does die this way, the last thing to do is the most valuable. Go back to the departed champion at their new company. That is a warm referral in everything but name, and the discipline for working it is the same as any other referral: move before the goodwill cools, be specific about what you are asking for, and never make them do your prospecting for you. The mechanics in the professional services warm call script transfer to this situation almost line for line.

The part nobody wants to hear

Every deal with exactly one advocate is a deal with an expiration date you cannot see. People change jobs constantly. If your close plan depends on one human being staying in one chair, you do not have a close plan. You have a bet.

So the real fix for a departing champion is not the ten-day plan. The ten-day plan is triage. The fix is multithreading every deal above a certain size from the first call, so that when someone leaves you lose a relationship instead of an opportunity.

The hardest part of all this is the day-five call, and it is hard because you only get to run it a few times a year and it never gets comfortable. You are talking to someone who has no reason to care yet, about something they did not choose, while trying not to sound like you are collecting on a debt they never signed for. If you want to get good at it, practice it out loud before you dial — that is exactly the kind of live, high-stakes conversation we built DrillCall to let reps rehearse against a realistic voice, so the first time you handle "honestly, I'm not sure we need this" is not on a call that decides your quarter.

Either way: when the notification comes, do not send condolences and wait. Call them that day. Find out where they went. Find out who inherited the work. And get back in the room before the pile gets sorted without you.