Unit economics
Flag renewal risk from seats that were bought but never used.
- Category
- Unit economics
- Signup
- None
- Your data
- Stays in your browser
- Also in
- Claude, via MCP
How does low seat utilisation affect renewal risk?
Utilisation = active seats ÷ purchased seats. Below 70%, this tool scales renewal risk linearly: risk = (70 − utilisation) ÷ 70, and ARR at risk = renewal ARR × risk. With 48 of 100 seats active on a ₹30 lakh renewal, utilisation is 48%, risk is 31% and about ₹9.4 lakh is at risk.
Only 48% of seats are active, a clear renewal red flag, with about $18,857 exposed. Trigger an adoption play now; low usage is the earliest churn signal you get.
Utilization predicts renewals months ahead of the renewal date. Idle seats are the quiet lead-up to a downgrade or a "we’re not using it" churn.
About this calculator
A customer who bought 100 seats but only actively uses 48 of them isn't a healthy renewal waiting to happen, they're a churn risk with a delayed timer. This assessor compares active seats against seats purchased to calculate utilization, flags the renewal risk band that utilization falls into, and translates that risk into the dollar amount of renewal ARR actually exposed.
How to use it
- Enter seats purchased, the total license count the customer bought.
- Enter seats actively used, typically logged in or active within the last 30 days.
- Enter the renewal ARR at stake for this account.
- Read seat utilization, the risk band, idle seat count, and the renewal ARR at risk.
Methodology
Utilization is active seats divided by purchased seats, expressed as a percentage. Idle seats is simply purchased minus active, the seats being paid for but not used.
Renewal ARR at risk uses a risk factor that scales linearly as utilization falls below a 70% healthy threshold: risk factor equals (70 minus utilization) divided by 70, clamped between 0 and 1. At exactly 70% utilization the risk factor is 0 (no ARR flagged at risk); at 0% utilization it's 1 (the full renewal ARR is flagged). Renewal ARR at risk is that risk factor times the renewal ARR figure you entered.
The tool bands utilization into three tiers: 70%+ is healthy, 50-69% is a watch zone, and below 50% is flagged at risk, matching the same 70% threshold used in the risk-factor calculation, so the qualitative band and the dollar-risk figure move together.
This is a single-snapshot model based on current utilization, it doesn't track utilization trend over time. A customer who was at 80% last quarter and 50% this quarter is a much sharper warning sign than one who has been steady at 50% for a year, even though both would show the same current risk figure here.
Utilisation and renewal ARR at risk
Utilisation = Active seats ÷ Purchased seats Idle seats = Purchased seats − Active seats Risk factor = clamp((70% − Utilisation) ÷ 70%, 0, 1) ARR at risk = Renewal ARR × Risk factor Band: 70%+ healthy, 50 to 69% watch, under 50% at risk
- Active seats
- Users who logged in or used the product in a recent period, such as the last 30 days.
- Purchased seats
- Licences the customer pays for.
- Renewal ARR
- Annual value of the contract up for renewal.
The 70% threshold and the linear risk scale are tool assumptions, not measured relationships. Low utilisation leads to downgrades (fewer seats at renewal) as often as to full churn, so ARR at risk includes both. Define "active" consistently; a login alone may overstate real use.
Worked example: 48 of 100 seats in use
A customer bought 100 seats at a renewal value of ₹30,00,000. Product data shows 48 users active in the last 30 days, three months before renewal.
- Utilisation = 48 ÷ 100 = 48%, in the at-risk band.
- Idle seats = 100 − 48 = 52.
- Risk factor = (70 − 48) ÷ 70 = 0.314.
- ARR at risk = ₹30,00,000 × 0.314 = ₹9,42,857.
- If 20 more users become active, utilisation reaches 68% and risk falls to 3%.
Three months is enough time to act: find out which teams have not adopted the product, run training for them, and agree with the sponsor what success looks like before renewal. If idle seats cannot be activated, a planned reduction is better than a surprise downgrade. Combine this with the renewals pipeline health grader for a fuller picture.
What is healthy seat utilisation?
The tool treats 70% or more as healthy, its own threshold. Check your own data:
- Compare renewals by utilisation band: did accounts under 50% shrink or churn more often?
- Look at the trend, not one snapshot. Falling utilisation is a stronger signal than a stable low figure.
- Look by team: a few teams that never adopted can drag a healthy account down.
Some customers buy seats ahead of planned hiring, so ask before treating low utilisation as risk.
Seat utilisation in India vs the US
Indian customers often buy seats for a whole team at once to get a price break, then roll out slowly, so utilisation can be low early in the contract. Track adoption from the first month. Shared logins also happen, which can make utilisation look lower than real use; seat terms and product controls help.
US customers frequently review licence counts at renewal, often through procurement or software management tools, so idle seats are likely to be noticed and cut. Proactively right-sizing can protect trust and the rest of the contract. For the pricing side, see the seat vs usage pricing calculator.
Common seat utilisation mistakes
- Counting a single login as an active user.
- Checking utilisation only in the month before renewal.
- Treating every idle seat as churn rather than a possible downgrade.
- Ignoring planned hiring that explains spare seats.
- Pushing more seats onto an account that is not using the ones it has.
FAQ
It's a commonly used practical benchmark, below roughly 70% active usage of purchased seats, procurement and finance stakeholders start noticing the gap between spend and value at renewal time, making the account meaningfully more likely to downsize or churn.
Not always, but it's one of the earliest and most reliable churn signals available, well before a renewal conversation happens. Low usage often precedes a downgrade or non-renewal by months, which is exactly why this tool exists: to flag risk early enough to act on it.
Trigger an adoption or re-engagement play immediately, targeted onboarding for unused seats, usage reviews with the account owner, or right-sizing the license count proactively before the customer does it unilaterally at renewal. Acting before the renewal date is far more effective than reacting after.
No, this tool is built specifically for per-seat/per-license pricing models. If your product prices on usage volume, API calls, or consumption rather than seats, a different usage metric (tied to your actual pricing unit) will be a more accurate churn predictor.
No. It can mean a slow rollout or planned growth. It does mean the customer is paying for value they are not getting, which raises the risk of a downgrade or churn.
Sometimes. Offering to right-size before renewal can protect the relationship and the rest of the contract, especially if the alternative is a full cancellation.
The same idea applies with usage against committed volume instead of seats. Swap active seats for used units and purchased seats for committed units.
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.