Put the agreement and the client outcome side by side
Identify the project, delivery owner, accepted proposal and any later confirmed changes. State the first deliverable and what must happen before it can begin. Include a reference to the full agreement rather than treating the summary as its replacement.
Capture the client outcome separately from the contracted work. A company might want a website to explain a new service while the agreed deliverables are four service pages. The wider goal gives context; it does not add deliverables by itself.
Find promises outside the main proposal
Review the relevant notes and messages for exceptions, such as an additional workshop or a different review process. Give each its own entry, source and delivery implication. A confirmed commitment, a client request and an option raised in conversation need different labels.
If accounts conflict, include both references and ask the responsible person to resolve them. A later draft is not automatically a replacement for an accepted agreement. A salesperson's recollection remains a recollection until it can be checked.
- Link the accepted scope and confirmed changes.
- Record each unusual promise, its source and effect on delivery.
- Assign unresolved questions before anyone commits to a schedule.
What Harbor Field can start with
Harbor Field and all people and records in this example are fictional. Its accepted proposal covers four service pages, and a later email confirms an extra discovery workshop within the fee. Delivery can plan for both. A second-language request has no recorded decision, so it stays open.
The delivery lead also needs the client to name the content approver. The person who joined the sales call is not automatically that approver. The original worked brief keeps the five source-linked entries as a supplement.
Review the handoff with the person receiving it
Walk the delivery lead through the brief. Ask them to locate the accepted scope, explain the exceptions and identify remaining questions. Record who reviewed it and what remains unresolved. If a source is inaccessible, use the existing approved access process rather than copying private correspondence into a broadly shared file.
At kickoff, confirm the first deliverable and review responsibilities. If the client has a different understanding, record the disagreement and return it to the person authorized to resolve it.
Preparing the brief with Areinum
Areinum Assistant can help organize the available information into a brief and list statements that need checking. Sales and the delivery lead still need to verify the records and agree on the handoff.
See the example
Sales-to-delivery handoff brief
Harbor Field, the people, source references and commitments in the worked brief are fictional.
| Topic | Handoff statement | Decision state | Source reference | Delivery implication | Owner | Next action |
|---|---|---|---|---|---|---|
| Agreed work | Four service pages for Harbor Field | Confirmed in fictional accepted proposal | Example: accepted-proposal-v3.pdf, section 2 | Plan delivery around four pages | Mina, delivery lead | Review page list with sales |
| Client outcome | Explain the new maintenance service clearly | Confirmed discovery note | Example: discovery-notes.md, 2026-10-12 | Use as context for content questions | Mina, delivery lead | Confirm wording at kickoff |
| Sales exception | One extra discovery workshop is included | Confirmed in fictional email | Example: email from Theo dated 2026-10-16 | Include workshop in delivery schedule | Theo, sales owner | Link confirmation for delivery |
| Additional request | Client asked about a second language | Open request; no agreement recorded | Example: sales-call-note dated 2026-10-14 | Do not schedule language work yet | Theo, sales owner | Clarify request and route scope decision |
| Approval contact | Content approver has not been confirmed | Unresolved | Example: kickoff agenda, open question 1 | Content review process needs confirmation | Mina, delivery lead | Ask client to name responsible approver |
- Replace the fictional project and source references. Keep one row for each promise, exception or unresolved dependency.
- Check each summary against its linked source and keep request, discussion and confirmed agreement distinct.
- Have the receiving delivery owner review the brief with sales, then record the review date and outstanding actions in the project record.
- Use the open items at kickoff. Route any new or conflicting scope through the responsible decision-maker before scheduling it.
Limits of this method
- A handoff summary cannot settle conflicting agreements or replace the original records.
- This brief covers transfer after a sale. Ongoing promise tracking and proposal review are separate workflows.
Questions you may have
Should sales hand over every email?
No. Link the relevant proposal, decisions and messages, and keep the full history in its normal restricted location.
What if the only record of a promise is a salesperson's memory?
Record it as a recollection, identify what it might affect and seek a supporting record or explicit clarification.
When is the handoff complete?
When the receiving lead has reviewed the brief, can access the necessary sources and understands what remains open. Sending the document alone does not show that review happened.
Sources and further reading
- Our sales to onboarding handoff currently depends on people remembering stuff, r/CustomerSuccess
A practitioner describes onboarding reconstructing sales promises, stakeholder context and next steps from notes or conversations. The post describes one person's experience.
The author's identity and role are not independently verified; the post does not establish an improvement from this brief.
A practitioner describes onboarding reconstructing sales promises, stakeholder context and next steps from notes or conversations.
Opened during drafting. The author's identity and role are not independently verified. Comments do not prove benefits or validate this brief, and relative display dates were not used to infer publication dates.
2026-10-18
The demo is in English. Access may need to be arranged.
Explore the demo