The Champion Departure Save: Rebuilding the Deal When Your Internal Champion Walks Out the Door — a 60-Minute Sales Training

🤝 The Pulse Training

Who this is for: AE / enterprise reps + CSMs + sales managers + RevOps deal-desk running deals or renewals where the named champion has just resigned, been reorged, promoted out, or gone quiet. This is the reactive playbook for the single most common silent deal-killer: champion departure — the moment your one warm contact updates their LinkedIn and your forecast quietly becomes fiction.

Why it matters now (cited): Per Gartner B2B Buying research, the typical enterprise buying group spans 6-10 decision-makers, and a meaningful share of named buying-group contacts change roles within a single 12-18 month enterprise cycle. The MEDDIC / MEDDPICC framework — originated at PTC (NASDAQ: PTC) by Jack Napoli and Dick Dunkel and now taught by firms such as MEDDICC Ltd (Andy Whyte) — scores Champion as a formal, gated deal element.

CSO Insights (now part of Korn Ferry, NYSE: KFY) and RAIN Group win-rate benchmarking consistently shows multi-threaded opportunities (3+ engaged stakeholders) close higher and slip less than single-threaded ones. The U.S. Bureau of Labor Statistics JOLTS series shows national quits running in the millions per month across the post-2021 period — turnover inside your accounts is not anecdotal, it is a macro condition.

What teams leave with: a 5-stage SAVE motion — SENSE, STABILIZE, SCOPE, SELL-AGAIN, SECURE — plus the 4 conversations reps avoid, a stakeholder re-map drill, a Counter-Case on when the save is the wrong move, two role-plays, a manager scorecard, and a one-page leave-behind card.

Manager brings: (1) every open deal with exactly one engaged contact, flagged. (2) The last 3 deals that slipped or died after a contact left. (3) A blank stakeholder map per at-risk deal. (4) The team's current single-threaded percentage from CRM.

Direct Answer

A deal does not die because your champion left — it dies because you found out late and asked the wrong person to fill the gap. Champion departure is a base-rate event, not bad luck: with 6-10 people in a buying group and roughly a quarter to a third of named contacts moving roles inside a 12-18 month window, any deal with a cycle longer than two quarters should *expect* at least one champion change.

The disciplined response is a 5-stage motion — SENSE (detect the signal early), STABILIZE (call the departing champion within 48 hours and ask who inherits the project), SCOPE (re-map the buying group as it exists today), SELL-AGAIN (re-run compressed discovery with the new owner because they never bought what the old champion bought), and SECURE (multi-thread to three engaged contacts so the next departure is a non-event).

Wrapped around that motion are the 4 conversations reps avoid and a Counter-Case test: not every departed-champion deal should be saved. This training is the runnable 60-minute meeting that installs all of it as a team habit.

⚡ TL;DR

• The event is predictable. Buying groups are 6-10 people (Gartner); ~25-35% of named contacts change role within 12-18 months. On a 6+ month cycle, a champion change is the base case.
• The loss is a detection failure. Deals are lost in the weeks *after* a departure that nobody acted on — not at the moment of departure itself.
• Run SAVE: SENSE → STABILIZE → SCOPE → SELL-AGAIN → SECURE. STABILIZE happens inside 48 hours; the departing champion's goodwill window is a heuristic ~10-14 days.
• Have the 4 hard conversations: call the departing champion; admit to the new owner you must re-earn the deal; tell your manager it is at risk *today*; decide to walk if SCOPE finds no owner, no budget, no pain.
• Run the Counter-Case first. Saving a zombie deal is more expensive than losing it. Test: real champion or talker? budget still authorized? does the recovered deal beat the next-best use of the hours?
• SECURE means three threads. One engaged contact is a single point of failure; two is fragile; three survives a departure.

MEETING AGENDA -- 60 MINUTES

*The agenda is a 60-minute core. Sections 2.5 (Counter-Case) and 6 (Leave-Behind) are 3-5 minute inserts a manager can run inside the existing blocks or as a 13-minute extended session. The timing is deliberate: more than half the hour is reps speaking — teaching this as a lecture defeats it.*

🎯 Bottom Line

A deal does not die because your champion left — it dies because you found out late and asked the wrong person to fill the gap. Run SENSE → STABILIZE → SCOPE → SELL-AGAIN → SECURE, have the 4 conversations you would rather skip, and re-map the buying group before you send another email.

THE NUMBERS -- WHAT THE RESEARCH ACTUALLY SAYS (READ FIRST)

📊 Verified Reference Numbers

Use these as anchors. Where a figure is a directional benchmark rather than a single audited statistic, it is labeled as such — never quote a benchmark as a hard fact to a buyer.

