CHURN IS DEAD
Your Champion Left. A New Contact Won't Replace Them.
7 min read · Customer Leadership
Your champion leaves. A new contact accepts the meeting. The account plan still says the rollout is on track.
Before treating that introduction as a recovery, ask what the departing person actually made possible.
Maybe they could get a team to change its workflow. Maybe they could settle a disagreement, find budget or tell you when the internal story was wrong. A friendly replacement may do none of those things.
A new contact restores a conversation. It does not, by itself, restore the customer's ability to carry out the plan.
That is the distinction to test before keeping the same milestone, expansion request or renewal assumption. It does not mean every departure puts an account in danger. It means the old evidence needs a check.
Find the work that left with the person
Start with a live commitment rather than an empty box in the contact map. What is the customer trying to get done next, and what did this person contribute to making it happen?
Take a planned rollout into another department. The departing champion may have arranged training, persuaded managers to release staff time and brought the right technical person into the conversation. Those are different contributions. One replacement does not have to inherit all of them, and the next person on the organisation chart may inherit none.
Write the missing contribution as a verb: approves the team's time, resolves the integration question, confirms the business goal, or explains the proposal to the person funding it. A job title alone cannot tell you whether that contribution is covered.
Do not build a large stakeholder exercise for every staffing change. Choose the nearest consequential commitment. If it can still happen with the people and authority already in place, the departure may require a straightforward handover. If it cannot, that is the gap to work on.
Separate willingness, knowledge and authority
A willing contact is useful. So is someone who knows how the product works. Neither fact establishes that they can approve the next step.
Microsoft's Dynamics 365 guidance distinguishes champions, end users, economic buyers and other stakeholder roles. That is guidance for recording a sales opportunity, not proof that a particular relationship model prevents churn. Its useful reminder here is that being involved in an account is different from having a specific role in its decisions.
Ask three practical questions about the next commitment:
- Who understands the work well enough to say whether the plan is usable?
- Who is willing to help it move through the customer organisation?
- Who can approve the time, money or change it requires?
One person can cover several of these. Several people can share the work. The point is to know which arrangement exists, rather than mark someone as the new champion because they answered an email.
Recheck the goal before retelling the success story
An introduction is a chance to learn what still matters. It should not require the new contact to endorse a business case they did not help build.
Bring a short account of what was agreed, what has actually happened and what remains open. Label the difference between an observed result and a goal that has not yet been reached. Then ask whether the next milestone still serves a current customer priority.
GitLab's public Customer Success handbook describes success plans as mutually agreed plans connecting outcomes, milestones, timelines and responsible people. That is one company's operating practice. It supports keeping those parts connected; it does not supply a universal checklist or a renewal prediction.
After a departure, review the connections. A milestone can remain technically possible while the customer no longer has a team assigned to use the result. An executive can still support the goal while the delivery owner has changed. A contact can remain enthusiastic while their manager has a different priority.
Record what the current people confirm. Keep old agreements as history, with their dates. Do not quietly convert them into new commitments.
Give the new contact a manageable request
“Can you be our champion?” asks someone to accept an unclear job. A smaller request is easier to understand and gives you better evidence.
For example: “The next step needs the operations team to test the export. Is that still useful, and who can agree the time for it?” The answer might identify an owner, change the task or reveal that the goal is no longer active. All three are useful information.
Avoid making the customer repeat every conversation. Offer the existing notes and a concise explanation of the open decision. Ask them to correct what is outdated. Keep private account information in the approved customer record, and share it only with people who should have access.
If they cannot make an introduction or commit resources, accept the boundary. The response is not necessarily low engagement. They may be helping as much as their role allows. Work with the account's commercial and delivery owners to reach the person who can decide, without asking the new contact to promise on someone else's behalf.
Decide what can continue
Use one short review to choose between continuing the next commitment, changing it, or holding a specific request until a decision is possible. These are editorial proposals, not a scoring model.
Continue when the goal still matters, the next task has an accepted owner and the required authority is available. Keep the plan, update the people and confirm the next date.
Change the plan when the goal survives but the route does not. Perhaps a smaller group can test the workflow while a new sponsor is appointed. Agree the smaller step with the customer; do not describe the original rollout as unchanged.
Hold the affected request when nobody can approve the resources, confirm the priority or accept the commitment. Name exactly what is waiting and who can resolve it. This is not a reason to stop unrelated support or working parts of the service.
For example, Microsoft's Power Platform sponsorship guidance assigns sponsors activities that include prioritising resources, approving funding and making decisions. It also recommends identifying a backup sponsor. That is product-adoption guidance, not a requirement to find a C-level buyer for every account. Use the authority the particular commitment needs.
A contact can be present while the decision is missing
Imagine a customer preparing to roll a reporting workflow into a second department. Its champion leaves before the trial. The replacement contact knows the product and is happy to meet. Nobody has yet agreed to give the second team time to test it.
This is a fictional example, not a customer story or a claimed result.
The weak update is “New champion engaged; rollout remains on track.” It turns a meeting into evidence of a commitment that has not been made.
A more useful update is: “The original goal is still supported by the operations lead. The next team's manager has not agreed test time. The contact will help arrange that conversation. Until the manager decides, the second-department trial date is unconfirmed.”
That does not label the contact as a problem. It identifies the missing decision. The next conversation can then address the actual constraint instead of adding another general product update.
If the manager agrees the time and a named person accepts the test, continue. If they want a different workflow, revise the trial. If nobody can confirm the priority, hold that rollout assumption and review the commercial implications with the appropriate account owner.
Run the check on one commitment
Use the Champion Change Check with the account team and the relevant customer contact. Keep it beside the existing plan rather than creating another account dashboard.
Write down the next commitment, what the departing person enabled, what is still covered, and what needs confirmation. Name the person who can make the missing decision and the next date. Choose what continues, what changes and what waits.
Do not turn this into a demand that every customer provide several senior contacts. A small customer may have one person wearing several hats. Nor does a departure justify an automatic forecast downgrade. Follow the account's evidence and commercial review rules; do not invent a probability from a job change.
The check cannot promise a renewal. It can stop a more basic mistake: treating an updated contact list as proof that an old plan still has the people behind it.
Recover the ability to do the work, then update the plan.
Sources and methodology
Sources checked 4 November 2026. The commitment check, worksheet and continue/change/hold choices are original editorial proposals. The reporting-rollout example is fictional. No measured effect on churn, revenue or renewal probability is claimed.
By Kuber Sethi · All issues · Subscribe