Turn a won deal into a customer onboarding handoff
Transfer the agreed scope, sales commitments and customer contacts to the delivery team. Prepare a kickoff and welcome message while keeping incomplete or disputed promises visible.
How this works
Turn the commercial record into a delivery-ready handoff without treating every optimistic sales statement as an approved promise. Keep the signed scope, later approved amendments, customer expectations and unresolved questions separately traceable.
This workflow coordinates an existing onboarding process. It does not decide contract validity, approve delivery capacity or grant customer access. Start from the organization’s actual readiness rule; payment, signature or compliance checks are required only when that rule specifies them.
Before you start
Handoff rule and receiving owner
Identify the milestone that permits transfer, the person who accepts the work, and the required onboarding fields. A CRM stage label alone may not satisfy this rule.
Authorized account evidence
Use the correct customer and deal IDs, current agreement version, relevant call notes and permitted correspondence. Keep unrelated accounts out of the packet.
Action permissions
Record which updates, invitations and messages the user has authorized and which must remain drafts. Confirm the destination team and approved customer contacts.
Prepare the inputs
- Deal snapshot
- Required
One CRM export or record with account_id, deal_id, stage and modified_at.
Resolve multiple opportunities for the same customer before reading attachments; preserve the source timestamp.
- Commitment evidence
- Required
Approved scope and amendments plus selected sales notes with document and passage references.
Separate agreed obligations from requests, forecasts and negotiation statements. Flag contradictions instead of choosing the most recent informal message.
- Onboarding checklist
- Required
Required fields, readiness conditions, owner roles and permitted communication template.
Identify blocking items explicitly; do not invent a delivery owner, deadline or access approval.
- Scheduling constraints
- Optional / conditional
Approved participants, availability, duration and time zones.
Use only when scheduling is in scope; a held slot is not an accepted invitation.
Implementation, step by step
Confirm that this engagement is ready for handoff
- Match the trigger to the exact account and deal. Read its current stage and the agreed readiness conditions before preparing external actions.
- Create a run key from the deal ID and milestone version. Check for an existing handoff so repeated notifications reopen the same work instead of creating another kickoff.
Checkpoint: One engagement, one readiness decision and one reusable handoff identifier are recorded.
Build a commitment ledger
- Extract scope, success criteria, timeline, exclusions, customer dependencies and any approved special terms. Attach a passage or record reference to each entry.
- Record informal sales promises separately with their speaker, date and verification status. Ask the accountable owner to resolve conflicts between these statements and approved scope.
Checkpoint: Every deliverable or promise is either evidenced as agreed or explicitly unresolved.
Assemble the receiving team’s packet
- Summarize the customer’s stated problem, stakeholders, approved scope, open dependencies and first milestones. Include the next question for each missing field.
- Name the receiving owner only from a verified assignment. Give that person enough context to accept, question or return the handoff rather than marking acceptance automatically.
Checkpoint: The packet distinguishes ready work, blockers, owner decisions and customer requests.
Prepare the kickoff and welcome materials
- Draft an agenda from the accepted scope and dependencies, then propose slots against real availability and time zones if requested.
- Draft a welcome message using verified contact details. Do not repeat an unapproved deadline or describe an unconfirmed feature as committed. Keep invitation, email and shared-channel creation as separate actions.
Checkpoint: Each proposed action has its destination, required approval and expected result.
Apply authorized actions and reconcile the handoff
- Execute only the actions already authorized by the user or approved workflow. Before each write, check for the existing document, event or message associated with the run key.
- Save returned identifiers and actual statuses. If a document is created but a calendar request fails, retry only the failed action after checking whether it nevertheless completed.
Checkpoint: The action ledger shows drafted, applied, failed and pending steps without duplicate sends.
Obtain acceptance and close the transfer
- Ask the receiving owner to confirm the packet is sufficient through the team’s established process. Keep unresolved commitments assigned until answered.
- Record acceptance separately from customer kickoff completion. A sent welcome message does not prove the receiving team is ready or the customer has attended.
Checkpoint: The handoff has an owner, acceptance state, next milestone and unresolved-item list.
Decisions along the way
Deal is marked won but a required readiness item is absent
Prepare the packet as blocked and identify the missing evidence; do not advance the delivery state.
A call note conflicts with the approved agreement
Show both references and ask the account owner to reconcile the promise. Do not silently remove the customer expectation.
The trigger is delivered again
Locate the existing run and update changed facts; preserve already applied action receipts.
No receiving owner or verified contact exists
Stop the affected transfer or external communication and request assignment; continue drafting unrelated packet sections.
What you will produce
customer-handoff.md
MarkdownA concise packet for the delivery owner.
Include: handoff_id · account_id · deal_id · readiness · agreed_scope · commitments · stakeholders · dependencies · receiving_owner · acceptance_state
handoff-actions.csv
CSVA separate ledger for safe resumption across systems.
Include: handoff_id · action · destination · authorization · status · external_id · last_checked_at · next_action
kickoff-and-welcome-drafts.md
MarkdownReviewable communication drafts without assumed booking or sending.
Include: participants · time_zone · proposed_slots · agenda · welcome_draft · unresolved_questions
Check the result
- Reconcile every promised deliverable against an explicit source or unresolved-item entry.
- Check that agreement revisions, customer IDs and contacts all belong to the same engagement.
- Verify that completed actions have external receipts and that failed actions did not already complete.
- Confirm that delivery acceptance, calendar booking and customer attendance have distinct statuses.
When something goes wrong
Agreement or call notes are unavailable
Create a partial packet listing the missing records and their owner. Do not reconstruct commitments from memory.
Another operator changes the deal mid-run
Compare the new record version with the snapshot and recheck readiness before applying remaining actions.
One system write fails
Retain successful action receipts, query the failed destination for possible completion, and resume only the unresolved step.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: prepare the handoff for deal D42 at its approved transfer milestone.
Inputs
The approved scope covers 18 seats and two training sessions. A call note asks for a third session but has no approval. The receiving owner is assigned; no kickoff event exists.
Expected result
Create one handoff for D42 with 18 seats and two agreed sessions. Record the third-session request as unresolved, prepare an agenda and welcome draft, and leave scheduling pending if sending invitations was not authorized. A repeated trigger reuses this packet.
Run a small pilot
Start small
Try one delivery team and a small set of won deals, including an amendment, missing owner and repeated trigger.
Record the baseline
Measure preparation time, first-kickoff delays and commitments the receiving team had to rediscover.
Agree success criteria
Agree acceptable completeness and correction levels before expanding; require zero duplicate customer invitations in the trial.
Stop or revise
Pause applied actions if disputed promises are presented as agreed or account records are mixed.
Keep the scope clear
- Do not change commercial terms, provision access or promise delivery dates as a side effect of preparing the handoff.
- Treat customer-specific communication and attachments according to the account’s existing access rules.
- Keep the output as a proposed operational transfer until the responsible owner accepts it.
Check before using
The account and delivery owners reconcile commitments, confirm readiness and approve any customer-facing message or booking.
Business activities
- Run sales conversations and proposals
- Onboard customers, partners, and members
- Deliver recurring client work
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Won-deal record · Approved agreement and sales notes · Delivery owner and onboarding checklist
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow