Login frequency, NPS drift, champion role changes, support tone, billing failures, competitor mentions. The six signals that consistently predict SaaS customer churn 30 days before cancellation — and how to act on each.
Most SaaS teams find out a customer is leaving the day they email to cancel. By that point the decision is already three to six weeks old — a champion left, a renewal review went poorly, a competitor shipped something that closed a gap. The save conversation isn't a save conversation; it's damage control on a decision that's already settled.
That gap — between the moment a customer mentally checks out and the moment they tell you — is the entire opportunity space for churn prediction. After working with hundreds of SaaS teams, six signals show up consistently in the thirty days before the cancellation email. Catch them and the conversation shifts from damage control to relationship repair. Each is below, with what to watch for and how to act.
The single most reliable signal of churn risk is also the simplest: how often is the customer's primary user logging in compared to their own baseline? A 30-day rolling average of daily active sessions tells you, per customer, whether engagement is normal, soft, or collapsed. The absolute number doesn't matter — what matters is the delta from their own baseline. A customer that used to log in nine times a week and now logs in twice has lost something you should know about, even if their plan is enterprise and the MRR is fine.
Action: when login frequency drops 40%+ from baseline over fourteen days, fire a save playbook. The drafted email should reference the specific feature or workflow they used to use most.
A customer who scored you a 9 last quarter and a 6 this quarter has told you, on a 0-10 scale, that something broke in the relationship. That signal is worth more than its absolute score — a 6 is fine if they're always a 6, and disastrous if they used to be a 9. NPS deltas of two or more points downward in either direction are a forced check-in.
The text comments are usually more useful than the score. NPS comments are the closest thing to a free-text exit survey that customers will actually fill in.
The single biggest predictor of enterprise SaaS churn is the champion leaving the customer's organization or moving to a different role internally. The new person inherits a tool they didn't buy and didn't pick — and inherited tools get re-evaluated at the next renewal cycle by default. LinkedIn job-title changes scrape cleanly; HRIS integrations are even better. When the champion changes, the renewal motion starts that week, not at renewal.
Support volume going up isn't the signal — supporttone shifting is. A customer that used to file polite tickets now files terse ones. A customer that asked questions now escalates. Modern LLMs read sentiment well enough that you can score every ticket and watch the rolling average per customer. A 0.4-point tone drop on a five-point scale, sustained for two weeks, predicts churn at 6-8x the base rate.
A customer that's decided to leave often stops caring about the billing relationship before the cancellation email arrives — failed card updates, ignored dunning emails, requests for monthly instead of annual. These signals are obvious in retrospect and easy to miss in real time, because finance and CS systems usually live in different tools. Stripe webhook events into your CS platform fix this for free.
Customers who mention a competitor by name in support tickets, on calls, or in NPS comments are evaluating their options. The most predictive subset is mentions paired with a question (“does your product also do X like Competitor Y?”) — that's a customer comparing feature-by-feature. Catching these requires reading the actual conversation surface, not just metadata.
A signal alone isn't actionable; six signals weighted into a health score are. The pattern: each signal contributes a weighted factor, the score updates daily, and the top three drivers per customer are surfaced in plain English. CSMs read three sentences, know the situation, and have a drafted save email waiting. The fight against churn becomes a fight you can run before the customer has decided.
Exeechain implements all six signals natively. Connect Stripe and drop in a tracking snippet, and the first scores land in fifteen minutes. Connect HubSpot or Salesforce, Intercom or Zendesk, and the model gets sharper week over week. Read the churn prediction feature for the technical details, or the health score guide for how the six signals combine.
Live in fifteen minutes. From $299/mo. Daily AI churn scoring with the top three drivers per customer.