The customer accepts the proposal by email. Sales celebrates, updates the forecast and moves on to the next opportunity.
Two days later, operations hears about the work for the first time. The promised start date is approaching, the delivery team has an older version of the quote and nobody knows whether the customer’s data, site access or named contact is ready.
The sale is real, but the start is not.
This is the sales-to-delivery handover gap: the point where commercial agreement must become a clear, owned piece of work. A reliable handover protects the customer experience without asking operations to reconstruct the sale from emails and memory.
Treat acceptance as a trigger, not the handover
A “yes” should start a defined internal process. It should not be the final step in sales and the first surprise for operations.
Agree what counts as acceptance in your business. It may be a signed proposal, approved purchase order or another authorised confirmation. Record the evidence, the date and the person who provided it. If a condition is still outstanding, label the work as conditional rather than allowing it to appear ready.
Lock the accepted commercial package
Operations needs the version the customer accepted—not the most convenient attachment in someone’s inbox. Keep the agreed proposal, scope, pricing, payment terms and material exclusions together, with a clear version or date.
Summarise what is included in plain language. Record quantities, locations, service levels, implementation assumptions and any customer responsibilities that affect delivery. Separate the agreed scope from options that were discussed but not purchased.
If the customer’s acceptance changes the proposal, capture the change before work begins. A verbal amendment that lives only in a salesperson’s memory is not a dependable operating instruction.
Create one operational summary
The delivery team should not need to read the entire sales history to understand the next move. Use a short handover summary that answers practical questions:
- What has the customer bought?
- Who is the customer’s day-to-day contact and who can approve changes?
- What outcome and deadline were agreed?
- What must the customer supply before work can start?
- Which internal team owns each next action?
- What remains open, risky or unconfirmed?
Name the receiving owner
A handover is incomplete until somebody accepts responsibility on the delivery side. “Operations” is a department, not an owner.
Name the person coordinating the start, then identify the sales owner who remains available for commercial context. Set a short review point where the receiving owner can ask questions before the customer is told that delivery has begun.
If capacity is unavailable, expose that immediately. Quietly assigning work to an overloaded team does not turn the promised date into a workable plan.
Separate requested dates from committed dates
Customers often state a preferred start date during sales conversations. That date should not automatically become an operational commitment.
Record the requested date, the date actually agreed and the dependencies that could change it. Examples include a deposit, data file, site induction, stock availability, signed authority or access credentials.
When a dependency belongs to the customer, name it and set a follow-up date. When it belongs internally, give it an owner. This makes delay visible before it becomes a dispute about what was promised.
Check readiness before announcing the start
Use a brief readiness check. Confirm that the accepted scope is clear, the owner is assigned, essential documents are present, capacity has been reviewed and the first customer action is agreed.
Do not mark the handover complete because a form was submitted. Completion should mean the receiving team can explain what happens next and has accepted the responsibility to make it happen.
A practical example
Consider a growing services business that wins a three-site customer. The proposal includes an initial setup, staff orientation and monthly support. The customer asks to begin on Monday, but the proposal assumes that each site will provide a contact list and access details first.
Without a handover, sales tells the customer that the team will “get started”, while operations schedules only one site and does not know that orientation is included.
With a structured handover, the accepted proposal and three-site scope are attached to the customer record. The sales owner records the customer sponsor, the site contacts still required and the Monday request. Operations confirms capacity for the following Wednesday, assigns a coordinator and sends one consolidated request for the missing information.
The customer receives a realistic start plan. Sales remains involved for the unresolved commercial question, and operations begins with the correct scope rather than an assumption.
Acknowledge the handover to the customer
Once the internal owner accepts the work, send a concise introduction. Confirm the delivery contact, the agreed first milestone, outstanding customer actions and the next scheduled update.
This message should align with the accepted proposal. Avoid introducing new commitments in the welcome email. If something has changed, route it through the agreed commercial process rather than hiding it inside delivery correspondence.
Track changes after acceptance
Customer needs can evolve between sale and delivery. Record requested changes separately from the original scope, with an owner and a decision. State whether the change affects price, timing, resources or the agreed outcome.
Keeping the accepted baseline visible allows sales, operations and the customer to distinguish a genuine change from a misunderstanding.
Close the handover with evidence
A completed handover should leave an audit trail: acceptance evidence, the correct commercial documents, named owners, a readiness decision, open dependencies and the customer’s confirmed next step.
Review stalled handovers regularly. If accepted work has no delivery owner, no start plan or an unresolved dependency, it needs attention before the customer has to chase.
MyTalent Business CRM supports customer, lead, sales, quote, invoice, order and stock-related business workflows. Explore Business CRM or talk to our team about the capabilities available for your organisation.
A good handover does more than move information. It turns a commercial promise into a clear, achievable start.