Use case: Retention Management
Retention isn't managed one customer at a time. It's managed at the portfolio level — with systems, not heroics.
The situation
Every CS team retains customers. The question is how. For most teams, retention is a combination of relationship management, reactive firefighting, and the personal judgment of individual CSMs. Some CSMs are exceptional at this. They know their accounts, they read the signals, they act early. Others miss things — not because they don't care, but because they're managing 60, 80, or 100 accounts and the signals that matter are buried in the noise.
The result is retention that's inconsistent, unpredictable, and heavily dependent on who owns the account. Your best CSM retains 95% of their portfolio. Your most stretched CSM retains 75%. And your business can't tell the difference until renewal season arrives.
The other problem is that reactive retention is expensive. A customer who has already decided to leave requires significant time, executive involvement, and often commercial concessions to save — if they can be saved at all. Every hour spent on a rescue conversation is an hour that could have been spent on three early interventions that prevented the problem in the first place.
Retention management at scale requires a system. Not a process that lives in a spreadsheet. Not a weekly meeting where CSMs talk through their riskiest accounts from memory. A live, continuous view of the portfolio that surfaces what needs attention, prioritizes by what's at stake, and ensures nothing slips through.
The approach
The role of CS is to manage and grow the customer base. That is the goal of the function. But here's what experienced CS leaders understand: you achieve that goal by not focusing on it directly.
Revenue follows customer health. A CS team that obsessively tracks renewals and expansion targets tends to push too hard, too early, on customers who aren't ready — and misses the early warning signals in accounts they thought were fine. A CS team that obsessively focuses on customer health — whether customers are achieving their desired outcomes, whether they're genuinely getting value, whether the relationship is alive and progressing — generates the retention and expansion as a consequence.
This means CS needs to own the revenue number but focus on the health signals. The renewal date matters. The ARR at stake matters. But they're context for prioritization, not the primary object of attention. The primary object of attention is always: is this customer succeeding? If yes, the revenue follows. If no, fix that first.
In practice, this means running your portfolio with both dimensions visible simultaneously — health and revenue — and using them together to decide where to focus.
The other principles are: continuous visibility over periodic reviews, systematic touchpoints over heroic ones, and early signals over late conversations. Retention is won in month 3 and month 6 — not at renewal.
How to do it in Startdeliver
Build a retention view that combines health and revenue
Create a saved list with health status, AI assessment, ARR, and renewal date all visible as columns. Sort by ARR. Now you have the two dimensions you need — health and revenue — in a single view, and you can prioritize based on both simultaneously.
A high-ARR customer with At Risk health gets immediate attention. A low-ARR customer with Neutral health gets a scheduled check-in. A high-ARR customer with Strong health and a renewal in 30 days gets a proactive value conversation. The list makes these priorities obvious without anyone having to figure them out manually.
Get early warning notifications before risk becomes churn
Startdeliver sends heads-up notifications when early risk signals arrive — before the situation becomes a problem. A drop in usage. A poor survey response. A support ticket going overdue. A customer who hasn't been contacted in 30 days. These signals surface automatically as notifications to the assigned CSM, so the team is acting on early signals rather than waiting for the customer to raise a concern.
The difference between an early signal and a late one is often the difference between a conversation that saves the account and one that just slows the exit.
→ How health assessment works · AI Assessments
Let the AI do the continuous monitoring
The AI reads every customer continuously — usage, feedback, support, relationship activity, goal progress — and updates the health assessment automatically. Your team doesn't need to manually review 80 accounts every week to know what's changed. The AI surfaces what matters.
When a customer drops from Actively Engaged to Needs Attention, the AI flags it. When a combination of signals suggests churn risk — declining usage, poor feedback, overdue support ticket, no CSM contact in 45 days — the AI reads the pattern and raises it.
Automate the retention rhythm
Configure automations that create touchpoints at the moments that matter — not based on a calendar, but based on what's happening in the account. When usage drops below a threshold, create a task for the CSM. When a customer hasn't been contacted in 30 days, send an automatic check-in. When a renewal is 60 days out and health is anything less than Good, alert the CSM and their manager.
The retention rhythm runs automatically. Your team focuses their attention on the accounts where human judgment adds the most value.
Track renewal pressure in context
Create a Renewals list filtered to customers renewing in the next 90 days, with health status and ARR visible. A customer renewing in 45 days with Good health across all signals is a very different situation from one renewing in 45 days with Poor experience health and no recent contact. Seeing both together — renewal timeline and health status — is what allows your team to have the right conversation at the right time rather than treating all renewals the same.
→ Lists & filters · Customer overview
Give managers portfolio visibility
The individual CSM manages their accounts. The Head of CS manages the portfolio. Use Impact dashboards to give leadership a portfolio-wide view of retention health — NRR trend, churn by segment, health distribution across the team, renewal pipeline. This is the data that turns CS from a cost center into a revenue function.
→ Dashboards & Reports · MRR & ARR
Use Jecta for high-volume portfolios
When CSMs are managing large account volumes, Jecta handles the consistent touchpoints — check-ins, usage nudges, renewal acknowledgments — so no account goes dark. The CSM focuses on the accounts that need genuine human attention. Jecta handles the ones that need a timely, personalized message.
What good looks like
Your team sees health and revenue together in every list view — so prioritization decisions are obvious rather than requiring judgment calls from memory
Early warning notifications arrive before risk becomes churn — your CSMs are acting on signals, not responding to customer announcements
Every customer has a current health status at all times — updated automatically as new data arrives, not reviewed manually once a quarter
Retention touchpoints happen on a consistent rhythm for every customer regardless of who owns the account or how stretched they are
Your Head of CS can see NRR trend, health distribution, and renewal pipeline in a single view — and can show the board that CS activity drives revenue outcomes, not just satisfaction scores
Renewal conversations start from a position of demonstrated customer health and value — not a scramble to justify the contract
Last updated
Was this helpful?