What a bad handoff costs
The customer signs on a Friday feeling understood. On Tuesday they meet the delivery team and are asked to explain their business from the beginning.
That moment does more damage than most teams realise. It tells the customer that the understanding they bought was one person's, not the company's, and it starts the relationship by making them do work. Churn analysis frequently traces back to a first fortnight that felt like starting over.
The test for a handoff
Could the delivery lead walk into the first conversation and accurately state what this customer is trying to achieve, without asking? If not, the handoff failed, however many fields were filled in.
The handoff document
One page. Six sections. Written by the salesperson while it is fresh, not reconstructed later.
| Section | What goes in it |
|---|---|
| What they are trying to achieve | In the customer's own words, not your product's |
| What was promised | Everything, including informal commitments made on calls |
| The people | Who champions it, who signs, who has to use it, who was sceptical |
| What they are replacing | Tool, spreadsheet, or a manual process, and what they liked about it |
| Constraints | Deadlines, technical limits, a compliance review, an internal politics problem |
| What worries them | The objection they raised most, even if you resolved it |
The last two are the ones most often missing, and they are the ones that predict trouble. A customer who worried three times about how long setup would take will judge the first fortnight against that worry, whatever else goes well.
Use their words. If they said "we lose track of who chased which supplier", write that. Translating it into your internal vocabulary loses the specific thing they care about, and the delivery team will end up demonstrating a feature rather than solving that problem.
The handoff call
Twenty minutes, sales and delivery, before anyone contacts the customer.
Delivery reads the document first
Sent at least a day ahead. The call is for questions, not for reading aloud.
If the document is read in the meeting, the meeting takes an hour and the questions that matter never get asked.
Day beforeWalk the promises line by line
Delivery confirms each one is achievable, and flags anything that is not. This is the moment to catch a problem, while it is still cheap.
Be specific about timing as well as capability. "Yes we can do that" and "yes we can do that by the date you promised" are different answers.
The critical sectionName the risks out loud
The sceptic on their side, the deadline that is tight, the integration nobody has confirmed.
Salespeople are reluctant to hand over problems, and delivery teams resent discovering them later. Naming them at handover costs nothing and prevents most of the friction between the two teams.
Say the awkward partsAgree the introduction
The salesperson introduces the delivery lead directly, ideally on a short joint call, and says plainly that this person now owns the relationship.
A warm, explicit handover keeps the trust the salesperson built. An email that says "looping in my colleague" transfers a contact, not a relationship.
Joint call beats an email
Handling promises that should not have been made
It happens in every company. Someone commits to a date, a capability, or an integration that does not exist.
The instinct is to hope it does not come up. It always comes up, and it costs far more in week three than it would have in week one.
Handle it directly. Someone senior contacts the customer early, says the commitment was made in good faith and cannot be met as described, explains what will happen instead, and offers something to make up for it. Customers are considerably more forgiving of an early, honest correction than of a discovery that they were told something untrue.
Then record it as a loss-prevention lesson rather than as a disciplinary matter. Over-promising under pressure is usually a symptom of a target structure, not a character flaw, and treating it as the latter guarantees the next one is hidden.
Making it happen every time
Make the document a required step, not a courtesy. No handoff call without it. If it is optional it will be skipped on exactly the complicated deals that need it most.
Keep it on the customer record. A handoff document living in a chat message is gone within a week. It belongs where the delivery team will look in month three when something surfaces.
Review it at the 30-day mark. Did the customer get what was promised? This one check catches most of the problems that otherwise appear at renewal, and it is a natural companion to the questions in our guide to win/loss analysis.
Automate the trigger, not the content. When a deal moves to closed-won, the handoff tasks should appear for the right people automatically. The document still has to be written by a human, as covered in what to automate first.
The structural fix underneath all of this is that the context should not need transferring at all. Most handoff failures are re-summarising failures: a meeting became a note, a note became a CRM entry, and the entry became a handover message, losing detail at every step. Siela keeps meetings, the customer record, and the resulting tasks on one shared context layer, so the delivery team can read what was actually said rather than a summary of a summary.
Frequently asked questions
- When should the handoff happen?
- Within a few days of signature, and before the first delivery conversation. A handoff that happens after delivery has already started means the customer has repeated themselves, which is the exact impression you were trying to avoid.
- Should the salesperson stay involved after handover?
- Introduced and reachable for a few weeks, then out. Staying involved indefinitely means the customer keeps routing questions through someone who cannot answer them, and the delivery relationship never forms.
- What is the single most important thing in a handoff?
- Everything that was promised, including the informal promises made on calls. Undocumented commitments are the leading cause of a delivery team unknowingly breaking a customer's expectations in week one.
- How long should a handoff document be?
- One page. Longer documents do not get read, and an unread handoff is worse than none because everyone believes the context was transferred.
- What if sales promised something we cannot do?
- Surface it at handover, not when the customer asks. Someone senior tells the customer early, explains what will happen instead, and offers something in compensation. Discovering it in week three costs far more than an awkward call in week one.