Business practice
Customer retention.
See an account going quiet while there's still time to do something about it. We help SaaS and AI companies with 20 to 200 people reduce churn and protect renewals, starting from the accounts you've already lost and ending with a review cadence your team owns.
Customers almost never announce that they're leaving. They go quiet, the QBR gets pushed twice, and then the non-renewal notice arrives.
By that point the decision was made months earlier, usually over something small. A sales-to-CS handoff nobody explained. An escalation that sat for three weeks. A question support answered one way and success answered another. None of it showed up in the numbers, because logo churn and NRR tell you what already happened, not which account is cooling now. And you're usually already paying for the people who could see it coming: in SaaS Capital's 2026 benchmarks, the median private B2B SaaS company spends 9% of ARR on customer support and customer success. The signal is usually sitting with those teams already.
The position worth reaching is one where the signal arrives early enough to matter. You know which accounts are cooling and why, the handoffs that used to cost you customers are documented and owned, and the review that catches the next one happens on a schedule rather than when someone remembers. Customer retention stops being a matter of hoping and becomes a matter of noticing.
The approach
Find it, fix it, watch it.
Find the exit.
Churn clusters. It happens at the same few points in the customer lifecycle, and you can find those points in the accounts you've already lost. The work starts with the losses you'd rather not revisit, because that's where the pattern lives.
Fix the handoff.
Most churn in SaaS is a handoff failure wearing another costume. Sales to implementation, implementation to CS, one CSM to the next, support back to success. Each transition is a place where a customer quietly reassesses whether they're still getting what they were sold.
Watch the signal.
The information that predicts churn already exists inside your company. Usage tapering off, escalations climbing, a champion who stops coming to the QBR, a new name from procurement copied on every email. It goes unused because nobody owns looking at it on a rhythm. That rhythm is the deliverable.
Recognize this
The churn that surprised you wasn't sudden.
- A customer left in the last year and the team still isn't sure why.
- Nobody can say what a new customer's first 90 days is supposed to look like.
- The experience visibly depends on which CSM the account happens to get.
- Expansion from your longest-standing accounts has thinned, and nobody has named the reason.
- Renewal conversations start late and feel awkward, every time.
The work
Four workstreams, in sequence.
Retention diagnostic
A structured review of the customer journey from the first sales call to renewal, checked against the accounts you actually lost and the ones that renewed smaller. You end up with a small number of named exit points rather than a general sense that service could be better.
The first 90 days
Customer onboarding redesigned around time to first visible value. Customers decide how they feel about a vendor early, and a strong opening buys tolerance later, including at renewal. It's usually the highest-return change on the list.
Handoff repair
Each transition documented with what gets communicated, by whom, and how the customer is told. The customer should never be the one who discovers a handoff happened, and at most companies they are.
The retention cadence
A short, scheduled review with a named owner and a small set of signals, so a cooling account surfaces while there's still time to act, not at the renewal. This is the workstream that makes the other three permanent.
Track record
This work has a history.
50%
Reduction in customer churn
50%
Faster customer onboarding
Sal Cervantes' documented results from operating roles before this practice, across 14+ years in SaaS customer operations, built with the same diagnostic and handoff work described above. They come from those roles, not from client engagements.
Related reading.
All insights
Retention
The six questions that find churn before it finds you
Churn in a SaaS company almost never looks like a decision. It looks like a slow drop in contact, a QBR that keeps getting rescheduled, a champion who stops replying, and then a non-renewal notice that arrives as a surprise to everyone except the customer.
Operations
The two-person dependency test
Every SaaS company has them. Two people, sometimes one, who hold a process together through memory and habit. They're usually excellent, they're usually loyal, and they're usually the reason nobody has ever needed to write the process down.
Questions
Asked before, answered plainly.
Often more so. Companies with strong retention usually hold it through a few individual relationships rather than anything written down: the founder who still takes the biggest accounts' calls, the CSM every customer asks for by name. That works until one of those people moves on. The work here turns personal relationships into company relationships, which is also what an investor or acquirer wants to see behind your NRR.
Almost nobody does, and cancellation surveys are rarely honest anyway. The reconstruction comes from what already exists: product usage, ticket history, email threads, QBR notes, billing changes, and the memory of the people who worked the account. That's usually enough to find the pattern, and the pattern matters more than any single case.
No. NPS and satisfaction surveys tend to be answered by the customers least likely to leave, and a customer on the way out rarely tells you the truth on a form. This work looks at behavior rather than stated sentiment, because behavior changes before an opinion ever gets said out loud.
Usually not. The signals are typically already in your CRM, your support desk, your product analytics and your billing system. Part of the work is an audit of what your existing tools already do, which regularly turns up health scores and reports you're paying for and not using. See process and workflow for how that assessment runs.
Retention work is often what a 30-Day Proof ships. The onboarding sequence, the sales-to-CS handoff, or the retention review can each be built and running inside 30 days with a measured before and after. If retention is your named concern, that's the natural place to start.