Success storyIllustrative
How a 180-person SaaS company saw churn risk 60 days before renewal
Customers rarely leave without warning. The warnings were just spread across three systems. The Revenue and Product & Tech agents put them into one ranked list every Monday.
2 min read
- Revenue
- Product & Tech
- Strategy
Illustrative story: a composite scenario built on sample data to show how the agents work. It is not a customer testimonial.
The challenge
Renewals belonged to a nine-person customer success team. They knew the largest accounts well. For everyone else, the first clear sign of trouble often came on the renewal call itself, when the customer had already made up their mind.
Looking back, the signs had been there. Logins dropped. Support tickets got sharper. A note in the CRM mentioned a new budget owner. But each signal lived in a different system and landed with a different team, so nobody put them together in time.
What they set up
- The Product & Tech agent read product analytics and the helpdesk, read-only. It tracked each account's usage against its own baseline, along with ticket volume, severity and time to resolve.
- The Revenue agent read the CRM and billing: renewal dates, contract value, recent notes from account managers and any change in champion or budget owner.
- Together they scored every account renewing in the next 90 days. Each Monday the Strategy agent sent customer success a ranked list, with the reasons behind each rank and links to the evidence.
What changed
- of warning before renewal, instead of finding out on the call
- ~60 daysof warning before renewal, instead of finding out on the call
- of accounts ranked by risk, in customer success's inbox every Monday
- 1 listof accounts ranked by risk, in customer success's inbox every Monday
- gross revenue retention, two quarters later
- +3 ptsgross revenue retention, two quarters later
The team didn't save every account. Some customers had outgrown the product or lost their budget, and no call would have changed that. The saves came from acting earlier, while a problem could still be fixed, rather than from discounts offered in the final week. The agents stayed read-only throughout. Account managers decided who to call and what to offer.
The lesson
Churn signals are rarely hidden. They are scattered. Seeing usage, support and account notes on one page, sorted by what to do first, gave a small team a head start it had never had.