The handoff meeting is where context gets lost, or doesn't. This gives the receiving team everything they need without a separate round of “wait, can you re-explain the deal.”
Customer
[Customer name]
Internal record links: [CRM record, contract, shared drive folder]
Internal record links: [CRM record, contract, shared drive folder]
| Information | Description |
|---|---|
| Hand-off date | [date] |
| Kick-off date | [date] |
| Go-live date | [date] |
| Team | Sales: [name] · Implementation/Onboarding: [name] · CSM: [name] · Product: [name] |
| Primary client contact(s) | [name, title, email] |
| Products / scope | [what was sold] |
| Price | [contract value] |
| Fee structure | [one-time, recurring, usage-based] |
Notes
Capture anything else the receiving team needs that a form field wouldn't catch, tone of the relationship, a promise made during the sale, a sensitivity to flag.
Why did they choose us?
[The actual reason, not the generic answer, this shapes how the receiving team should frame value going forward.]
Company culture
[Anything about how this customer operates, communicates, or makes decisions that the next team should walk in knowing.]
Did any key contacts complete a demo?
[Who saw the product live before signing, and what resonated, it tells you what to reinforce during onboarding.]
A handoff meeting without this filled out ahead of time turns into the receiving team re-asking the customer questions sales already answered, which reads as disorganized on day one.