Sales-to-CS handoff

Compiles the sales-to-customer-success handoff pack when a deal closes — commitments made during the sale, stakeholder map, success criteria, timeline promises, pricing terms, and open risks — from opportunity history in Computer. Use when a deal closes-won, when the user mentions onboarding handoff, kickoff prep, "what did sales promise," or a CSM asks for context on a new account.

The most expensive sentence in SaaS is "sales never told us that." The customer told you everything — in threads, calls, and the proposal — and then the knowledge walked out of the deal. This skill makes the handoff a compilation problem instead of a memory problem.

When to run

  • An opportunity moves to closed-won (recommended trigger), or a CSM asks for account context
  • "Prep the kickoff for Acme" / "what was promised in this deal"

Computer scopes

  • CRM: the won opportunity, contacts, products, terms
  • Email + meeting notes: full deal-cycle threads and call summaries
  • Docs: proposal, order form, mutual action plan, security review artifacts

Workflow

  1. Anchor on the won opportunity; collect the full deal-cycle record set.
  2. Extract commitments: every promise of functionality, timeline, service level, or pricing concession — quoted verbatim with source and who made it. Distinguish contracted terms from conversational promises; both matter, label them differently.
  3. Build the stakeholder map: champion, economic buyer, blockers-turned-supporters, and who actually shows up to meetings, with influence notes from the record.
  4. State success criteria in the customer's own words — what they said "good" looks like.
  5. List open risks: unresolved objections, competitor still in the building, security follow-ups.
  6. Assemble the pack and propose the first-30-days checklist derived from the commitments.

Guardrails

  • Autonomy: L0. Compiles and drafts; never contacts the customer.
  • Verbatim means verbatim — commitments are quoted, cited, and never paraphrased into something stronger than what was said.

Output

Handoff pack: account snapshot → commitment ledger (contracted vs. conversational) → stakeholder map → success criteria → risks → proposed 30-day checklist. Doc export for kickoff.

Eval fixtures

  • Set: 25 sandbox deal cycles with a seeded gold list of commitments (including 5 subtle ones buried in threads) and stakeholder ground truth.
  • Rubric: commitment recall (especially the buried ones), verbatim fidelity, correct contracted/conversational labeling, stakeholder map accuracy.
  • Ship gate: commitment recall ≥ 0.9; zero over-promised paraphrases.

Run sales-to-cs handoff on your own data.

Language

Certified Secure

secure