Somebody leaving happens a handful of times a year. A win happens every time you sell. The account moves from the person who spent months learning it to the people who now have to deliver it, and almost nobody treats that as a handover at all.
It runs whenever a won deal moves to people who did not sell it. In most organisations that is every new logo, every new business unit or product line sold into an existing customer, and every expansion large enough to start a new implementation. Where the team that won the deal keeps the account, nothing crosses and there is nothing to hand over.
None of these are framed as a handover problem when they are described. They are described as delivery problems, as churn, or as a quarter that came in short.
Drawn from conversations with more than twenty go-to-market leaders in 2026. Paraphrased and anonymised.
Each one receives a different retelling of the same account, assembled by hand, at a different moment, by a person with less of the original context each time.
Inherits the relationship and the promises, usually from a call and a document written at the end of a long quarter.
Needs the technical picture, the constraints, and what was actually agreed rather than what was scoped.
Arrives last, sat in none of the sales conversations, and reconstructs the account from whatever survived the first two handovers.
Two guided sessions with the account executive while the deal is still fresh, structured per account, so everyone downstream receives the same thing rather than a summary of a summary.
Illustrative. Every field in the handover is marked covered, mentioned or missing, so the manager can see how complete the account is before it is signed over, and which answers are still too thin to sign off on.
Everything below already exists in most companies, and none of it survives the moment an account changes hands.
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.
Three levers, and each one traces back to something you can measure in your own numbers rather than ours.
Delivery starts with the full picture on day one instead of assembling it, so the account reaches productive use sooner. Valued at margin, not revenue.
Fewer clarification loops back to a seller who has moved on, and fewer decisions made twice because the reasoning behind the first one was never recorded.
On large accounts, a weak start puts the expansion and the first renewal at risk. A clean handover protects a share of that, and the share is the number worth arguing about.
In one conversation this August a sales leader did the arithmetic out loud: roughly one hundred new customers a year, one to two weeks between the signature and the start of implementation, and nothing crossing that gap except a win mail and the contract. By their own account it had already cost them deals and customers. Drawn from conversations, paraphrased and anonymised.
The offer is called the first handover, and it is a service rather than a software subscription. Matthias Drebes runs it with you: he agrees the criteria at the start, moderates all three sessions himself, and takes you through the readout at the end. This is not a login you are handed, it is work done next to you. Two documents come out of it, the briefing the incoming owner works from and the readout whoever decides works from.
We agree what this handover has to carry and how you will judge it once it is done. You name the won account and the person who sold it.
The person who sold the account is taken through it in three structured sessions. handedover asks the questions rather than reading your systems, so nobody is left in front of an empty template.
The incoming owner receives a briefing scoped to their role. The coverage matrix marks every field covered, mentioned or missing while the person handing over is still in the room.
Results against the criteria you set before the start, a business case on your own numbers, and a recommendation. The person who handed the account over receives a certificate for the work.
What you provide is the person handing over, the account in scope, and consent for the recordings. Nothing further is needed from your team. Data stays in the EU throughout, enforced in code and checked at start-up rather than asserted in a policy. The earliest start is mid-October 2026.
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 deals you close in a year and who receives them afterwards. If the first handover does not look worth it from those two answers, I will say so.