Sales to CS Handoff Playbook 2026

The trigger is the CRM stage change to closed-won — no form for the AE to fill in, because forms don't get filled the week of a close. The record carries what sales already captured:

• Contract & plan — what they bought, seats, term, start date.
• Promised use cases — the problems this deal was sold to solve. If these aren't a CRM field yet, make them one; it's the single highest-value line in the whole brief.
• Stakeholder map — champion, economic buyer, the skeptic who almost killed the deal.
• Sales call notes — objections, competitors considered, timeline pressure.

The payload lands in #cs-handoffs as a formatted brief and the account gets its CSM assigned in the thread. Public-by-default matters: the CS lead sees every incoming account and its context, unclaimed handoffs are visible, and six months later the thread is the archaeology record when someone asks "what were they actually promised?" The AE's only job is to answer questions in-thread during week one — a far lighter lift than a live handoff meeting per deal, and it leaves a paper trail.

The CSM runs kickoff within seven days of close — tune the window to your motion, but put a number on it and track it. Because the brief already answers "what did you buy and why," kickoff starts at "here's the plan to get you live," not "tell me about your business." Set three things in the room: the first-value milestone in the customer's words, who on their side owns setup, and the date of the next working session. Momentum is the deliverable.

From the first event, watch the account against its cohort and emit the fields the checkpoint reads: days to first value, seats active versus seats sold, activation percentage against your milestone list, and momentum compared to accounts that onboarded successfully. The baseline captured in these 30 days becomes the account's healthy reference for the rest of its life — the renewal radar and churn plays all grade against it later. Day zero is when "normal for this account" starts being defined.

One question, read from the data: is this account moving like your healthy cohort did at the same age? Day 14 is the default because it's late enough to be fair and early enough to fix — a stalled account at day 14 has lost a sprint; at the first QBR it has lost the habit. On-track accounts continue to first value with no intervention; the play's job for them was making sure nobody had to check manually.

A day-14 stall is almost never laziness — it's a blocker: IT hasn't provisioned, the champion got pulled onto something, the promised use case turned out to need an integration nobody scoped. The CSM takes the specific gap from the data (seats sold but never activated, milestone one untouched) to the champion and rebuilds the plan around whatever the real obstacle is. Log the blocker category; after a quarter, the pattern tells you what your onboarding actually breaks on.

The play closes when the account hits its first-value milestone inside 30 days — or explicitly misses. Track outcomes per lane: how many on-track accounts stayed on track (if they didn't, day 14 is checking the wrong things), how many stalled accounts recovered after the re-plan, and which blocker categories keep recurring. Feed the recurring ones back to sales — some "onboarding problems" are really deals sold a use case the product needs help delivering.