Sales to implementation handoff
Everything the next team needs to know about this customer, recorded once, so the kickoff call is about their timeline rather than a recap of yours.
Record it in this order
Who they are and what they bought, camera on
Two minutes, in your own words. Company, team size, the deal shape. Tone matters here: implementation needs to know whether this account is enthusiastic or nervous.
The problem they are actually solving
Not the feature list. The thing that was broken enough for them to buy. This is the context that never survives a CRM field.
What you promised, on screen
Walk the proposal or the notes. Say plainly what was committed to and what was left vague, because the vague parts are where implementations go wrong.
Their environment and constraints
Existing tools, integrations, security review, whoever the internal blocker is. Show the account setup if it already exists.
The risks you would flag
The champion who might leave, the department that has not agreed yet, the deadline nobody wrote down.
Why record instead of a handoff meeting
- Implementation watches it before the call, so the call is about plans instead of recap.
- The written guide alongside gives them something scannable to re-check in week three.
- Whoever joins the account later gets the original context, not a summary of a summary.
- You record it once at the point you actually have the context, rather than reconstructing it a week later.
What to annotate afterwards
- Blur pricing, contract terms, and anything from the CRM that should not travel further.
- Add a warning callout on each risk, so they are impossible to skim past.
- Keep it private to the workspace. This one is never a public link.
Keeping it useful
Comments on a Team plan turn the handoff into a thread: implementation can ask a timestamped question rather than booking a follow-up. Related: sales and implementation.