The 7 Renewal Risk Signals to Review Before Every Renewal in 2026

The renewal conversation is usually the first time anyone looks hard at an account, and by then the decision has typically already been made somewhere else. The signals that predicted it were available for months, scattered across a help desk, a call recorder, and a CRM, none of which were consulted because the account's usage looked fine.

Seven signals belong in a renewal risk review: the unresolved ask, champion status, the support driver mix, sentiment trajectory, adoption breadth, competitor mentions, and the commercial history. Usage trend is not on the list as a standalone item, not because it is useless but because it is the last of these to move. By the time it does, the review is a post-mortem.

A renewal review is not a health score refresh

The two get conflated and they do different work. A health score is a continuous triage mechanism: it ranks a book of accounts so a CSM knows where to spend the week. A renewal review is a deep read on one account inside a defined window, and its job is to produce a specific plan for a specific conversation.

The score tells you which account to look at. It cannot tell you what to say. That requires the evidence underneath the score, and most reviews never get to it because the evidence lives in text nobody has read.

What a renewal review has to do

1. Cover the window, not the quarter. Scope to accounts renewing in the next 90 days, reviewed on a fixed cadence, so nothing arrives at 30 days out as a surprise.
2. Read the account's own words. An adaptive taxonomy categorizes everything this account said across tickets, calls, reviews, and surveys, which is what turns "they have filed a lot of tickets" into "they have raised the same export limitation in four of the last six months."
3. Attach the money and the timing. A customer context graph ties that feedback to the account, its ARR, its segment, and its renewal date, so the review is ordered by exposure and the evidence is already joined to the contract.

The 7 renewal risk signals to review before every renewal

1. The unresolved ask

Every request this account has made that has not shipped, with the date first raised and the number of times repeated. This is the strongest single signal in the set and the one most reviews skip, because it requires a history rather than a snapshot. An account that has asked for the same capability in three consecutive quarters has a documented, dated reason to evaluate alternatives, and they will bring it to the renewal call whether or not you do.

2. Champion status

Whether the people who bought and championed the product are still there and still engaged. A champion leaving is the most common cause of a renewal going sideways without any product signal preceding it. Check for the original buyer's activity, new names appearing in threads, and whether anyone senior has engaged in the last quarter.

3. The support driver mix

Not ticket volume. What the tickets were about. Contacts concentrated on advanced configuration read as depth of use. Contacts concentrated on a recurring defect, or on basics from a mature account, read as friction and as an enablement failure respectively. Same count, opposite implications. See churn risk detection from support data.

4. Sentiment trajectory

The slope over the contract term, drawn from every channel rather than from survey responses. Direction matters more than level: an account at moderate sentiment trending down is a worse position than a historically critical account that has been improving. See correlating CSAT with churn risk.

5. Adoption breadth

How many distinct users and teams, and whether the admins are among them. Single-user dependency is the quiet risk in B2B: the account is healthy right up until that person changes roles. Pair it with seat utilization against contracted seats, since unused seats are both a churn signal and the first thing procurement cuts.

6. Competitor mentions from the account

Anyone at this account naming an alternative, in any channel. Highest specificity of anything on the list, and almost never in a renewal review because it requires reading support tickets and calls rather than checking a CRM field. A customer who mentions a competitor in a support thread has told you what the renewal conversation will be about.

7. Commercial history

Last renewal outcome and terms, discounting history, invoice status, and any open billing dispute. This is lagging relative to the rest and it belongs in the review as context for the conversation rather than as a predictor. A discount granted last cycle sets the anchor for this one.

The evidence is what turns a flagged account into a plan

Here is the part that changes the meeting. Most renewal reviews produce a status: green, yellow, red, with a sentence of justification. A rep leaves with a risk rating and no more idea what to say than before.

The version that works produces three things per account: the specific unresolved thing the customer will raise, in their own words, with dates. The name of the person whose absence or presence determines the outcome. And the one concrete commitment you can make that addresses the first.

That is a plan, and it is assembled almost entirely from text the company already holds. The reason it usually is not assembled is effort: reading a year of one account's tickets, calls, and survey responses takes a CSM most of a day, and a book of thirty accounts renewing in a quarter makes that arithmetic impossible by hand.

Which is why the honest constraint here is the same as everywhere else in this stack. The review is not hard to design. It is hard to run at the cadence a book of business requires, unless the reading is already done. See feedback signals that indicate customer churn risk and churn analytics dashboards built from customer feedback.

How to run it

Run it monthly against a rolling 90-day window, so every account gets reviewed at least twice before its renewal and nothing arrives unexamined. Order the list by ARR at risk, not alphabetically and not by score.

For each account, produce the three outputs above rather than a color. Assign one owner and one action with a date. Track the outcome against the review so the signals can be weighted against what actually happened, which is the only way the review gets better rather than just more frequent.

Close the loop on the unresolved asks explicitly, including the ones you are not going to build, because an honest no is a better renewal position than an unanswered request. See the five stages of closing the customer feedback loop.

The decision rule: if the review cannot name the sentence the customer will say on the call, it is not finished.

FAQ

What signals predict renewal risk?

Unresolved requests the account has repeated over time, champion departure or disengagement, the mix of what support contacts were about rather than their count, sentiment trajectory across channels, adoption breadth and seat utilization, competitor mentions from anyone at the account, and commercial history including discounting and billing disputes.

When should a renewal risk review happen?

On a rolling 90-day window reviewed monthly, so each account is examined at least twice before its renewal date. Reviews that start at 30 days out arrive after the customer's internal decision process has usually begun.

How is a renewal review different from a customer health score?

A health score ranks a whole book continuously so a CSM knows where to spend time. A renewal review is a deep read on one account inside its renewal window, and its output is a conversation plan rather than a rating. The score points at the account; the review supplies what to say.

How does Enterpret support renewal risk reviews?

Enterpret categorizes everything an account has said across tickets, calls, reviews, surveys, and community with an adaptive taxonomy, which produces the unresolved-ask history, the driver mix, the sentiment slope, and any competitor mentions without anyone reading a year of records. The customer context graph ties it to ARR, segment, and renewal date, so the review is ordered by exposure. It can run as a scheduled job against a rolling window.

Should usage data be part of a renewal review?

Yes, as context rather than as the leading signal. Usage decline is real but it is typically the last indicator to move before a churn, which makes it a confirmation rather than a warning. The text-based signals move earlier and are what give a review enough lead time to change the outcome.

If your renewal reviews produce a rating rather than a plan, see how Enterpret handles voice of customer software.

‍