How to hand a won deal over from sales to delivery
A step-by-step routine for turning a won deal into a live project — covering confirmation, knowledge handover, staffing, and commercial setup so delivery starts with full context.
Written By Lauri Eurén
Last updated 6 days ago
When a deal is won, the tentative plan you built during the sale becomes a real Project. The handover is where it turns into a delivery setup with the right team and financials in place.
A clean handover is as much about expectations and tacit knowledge as it is about data. The goal is to let your firm sell work and drop a delivery team into it without losing what the salesperson knows. This routine sequences both, and the UI detail for each step lives in the linked articles.
When to run it
The handover can start as early as the proposal, when the sales team brings in the people planned to deliver the work to help write it. It continues when the deal reaches negotiation, or any stage where everyone is comfortable planning in more detail. At that point, have early conversations with key team members.
The real handover happens at the moment a deal is confirmed (won in your CRM, signed, or sometimes a verbal agreement with the client). Running it promptly means the team is booked before someone else's project claims their time.
Who's involved
These people take part in the handover:
- The salesperson who owned the deal.
- The incoming project manager or account manager (sometimes the same person).
- Resourcing.
- Finance, who confirm the commercial setup.
The project team should also attend the pre-kickoff.
The routine
1. Confirm the project — and know who owns it
Mark the Project as confirmed. It was tentative while in the pipeline.
If the deal came from your CRM, the deal owner carries over as the project owner. Whoever picks up staffing or delivery then knows who to talk to about what was actually sold and promised.
If the integration already created the Project, use that one. Merge any duplicate rather than creating a second by hand. See Salesforce CRM; HubSpot CRM; Pipedrive CRM; Connect CRM via the REST API
2. Pass on what was really sold
Before you configure anything, get the salesperson and the incoming project manager or account manager together for a short pre-kickoff. Cover what was sold, what the client expects, and the nuances that never make it into a proposal or statement of work.
Setting expectations explicitly at this point is what lets sales hand off cleanly. It's the difference between a team that inherits context and one that starts cold.
3. Capture the staffing nuance — and let it drive who you pick
The proposal rarely captures everything that matters for staffing, such as the client's real working style, chemistry, and who would genuinely fit. Pull that out of the salesperson now. Record it where delivery will see it: a note on the Project, or as part of the staffing discussion. Everyone who can see the Project can read its notes, so keep sensitive remarks out of them.
Because Operating has an MCP server (AI chat (LLM) via MCP), you can also turn that tacit knowledge into staffing suggestions. Ask in plain language, for example "who works well with this kind of client, or with these people, for this role?". This surfaces fits the proposal never codified.
See How to staff a project from scratch and How to run a staffing routine with Operating.
4. Build the team and confirm the plan
Turn the rough team shape from the sale into real Positions. Set the role, seniority, site, and skills for each Position, and replace placeholders with named people.
Confirming the Project in step 1 already flipped its Allocations to confirmed. Here you adjust their dates and intensity to the real delivery timeline rather than promoting them. Confirmed Allocations are what drive capacity and forecast. See What are Positions and Allocations? and How to manage allocations.
5. Set the commercial configuration
Set these on the Project:
- Billing type
- Currency
- Rate card
- Budget(s)
- For fixed-price: the revenue recognition method
- For a retainer: the fee, the periods and any included hours. See How to set up a retainer project.
If a CRM created the Project, its Budget may already be prefilled from the deal value. Confirm the amount and dates are right rather than re-entering them.
This is the financial backbone delivery is measured against. See Budgeting and profitability: a worked example, What are the billing types? , and How revenue recognition works in Operating.
6. Hold the internal kick-off
With the team named and the setup in place, hold an official internal kick-off: this is the project, this is what we sold, these are the expectations. Making that explicit turns a closed deal into delivery that starts with shared context rather than a cold start. The salesperson should attend this meeting.
End state
At the end of the handover you have:
- A confirmed Project with a known owner.
- A team built from real Positions, with confirmed Allocations.
- A complete commercial setup.
- Just as important, a delivery team that knows what was sold and what's expected.
The Project is ready to deliver and already feeds capacity and forecast correctly.
Related articles
Was this helpful?
More in Best practices & routines
How to run the invoicing process end to endHow to run a month-end closeExample saved views worth building and pinningHow to structure permissions based on your company cultureStill need help? Ask the team