The Lab is live. 15 essays from the frontier of AI-native GTM.

Read
System
/
Skills
/
Sales Handover

Sales Handover

On Friday the account belongs to the rep who made every promise in it. On Monday it belongs to a CSM working from a summary. This skill turns closed-won deal state into the customer's starting state without the loss: goals, commitments, stakeholders, pricing context and known risks, mapped through an owned handover schema and your Products, Persona, Pricing, Customer Outcomes, Onboarding and Escalations memories. The rep vouches for each commitment before it carries, the CSM starts onboarding from what was actually sold and promised, and when churn later traces back to a handover gap, the handover requirements change, and the new requirement carries a version number.

Used across

Sales

Customer Success

Referenced by

Sales Handover

Onboarding

Applies

Products

Persona

Pricing

Customer Outcomes

Onboarding

Escalations

Sales Handover Skill Hero
Sales Handover·3 HANDOVERS IN FLIGHT TODAY
Handing over Elmswell…
TriggerClosed won · Elmswell Group · $200K
Live stateReading Deal State · commitments, people, terms
Applying skillRunning Sales Handover v3
Maps closed-won state onto the handover schema
Carries goals, stakeholders and pricing context
A support commitment exists only in a transcript
Success metric promised, target never recorded
Reference memoryAgainst Products · Pricing · Customer Outcomes · Onboarding
ActionHandover written and vouched, commitments logged for CS
Skill
Sales Handover
v3v4
Sales HandoverElmswell commitments vouched
See the capability Run 9 times today
Upgrade proposed
Transcript-only commitments held until the rep vouchesv4
7 of 21 commitments were found only in transcripts.
Approve upgrade to Sales Handover?
The current way > AI added on > AI-native

The deal becomes a customer

What sales learned is worth most in the weeks right after close. That is also when most of it disappears.

01 | The Current Way

02 | AI Added On

03 | AI-Native

A deal closes and the account moves to a CSM

Whatever the rep remembers

The rep writes the handover from memory between other deals. The call runs half an hour, and a promise from month two rarely makes it in.

Eight months compressed to highlights

A generated summary keeps the loudest threads and drops quiet commitments, because nothing tells it what a complete handover must contain.

The account arrives with its promises

The CSM receives goals, stakeholders, commitments, pricing context and risks in one structure, each confirmed by the rep before it carries.

The kickoff call is on the calendar for Thursday

Onboarding opens with re-discovery

The CSM asks the customer to restate goals sales already captured. Stakeholders repeat themselves; the relationship opens with an apology.

The kickoff inherits a paragraph

A summary cannot say which success criteria won the deal or which risk needs watching first, so the plan gets rebuilt by asking again.

Onboarding plans against known goals

The CSM runs the kickoff from success criteria, stakeholders and risks mapped to your Onboarding memory. The first call looks forward.

Referenced by

Capabilities that run this skill

Sales

Sales Handover

+
SEE HOW IT WORKS

Customer Success

Onboarding

+
SEE HOW IT WORKS
The Platform

One system that understands, decides, acts and learns.

Every GTM signal flows through an AI-native operating layer into a system that runs on the surfaces your team already uses.

Explore the GTM System →
GTM Data & Knowledge
CRM · Emails · Calls · Marketing · Product · Support · Documents · Research
AI-Native Operating Layer
Context · Memory · Skills · Agents · Decision Traces
AI-Native Sales System
Understand
Deal State
Qualification
Stakeholders
Risk
Decide
Pipeline Review
Forecast
Meeting Prep
Prospecting
Act
Follow-up
Next Steps
Updates
Escalation
Learn
Upgrade ICP
Upgrade Prospecting
Upgrade Sales Process
Upgrade Messaging
Surfaces
CRM · Slack · Teams · ChatGPT · Claude · MCP · API
Output
Briefings · Artifacts · Alerts · Recommendations · Approvals · Actions

SEE WHY REVOPS + MARKETING LEADERS CHOOSE REVENUE LABS

The GTM teams that learn fastest will win. Build yours a system that learns.

An advantage competitors cannot buy back: years of success and failure, codified.

FAQ

What buyers ask

If it's not here, we'll answer it live.

Talk to us
What should an AI sales-to-CS handover include?

The commitments made, the goals the customer bought against, the stakeholders and their roles, the pricing context and the known risks. Here the handover schema makes that list explicit: every field filled with evidence or named as a gap, and commitments carry only once the rep has confirmed them.

How do you preserve deal context after close?

By mapping it into the record customer success runs on, at close. Everything the deal established becomes the customer's starting state through your Products, Persona, Pricing, Customer Outcomes, Onboarding and Escalations memories, with the rep confirming commitments and sensitive context first.

Is this the handover Meeting Booked Analysis covers?

It guards a later boundary than Meeting Booked Analysis, which carries prospecting context into sales when a meeting books. By close the stakes have grown: months of commitments, stakeholders and pricing history must become a customer record, and whatever drops surfaces as next year's churn story.

What teaches the handover?

Onboarding and churn outcomes teach it. When Churn Analysis traces a loss back to a promise that never crossed the boundary, the handover schema gains a requirement, approved by the sales and CS leads who own it, and every later handover checks for what that one missed.

Which parts stay human?

Commitments and anything sensitive. The rep signs off what was promised before any of it enters the customer's record, the onboarding and escalation standards it maps to belong to the CS lead, and it is the CSM who opens and words every conversation with the new customer.