How to read this table. Two figures are *definitional* (buying-group size, MEDDPICC gate) and safe to state plainly. Three are *directional benchmarks* (cycle length, turnover rate, win-rate gap) — true as ranges, not as decimals. Two are *practitioner heuristics* (the 10-14 day window, the rule of 3) — they are coaching rules, not statistics, and should be taught as such.

One is a *macro series* (BLS JOLTS quits) — accurate as a published trend, not a per-account prediction. Reps who quote a heuristic as a hard number lose credibility the moment a buyer asks for the source. The honest framing is always: *"the research says single-threaded deals slip more — and on this deal, here is our exposure."*

🧮 The Base-Rate Arithmetic — Why Every Rep Should Do This Once

Here is the calculation that turns "bad luck" into "predictable risk." Take a deal with 6 named buying-group contacts and a 9-month cycle. If roughly 30% of named contacts change role inside a 12-18 month window, then over a 9-month slice the per-contact probability of a move is on the order of one in five to one in six.

Across 6 contacts, the probability that *at least one* of them moves before close is well above half. Now narrow it to the single person who is actually your champion: even at a one-in-five individual chance, that is a one-in-five deal-threatening event you did not plan for. Multiply across a 30-deal pipeline and several of your committed deals *will* lose their champion this quarter.

The arithmetic is the argument: you are not unlucky, you are unprepared. The fix is not to hope; it is to multi-thread so the one-in-five event stops being a deal-killer.

SECTION 1 -- COLD OPEN (0:00-0:10)

🟡 Coach Note

Do not open with slides. Tell the two-rep story, then put one number on the board: how many open deals in this room have exactly one engaged contact. Make the room sit with that number for ten seconds before you say another word.

1.1 The Story — Same Event, Opposite Outcomes

Rep A had a $90K new-logo deal at "verbal yes." Her champion was a VP of Operations who loved the product and had been carrying it internally for two months. One Monday the champion's LinkedIn updated: new company. Rep A emailed the champion's old address (bounced), then waited a week hoping a replacement would surface, then emailed "just checking in" to the same dead thread.

The deal went to no-decision. Nobody at the account ever told her no — there was simply no one left who knew why the project existed.

Rep B had a near-identical deal. Same signal: champion's calendar invite got declined with "no longer with the company." Within 48 hours Rep B had (1) pulled her notes and written down every other name the champion had ever mentioned, (2) called the champion personally on their cell to ask one question — "who inherits this?" — and (3) emailed the champion's manager with a tight, value-anchored recap and a request for a 20-minute handoff call.

The deal closed six weeks later, smaller, but it closed.

Same event. The difference was not luck. Rep B treated champion departure as a known failure mode with a known response.

1.2 Why This Is A Pattern, Not Bad Luck

📎 The Base-Rate Case

Per Gartner B2B Buying research, enterprise buying groups span 6-10 people and contact turnover inside a 12-18 month cycle is routine. Do the arithmetic: if roughly a quarter to a third of named contacts move within that window, then on a deal with a cycle of 6+ months the *expected* number of champion changes is greater than zero — departure is a base-rate event, not an unlucky one.

Per The Challenger Customer (Brent Adamson, Matthew Dixon, Pat Spenner and Nick Toman, CEB / Gartner), the contact most pleasant to sell to ("Talker") is frequently not the one who drives consensus ("Mobilizer") — so even before a departure, a single-threaded deal may be threaded to the wrong person.

MEDDPICC treats an unvalidated Champion as a stage gate precisely so this risk is caught before close.

The macro backdrop reinforces this. The U.S. Bureau of Labor Statistics JOLTS report has shown national quits in the millions every month across the post-2021 labor market.

Your buyers live inside that statistic. A champion is not a fixed asset on the deal — they are a person with a career, a recruiter in their inbox, and a manager who might reorg them next quarter. Treating the relationship as permanent is the original error; the departure just reveals it.

⚠️ Common Trap

*"There's nothing you can do when your guy leaves."* False. There is a narrow window — a practitioner heuristic puts it at roughly 10-14 days — where the departing champion still has goodwill and the organization still remembers the project. The save is mostly about speed and about asking the right two people the right two questions.

1.3 The Number On The Board

Before the teach, the manager writes one fraction on the whiteboard: single-threaded open deals / total open deals for the room. If that number is anything above zero — and it always is — the rest of the hour has its mandate. The cold open is not a story for entertainment; it is a setup for a number the room cannot argue with.

The reason this number works as an opener is that it is *the room's own data*, not a benchmark from a research firm. A rep can dismiss a Gartner statistic as "not how our market works." A rep cannot dismiss the fact that fourteen of their own twenty open deals are threaded through exactly one person.

The cold open converts an abstract industry truth into a concrete, personal exposure that every person in the room is now staring at. That is the emotional pivot the rest of the training depends on.

1.4 What The Cold Open Is Really Teaching

