There's a moment every Customer Success Manager recognizes.
You're on the kickoff call with a customer Sales just closed. The customer is asking about their original use case, their stakeholders, their timeline. And you're trying to answer without revealing that you're piecing it together in real time.
One CS leader put it bluntly on Reddit:
"It looks bad on our kickoff calls with customers when we are lowkey fishing for the insights the sales team should have already gotten us."
That isn't an edge case. That's the default state of Sales-to-CS handoffs at most B2B SaaS companies. And the damage it creates stays invisible until three, six, or nine months later, when customers churn at rates nobody can explain.
This post is about why that happens, what it actually costs, and which fixes work versus which ones just look like work.
The handoff is broken by design, not by accident
The problem isn't that your AEs are bad at their jobs. The problem is that the system rewards them for closing, not for retention.
Sales commission is tied to bookings. Customer Success is measured on renewals, upsells, and NPS. Over the long run these goals align. In the short run of any individual deal, they pull in different directions.
An AE who spends three hours documenting nuanced context for a handoff is an AE who isn't closing the next deal. One CS professional on Reddit described the incentive gap directly:
"They don't seem to care about churn. It's all new revenue for them. If they fuck up and the fix doesn't increase revenue, they don't care."
The other problem is structural. CS inherits an entire customer relationship through a 15-minute handoff call, if they're lucky. Sometimes it's a Slack message with a Zoom link. Sometimes it's a meeting that gets rescheduled three times.
Either way, CS is expected to reconstruct months of sales conversations, stakeholder dynamics, and technical requirements from a fraction of the context the AE actually had.
Most companies try to fix this with a 20-question discovery document. AEs are supposed to fill it out before deals close. They rarely do, at least not thoroughly. And when they do, the answers are often generic enough to be meaningless.
"Customer wants better reporting" is not the same as "VP of Finance can't justify renewal to the CFO because reporting doesn't show ROI in board format, evaluating alternatives in Q2." But that's the quality of signal most handoff forms actually capture.
What "broken handoff" actually looks like
Before the downstream damage shows up, there are specific patterns that repeat across companies. If any of these sound familiar, your handoff is already costing you money.
-
Double-discovery as standard practice. CSMs run an internal kickoff call to do discovery on the salesperson, before they can do discovery on the customer. The time this consumes across hundreds of deals per year is enormous.
-
Gong recordings as last resort. Some CSMs now spend 1-2 hours per complex deal watching recorded sales calls before kickoff, because the handoff doesn't surface what matters. This doesn't scale. No CSM can watch every recording of every deal in their book.
-
Different stakeholders, different expectations. The signer isn't the user. The evaluator isn't the champion. The champion isn't the economic buyer. Sales calls surface these dynamics, but handoffs compress them into a single "point of contact" field in Salesforce.
-
Promises that don't match the contract. AEs make verbal commitments in the last week of the quarter. Some are reasonable. Some are aspirational. Some are outright wrong. CS inherits all of them, and the customer judges success against what they heard, not what was signed.
The cost isn't a single number. It's compound: delayed onboarding, renegotiated expectations, earlier-than-expected churn, and a layer of constant rework that never gets line-itemed on anyone's budget.
The data is there. Nobody's connecting it.
Here's the thing most CS and RevOps leaders already know but rarely say out loud: the information needed to fix handoffs already exists in your company's tools. It's just scattered across systems that don't talk to each other.
Each tool owns a slice of the story:
- Your CRM has deal stages, close dates, contract values, and whatever fields the AE filled out.
- Your call intelligence platform (Gong, Chorus, Clari) has the actual sales conversations.
- Your NPS tool has early satisfaction signals.
- Your CS platform has usage data, health scores, and churn records.
Each system knows part of the story. None of them knows all of it.
This is exactly the pattern we surfaced in one of our use cases. A sales leader suspected something was off about retention but couldn't pinpoint the cause. When we connected the CRM, the NPS platform, and the churn records, a clear pattern emerged:
Customers acquired by one specific AE were churning at 62% within 90 days, compared to 18% team average. Deal sizes were 40% smaller. NPS scores were significantly lower. The pattern had been consistent for 90 days.
This wasn't a single bad deal. It was a systematic problem in how one AE qualified prospects and handed them off to CS. And it was invisible because the data lived in three different tools, and no single report could cross-reference acquisition source with customer lifetime value.
Why forms and process fixes don't work
Most companies try to fix broken handoffs by adding more process. Required CRM fields. Handoff templates. Mandatory kickoff calls. In theory, these create accountability. In practice, they create theater.
Required CRM fields produce garbage data. If an AE has to fill out 20 questions to close a deal, they will fill them out. But the content will be whatever gets past the validation rule. "Competitor concern" becomes "Yes." "Decision criteria" becomes "Price and features." The field is populated, the process is followed, and the signal is worthless.
Handoff calls create the illusion of knowledge transfer. A 15-minute call can surface the top three things the AE remembers. It can't surface the things they didn't think were important but turn out to matter, the things they forgot, or the things they never knew because the customer didn't tell them directly.
Gong recordings are useful but don't scale. One CSM might watch every call for their top accounts. No CSM can watch every call for their full book.
The deeper issue is that no single system owns the full journey from first contact to renewal. Each tool owns a slice. The human operator, usually the CSM, becomes the integration layer between those slices. At small scale, that works. At scale, it breaks.
What actually fixes broken handoffs
The fixes that work share one characteristic: they change the system, not just the process layered on top of it.
1. Tie Sales compensation to retention
If AEs are measured only on bookings, they will optimize for bookings. If some portion of their commission is tied to 90-day or 12-month retention, they will start caring about handoff quality. Clawbacks on churned customers work. So do accelerators tied to expansion revenue. The specific mechanism matters less than the signal it sends.
2. Create a shared system of record across Sales and CS
Not another form. A living model that connects deal data, sales conversations, onboarding milestones, and retention outcomes. When CS can see the full journey of every account from first touch to current state, and when Sales can see what happened to every deal they closed after handoff, both sides start behaving differently.
3. Auto-flag patterns, not individual deals
A single bad handoff is a coaching conversation. A systematic pattern across 90 days is a structural problem. Most CS teams catch the first and miss the second. Systems that detect cross-deal patterns (by AE, by deal size, by customer segment) surface the problems that matter at the scale they matter at.
4. Monitor the gap between promise and delivery
What did the customer hear on the sales call? What does the contract say? What is the customer actually using in the product? When these three diverge, you're watching churn form in real time. Most companies only discover the divergence at renewal.
5. Build early warning signals, not late diagnostics
The difference between a CS team that prevents churn and one that reports on it is where in the timeline they catch problems.
| Catch at | Cost | Actionable? | | --- | --- | --- | | Renewal (month 12) | Already lost the customer | No | | Health score decline (month 6) | Expensive rescue effort | Sometimes | | Usage drop (month 3) | Still recoverable | Yes | | Sales to CS handoff (week 1-2) | Fixable before anything breaks | Absolutely |
This is what operational intelligence platforms like Nerra AI do automatically. We connect your CRM, sales call platform, NPS tool, and CS system, and surface exactly these patterns without anyone having to build reports.
But even without a tool, the starting question is the same: who in your company can see the full journey from deal close to 90-day retention? If the answer is "no one," that's the first problem to solve.
The 90-day test
Here's a diagnostic you can run on your own company without any new software.
Pick the last 30 new customers. For each one, track:
- The closing AE
- Days from contract signing to kickoff call
- NPS score at day 30
- Feature adoption rate at day 60
- Renewal status (or churn risk score) at day 90
Cross-reference the results. You will almost certainly find patterns: specific AEs whose customers consistently underperform, specific deal sizes where handoff quality drops, specific customer segments where the gap between sold and delivered is widest.
Most CS leaders know these patterns exist. Very few have the data to prove them in a way that gets Sales leadership to change behavior.
Closing that gap is the whole ballgame.
If you want to see how Nerra AI detects these patterns automatically across your stack, read how one sales leader exposed a 62% churn pattern that was invisible to their CRM.