Which Leading Indicators of Renewal Predict It, and Which Do Not?

Leading indicators of renewal divide into three tiers by what they observe: the decision makers, the work, and the product. Contact-level signals sit in the top tier because a B2B renewal is decided by two or three named people, and a departure or a lengthening reply time reaches you months before anything appears in a usage chart. Work-level signals (onboarding milestones, unresolved escalations, unanswered business questions) come second. Product usage sits third, because it aggregates hundreds of users to describe a decision taken by a handful.

The one measured comparison we found in the corpus makes the point about work-level signals better than any usage chart. A practitioner ran a cohort analysis in 2026 across their own accounts and reported that the strongest predictor of month-12 renewal was neither account size nor owner.

Treat 91% against 67% as one team's result on one account base, not as a benchmark; no public dataset on indicator strength exists to compare it against. The transferable finding is the shape: a small structured moment, consistently completed, outranked the variables everyone discusses. The same practitioner put it more bluntly, and the sentence is worth pinning above any signal workshop.

Nine indicators earn a place on a shortlist, and the ordering below is by typical warning time, longest first. Warning times are the ranges we see in practice and should be replaced with your own medians as soon as you have four quarters of closed renewals to measure. Separation is the gap in renewal rate between accounts where the indicator is clear and accounts where it has fired.

Notice how few of the nine live in a product analytics tool. Five of the nine sit in email, calendar, CRM, billing or a support queue, and only two in product analytics, which is why signal projects stall on plumbing instead of modelling. What are the early warning signs of churn when data is scattered covers pulling them out of the tools you already have.

Positive renewal signals get left out of almost every health model, which is why scores are good at flagging trouble and useless at telling a CSM where to spend a spare afternoon. A risk-only model treats the absence of bad news as health, and the absence of bad news is also what a quietly disengaging account looks like. Five positive signals are worth recording as their own fields.

Recording positive signals also fixes a reporting problem. A forecast built only on risk gives every account the same starting assumption and pushes CSMs to argue accounts down from green; a model carrying both directions lets an account earn its category. How do I improve renewal forecast accuracy on my accounts covers the categories themselves.

Rank each candidate on two numbers computed from four quarters of closed renewals: separation and save window. Separation tells you whether the indicator carries information. The save window tells you whether the information arrives in time to be used. An indicator needs both, and most published signal lists supply neither.

1. 1

   Build the outcome list

   Every renewal decision from the last four quarters: renewed, churned, contracted above 20%, with the decision date and not the contract end date. The two differ by weeks and the gap matters here.

2. 2

   Reconstruct each candidate indicator as it stood 180 days out

   If your systems cannot show a past state, rebuild from raw events: emails, calendar entries, tickets, billing changes. Anything you cannot reconstruct cannot be ranked, and that is itself a finding.

3. 3

   Compute separation for each candidate

   Renewal rate with the indicator clear, minus renewal rate with it fired. Do it one indicator at a time, before any combining.

4. 4

   Compute the median lead time and the save window

   Days from first firing to decision date. Subtract the days your save playbook needs. Drop anything with a negative save window from the live queue and keep it for post-mortems.

5. 5

   Compute coverage and cost to collect

   Rank what survives by separation, then discard anything you cannot compute on most of your accounts or automate within a quarter.

6. 6

   Test the top three together

   Count renewals and churns where two or more of the surviving indicators fired inside the same 90 days. Combinations usually separate further than any single field, which is what practitioners keep reporting.

Logins rank low because they aggregate the wrong population. A 200-seat account can hold its login count steady while the budget holder stops attending, the champion leaves and the original use case quietly dies, because the count is dominated by users who have no part in the renewal. Total volume also moves for reasons unrelated to health: a seasonal peak, a reporting deadline, one team running a backlog.

Survey scores rank lowest of the nine for a different reason. Response rates are low, and the people who answer are rarely the people who decide. In 4,978 public G2 reviews of five customer success platforms, 217 mention NPS and 49 mention CSAT, and the complaints concentrate on reliability rather than on availability. Customer effort score vs CSAT vs NPS sets out which of the three is worth running and what to ask instead.

Neither signal is worthless. Both become useful when read as change against the account's own baseline and narrowed to the people who matter: logins by the admin and the champion, not by everybody; survey responses from named deciders, not from the contact list. That reframing is also what turns a level-based customer health score into one that moves before a renewal does.

A signal is a post-mortem field whenever its save window is zero or negative: by the time it fires, the playbook cannot finish before the decision is taken. Three common fields fail this test at most companies. A cancellation request. A renewal call that has been rescheduled twice and then dropped. A contract sent back with legal changes. All three correlate beautifully with churn and all three arrive too late to change it.

Keep those fields, but keep them somewhere else. Post-mortem fields belong in the churn review, where their job is to point at the leading indicator that should have fired earlier. That is the loop most signal work is missing: every churn should end with a named indicator that was available and ignored, or a note that no indicator existed, which becomes next quarter's instrumentation work.

The corpus also shows how rare this discipline is. Only 9 of 4,978 public G2 reviews (0.2%) mention leading indicators at all, against 686 (13.8%) that mention churn. Teams talk about the outcome roughly 76 times more often than the thing that predicts it, and reviewers who went looking for indicators in their tooling sometimes found nothing.

One honest note on benchmarks. No trustworthy public figure exists for the predictive strength of renewal signals, or for renewal forecast accuracy, in B2B SaaS: the ranges quoted elsewhere come from vendor and consultancy posts with no sample and no method. Retention itself is measured, and SaaS Capital's September 2025 survey of more than 1,000 private B2B SaaS companies puts median gross revenue retention at 91%, which tells you what a normal account base loses but nothing about which signal saw it coming. Your own closed renewals are the only dataset that answers that.

GainTrace connects billing, CRM, product usage, email and support, then scores each account on change against its own baseline, including the contact-level signals most scores omit. Because renewals and churn flow through the same system, the separation and lead time of every signal are measured continuously against your own outcomes. Churn prediction ranks the accounts most likely to move with the signals that drove the call, and customer health shows each signal with its refresh interval beside it.