The two-rep story is not about Rep B being smarter or more talented than Rep A. Both reps had the same information, the same product, the same deal size, and the same signal land in their inbox on the same kind of Monday. The only variable that differed was whether the rep had a *named, rehearsed response* to a *known failure mode*.

This is the single most important framing in the training, and the manager should say it explicitly: champion departure is not a skill problem, it is a preparedness problem. Reps do not lose these deals because they are bad at selling. They lose them because, in the moment the signal arrives, they have no script — so they default to the most natural human response, which is to wait and hope.

The entire SAVE motion exists to replace "wait and hope" with a sequence the rep can run on reflex, the same way a pilot runs a checklist. Pilots are not calmer than other people in an emergency; they have a checklist, and the checklist makes them calm.

Transition: "Next 50 minutes: the 5-stage SAVE motion, the 4 conversations you avoid, two role-plays, and a test for when the save is the wrong move."

SECTION 2 -- THE TEACH (0:10-0:35)

🟡 Coach Note

25 minutes. 5-stage SAVE motion (~12 min), 4 avoided conversations (~9 min), stakeholder re-map drill (~4 min). Teach the stages as a sequence reps can recite — if they cannot say the five words in order at the end, the teach failed.

2.1 The 5-Stage SAVE Motion

The SAVE motion is deliberately an acronym because reps under deal pressure do not retrieve frameworks — they retrieve words. SENSE, STABILIZE, SCOPE, SELL-AGAIN, SECURE. Five words, one sequence, run in order.

2.1.1 Stage 1 — SENSE

You cannot save a departure you detect three weeks late. SENSE is the set of early-warning signals: a champion who stops replying within their normal cadence, declined recurring meetings, a LinkedIn change, an out-of-office that names someone new, a "let me loop in a colleague" with no follow-through.

Per Force Management's Command of the Message discipline, "who validated this" is as important as "what was said" — so champion validation must be re-confirmed, not assumed, every time a sponsor's behavior shifts. The structural fix: for every deal, a manager should be able to name at least three engaged contacts.

A deal with one engaged contact is already in a departure-risk state whether or not anyone has left yet.

Bold-lead detection signals:

• Cadence break: A champion who replied within hours now takes days, or replies in one line where they used to reply in paragraphs.
• Calendar drift: Recurring syncs get declined, rescheduled, or quietly stop appearing.
• LinkedIn change: New title, new company, or a profile that suddenly goes active after months of silence.
• Out-of-office tell: An auto-reply that routes to "a colleague" you have never spoken to.
• Hand-off language: "Let me loop in someone" with no follow-through is often a soft exit, not a courtesy.

2.1.2 Stage 2 — STABILIZE

The first 48 hours. Two moves only: (1) reach the departing champion directly — personal cell, personal email if you have it — and ask the single most valuable question available: *"Congratulations. Before you go — who inherits this project, and what should I tell them?"* A champion who liked you will hand you a name and a sentence of context.

(2) Do not blast the account. Do not email five people "I heard Dana left." That signals panic and makes you look like a vendor managing your pipeline rather than a partner solving their problem.

STABILIZE is mostly about restraint. The instinct under pressure is to *do more* — more emails, more contacts, more activity. The discipline is to do exactly two precise things and resist the rest.

2.1.3 Stage 3 — SCOPE

Re-map the buying group as it exists today, not as it existed when the champion was there. Who owns the budget now? Who owns the pain now?

Who was the champion's manager, and do they care? Is there a coach — someone friendly but without power — you can use to navigate to the new owner? Per MEDDPICC, separate the roles cleanly: Economic Buyer, Champion, Coach are not interchangeable, and a Coach is not a substitute for a Champion.

SCOPE produces a written map: every name, their role in the decision, their current temperature, and whether the original business case still belongs to them.

2.1.4 Stage 4 — SELL-AGAIN

This is the stage reps skip, and it is the whole game. The new owner did not buy what the old champion bought — per Winning by Design's bowtie model (Jacco van der Kooij), the renewal or hand-off buyer is frequently not the original purchaser, and value must be re-established as "recurring impact" rather than assumed.

You must re-run a compressed discovery and re-establish value with the new owner as if it were a new deal — because to them it is. Do not say "your predecessor already agreed to this." Say "here is the problem this was bought to solve — does that problem still matter to you?"

The word "compressed" matters. You are not starting a six-week discovery cycle from scratch — you already know the account, the use case, and the original business case. What you are re-running is the *value confirmation*: does the new owner have the pain, does it rank high enough to fund, and do they personally win if it gets solved.

2.1.5 Stage 5 — SECURE

Lock the deal against the next departure. Multi-thread on purpose: get the value narrative in writing and shared with at least three people, confirm the new champion has a personal win (the MEDDIC definition of a true champion), and put a mutual action plan in place that does not depend on any single name.

SECURE is what makes the next champion departure a non-event. A deal that exits SECURE correctly should be able to survive losing *any one* of its three threads without going to no-decision.

