What to Do When Your Champion Leaves During Onboarding

Your champion is the person on the customer side who pushed to buy your product, ran the internal evaluation, and owns making it succeed. When that person resigns three weeks into implementation, you lose your advocate, your context source, and usually your only working relationship at the account, all at once.

The data says this is the moment accounts are won or lost: champion departure raises 12-month churn odds to 51%, and a response inside 48 hours measurably cuts that risk. This playbook covers the first 48 hours, how to brief a replacement without restarting the project, when to move the go-live date, and how to stop a single resignation from ever having this much power again.

How much does churn risk increase when a champion leaves?

A lot. Analysis presented by Sturdy at the BIG RYG customer success conference found that when a customer champion leaves, there is a 51% chance the account churns within the next 12 months. When the departing contact is an executive, it gets worse: 65% of accounts with an executive change will not renew a SaaS contract. Sturdy's team called the unmanaged key contact change the single greatest leading predictor of churn.

Speed changes the outcome. The same research found that when customer success teams act on an executive change signal within the first 48 hours, the customer is 33% more likely to renew.

That last row deserves attention: ChurnZero's internal research found only about half of customer success organizations have a documented play for a key contact change. Most teams improvise the most predictable churn event in the book.

Why is a champion departure worse during onboarding than after go-live?

Because during onboarding, almost all of the value the customer has received is still promised value. After go-live you have live workflows, trained users, and usage data making your case. Mid-implementation you have a project plan, a half-finished data migration, and one person who understood why any of it mattered. OnRamp's roundup of onboarding research puts up to 67% of churn inside the onboarding window, and that is with champions who stay.

Three things make the mid-onboarding version of this event uniquely dangerous:

• The knowledge is undocumented. Requirements were explained on calls. Exceptions were agreed in Slack DMs. The reasoning behind the rollout order lives in your champion's head. None of it has been operationalized yet.
• The relationship is single-threaded by default. Early in a project, the champion often is the relationship. Other stakeholders attended a kickoff call once. In OnRamp's 2026 survey of 161 CS and onboarding leaders, 62% said they lack visibility into onboarding progress; when the one person who had visibility exits, projects stall silently.
• The successor has switching incentives. As SaaStr's Jason Lemkin puts it, if the new stakeholder used a competitor at their last company, they will almost immediately think about swapping you out. They never chose you, and mid-implementation is the cheapest possible moment to reverse the decision.

A stalled project with a missing champion looks a lot like a customer going dark, and the response overlaps. If you are getting silence rather than a resignation notice, start with our playbook for when a customer goes dark during onboarding.

What should you do in the first 48 hours?

Move fast and stay administrative. Your goals are a named successor, a complete inventory of what the champion held, and visible project momentum. Selling comes later.

1. Confirm the departure and ask for the successor. If the champion gave notice, get 30 minutes before their last day. Ask who inherits the project, ask for a warm intro in writing, and ask what the successor will care about. If there is no named successor, ask your executive sponsor who owns the project now.
2. Inventory everything the champion held. Pending approvals, system credentials and admin access, action items assigned to them, decisions only they knew the rationale for, and any meeting they anchored. Every one of these needs a new owner within the week.
3. Send the successor a trust-first note. Congratulate them, offer a short walkthrough of where the project stands, and stop there. Every vendor they inherited is emailing them a pitch this week; the one that shows up with an organized project state and zero pressure reads differently. This is the move the 48-hour renewal data rewards.
4. Brief your own side. Flag the account as at-risk in whatever health tracking you run, tell your exec sponsor a champion change is in progress, and tighten your status cadence. If the account is large, this is when your leadership should offer the customer's leadership a touchpoint.
5. Keep the workstreams moving. The migration, the integration build, the scheduled training sessions: all of it continues. Visible momentum is the strongest argument that the project deserves to survive its sponsor change.

How do you brief a replacement without restarting the project?

Hand them a project state package they can absorb in 30 minutes, then run a 45-minute re-kickoff. The goal is for the successor to inherit the project's decisions rather than re-litigate them, and the way you earn that is by showing where each decision came from.

The package should contain five things:

