The moment a sale is agreed is also the moment a service business is most at risk of disappointing the customer it has just won. Information gathered during the sales process — commitments made, preferences noted, concerns raised — has to travel from the person who sold the work to the person who delivers it. When that transfer fails, the customer notices.
This guide explains why sales-to-delivery handovers break down, what information must always transfer, and how to build a consistent process that works even when staff are busy.
Why Handovers Break Down
The most common reason is that the sales and delivery functions operate as separate worlds. Sales staff focus on winning the work. Delivery staff focus on doing it. The handover sits in between, owned by no one in particular and done differently every time.
In small businesses, this is often made worse by informality. A verbal mention in a shared office, a forwarded email with no context, or an assumption that the delivery team can read back through the original enquiry thread — none of these are reliable. Each creates a different set of gaps.
The consequences are predictable. The delivery team discovers commitments they did not know about. The customer repeats information they already gave. A delivery manager contacts a customer to ask a question the salesperson already answered. All of this signals to the customer that the business is not as organised as they had hoped.
What Information Must Transfer
A reliable handover covers six areas without exception:
- Customer contact details and preference — not just an email address, but how the customer prefers to be reached and who the primary contact is on their side
- What was agreed — a clear, specific description of the scope of work, including any variations from a standard offering
- Commitments made — deadlines, pricing, inclusions, anything the customer is expecting that goes beyond the written proposal
- Constraints and sensitivities — access restrictions, timing requirements, topics the customer is sensitive about, anything that will affect how the work is delivered
- Context from the sales conversation — why the customer chose you, what alternatives they considered, what matters most to them
- The relationship status — is this a new customer or a returning one? Do they already have a relationship with anyone in the delivery team?
A Practical Handover Template
The simplest effective handover is a short document with fixed sections, completed by the salesperson before any delivery work begins. The purpose of a template is not bureaucracy — it is to make it impossible to forget something important.
A basic template should include: customer name and contact; project reference or invoice number; scope summary in two to three sentences; key commitments and deadlines; any known constraints; context notes (what the customer cares about most); and the date by which the delivery team needs to be in contact with the customer.
Keep it to one page. If it takes more than ten minutes to complete, it will not get completed consistently. The goal is a document the delivery team can read in under five minutes and feel confident starting work.
The Handover Call
For anything more complex than a straightforward, repeatable service, a brief call between the salesperson and the delivery lead improves outcomes considerably. It gives the delivery team a chance to ask questions and pick up on context that does not transfer well to a written document — tone of voice, level of technical knowledge, how much hand-holding the customer is likely to need.
The call does not need to be long. Fifteen minutes is usually sufficient. The document should be read before the call, not during it.
How to Test Whether the Handover Is Working
The simplest test is a single question asked at the end of each project: did your delivery team have to contact the customer to ask for information that should have been in the handover? If the answer is yes more than occasionally, the handover process has gaps.
A secondary measure is customer feedback in the early stages of delivery. Customers who feel they are having to repeat themselves or re-explain their requirements are experiencing a handover failure. That dissatisfaction often shows up in project reviews or cancellations before it shows up in complaints.
Review the handover template every three to six months. As the business grows and the range of work changes, the information that needs to transfer will change too.