There is a subtle discipline inside SECURE that reps miss: the value narrative must be *written down and shared by the buyer's own people*, not just by you. A one-pager that lives only in your sent folder dies when your one contact dies. A one-pager that the new champion has forwarded internally, that the economic buyer has seen, and that a coach can reference — that document survives a departure because it now lives inside the account's own memory.

The goal of SECURE is to move the business case out of a single person's head and into the organization's shared record.

🔐 The SECURE Checklist — What "Hardened" Actually Means

A deal is genuinely departure-proof only when all four of these are true. Anything less is a deal that merely *feels* safe.

• Lead-in: three engaged contacts, not three names in the CRM. Engaged means they have spoken with you and have a reason to want the project to succeed — not that you have their email.
• Lead-in: the value narrative is in writing and has been forwarded internally by someone at the account, so it survives any single departure.
• Lead-in: the new champion has a confirmed personal win — a promotion case, a metric they own, a problem that makes them look good when solved. A champion with no personal stake is a coach.
• Lead-in: a mutual action plan exists with named owners on both sides for every remaining step, so no step is blocked on one person's calendar.

🔄 The Champion Departure Save Flow

2.2 The 4 Conversations Reps Avoid

The SAVE motion fails not because reps do not understand it but because each stage contains a conversation reps would rather not have. Naming the four conversations explicitly turns avoidance into a checklist.

Conversation 1 — Calling the departing champion directly. Reps feel it is intrusive. It is the opposite: a champion who liked you wants the project to survive and is usually happy to make one introduction on their way out. Skipping this call forfeits the single highest-value asset you have.

The departing champion is the only person on earth who can tell you both who inherits the project *and* how to frame it for them.

Conversation 2 — Admitting to the new owner that you have to re-earn the deal. Reps want to act as if the deal is still 90% done. The new owner can smell that. Naming it — "I know this landed on your desk; I would like 20 minutes to make sure it still makes sense for you" — builds more trust than pretending.

The new owner has no sunk-cost attachment to the deal; pretending they do is the fastest way to lose them.

Conversation 3 — Telling your own manager the deal is now at risk. Reps leave the forecast untouched and hope. That converts a recoverable save into a blown-quarter surprise. The deal should move to a risk category the day the champion leaves.

A manager who hears "champion left, here is my SAVE plan" in week one can help; a manager who hears "the deal slipped" in week twelve cannot.

Conversation 4 — Deciding to walk. If after SCOPE there is no owner, no budget, and no inherited pain, the honest move is to disqualify, not to keep emailing a headless account for two more quarters. This is the conversation that feeds directly into the Counter-Case.

2.3 The Stakeholder Re-Map Drill

Each rep takes one open deal and lists, on paper, every contact, their role (economic buyer / champion / coach / blocker / user), and their current temperature. Any deal with only one warm name is flagged. The test: *if this person left tomorrow, who picks up the phone?*

This drill is intentionally low-tech — paper, not CRM — because the goal is the realization, not the data entry. Reps almost always discover that a deal they considered healthy is in fact threaded through exactly one person. That moment of recognition is the entire purpose of the teach.

2.4 The Three Departure Variants — One Motion, Three Clocks

Reps treat "champion departure" as one event. It is really three, and each runs the same SAVE motion against a different clock and a different emotional reality.

Lead-in: the resignation variant is the cleanest to detect and the most time-pressured. The champion is gone, the goodwill window is ticking, and STABILIZE must happen fast. The companion entry for the softer reassignment case is (q70).

Lead-in: the reorg variant is the most deceptive, because your champion still answers the phone — they just no longer have any authority over your project. Reps waste weeks selling to a person who structurally cannot buy. SCOPE is the cure: it forces you to confirm *current* mandate, not historical relationship.

Lead-in: the promotion variant is the one reps over-celebrate. Discussion prompt 6 covers it directly, and (q1152) is the deep-dive. A promoted champion *can* be your best asset — sponsoring you from a more senior seat — but only if you confirm it.

A champion promoted into a role with new priorities may quietly let your project lapse, not out of malice but because it is no longer their problem.

🎯 Bottom Line

SENSE early, STABILIZE in 48 hours, SCOPE the new map, SELL-AGAIN to the new owner, SECURE against the next departure. The save is speed plus the right two questions.

SECTION 2.5 -- THE COUNTER-CASE: WHEN THE SAVE IS THE WRONG MOVE

🟡 Coach Note

Spend 4-5 minutes here, between the Teach and the Discussion. The 5-stage SAVE motion is the default — but a default is not a law. The most expensive mistake in this training is not failing to save a deal; it is *successfully* saving a deal that should have died, and carrying it through three more quarters of forecast.

2.5.1 The Honest Objection

