How to find unused software licences
An unused licence is a paid seat whose holder has not signed in or done anything in the product for a period you define, typically 30 to 90 days. You find it by comparing the vendor's seat list with its activity data, you confirm it by asking the holder, and you remove it before the notice date of the contract, because most contracts only let you reduce seats at renewal.
An unused licence costs the same as a used one. Finding it needs no estimate and no benchmark: the vendor already records who holds a seat and when that person was last active. The work is to read both lists, compare them, and act before the contract renews.
What "unused" means
A seat is unused when three things are true at once: it is paid for, it is assigned to a person, and that person has not been active for longer than a threshold you chose. Each part needs its own source.
| Question | Where the answer is |
|---|---|
| Is the seat paid for? | The subscription: plan, number of seats, price per seat, renewal date |
| Who holds it? | The vendor's member or user list |
| When was the holder last active? | The vendor's activity or audit data: last sign-in, last action |
| Is the holder still employed? | Your directory or HR system |
Two cases need no threshold. A seat held by someone who has left is unused. A seat that is paid for and assigned to nobody is unused. Both are found by a join, not by judgement.
Step 1: read the seat list and the subscription
Export the user list of each application with the role or licence type of every user. Next to it, note what the subscription says: how many seats are paid, what one seat costs per month, when the term ends and by when notice has to be given. If the vendor has an admin API, use it instead of an export. An export is a photograph; an API can be read again next week.
Step 2: add activity
For each seat, find the date of the last activity. Vendors differ in what they record: some give the last sign-in, some the last action, some only a monthly usage report. Write down which one you used. A last sign-in that is 200 days old is strong evidence. A missing value is not: it can mean "never used" or "this vendor does not report it".
Step 3: apply a threshold and sort by cost
Mark every seat without activity for longer than the threshold. Then multiply: seats marked, times price per seat, times twelve. That product is the yearly cost of the seats in question. It is not yet a saving, because nobody has confirmed that the seats can go.
A worked example with invented figures: 40 seats at 30.00 a month, of which 6 show no activity for 90 days. 6 × 30.00 × 12 = 2,160.00 a year in question.
Step 4: ask the holder
Activity data has blind spots. A person may use the tool through an integration, through a shared screen in a weekly meeting, or only at quarter end. So ask, and make it easy to answer: name the application, say when the last activity was recorded, and offer two answers, "I still need it" and "release it". How to word this, and how to follow up without nagging, is covered in asking employees about their licences.
Do not ask people who must not be asked. Works councils, executives or people on leave may be excluded by policy. Keep that list in one place and check it when a message is sent, not only when it is drafted.
Step 5: act before the notice date
A released seat saves money at the next renewal, or at once when the plan is billed monthly. Collect the releases, reduce the seat count with the vendor, and do it before the notice date. If the renewal is close, the same data is the basis for the talk with the vendor: see preparing a SaaS renewal. If many holders use only the basic features, a cheaper plan may fit better than fewer seats: see right-sizing SaaS plans.
What goes wrong
- One threshold for every tool. A design tool used daily and a survey tool used twice a year need different periods.
- Counting before confirming. A total of "seats in question" reported as savings will not survive the first holder who says they need the seat.
- Removing without a record. Note who released the seat and when. The question comes back at the next audit.
- Doing it once. People join, leave and change roles every month. The comparison has to be repeated, which is the argument for reading the vendor's API instead of an export.
How Cureman does it
Cureman reads seats, plans and activity through read-only connectors to the vendors, applies the inactivity period the organisation has set, and lists every seat in question with its calculation: seats, price per seat, months. A list price that nobody has verified is labelled as unverified and kept out of totals. Where the data cannot answer, it drafts the question to the seat holder by email or Slack; a person approves the draft before anything is sent, and nobody on the organisation's do-not-contact list is asked. Answers are filed, people who do not answer are followed up as the approved plan says, and the finding counts as a saving once it is marked done. The module is described on the page about licence optimisation.
Questions and answers
What counts as an unused software licence?
- A paid seat whose holder shows no activity in the vendor's data for a period the organisation has set, for example 60 days. Activity means a sign-in or an action in the product. A seat that is assigned to someone who has left the company is unused whatever the activity data says.
How many days of inactivity should the threshold be?
- Long enough to cover holidays and tools that are used once a quarter, short enough to act before the next renewal. Many organisations start with 60 or 90 days and set a shorter period for expensive seats. The threshold is a starting point for a question to the holder, not a verdict.
Can a seat be removed during the contract term?
- Usually the seat can be unassigned at once, but the price only falls at renewal, unless the plan is billed monthly or the contract allows a reduction. That is why the date that matters is the notice date of the contract, not the day the seat was found.
Should employees be asked before a licence is removed?
- Yes, where the data cannot answer the question. Activity data misses use through an integration, a shared login or an API token. A short question to the holder with two answers, keep or release, settles most cases and avoids removing a seat somebody needs next week.