Most SaaS companies train their CS teams on the product. Almost none train them on the conversation. Here’s why that gap is costing you customers.
A SaaS company (bootstrapped) came to me with a churn problem they couldn’t explain. Their product worked. Their CS team was excellent. Their NPS was decent. But customers were quietly leaving at renewal — and nobody could pinpoint why.
When I sat down with their CS team and listened to their kickoff calls, the problem was obvious within five minutes.
They were running product tours disguised as onboarding calls.
Every call followed the same pattern: brief introduction, rapid-fire feature walkthrough, documentation sent, next call booked. Efficient. Friendly. And almost entirely useless from a retention standpoint.
Nobody was asking why the customer bought it.
Nobody was finding out what was personally at stake.
Nobody was defining what success looked like in 30, 60, or 90 days.
The CS team was setting customers up to use the product — not to succeed with it. Those are very different things.
The SaaS Retention Problem Nobody Talks About
Everyone in SaaS knows churn is expensive. The numbers are well-documented:
- Acquiring a new customer costs 5-7x more than retaining an existing one
- A 5% improvement in retention can increase revenue by 25-95%
- Most SaaS companies lose the renewal decision in the first 90 days — they just don’t find out until month 11
What’s less discussed is where the retention problem actually lives. Most companies look at their product, their pricing, their support response times. Very few look at their CS conversations — specifically, what their CS team is saying and not saying in the critical first call with a new customer.
That’s the gap retention coaching fills.
What Retention Coaching Actually Is
Retention coaching is not customer success training in the traditional sense. It’s not teaching your CS team how the product works, how to run a QBR, or how to handle a difficult customer. Your team probably already knows those things, but it can be useful to assess this to make sure
Retention coaching is primarily about changing the fundamental posture of every customer conversation, from reactive to intentional, from product-focused to outcomes-focused, from transactional to relational.
In practice, it looks like this.
You sit down with a CS rep. You listen to their calls. You identify the specific moments where the conversation drifted away from retention and towards feature explanation. You give them a framework, a set of questions, and a clear standard to meet before every call ends. Then you watch the next call, and the one after that, and you coach the gap between where they are and where they need to be.
It is specific, practical, and measurable. And done consistently, it is one of the fastest ways to move your retention numbers. FACT
What We Found on the Calls
When I reviewed the kickoff calls at this SaaS company, the same patterns appeared across multiple CS reps and multiple customers.
Pattern 1: Discovery abandoned at the first answer. CS reps would open with a good question — “why did you get this tool, what are you trying to achieve?” — and then the moment the customer gave any answer, the rep would pivot immediately to product explanation. The opening question became a formality rather than an invitation to go deeper.
Pattern 2: Nobody knew who was in the room. On one call, there were four or five people from the customer’s side. The CS rep never asked for introductions. By the end of the call, they didn’t know who the decision maker was, who the day-to-day user was, or who would ultimately decide whether to renew. That information gap is a retention time bomb.
Pattern 3: No success definition. Call after call ended with next steps — the next call booked, documentation sent, action items noted — but no agreed picture of what “working” actually looks like. Without that, the CS rep has no scorecard. And without a scorecard, the renewal conversation is a guessing game.
Pattern 4: Information from sales never made it into the call. The CRM had rich notes from the sales team — primary pain, growth targets, urgency. The CS rep had access to all of it. None of it was referenced on the call. The customer had to re-explain their own situation from scratch.
None of these are character flaws. They are present in almost Every Single Customer Success Team. They’re habits — habits formed in the absence of a clear framework and consistent coaching. They’re also completely fixable.
The Framework We (at Loyalty) Built!
Rather than give the team a generic list of best practices, we built a specific framework for their kickoff calls. We called it FACTS — five conversation zones that every CS rep needs to cover before a kickoff call ends.
F — Failure History. What broke before? Understanding why a customer struggled to solve this problem in the past tells you exactly what your product needs to deliver — and gives you the most powerful renewal story imaginable twelve months later.
A — Accountability. Who is watching this? The person on the call is rarely the only one this needs to work for. A CS rep who doesn’t know who the internal stakeholders are can’t build champions — and champions are what win renewals.
C — Consequence. What’s personally at stake? This is the question most CS reps skip because it feels uncomfortable. It’s the most important one on the call. When you understand what’s riding on this for the person in front of you, you stop being a software trainer and start being someone genuinely invested in their success.
T — Timeline and Triggers. When does this need to be real, and why? Real urgency — a board meeting, a partner launch, an internal review — is the pacing engine for onboarding. Without it, there’s no shared deadline to work towards, and activation drifts.
S — Success Definition. What does winning look like? This is where you agree on a scorecard together, out loud, on the first call. Renewal decisions are comparison exercises. If you don’t set the benchmark, the customer sets it in their head — without you.
The rule was simple: before ending any kickoff call, the CS rep must be able to complete this sentence:
“[Customer] needs [specific outcome] by [specific date] because [specific reason], and we’ll know it’s working when [specific signal].”
If they can’t complete it, the call isn’t finished yet.
What Changed — and How Fast
Within the first two weeks of coaching, something interesting happened. The calls got longer. Not because the reps were talking more — but because the customers were. Once reps stopped rushing to product explanation and started sitting in the discovery zone a little longer, customers opened up. They talked about past failures. They named internal pressures. They described what they were really trying to prove, and to whom.
That information changed everything.
One CS rep went from a kickoff call where he covered features, integrations, and next steps comprehensively, but couldn’t tell me what success looked like for the customer after 45 minutes, to calls where he was asking about internal stakeholders, surfacing personal stakes, and naming 30-day wins before the call ended.
The CSP info changed too. What had been a project checklist: calls completed, features ticked, integrations noted- became a retention record. Fields for success definition, stakeholder mapping, personal stake, agreed timelines. Information that would still be useful at renewal, not just at week two.
The pre-call preparation habits changed. Reps started reading CRM notes before joining calls. Sales handoff information that had been sitting unread started shaping opening questions. New customers stopped having to re-explain themselves.
The Metrics That Matter
Retention coaching is not a slow burn. The early indicators show up fast.
Time to first value decreases. When a CS rep knows exactly what success looks like for a customer, they stop covering everything and start prioritising what matters. Customers reach their AHA moment faster.
Activation rates improve. Customers who feel understood on the kickoff call engage more between calls. They do the homework. They pull in their Salesforce admin. They book the next call without being chased.
At-risk accounts surface earlier. When every kickoff produces a documented success definition, it becomes immediately obvious when an account is drifting. Instead of finding out at month ten that a customer doesn’t feel they’re getting value, you know at month two — when there’s still time to do something about it.
Renewal conversations get easier. This is the big one. Twelve months after a FACTS-driven kickoff, the CS rep can open the account record and say: “On day one, you told me you needed X by Y because Z. Here’s where you are.” That’s a completely different renewal conversation from “so, how’s everything going?”
Why Most CS Teams Don’t Do This
Retention coaching surfaces an uncomfortable reality: most CS teams are trained to be product experts, not conversation experts. And most CS leaders measure the wrong things — calls completed, tickets resolved, NPS scores — rather than the leading indicators that actually predict renewal.
The result is a team that works hard, genuinely cares about customers, and still loses accounts they shouldn’t lose — because nobody ever told them that the kickoff call is a retention event, not an orientation session.
Changing that requires more than a framework document. It requires someone listening to the calls, giving specific feedback, and raising the standard consistently over time. That’s what retention coaching is. And for a SaaS company with a churn problem, it’s often the highest-leverage investment available — because it costs less than a new hire, moves faster than a product change, and compounds with every call the team runs from that point forward.
