Sales to CS Handoff Playbook 2026
Start while the deal is fresh. This play puts the deal's promises on the CRM record at closed-won, gets kickoff done inside a week, and at day 14 compares the account with customers who onboarded well. On track, it's left alone with a note; stalled, the CSM gets a drafted setup session or re-plan to run.
The week a customer signs is a good week to move. The champion just went to bat internally, and your best-onboarded accounts show you what those first two weeks should look like.
This play carries the deal's promises from sales to CS on the account record, gets kickoff done inside a week, and at day 14 checks how the account stacks up against those good starts. Each account ends with a move your CSM decides on, or a note on why there isn't one.
Measure it on the share of accounts reaching first value inside 30 days, handoff-to-kickoff time, and stalled starts recovered by day 30 – and, a year on, first-year renewal rate.
How it works12 steps
01SignalLet closed-won start the play
No form for the AE to fill in the week of a close – the record already carries:
- Contract, seats & go-live: plan, seats sold, term, and the date the customer plans to start (often not the signature date).
- Promised use cases: what the deal was sold to solve. If this isn't a required field at closed-won yet, make it one.
- Stakeholder map: champion, economic buyer, admin, and anyone who pushed back.
- Sales call notes: objections, tools replaced, deadlines.
02ActionWrite the handoff brief on the account record
A workflow on closed-won writes the brief below as a note on the company record, assigns the CSM and creates the kickoff task. A Slack message to #cs-handoffs can say it's there; the record is where it lives, so "what were they promised?" always has one answer. The AE's job in week one is to answer the CSM's questions on the record.
03Human stepRun kickoff inside a week, starting from the brief
Default: within seven days of go-live. The brief already answers "what did you buy and why", so the call starts at the plan. Leave with three things on the record: the first-value milestone in the customer's words, who owns setup on their side, and the date of the next working session.
04ScoreAt day 14, compare with customers who onboarded well
Build the benchmark once, refresh it quarterly:
- Comparison customers: same segment (plan tier, size band), signed in the last 18 months, reached first value inside 30 days and are still active at six months. Aim for 20; with fewer, label it low confidence.
- First value: the milestone those customers shared – the first report sent, the first project live. Your CS lead names it.
- Their day 14: the median milestones hit, the share of seats active (default, active in the last seven days), and how recently the champion was active.
At day 14 from go-live, put the new account beside that. Say good starts had three of five milestones and 60% of seats active by day 14, and an account that bought 40 seats has one milestone and six active seats. (The numbers are illustrative.)
Run it as a saved query in PostHog, Amplitude or Mixpanel, or a spreadsheet. Under about a hundred accounts, do it by hand.
05ScoreCheck the records before calling it a stall
- Tracking complete? Every workspace sending events, users mapped to the account. Patchy tracking looks like a stall.
- Go-live date moved? Count from the real start, not the signature.
- Blocker already logged? An open IT review or SSO ticket with a date means someone is on it.
If kickoff hasn't happened yet, that's the first job: book it.
06DecisionDecide whether there's a move worth making now
On track (defaults to tune): milestones at or above the good starts' median, seats active within 20 percentage points of theirs, and the champion active in the last seven days. Also leave it alone if the records explain the gap: go-live moved, tracking being fixed, or a logged blocker with a date. Everything else is stalled.
07ActionOn track: leave it alone, and write down why
Set Recommended move to No move, write the reason in one line, and set Review date to day 30 (or the blocker's date). A check-in call on an account that's moving only costs the customer time. The leave-it-alone play covers the call in full.
08DecisionName what's in the way
- Setup: seats sold but few invited, SSO or the key integration not connected, admin tasks untouched. Setup session.
- Plan: setup is done but milestone one is untouched, or the champion hasn't been active in seven days. Re-plan with the champion.
09ActionDraft a setup session for their admin
The invite below, naming the setup steps still open, to the person who has the keys.
10ActionDraft a re-plan with the champion
The note below: the milestone agreed at kickoff, what's done, what isn't, and a new date. If the promised use case needs something nobody scoped, bring the AE back in – that's a note for sales too.
11Human stepYour CSM decides and runs the move
The CSM reads the evidence and runs it as drafted, changes it, or passes. Before acting, record the success measure and the review date: milestone one done within a week is progress; first value by day 30 is the result. Once a lane's drafts have been right for a few weeks, your team can choose to automate it – the setup-session invite is a good first candidate.
12OutcomeDay 30: review what changed, then sharpen the benchmark
On the review date, record three answers: did they reach first value, did the move help, and what else played a part? If not, change the move, stop, or give it time with a new date. From here the account moves to the onboarding-cliff play until day 90, then the weekly check. Each quarter, tally the blockers behind the stalls: the recurring ones show what onboarding breaks on, and which promises sales should change.
Setup and templates
Sources: contract, seats, go-live date, use cases and contacts from the CRM deal; milestones, active seats and the champion's last active day from a saved query in PostHog, Amplitude or Mixpanel; open blockers from support tickets. By hand: one spreadsheet row per new account, filled at kickoff and day 14. Account-level numbers need your analytics tool's account add-on (group analytics in PostHog, Accounts in Amplitude, Group Analytics in Mixpanel) and a group call in your app. Save the query, then subscribe to it (in Amplitude, add it to a dashboard and subscribe to that) so the result lands in your inbox or Slack on the schedule you set.
Company properties in HubSpot (Starter or above; free HubSpot allows 10 custom properties in total), or your CRM's account object:
| Property | Type | Filled by |
|---|---|---|
| Promised use cases | Single-line text | AE at closed-won |
| Go-live date | Date picker | AE, confirmed at kickoff |
| First-value milestone | Single-line text | CSM at kickoff |
| Kickoff date | Date picker | CSM |
| Milestones vs good starts | Number (% of benchmark) | Day-14 check |
| Seats active vs sold | Number (%) | Day-14 check |
| Champion last active | Date picker | Day-14 check |
| Recommended move | Dropdown select: Setup session · Re-plan with champion · No move | Day-14 check |
| Move reason | Single-line text | Day-14 check |
| Success measure | Single-line text | CSM |
| Review date | Date picker | Day-14 check, then CSM |
| Review result | Dropdown select: First value by day 30 · First value, late · Not yet · Stopped | CSM |
The automation here uses HubSpot workflows (any Professional hub). On Free or Starter, run the same saved view and create the tasks by hand. Two saved views: new accounts (Recent deal close date is less than 14 days ago, Kickoff date is unknown; on Salesforce, a report on opportunities) and this week's list (Recommended move is known and Review date is this week or overdue). In HubSpot that's two filter groups: Review date is This week, or Review date is before Today. Closed-won creates "Kickoff: [company]" for the CSM; each move creates "Handoff: [move]" with the draft in the body. Build the handoff workflow on companies (trigger: an associated deal is closed-won) so the note lands on the company; the brief's fields come in as tokens from the deal. Slack messages come from a HubSpot workflow (Professional or Enterprise) with the HubSpot Slack app; add the app to any private channel.
Handoff brief (note on the record): bought [plan], [seats] seats, go-live [date] · promised: [use cases] · champion [name], buyer [name], admin [name] · watch for: [objections, tools replaced, deadlines] · AE: [name].
Setup session (to the admin):
Hi [name] – [company] has [seats] seats, and [invited] people are in so far. [Setup step] is the step that gets the rest of the team going. Would thirty minutes this week help? We'll do it together.
Re-plan (to the champion):
Hi [name] – at kickoff we set [milestone] by [date]. [What's done] is done; [what isn't] hasn't started. What's getting in the way? If it helps, let's pick a new date and I'll take [task] off your plate.
No move: "No move – [reason]. Recheck [date]."
How Accoil fits
Accoil is a customer-success consultancy with our own tooling, and this is a play we run with you, not for you. We build the benchmark from your customers who onboarded well with your team, and you approve it. Every week we check the new accounts in the agreed segment that reach day 14, and the recommended move and its evidence land on the account record in your CRM – we recommend HubSpot – at a pace your team can actually run. Your team makes every call. Nobody from Accoil contacts your customers. After the agreed window we review what changed together, and you keep the playbook, the benchmark and the analysis.
Running it yourself? Swap HubSpot for Salesforce or Pipedrive. The play stays the same. On Salesforce, the field writes need API access (Enterprise and up, or an add-on on Professional). On Pipedrive, automations and date triggers need the Growth plan.
Thirty minutes with Kate, Simon or Peter on one example segment: what a successful customer looks like, where the gaps are, and whether there's work worth doing this quarter.
Talk to a founder →Keep reading
Onboarding Cliff Rescue Playbook 2026
Your best customers show you what the first 90 days after go-live look like. This play checks every new account against them at the same stage each week, confirms the slip is real, and puts the move on the account in your CRM: an unblock call on the missed step, a note for the champion, a self-serve nudge – or no move, with the reason noted.
Trial Activation Playbook 2026
Your converted customers show you what a good first week looks like. This play checks every trial against that pace each day, confirms a trial is really stuck before anyone acts, and puts the move on the account in your CRM: personal outreach for high-fit trials, an unblock message or check-in your team chose to automate – or no move, with the reason noted.
Support-to-Expansion Goldmine Playbook 2026
When a customer asks support for a higher limit or a missing feature, they have written down what they want to buy. This play catches the tagged ticket, compares the account with your successful customers, and puts the move on the account in your CRM with the ticket attached: an upgrade conversation, an add-on or seats offer – or no move, with the ask passed to product.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.