A champion departure is sometimes information, not an accident. Reps are trained to treat the departure as a logistics problem — a relay baton dropped, pick it back up. But sometimes the champion left *because* the project was already dead internally and they could see it. Sometimes the champion was the only person who ever wanted your product, and their departure is the organization quietly correcting a mistake.

Running a heroic SAVE motion on that deal does not rescue revenue; it manufactures a zombie in your pipeline.

A zombie deal is uniquely expensive because it costs twice: once in the forecast — it inflates commit and then collapses it, damaging your credibility with your own manager — and once in opportunity cost, because every hour spent reanimating it is an hour stolen from a deal that could actually close.

2.5.2 Three Cases Where You Should NOT Run The Full Save

Case 1 — The champion was a "Talker," not a "Mobilizer." Per The Challenger Customer, a pleasant, responsive contact with no organizational pull is not a champion at all — they are a talker. If your only "champion" never produced a second meeting, never got you budget confirmation, and never named the economic buyer, then their departure changes very little, because the deal never had a real spine.

Do not spend two weeks of SAVE energy reconstructing a relationship that was decorative. Re-qualify from zero or disqualify.

Case 2 — The departure coincides with a strategy or budget reset. If the champion left as part of a reorg, a reduction in force, a leadership change, or a budget freeze, the project's sponsor may not have left — the project's *funding* did. No save motion recovers a deauthorized budget.

The correct move is to re-qualify the timeline honestly, move the deal out of commit, and re-engage when the new structure settles, which may be one or two quarters out.

Case 3 — The math no longer works. A save is justified when the recovered deal still clears your opportunity cost. If saving a $40K renewal will take 25 hours of re-discovery, re-proving value, and re-threading across a skeptical new team, and you have a $200K new-logo deal starving for that same time, the save is the wrong allocation even if it is winnable.

Winning by Design's framing is useful here: protect *recurring impact*, but not at a cost that destroys your overall number.

2.5.3 The Counter-Case Test

⚖️ The Counter-Case Test

Before committing to a full SAVE, answer three questions out loud: (1) Was the departed champion a real champion — did they ever sell for me when I was not in the room? (2) Is the budget still authorized, or did it leave with the person? (3) Does the recovered deal still beat the next-best use of these hours? Two or more "no" answers means the disciplined move is to disqualify or defer — not to save.

The save motion is a scalpel, not a reflex. A rep who can articulate *why they chose not to save a deal* is operating at a higher level than one who saves everything.

What this does not mean. This is not permission to give up the moment a deal gets hard. The Counter-Case is a deliberate, evidence-based checkpoint — run SCOPE first, gather the facts, *then* decide. The failure mode the Counter-Case guards against is not effort; it is misallocated effort and a forecast full of deals nobody at the account actually owns.

The order is fixed: SENSE, STABILIZE, SCOPE — *then* the Counter-Case test — and only then SELL-AGAIN. You never disqualify before you have the SCOPE facts in hand.

2.5.4 The Cost Of A Zombie — Why This Section Pays For Itself

It is worth being precise about why a wrongly-saved deal is so expensive, because reps under-rate it. A zombie deal damages a rep in three separate places:

• Lead-in: forecast credibility. A zombie sits in commit, inflates the rep's number, and then collapses at quarter-end. The second time a manager sees this from the same rep, every future commit from that rep is discounted. Forecast trust, once spent, is slow to rebuild.
• Lead-in: opportunity cost. Every hour spent reanimating a dead deal is an hour stolen from a live one. A rep with 25 hours invested in a $40K zombie has, in effect, chosen not to invest those hours in a deal that could have closed. The zombie's true cost is not $0 — it is the value of the deal that starved.
• Lead-in: morale and momentum. Working a deal that everyone privately knows is dead is corrosive. It teaches the rep that activity and progress are the same thing. They are not. A clean disqualification frees the rep to do work that compounds.

Per Winning by Design's emphasis on protecting *recurring impact*, the discipline is to spend your finite hours where they generate durable revenue — and a zombie, by definition, generates none. The Counter-Case is not pessimism. It is portfolio management applied to your own calendar.

🟢 The Disqualification Script

Reps need a way to disqualify cleanly that does not feel like failure. Here is the language: *"I've looked at this honestly since [champion] left. Right now there is no clear owner, the budget went with the reorg, and I don't want to waste your time or mine pretending otherwise.

I'd like to close this opportunity out for now and circle back next quarter once the new structure settles — if the problem still matters then, we'll pick it back up."* This script protects the relationship, corrects the forecast, and leaves a clean door open. It is a *good* outcome, and the manager should treat it as one.

SECTION 3 -- THE DISCUSSION (0:35-0:45)

🟡 Coach Note

8 prompts. Reps audit their own open deals out loud. Count to five after each — the silence is where the honest answers come from.

