RevOps
Grade renewal risk 90 days out and value the ARR on the line.
- Category
- RevOps
- Signup
- None
- Your data
- Stays in your browser
- Also in
- Claude, via MCP
How do you score renewal risk for a customer account?
Rate four signals as positive, flat or negative: product adoption (weight 30), realised value (30), executive sponsor (20) and support sentiment (20). Positive scores full weight, flat half, negative zero. The total out of 100 is the health score; 100 minus health is churn risk, and ARR × churn risk is the ARR at risk.
On watch, $22,500 is soft. The weakest signals are where to intervene now, 90 days out, while there’s still time to change the trajectory.
Adoption and realised value carry the most weight because they predict renewals better than sentiment, a happy user who doesn’t use the product still churns.
About this calculator
By the time an account explicitly signals it won't renew, it's usually too late to change the outcome, the leading indicators showed up 60-90 days earlier in adoption trends, sponsor strength, and support sentiment. This grader scores those four signals into a weighted health score and translates the resulting churn risk directly into the ARR that account puts on the line.
How to use it
- Rate four 90-day signals as Positive, Flat/neutral, or Negative: product adoption/usage trend, executive sponsor strength, support sentiment/ticket trend, and realized value versus goals.
- Enter the account's ARR.
- Read the health score out of 100, the risk band (Healthy, Watch, or At risk), churn risk as a percentage, and the ARR at risk.
Methodology
Each signal carries a weight, adoption 30, sponsor strength 20, support sentiment 20, realized value 30, and scores 1 point (Positive), 0.5 (Flat/neutral), or 0 (Negative). The health score is the sum of weight × points across all four signals, out of 100.
Churn risk is simply 100 minus the health score, the inverse of health. ARR at risk is account ARR × churn risk percentage, a risk-weighted exposure figure rather than an assumption that the account will definitely churn.
Health score of 75+ bands as Healthy, 50-74 as Watch, below 50 as At risk, thresholds meant to separate accounts needing only light-touch attention from ones needing an active save play.
Adoption and realized value carry the heaviest weight (30 each) deliberately, because usage and outcomes predict renewal better than sentiment alone, a customer who reports being happy in a check-in call but has declining product usage is still a real churn risk the sentiment alone wouldn't catch.
Weighted renewal health score
Health score = 30 × Adoption + 20 × Sponsor + 20 × Support + 30 × Value (each signal: Positive = 1, Flat = 0.5, Negative = 0) Churn risk % = 100 − Health score ARR at risk = Account ARR × Churn risk % Band: 75+ Healthy, 50 to 74 Watch, under 50 At risk
- Adoption
- Is usage growing, steady or falling across the people and features the customer bought?
- Value
- Can the customer point to the outcome they bought the product for, in their own numbers?
- Sponsor
- Is there a senior person who backs the product and will sign the renewal?
- Support
- Are support interactions positive, or are there open escalations and complaints?
- ARR at risk
- A risk-weighted exposure for prioritising, not a forecast that this amount will churn.
Adoption and value carry the most weight because they are about what the customer does and gets, not what they say. Churn risk here is a simple inverse of the score, not a calibrated probability. To make it one, compare past health scores with what actually renewed and adjust the weights.
Worked example: a ₹40 lakh account 90 days before renewal
A SaaS company reviews a customer worth ₹40,00,000 ARR. Usage is flat, the sponsor is engaged and positive, there are two open support escalations, and the customer cannot yet show clear results from the product.
- Adoption flat = 30 × 0.5 = 15.
- Sponsor positive = 20 × 1 = 20.
- Support negative = 20 × 0 = 0.
- Value flat = 30 × 0.5 = 15.
- Health score = 15 + 20 + 0 + 15 = 50, which is the bottom of the Watch band.
- Churn risk = 100 − 50 = 50%, so ARR at risk = ₹40,00,000 × 50% = ₹20,00,000.
- Resolving the escalations alone (support to flat) lifts the score to 60.
The sponsor is the asset here, so use them: agree a short plan to close the escalations and a value review that shows results in the customer's own numbers before the renewal conversation. Score every account due in the next two quarters the same way and rank by ARR at risk. For the revenue effect across the base, use the net revenue retention forecaster.
What is a good renewal rate to aim for?
Judge renewal performance against companies at a similar price point. SaaS Capital recommends comparing retention by ACV, and reports a median net revenue retention of 102% for private B2B SaaS companies with ACVs of $25,000 to $50,000 in its 2025 data.
For the health score itself, a good model is one that predicts. Check it each quarter:
- Of accounts scored At risk, how many churned or shrank?
- Of accounts scored Healthy, how many did?
If both groups renew at similar rates, the signals or weights need changing.
Renewal risk in India vs the US
Indian B2B renewals often involve a fresh price negotiation and a new purchase order each year, even when the customer is happy, so a healthy account can still be a late renewal. Start renewal paperwork 60 to 90 days ahead and confirm who raises the PO. For SMB customers, the "sponsor" is often the founder; if they lose interest, adoption usually falls soon after.
US mid-market and enterprise renewals more often auto-renew under contract terms, which makes the risk quieter: customers who plan to leave give notice before the auto-renewal date. Track notice periods in the CRM and score accounts before that date, not before the renewal date. To size the team that runs these reviews, use the customer success capacity planner.
Common renewal health scoring mistakes
- Scoring sentiment from the last call instead of usage and outcomes.
- Treating churn risk from the score as a probability without checking it against past renewals.
- Scoring accounts only in the month before renewal, when there is no time to act.
- Ignoring partial churn: seats or modules dropped at renewal count as lost revenue.
- Letting each CSM interpret "positive" and "flat" differently. Write down what each rating means.
Sources
- What is a good retention rate for a private SaaS company?, SaaS Capital. Accessed 2026-10-19.
Go deeper
FAQ
Because a happy relationship with a strong sponsor doesn't prevent churn if the product isn't actually being used or isn't delivering the value the customer signed up for. Sentiment and sponsor strength matter, but usage and outcomes are the more reliable leading indicators of an actual renewal decision.
Identify which specific signal is weakest and intervene on that signal directly, 90 days out is enough runway to change trajectory on adoption or realized value if you act, but that window closes fast as renewal approaches.
No, it's a risk-weighted exposure figure, ARR × churn risk percentage, not a hard prediction. Treat it as a way to prioritize save-play effort across accounts by dollar exposure, not as a forecast that specific dollar amount will actually be lost.
A customer health score combines signals such as usage, outcomes, relationships and support history into one number that indicates how likely an account is to renew or grow.
Usage signals can update weekly or monthly from product data. Sponsor and value signals need a human review, typically each quarter and again 90 days before renewal.
Yes, but keep it small enough that people can explain why an account scored as it did. Add a signal only if past renewals show it predicts churn better than the existing four.
Numbers looking off?
If the model says one thing and the pipeline says another, that gap is usually where the revenue is. A 30-minute call finds it.
It starts with a 30-minute call. Pick a time below.