Sales-to-operations handover: what a won deal should pass on
A won-deal handover should transfer agreed scope, customer context, responsibility, and readiness for delivery. Changing a CRM stage is only one part of confirming that work can begin.
By Oyerinde Alfred · AI engineer · RevOps & business operations specialist
Quick answer: A won-deal handover should transfer agreed scope, customer context, responsibility, and readiness for delivery. Changing a CRM stage is only one part of confirming that work can begin.
Define what delivery needs to know
Ask the service team which missing information delays a start. Common questions concern the service location, start date, agreed scope, commercial contact, and any commitments made during the sale. Identify the authoritative document or record for each rather than copying partial details into many tools.
Distinguish estimated sales information from confirmed delivery information. A verbal intention to buy may not satisfy your contract or payment requirements. The business should decide the prerequisites for a handover, and the workflow should make missing prerequisites visible.
Connect a confirmed event
A proposed integration can create a project or onboarding task when the team confirms readiness. Include the CRM opportunity identifier and store the new delivery record identifier back in the CRM. That link helps both teams investigate the same work without duplicating an entire database.
Test a changed start date, amended scope, reopened opportunity, and duplicate stage change. Decide whether the workflow updates the existing delivery record or asks for review. Automatic creation without a matching rule can create multiple projects for one contract.
Make the handover accountable
Name the person sending the handover and the person accepting it. An acknowledgment task or readiness check can be enough for a small team. Give exceptions a place to live, such as missing documents or unclear service details, rather than letting them disappear into an email thread.
Review the first few handovers with sales and delivery together. Record the information they repeatedly ask for and improve the template. Keep reporting focused on whether work starts with the right context, not just whether an integration ran successfully.
A practical checklist
- List confirmed scope and start prerequisites.
- Link CRM and delivery record identifiers.
- Test amendments and duplicate events.
- Name sender, recipient, and exception owner.
Should delivery tasks live inside the CRM?
They can if the system supports the team’s needs, but that is a workflow choice. If delivery already works well in another tool, a narrow handover may be enough. Avoid replacing a useful delivery process just to keep every task in one platform.
Continue with a related guide
Read the related guide, explore the CRM and automation library, or use the CRM readiness checklist.
Sources and editorial notes
Prepared on 11 October 2026. This guide combines linked product documentation with a proposed implementation approach. Examples are illustrative. Platform capabilities, editions, and charges change; confirm requirements with the provider before buying. No vendor sponsorship or affiliate links are used in this article.
Explore the related service
Revenue operations & CRM
Map your customer journey, organize the pipeline, and connect the follow-up process.
View the service →Have a system in mind?
Let's discuss what you want to improve or build.
New notes, no noise
I publish when there is something worth reading. Usually twice a month.