What a won-deal checklist should capture
A won-deal handover checklist should capture the commercial context the contract leaves out: why the customer bought, what was conceded in negotiation, who holds influence and which promises were made verbally. The seller completes it before the handover meeting, so delivery reads it in advance and uses the meeting to ask questions rather than take dictation.
Use the same checklist for every won deal above a threshold your commercial team agrees, and a lighter version for smaller repeat orders. Consistency matters more than length. When delivery leads know that every significant deal arrives with the same eight answers in the same order, they stop chasing sellers for basics and spend the handover time on the parts that are genuinely unclear.
Gaps the contract leaves for the delivery team
A contract describes deliverables, prices and obligations. It rarely says that the customer chose you because the previous supplier missed every deadline, which tells delivery that schedule reliability matters more than anything else. It will not mention that the finance director agreed only after a phased payment plan, or that the operations manager still prefers the competitor.
Those facts shape how delivery should behave from the first day: whom to update, what to protect, which complaints to expect. Without them, a capable project team can do everything the contract asks and still disappoint the customer, because it spent its attention on the wrong things in the first month.
The eight-point checklist
Keep each answer brief. A few lines per item is enough if they are specific. Where an item does not apply, write 'none' rather than leaving it blank, so reviewers can tell a deliberate answer from a skipped one.
- Buying reason: the problem the customer is solving and what success looks like to them
- Why us: the reasons they chose your company over alternatives, in their words if possible
- Decision-makers and influencers: names, roles, and who supported or resisted the purchase
- Concessions given: discounts, extended terms, free items, and any conditions attached
- Verbal or informal promises: anything said in meetings or messages that is not in the contract
- Timeline commitments: dates the customer is working towards and why those dates matter
- Commercial terms for finance: billing entity, payment milestones, retention and purchase order references
- Known risks: competitor still involved, internal politics, technical doubts or budget pressure
Recording concessions and verbal promises honestly
Items four and five are the ones sellers are most tempted to leave thin. Admitting a large discount or an off-contract promise can feel like admitting a mistake. Make it clear that the checklist is not a disciplinary record. A promise disclosed at handover can be planned for. A promise discovered at kickoff costs time, margin and trust.
Ask the seller to search their own email and messages for the deal before completing the checklist. Phrases such as 'we can include', 'no problem' and 'I will check but should be fine' often point to commitments the customer remembers clearly.
Write concessions with their conditions attached. 'Extra discount granted' is incomplete. 'Extra discount granted on condition the customer signs before year end and accepts a single delivery site' tells delivery and finance what the customer has agreed to in return, and what to raise if the customer later asks for a second site at the same price.
Sign-off before delivery accepts the deal
The sales manager reviews the checklist first, checking it against the opportunity history and asking about anything that looks vague. The delivery lead then accepts it, or returns it with questions. Finance confirms the commercial terms section matches what will be invoiced. Only when all three have signed off does the opportunity move to a handed-over status.
If the checklist comes back more than once, treat that as a coaching point for the seller, not a reason to drop the standard. Agree a response time for each reviewer as well, because a checklist that sits unread for a week delays the project start and gives sellers a reason to skip the process next time.
Keeping the checklist with the deal record
Store the completed checklist on the won opportunity, not in a shared drive folder with a different naming scheme. Delivery will refer to it during the project, and the account owner will want it again at renewal, when the original buying reasons and concessions shape the next negotiation.
A CRM that links opportunities, accounts and handover keeps this context in reach for everyone who needs it. BukuCRM, Fasttrade's product for sales teams, includes handover to delivery as one of its core areas. Fasttrade can confirm whether its scope covers your checklist and sign-off steps.
Frequently asked questions
Who should complete the won-deal handover checklist?
The account owner who closed the deal completes it, with input from presales or specialists who were involved. The sales manager reviews it for gaps, the delivery lead accepts it, and finance checks the commercial terms. Spreading the review this way catches missing promises and billing details before the project starts.
What if the seller made a promise delivery cannot keep?
Record it on the checklist anyway. Disclosure at handover gives the sales manager and delivery lead time to decide how to respond, whether by absorbing the cost, offering an alternative, or explaining the position to the customer. A hidden promise usually surfaces later at a much worse moment.
Is the handover checklist useful after the project starts?
Yes. Delivery teams refer to it when making trade-offs, because it shows what the customer values most. Account owners use it at renewal or expansion, since the original buying reasons and concessions shape the next negotiation. Keeping it on the won opportunity makes it easy to find years later.
Next step
Explore BukuCRM or tell Fasttrade what your team needs.
These articles explain enterprise process design. Product availability and detailed scope are confirmed in conversation.