Sales To Cs Handoff

CS Handoff

Design the process that moves a customer from the seller who won them to the owner who keeps them. Lincoln Murphy's diagnosis frames the stakes: "Customers hate three things: surprises, uncertainty, and repeating themselves" - and a poor handoff delivers all three before the customer's first call with CS. He attributes customers ghosting during onboarding "100% of the time" to a poorly designed - or not-designed-at-all - sales handoff process.

The design job has six decisions:

• The trigger event and its gate.
• The required data set.
• The artifact it travels in.
• The timing clocks.
• The meeting pattern.
• An accountability chain with an explicit acceptance step.

The named canon, where it genuinely helps:

• Winning by Design's Bowtie Model places Commit at the center of one continuous revenue lifecycle - the handoff is the seam between its two halves, not the end of a funnel.
• Murphy's Desired Outcome (Goal + Appropriate Experience) defines what must transfer: the customer's actual goal _and_ the experience they need to feel successful, not just contract terms.
• Murphy's touch-level segmentation sets coverage by what a segment needs, never by what it pays.
• Kristi Faltorusso's "10 Essentials" checklist is the best-known practitioner inventory of the information that must move ("If you are aligned on all of these details, you will be set up to have a productive partnership kickoff").
• Time to First Value (TTFV, Murphy) is the clock that starts ticking at the handoff moment.

Boundaries, stated because readers expect them here:

• Not employee/new-hire onboarding - ramping a new internal hire is a different job entirely.
• Not the drafting of a single recap email.
• Not the post-kickoff onboarding curriculum or 90-day success plan - this skill's job ends when the customer is successfully received by the post-sale owner and the first-value clock is running.
• Not health scoring or churn-signal discovery (sibling skills own those), though early-life churn is a legitimate outcome measure for handoff quality.
• Not pipeline-stage redesign - closed-won entry criteria are a gating input here, taken as given.

Interview

Ask before designing. One question per message; offer multiple-choice answers where possible. Skip anything already answered.

• Which motion(s), and the segment mix? (a) sales-led enterprise/high-touch, (b) mid-market, (c) high-volume SMB, (d) PLG/self-serve, (e) B2C subscription - often several at once.
• Who exists post-sale? (a) dedicated named CSM, (b) pooled CS, (c) implementation/onboarding team then CSM, (d) no human - automated lifecycle only.
• How many closed-won deals per month, per segment? (Decides how heavy the artifact and meeting pattern can afford to be.)
• Today, how long from closed-won to kickoff (or first lifecycle touch)? Is it even measured?
• What does the CRM actually capture at closed-won today - enforced required fields, call recordings, free-text notes only?
• Is the AE compensated or held accountable past close (clawback, onboarding milestone, required intro)? This decides how much the process can ask of sales.
• Who can block or accept a handoff today? Has CS ever rejected one?
• What breaks today - customers repeating themselves, ghosting, kickoff delays, CSMs doing archaeology in old email threads?
• By when must the improved handoff be live - this quarter's closes, or next fiscal year? A hard date promotes the wiring and the live kickoff and defers the packet document.
• One-off fix, or a compounding asset? A compounding mandate promotes the acceptance step, whose reject codes only start rewriting the packet from the second quarter on.
• The effort ceiling: how many customer-success hours per handoff can the receiving team actually spend, and does CS have the standing to reject a rep's work? A low hour ceiling deletes the packet document and the internal sync; no standing deletes the acceptance step until a manager sponsors it.

Ceremony, Ranked

Five things a handoff process can buy, ranked by retention bought per hour of customer-success time. Build down the list and stop where the segment's hour ceiling runs out. The axes disagree, which is the point - the strongest rung and the cheapest rung are not the same rung.

• efficiency: wiring > live customer kickoff > internal sync > acceptance step > per-deal packet document
• value: live customer kickoff > internal sync > wiring > per-deal packet document > acceptance step
• effort (CS hours per handoff): per-deal packet document > live customer kickoff == internal sync > acceptance step > wiring

The == on effort is real: kickoff and sync each cost about an hour of the receiver's time. What separates them is coordination and reversibility, not hours - the kickoff runs against the customer's calendar and gets one attempt, which is why efficiency ranks it above the sync where raw hours cannot.

Default rung: wiring plus the live kickoff, in every segment where a human receives the customer.

• Add the internal sync when more than one internal team delivers, or when commitment-related reject codes keep recurring.
• Add the packet document only when implementation genuinely spans teams.

What this order starves: the full high-touch ceremony - packet document, internal sync, line-by-line commitments review - loses every efficiency round, because its value concentrates in the few deals that would otherwise have failed loudly while the average deal shows no return. Promote it whole, ratio ignored, when: