What to Do the Week Your Champion Leaves

Most teams learn about a champion departure by accident, a bounced email, a LinkedIn update, or a renewal call that goes strangely quiet. Build a lighter weight detection habit instead: check engagement patterns for a sudden drop from a key contact, and have your CSMs ask, as a routine part of every check in, whether anything has changed on their team. Waiting for a formal signal like a renewal conversation to reveal a departure that happened months earlier means you are starting the recovery process far later than you needed to. By the time a renewal call surfaces it, the account has often already quietly decided how the relationship is going to go, and you are negotiating from behind instead of getting ahead of it.

The person who inherits a departed champion's responsibilities usually does not share their predecessor's history with your product, and often was not part of the original buying decision at all. Treat the first conversation with them less like a check in and more like a compressed re-onboarding: what problem the tool solves for their team, what has been achieved so far, and why it is worth their continued attention. Assuming they already understand the value because their predecessor did is the single most common mistake in this situation.

The best defense against champion turnover is never having a single point of contact in the first place. During onboarding and every QBR after, actively work to identify and build a relationship with at least one additional stakeholder, even a lighter touch one, who understands enough about the value delivered to speak up if the primary champion ever leaves. Accounts with two engaged stakeholders survive a departure far more often than accounts with one, simply because someone remains who remembers why the tool matters. This does not need to be a heavy lift: a shared dashboard invite, a second person copied on renewal correspondence, or a brief introduction during a QBR is often enough to plant that redundancy without adding real overhead to the relationship.

For example, if the only person who ever logs in is your champion, a shared dashboard invite for a colleague or a second person copied on renewal emails costs almost nothing. A common mistake is asking the champion for an introduction only after they give notice, when they are distracted and the request feels awkward. Make the ask during a QBR while things are calm, and frame it as making sure their team benefits from the work they set up. The decision rule: if you cannot name a second person who could explain why the tool matters, treat the account as exposed.

It is tempting to let a quiet transition stay quiet, hoping the new contact reaches out when they are ready. That instinct usually costs time you do not have. Reach out proactively within a week of learning about the departure, acknowledge the transition directly, and offer a short call to get the new contact up to speed on their own terms. A direct, low pressure outreach signals that the relationship matters to you beyond the person who happened to sign the contract, which is exactly the impression you want to leave with someone deciding whether to keep paying for a tool they did not choose themselves.

Use this sequence after you learn about a departure:

1. Confirm the change by checking for a sudden drop in engagement from the key contact and asking your CSM what they have heard.
2. Reach out to the new contact within a week, and acknowledge the transition directly instead of waiting for them to call.
3. Offer a short call that works like a compressed re-onboarding: what problem the tool solves for their team and what has been achieved so far.
4. Identify at least one additional stakeholder who understands the value, so the account no longer rests on a single person.

Not every account carries the same risk here. Build a simple flag for accounts where engagement concentrates almost entirely in one person's activity, with no secondary contact showing up in usage or communication data at all. Those accounts deserve a proactive multi stakeholder push well before any departure, since the cost of building that redundancy in advance is far lower than the cost of a rushed recovery after the fact.