The calculation and the definition that breaks it
The arithmetic is simple. An account with 400 provisioned seats and 260 active users in the last 30 days is at 65% utilization.
The definition of active is where the number goes wrong. Counting logins inflates utilization by including users who open the product, look at a dashboard, and leave. A defensible definition requires a meaningful action, such as creating a record, running a report, or completing the workflow the seat was purchased for. Pick one definition, write it down, and never change it mid-year, because a redefined denominator makes every historical comparison meaningless.
Measure on a rolling 30-day window rather than a calendar month. Calendar months distort around holidays and quarter ends, and a rolling window shows the trend without the seasonal noise.
Why it predicts contraction rather than churn
Low utilization rarely kills the account. It shrinks it. The customer keeps the product, cuts the idle seats, and the damage lands as contraction in the ARR waterfall instead of a lost logo.
That distinction matters for how the risk gets managed. A logo save requires an executive conversation. A seat save requires proving the idle users have a reason to log in, which is an onboarding and enablement problem rather than an executive escalation. Accounts drifting below their historical utilization band should trigger a targeted activation campaign against the specific users who stopped, not a general check-in call.
- Track utilization by department inside large accounts. Aggregate numbers hide the one team that stopped entirely. - Compare current utilization to the account's own baseline rather than to a cross-customer average, since a research team and a sales team will never look alike. - Flag any account where seats were added in the last two quarters and utilization fell, because that combination means the last expansion never landed.
The expansion side of the same number
Utilization running near capacity is the cleanest expansion trigger in a seat-based model. The customer is already rationing access, and the request to buy more seats originates inside their organization rather than from a rep.
That makes utilization a forecast input, not only a retention metric. Accounts near their ceiling belong in next quarter's expansion pipeline with a specific seat count attached, which is how net revenue retention gets modeled from behavior rather than from hope. Feeding those accounts into the process you use to forecast revenue turns a customer success metric into a line the finance team can plan against.
Frequently Asked Questions
How do you calculate license utilization rate?
Divide active licenses by provisioned licenses for the period and express it as a percentage. An account with 400 seats where 260 users logged in during the last 30 days sits at 65%. Define active once and hold it constant, because a definition that shifts between logins and meaningful actions makes the trend line useless.
Does a login count as an active license?
It is the weakest possible definition. A better one requires a meaningful action inside the product, such as creating a record, running a report, or completing the workflow the seat was bought for. Login-based utilization consistently overstates the number and hides the seats a customer is about to cut.
What does low license utilization predict?
Contraction more often than full churn. The account stays but buys fewer seats, which shows up as a hit to net revenue retention rather than a lost logo. Procurement teams run this exact calculation before the renewal, so the vendor who has not run it first walks into the meeting with worse data than the customer.
Is high utilization always good?
High utilization is the strongest expansion signal you have, because the customer feels the constraint before you mention it. An account running near full utilization with new users waiting on access is a seat expansion conversation, and it converts far more reliably than an expansion pitch into an account with idle licenses.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like license utilization rate into prescriptive action for your team.
Schedule a Demo