• Goals and success metrics as defined at the start, ideally traced back to the sales-to-onboarding handoff so the successor sees what their own company said it was buying.
• A decision log with sources. Every significant decision, who made it, and a link to the call or message where it happened. This is what makes "that was already decided" a fact rather than a claim; see our guide to tracking decisions in customer Slack channels.
• The current plan against original dates, in the same format as your onboarding plan, with slippage shown honestly.
• Open action items by owner, flagging everything that belonged to the departed champion and needs reassignment.
• The top three risks and what you are doing about each. The champion change itself should be risk number one.

For the re-kickoff meeting, the strongest format is the one Ali Cudby of Alignmint Growth Strategies teaches: "you, we, me". Start with the successor's role and goals, then frame the project in the words they just used, and end with the single thing you need from them. Expect goal drift: successors frequently carry different priorities than the person who bought. Validate the success criteria explicitly and record any changes as new decisions, because a quiet goal change discovered at go-live is far more expensive than one surfaced in week one.

Should you move the go-live date?

Usually yes, and you should do it openly. A day-to-day champion change typically costs one to three weeks of timeline; an executive sponsor change can cost more, because approvals and budget questions reopen. A re-baselined date with a stated reason keeps trust; a silent slip spends it. Update the plan, tell your sponsor the new date and why, and tighten your status update cadence so nobody wonders whether the project lost its driver.

Set an escalation clock at the same time. If no successor is named within two weeks, take a paused-clock proposal to the economic buyer: here is what is done, here is what is blocked waiting on an owner, here is the restart plan the day one exists. That framing makes the cost of the vacancy their problem to solve rather than your timeline to absorb.

How do you prevent single-threading before it happens?

Assume every contact you have will change jobs during the life of the account, because on average they will. UserGems' analysis puts about 20% of CRM contacts changing jobs every year, and U.S. Bureau of Labor Statistics data shows median employee tenure fell to 3.9 years, with workers aged 25 to 34, the age band of many day-to-day project owners, at just 2.7 years. Over a 90-day implementation plus a 12-month contract, stakeholder turnover is the expected case.

Prevention is cheap and mostly procedural:

• Apply a rule of three from kickoff. An executive sponsor, a day-to-day owner, and a technical owner, all present at kickoff and all on the project channel. The buying committee that approved the purchase had 6 to 12 people in it, so the names already exist in the sales record; pull them through the handoff instead of letting the relationship collapse to one thread.
• Write the champion-departure play down. Only about half of CS organizations have one, which means having one at all is a competitive edge. Five steps and a note template are enough.
• Watch for the signal. LinkedIn changes, out-of-office replies that name a different person, a champion who stops responding in a channel that used to be active. Departure risk usually announces itself before the announcement.
• Document decisions where the team works, as they happen. A record built during the project costs minutes; a reconstruction after a departure costs weeks.

Project knowledge should outlive any single stakeholder

The lasting damage from a champion departure is rarely the relationship. It is the knowledge that leaves with them: the requirement explained once on a call in week two, the exception agreed in a DM, the reason phase two was sequenced before phase three. If that context lives in a shared record, a departure costs you a meeting. If it lives in one person's memory, it costs you a month of re-discovery, and some of it never comes back.

The habits that protect you are the same ones that make projects run well anyway: one channel for project communication instead of scattered DMs, meeting notes that highlight decisions and owners, and a written weekly status even when you also gave it verbally.

This is the problem Stipulate works on. It reads your customer Slack channels and call transcripts and maintains an evidence-linked record of every decision, commitment, risk, and stakeholder, each tied to its source message. When a champion leaves, their context stays in the record, and the successor gets briefed from cited evidence instead of recollections.

Next steps

If a champion just left one of your accounts, run the 48-hour list today: confirm the successor, inventory what the champion held, send the trust-first note, brief your sponsor, and keep the workstreams visibly moving. Then build the project state package and book the re-kickoff before the end of the week.

If it has not happened to you this quarter, it is scheduled to. Do four things while it is cheap:

1. List every active onboarding with a single point of contact. Each one is carrying a 51% risk you have not priced in.
2. Add the rule of three to your kickoff template so multithreading is structural rather than heroic.
3. Write the five-step departure play and put the successor note template next to it.
4. Move decision and commitment records into a shared system during the project, so the next departure costs a meeting instead of a month.