The Account Didn’t Churn. Your Champion Left.

You have seen this shape before. Usage is fine. The last survey came back positive. The renewal has gone through twice without anyone picking up a phone. Then the one person who answered your emails takes a job somewhere else, and the next renewal arrives as a procurement review with three new names on it.

Nothing broke. The product did not degrade, the price did not move, the service did not slip. What happened is that the account contained exactly one relationship, and that relationship walked out of the building with a box and a new email address.

The tenure math nobody prices into a renewal

Median tenure for American wage and salary workers is 3.9 years, the lowest figure since January 2002, according to the Bureau of Labor Statistics. Men sit at 4.2 years, women at 3.6. Those are medians across every industry and every age group, which means half the workforce is below that line rather than near it.

Put a three year contract next to a 3.9 year median and the conclusion is uncomfortable. Your champion leaving is not a risk to be mitigated. It is the base case with an unknown date attached. Most account plans treat it like weather. It is closer to a calendar entry nobody has shown you.

The other half of the picture is what those people do once they are gone. UserGems studied past champions who had moved to new companies and found that 91 percent did not repurchase on their own, even three months into the new role, and even at vendors with strong Net Promoter Scores. Being liked is not the same as being remembered at the moment a budget opens.

Three things leave, and you only count one

The relationship

This is the loss everyone notices. The person who took your calls, argued your case in the budget meeting and forwarded your deck to their boss is gone. Their replacement has no history with you and no reason to defend a line item they did not choose.

The context

Harder to see, more expensive. Your champion knew why the contract was structured the way it was, which features were negotiated in, which outage you fixed on a Sunday afternoon, and which competitor was rejected and why. None of that is written anywhere the new person will read. What they inherit instead is a number in a spreadsheet next to a vendor name.

The contact details

The unglamorous one, and the one that decides how fast you recover. The replacement inherits the software, the contract, the shared channel and the ticket history. They do not inherit a phone. Your name, your mobile number and the fact that you are the person to call when something breaks lived in one person’s contacts app, and that app left with them.

So the new stakeholder does what every new stakeholder does. They search an inbox they were never part of, give up, and email a generic support address instead. You find out there was a problem at the point where the problem is already a ticket.

Multi-threading is a contact problem before it is a strategy

Every account plan says multi-thread. Very few say how, beyond booking more meetings. The mechanical version is narrower and easier to audit: by the end of the first quarter, at least three people inside the account should be able to reach you directly, without asking anyone’s permission and without searching an archive.

Three, not two. Two is usually the champion plus the champion’s manager, and managers leave for the same reasons at the same rate. You want people whose exits are uncorrelated:

• the economic buyer, who signs and rarely uses
• the daily user, who never signs and always notices first
• someone one team over, who inherits the account when a reorg moves it

Then make yourself savable, which is a different job from being known. Most of the time you hand people an email signature they would have to retype, or a card that goes into a jacket pocket and comes back from the dry cleaner. Neither ends up in a phone. What ends up in a phone is a contact that arrives complete, with your photo, title, company and number already filled in, in the seconds while you are still standing in front of the person. If that is your job, get the HeyDrop app and share by QR, NFC, AirDrop or a link, or drop the card straight into Apple Wallet or Google Wallet. Whoever you hand it to installs nothing. When the exchange runs the other way and you are handed paper, the AI Contact Scanner reads the card or the conference badge and files it as a structured contact rather than a photo you will never open again.

The version of this problem that belongs to the company

Now reverse it. Your champion stays and your account executive leaves, which at a 3.9 year median happens just as often. If the only reachable human on your side was that one rep, the client is now in exactly the position you were in: a contract, a login, and nobody to call.

The fix there is structural rather than personal. Everyone who touches the account should be reachable, and should look like the same company while doing it: the account executive, the customer success manager, the support lead, the implementation engineer. In practice that means cards created centrally instead of by each person in their own style, correct titles, one brand, and the ability to switch a card off the day somebody hands back their laptop. If you run the team, set your team up on HeyDrop, and export what everyone collects to CSV or Excel so it lands in the CRM instead of on twelve separate phones.

That last part carries more weight than it sounds like it does. A contact that exists only in a personal phone is not a company asset. It is a personal one, and it leaves when the person leaves.

The thirty days after you find out

You will usually learn about the move from a LinkedIn update, an auto-reply or a bounce. However it reaches you, treat it as a two sided event, because it is.

Inside the account, get a meeting with the replacement before the renewal enters procurement rather than after. Bring the context your champion kept in their head, written down: how the contract is structured and why, what was tried and abandoned, which problems you have already solved. You are not selling in that meeting. You are rebuilding the file that walked out.

Outside the account, your champion has just arrived somewhere new, with a budget, a mandate to change things and a tool they already know how to operate. The UserGems figure says almost none of them come back unprompted. It does not say they would say no. It says nobody asked.

None of this needs new software or a new process. It needs someone to notice that the healthiest looking account in the book may be resting on one person’s employment, and that the cheapest insurance available is making sure more than one human there can find you without having to look anything up.

This article and its accompanying image were generated with the assistance of AI.