1 — "How late did you find out, last time?" Most reps admit one to three weeks. Manager: *"Late detection is the whole loss. Build the signal into your weekly review."*

2 — "Who do you call first?" The departing champion, on their cell, within 48 hours. Manager: *"Their goodwill expires fast — the 10-14 day window is real. Use it."*

3 — "When do you tell me the deal is at risk?" The same day. Manager: *"A surprise in week 12 is worse than honesty in week 1."*

4 — "When do you walk?" No owner, no budget, no inherited pain after SCOPE — run the Counter-Case test. Manager: *"Disqualifying is not failing. Emailing a headless account for two quarters is."*

5 — "Renewal champion left — different?" Yes — clock is the renewal date, and the new contact often does not know the value story at all. Manager: *"Re-prove impact before you re-quote."*

6 — "What if the champion was promoted internally?" Often the best case — they may still sponsor you from a higher seat, but confirm it, do not assume it.

7 — "How many threads is enough?" Three engaged contacts minimum on any deal above your team's threshold. Manager: *"One is a single point of failure. Two is fragile. Three survives a departure."*

8 — "One open deal to re-thread this week?" Each rep names one. Manager: *"CRM task, due Friday."*

💬 Facilitation Note

The discipline in this block is the manager's, not the room's. The temptation is to answer your own prompt to fill the silence. Do not.

Prompt 1 in particular almost always produces a defensive first answer ("I caught it pretty fast") that, after five seconds of silence, becomes the real answer ("...actually it was three weeks"). The five-second count is the technique.

3.1 The Three Audit Questions Reps Should Take Back To Their Pipeline

The eight prompts above are the in-room version. The portable version — the three questions a rep should run against every open deal in their pipeline after this training — is shorter:

The point of porting the discussion into a three-question audit is repeatability. The training happens once; the audit happens every week, in the rep's own pipeline review prep, for as long as they sell. A manager who hears these three questions answered crisply in a one-on-one knows the training took.

3.2 Detection Mechanics — Building SENSE Into The CRM

The most common failure in the whole motion is late detection, and the most durable fix is structural, not behavioral. You cannot rely on a rep "remembering to watch" — you build the watching into the system.

• Lead-in: a last-contact-date field. Every deal shows the date of the last two-way interaction with each named contact. A contact whose last-contact date crosses a threshold flags automatically. This converts SENSE from a vigilance task into a report.
• Lead-in: an engaged-contact count as a required field. A deal cannot advance a stage without a number in this field. A "1" triggers a single-threaded flag visible to the manager. The system, not the rep, enforces multi-threading.
• Lead-in: a LinkedIn-change check in weekly review. A two-minute scan of key champions' profiles before pipeline review catches departures days earlier than waiting for a bounce.
• Lead-in: a calendar-decline alert. A declined recurring meeting from a champion is a leading indicator. Treating it as a SENSE trigger, not an administrative annoyance, buys days of response time.

The principle: a rep's attention is a scarce, unreliable resource. Wherever possible, move detection out of the rep's head and into a field, a flag, or a report.

SECTION 4 -- TWO-PERSON ROLE-PLAY (0:45-1:05)

🟡 Coach Note

Pairs. Two scenarios, 10 minutes each, 60-second reset between. The rep runs the SAVE motion out loud; the partner plays the prospect and uses the scripted deflection at the marked minute.

4.1 Role-Play 1 — New-Logo Deal, VP Sponsor Just Left

Setup: A $110K new-logo deal at "verbal yes." The champion, a VP of Operations, resigned Friday. The rep, Priya, has notes mentioning a Director of IT and the VP's manager (a COO). Run SENSE → STABILIZE → SCOPE → SELL-AGAIN → SECURE — and apply the Counter-Case test before committing.

