handedover

The won deal handover

We run the handover while the win is fresh.

A won account is still whole in one person's head for a few days, and then next quarter starts. We work through it with them in that window, and what is thin is visible before they move on.

It runs whenever a won deal moves to people who did not sell it. Where the team that won the deal keeps the account, nothing crosses and there is nothing to hand over.

What we hear

The same things come back, in almost every conversation.

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.

The customer explains their own history a second and a third time, to people who work at the same company as the person they already told.
Delivery spends the first weeks rebuilding context the account executive already had, and the go-live date moves accordingly.
An expectation set in month four of the deal cycle surfaces in month two of delivery, and nobody can say who set it.
Clarification loops run back to the account executive, who has already moved on to next quarter and answers from memory.
The account goes quiet after it changes hands, and the dip is booked as ramp, as procurement, or as market softness.

Drawn from conversations with go-to-market leaders in 2026, paraphrased and anonymised. No count is claimed here, because a count would suggest a survey and this was not one.

Why it gets worse

A won account is often handed on three times, to three different teams.

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.

First

Customer success

Inherits the relationship and the expectations that were set, usually from a call and a document written at the end of a long quarter.

Then

Delivery and services

Needs the technical picture, the constraints, and what was actually agreed rather than what was scoped.

Often

An implementation partner

Arrives last, sat in none of the sales conversations, and reconstructs the account from whatever survived the first two handovers.

What gets captured

Once, at the win. In one standard shape.

Taken once from the person who won the account, and structured per account, so everyone downstream receives the same record rather than a summary of a summary.

Enterprise account · won
Illustrative example of a won deal brief
Who decides
The signature came from the CFO's office, although the sponsor ran the evaluation. Renewal will go the same way.
Why we won
Chosen on migration risk. Any delivery slip reopens the argument they had internally before signing.
Expectations set
An expectation of reporting in phase one, set verbally in a workshop and never written into the contract.
Success, in their words
"We stop chasing this manually by the end of Q2."
Watch out
The technical lead was overruled during the evaluation. Handle the kickoff carefully.

Illustrative, shortened to five fields. How each field is marked is described under day four below.

The first handover

Five working days, two sessions, alongside your kickoff.

The offer is called the first handover, and it is a service, not a subscription. Matthias Drebes runs it with you: he agrees the criteria at the start, moderates every session himself, and takes you through the readout at the end. Two documents come out of it, the briefing the incoming owner works from and the readout whoever decides works from.

The sessions run alongside your kickoff, not before it. The receiving side makes first contact as it does today, and the briefing is in their hands before the first working session with the customer.

Day one

The criteria, and the first session

We agree together 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, and the first session follows in the same call.

Days two to three

The second session

The person who sold the account is taken through the rest in a second structured session; a third follows only where the coverage comes back thin. handedover asks the questions rather than reading your systems, so nobody is left in front of an empty template.

Day four

The briefing

The incoming owner receives a briefing scoped to their role, before their first working session with the customer. The coverage matrix marks every field covered, mentioned or missing while the person handing over is still in the room.

Day five

The readout

One page: results against the criteria you set before the start, the coverage per account, 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. Processing runs in the EU, and the residency check is enforced in code at start-up rather than asserted in a policy.

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 obvious objection

You already have notes. That is precisely the problem.

Most companies already have the first three below, and each of them records something. None of them asks the person who sold the account for what was never written down.

Instead of

A handover document

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.

Instead of

Recordings of customer calls

A recording of a customer call captures what was said, and the handover is what it meant for the people taking over. Forty hours of audio does not tell the new owner what to do on Monday.

Instead of

A field in the CRM

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.

And not

A replacement for any of them

handedover does not replace your CRM and does not write back into it today. It is not a wiki, because it runs once, at the moment the account crosses. It does not sit on your customer calls and it does not read recordings out of another system. It has no outcome data of its own yet, which is why every number in the conversation is yours.

Why at all

What was sold is an expectation, and no system passes that on.

The customer feels it first. Expectations that were set and not met lower satisfaction and the intention to continue.1 Churn concentrates in the earliest tenure,2 and when the counterpart on an account changes, the nearest study puts the loss at 13 to 17 per cent of its annual sales.3

One remedy has been tested. Early contact from the receiving side, with nothing to sell, reduced churn in a controlled field experiment.4 The size for your own accounts has to come from your own figures, which is what the cost calculator is for. The full argument, with the sales cycle and the seam, is on the front page.

What it is worth

Three lines you already report.

Each one traces back to a measure on your own won deals. The baseline takes those measures from an export of last year’s.

Gross retention

Churn at the first renewal

The first renewal is where an expectation that never reached the receiving side is paid for. Measured as the share of won accounts gone within twelve months, when your export carries a status column.

Net retention

Time to first expansion

An expansion closes in about 52 days once it starts,5 so the time is lost before the start, and a receiving side without the map starts late. Measured as days to the next opportunity on the account.

Cost of sales

Rework after close

Every question that goes back to the seller after close is selling time spent twice, and every week delivery spends rebuilding context moves go-live, valued at margin.6 Measured as seller activity after close.

Led by Matthias Drebes, who runs every first handover himself. Thirteen years in enterprise sales, seven of them at Celonis while it grew from 100 to 3,000 people.

Get in touch.

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, we will say so.

We reply within two working days. Two emails at most, no sequence. Or skip the form and book thirty minutes with Matthias. You pick the slot, the invitation follows by email. Or write to mat@handedover.ai at any time.

Sources

Six sources, in order of appearance
  1. Bhattacherjee, A. (2001). Understanding Information Systems Continuance: An Expectation-Confirmation Model. MIS Quarterly 25(3).
  2. Fader, P. S., Hardie, B. G. S. (2007). How to Project Customer Retention. Journal of Interactive Marketing 21(1). Fader, Hardie, Liu, Davin, Steenburgh (2018). “How to Project Customer Retention” Revisited: The Role of Duration Dependence. Journal of Interactive Marketing 43.
  3. Shi, H., Sridhar, S., Grewal, R., Lilien, G. (2017). Sales Representative Departures and Customer Reassignment Strategies in Business-to-Business Markets. Journal of Marketing 81(2). Cited as the nearest published event, not as a figure for any reader's own accounts.
  4. Becker, J. U., Spann, M., Barrot, C. (2020). Impact of Proactive Postsales Service and Cross-Selling Activities on Customer Churn and Service Calls. Journal of Service Research 23(1).
  5. Ebsta and Pavilion, 2025 GTM Benchmarks.
  6. Ton, Z., Huckman, R. S. (2008). Managing the Impact of Employee Turnover on Performance: The Role of Process Conformance. Organization Science 19(1).