A rep resigns, moves into a new role, or a territory is recut. Reassigning the accounts takes an afternoon in the CRM. Everything that made those accounts winnable took years to learn, and it leaves with the person unless somebody deliberately takes it out of their head first.
Each of these gets booked somewhere else in the forecast, which is exactly why the transition itself never becomes a problem anyone owns.
Drawn from conversations with more than twenty go-to-market leaders in 2026. Paraphrased and anonymised.
All three move accounts between people. Only the first one usually triggers any process at all, and even that one tends to run on goodwill and a shared calendar.
The one case that is recognised, and still the one where shame and a short notice period do most of the damage.
Still in the building, so everyone assumes the knowledge is reachable. In practice their attention moved the day the new role started.
Nobody is leaving at all, so no process fires, and dozens of accounts change hands in a single planning cycle.
Two guided sessions with the outgoing person, account by account. No blank page and no homework, because the system asks and they answer, and the manager and the team verify what comes out.
Illustrative. Every field in the handover is marked covered, mentioned or missing, so the manager can see how complete the account is while the person is still there to answer, rather than finding out three months later.
Everything below already happens in most companies, and none of it tells a manager whether the handover was any good while there is still time to act.
Written at the end of a long quarter, by someone whose attention has already moved on, and read once. Nobody can tell whether it is complete, because there is nothing to compare it against.
A recording captures the interaction. The handover is the interpretation of it. Forty hours of audio is not an answer to what the new owner should do on Monday.
The CRM holds the stage and the close date. It does not hold why this account was discounted and that one was not, and a free-text box nobody verifies does not change that.
It is simply booked under other names. Three levers, each one traceable in your own numbers rather than ours.
The successor starts with the reasoning rather than rebuilding it, which pulls weeks out of the period where the account is effectively unattended.
Peers and the manager stop absorbing the questions the leaver used to answer, because the answers sit in the handover instead of in people's memories.
The accounts most exposed are the ones held together by one person. A clean handover protects a share of that revenue, and the share is the number worth arguing about.
Run on a real transition, or a simulated one if nobody is leaving right now, and measured against criteria you set before it starts.
We agree the success criteria together and align on the approach.
Context is captured from the handover conversations, with minimal effort on your side.
A joint handover meeting, run through handedover on the accounts in scope.
Results against your criteria, a business case on your numbers, and a recommendation.
What you need to provide is the person handing over, the accounts in scope, and consent for the recordings. What you end up with is a decision paper for whoever signs, rather than an open question. Hosted in the EU throughout, with data residency enforced in code and checked at start-up.
Built by Matthias Drebes, who spent thirteen years in enterprise sales, seven of them at Celonis helping the sales organisation grow from 100 to 3,000 people, and watched the same context leave the building every time an account changed hands.
Tell us roughly how many people changed seats last year and how many accounts moved with them. If the first handover does not look worth it from those two answers, I will say so.