🎤 PROSPECT -- the COO (the departed VP's manager)

Busy, mildly aware the project exists, no emotional ownership. Deflection (min 5): *"Honestly, that was Dana's initiative. I'm not sure we're moving forward on it right now."*

🎤 REP -- Priya

• STABILIZE: Calls departed VP first: *"Before you go — who should own this, and what should I tell them?"*
• SCOPE + SELL-AGAIN: To the COO: *"Dana brought us in to fix [specific operational problem costing X]. I am not asking you to honor a prior decision — I am asking whether that problem still matters to you. If it does, 20 minutes. If not, I will close this out cleanly."*
• SECURE: Gets the Director of IT into the next meeting; sends a one-page value recap to both.

What good looks like: Priya does not argue with the COO's deflection. She agrees with its premise — yes, this was Dana's initiative — and reframes around the *problem*, not the *prior decision*. She offers the COO an easy exit ("I will close this out cleanly"), which paradoxically makes the COO more willing to stay engaged, because the rep is not trapping them.

60-Second Reset

4.2 Role-Play 2 — Renewal, the Only Contact Was the Departing Admin

Setup: A $40K annual renewal due in 45 days. The only account contact, an operations admin who handled the tool day-to-day, has left. No one else has ever spoken to the vendor. The rep, Sam, must find an owner and re-prove value before the auto-renewal date — and decide, honestly, whether this is a save or a Counter-Case.

🎤 PROSPECT -- new operations manager

Inherited the tool, does not know why it was bought, sees a renewal invoice and is skeptical. Deflection (min 6): *"I see we pay you $40K a year. I genuinely don't know what this does for us. Why wouldn't I cut it?"*

🎤 REP -- Sam

Re-proves recurring impact with usage data and the original business case, names a new internal owner, and proposes a 30-minute value review before the renewal date — not a re-quote first.

What good looks like: Sam treats "why wouldn't I cut it" as a fair question, not an attack. He answers it with evidence — usage data, the original business case — rather than urgency. Critically, Sam also runs the Counter-Case test out loud at the end: if the usage data is thin and no one has the pain, the disciplined call is to surface that to his manager, not to discount his way to a renewal that should not happen.

🟡 Coach Note

Watch for: rep pretending the deal is still done; rep skipping the call to the departing contact; rep re-quoting before re-proving value; rep failing to run the Counter-Case test and committing to a save that does not clear opportunity cost; rep blasting the account with panic emails instead of two precise STABILIZE touches.

SECTION 5 -- DEBRIEF + COMMITMENTS (1:05-1:10)

🟡 Coach Note

Three debrief questions, then commitments in the CRM. Commitments that are not written into the CRM in the room do not happen.

Debrief 1 — "Which stage did you skip?" Most skip SELL-AGAIN. Manager: *"Skipping SELL-AGAIN means you are forecasting a deal the current owner never agreed to."*

Debrief 2 — "Which conversation did you avoid?" Usually calling the departing champion. Manager: *"That call is free and it is the highest-leverage thing you can do."*

Debrief 3 — "Which open deal is single-threaded right now?" Each rep names one. Manager: *"Re-thread it this week."*

🎤 Commitment Ritual

Open the CRM. Three lines: (1) one open deal that is single-threaded today; (2) the next contact you will add to it; (3) one deal where a champion already left that you will re-run SAVE on — or run the Counter-Case test and disqualify. Read aloud.

The reading-aloud is not theatre. A commitment spoken to the room is socially load-bearing in a way a private CRM note is not. The manager's job in the following week is to reference these three lines by name in the next one-on-one — which is what converts a training into a behavior change.

SECTION 6 -- LEAVE-BEHIND (1:10-1:13)

📋 Leave-Behind -- The Champion Departure Save Card

THE 5-STAGE SAVE MOTION: (1) SENSE — name three engaged contacts per deal; one warm name = departure-risk now. (2) STABILIZE — within 48 hours, call the departing champion and ask who inherits the project; do not blast the account. (3) SCOPE — re-map the buying group as it is today: owner, budget, pain, coach.

(4) SELL-AGAIN — re-run compressed discovery with the new owner; never say "your predecessor agreed." (5) SECURE — multi-thread to three, get the value narrative in writing, confirm the new champion's personal win.

THE 4 AVOIDED CONVERSATIONS: call the departing champion directly; admit to the new owner you must re-earn the deal; tell your manager the deal is at risk the same day; decide to walk if there is no owner, no budget, no pain.

THE COUNTER-CASE TEST: before committing to a full save, ask — was this a real champion or a talker? is the budget still authorized? does the recovered deal beat the next-best use of these hours? Two "no" answers = disqualify or defer.

THE NUMBERS: 6-10 buyers per group (Gartner). ~25-35% contact turnover per 12-18 months (directional). 48-hour STABILIZE rule. 10-14 day goodwill window (heuristic). 3 engaged contacts minimum.

NEVER DO: email a dead thread and wait; pretend the deal is still 90% done; leave the forecast untouched after a champion leaves; re-quote a renewal before re-proving value; rely on a single contact; save a zombie deal that fails the Counter-Case test.

🎯 If You Only Remember One Thing

The deal does not die when the champion leaves — it dies when you find out late and ask the wrong person to fill the gap. Move in 48 hours, ask "who inherits this," and re-sell the new owner as if it were day one. But run the Counter-Case test first: the save motion is a scalpel, not a reflex.

THE MANAGER SCORECARD -- COACHING THE SAVE AFTER THE MEETING

🟡 Coach Note

The training installs the motion; the scorecard sustains it. Use this in weekly pipeline review and one-on-ones for the four weeks following the session.

A 60-minute training changes behavior for about a week unless the manager reinforces it. The mechanism is a small set of questions asked consistently in pipeline review until they become reflexive.

6.1 The Two Manager Anti-Patterns

Anti-pattern 1 — rewarding the heroic save. If the only champion-departure deal that gets celebrated is the dramatic last-minute rescue, the team learns that the *save* is the prize. It is not. The prize is the deal that never needed saving because it was multi-threaded from the start.

Celebrate the boring three-threaded deal more loudly than the heroic one-threaded rescue.

Anti-pattern 2 — punishing the disciplined disqualification. If a rep runs the Counter-Case test, concludes honestly that a deal is a zombie, and disqualifies it — and then gets treated as though they "lost" a deal — you have just taught the entire team to never run the Counter-Case again.

A clean, well-reasoned disqualification is a *good outcome*. Score it as one.

🔁 The Save-To-Prevention Loop

The loop is the point. Every champion-departure save, run correctly, should reduce the number of single-threaded deals that *create* the next departure crisis. A team that runs this well sees the frequency of emergency saves decline over two or three quarters — not because departures stopped, but because the deals were built to survive them.

RELATED PULSE Q&A -- CROSS-LINKS FOR DEEPER PREP

This training is the runnable 60-minute meeting on champion departure. The Pulse RevOps library has tightly related single-question entries the manager can assign as pre-reads or pull into the Discussion block:

• Lead-in: the closest companion to this training — (q70) "What's the right play when the champion gets reassigned mid-deal?" Reassignment is a softer variant of departure — the champion is still in the building but no longer on your project. Use it to brief reps before the SENSE and SCOPE stages.
• Lead-in: the internal-promotion case from Discussion prompt 6 — (q1152) "What's the right way to recover a deal where your champion got promoted out of the buying role mid-cycle?" Often the best-case departure, but only if you confirm continued sponsorship rather than assume it — pair this with the SELL-AGAIN stage.
• Lead-in: the prevention side of this training — (q183) "What's the right way to multithread a deal with a single champion?" The SECURE stage exists to make the next departure a non-event; q183 is the deeper how-to on building the second and third thread before you ever need them.
• Lead-in: the engine behind the Counter-Case — (q62) "When does a 'champion' actually become a champion vs a contact?" If you cannot tell a champion from a contact, you cannot tell a real departure from a non-event — assign this before teaching Section 2.5.
• Lead-in: the RevOps and manager lens — (q38) "How do you forecast when half the pipeline is single-threaded?" Champion departure is a forecasting problem as much as a selling problem; this entry connects the SAVE motion to commit-category discipline.
• Lead-in: the detection-and-escalation companion — (q330) "A champion keeps slipping the demo (slip-then-slip) — how do we know when to move to a new contact or escalate around them?" The companion to the SENSE stage — when a champion is going quiet but has not formally left.
• Lead-in: the budget-reset Counter-Case in concrete form — (q249) "A buyer whose champion just got hit with a hiring freeze and lost their team expansion budget." This is Counter-Case Case 2 made concrete — use it to teach the difference between a sponsor leaving and a budget leaving.
• Lead-in: the adjacent dark-deal play — (q47) "Recover a mid-stage deal that's gone dark for 3 weeks." The adjacent motion when the silence is not a confirmed departure yet — useful to contrast with SENSE, where the departure is confirmed.

HOW THIS SITS INSIDE YOUR OPERATING MOTION

Weekly pipeline review — every deal must show three engaged contacts or get flagged single-threaded. Day of departure — deal moves to a risk category, manager notified. 48-hour rule — departing champion is called within two business days.

Stakeholder map — refreshed on every at-risk deal before the next outbound touch. Counter-Case checkpoint — before re-committing a saved deal to forecast, the rep confirms it passes the three-question test. Monthly — the manager reviews single-threaded percentage as a leading indicator; a falling number is the real proof the training landed.

This training is not a one-time event. It is the installation of a default — *multi-thread by default* — that every subsequent pipeline review reinforces. The SAVE motion handles the crisis you have today; the operating motion ensures you have fewer of them next quarter.

📊 Sources Referenced In This Training

Gartner B2B Buying research (buying-group size and stakeholder turnover); The Challenger Customer — Brent Adamson, Matthew Dixon, Pat Spenner, Nick Toman, CEB / Gartner (Talker vs Mobilizer); MEDDIC / MEDDPICC methodology — originated by Jack Napoli and Dick Dunkel at PTC (NASDAQ: PTC), taught today by MEDDICC Ltd / Andy Whyte (Champion as a stage gate); CSO Insights, now part of Korn Ferry (NYSE: KFY) — sales-cycle and win-rate benchmarking; RAIN Group — multi-threaded win-rate research; Force Management — Command of the Message (validation discipline); Winning by Design — Jacco van der Kooij, the bowtie / recurring-impact model; U.S.

Bureau of Labor Statistics — JOLTS quits series (macro turnover backdrop). All directional benchmarks are labeled as ranges; all practitioner heuristics (the 10-14 day goodwill window, the rule of three) are labeled as coaching rules, not audited statistics.