Key takeaways
- List every software and AI tool you pay for, with an owner, a seat count, a price model and a renewal date. Start from invoices and card statements, since the tools teams buy themselves never pass through IT.
- Compare seats with real usage. Pick a threshold, such as no activity in 60 or 90 days, and treat anything past it as a candidate to reclaim.
- Reclaim in order of least disruption: reassign first, downgrade second, cancel last.
- Review the seat count a full notice period before each renewal, so the number you negotiate with is the number you actually use.
- Close software and AI access from the same leave date that triggers the laptop return.
Ask finance what the company spends on AI tools and someone can usually find a number, but ask how many of those seats were opened last month and the room goes quiet. Software licences have always leaked like this, as people leave, switch tools or get a seat through a ticket that never gets tied back to them. AI tools speed the leak up, because teams buy them directly, often on a card, and adoption moves faster than anyone's spreadsheet.
This guide answers one question: how can we find and reclaim unused software licences and AI tool seats? There are five steps, they work with a spreadsheet if that's what you have today, and we'll point out where an IT lifecycle engine takes the manual part off your plate.
What counts as an unused licence or AI seat?
An unused licence is a seat you pay for that nobody has used within a period you define, for example the last 60 or 90 days. An unused AI seat is the same thing for an AI tool: a Copilot, ChatGPT or Claude licence assigned to someone who rarely or never opens it.
They tend to come from four places:
- Leavers: the person is gone, but the seat is still assigned and still billed.
- Switchers: someone moved to a different tool and kept the old seat.
- Idle seats: requested for a project, used for a week, then forgotten.
- Duplicates: two teams paying for tools that do the same job.
AI tools add one more wrinkle. Some are billed by consumption, through credits or tokens, instead of per seat, and then the question shifts from who has a seat to who is spending, on what, and whether anyone is keeping an eye on it.
Step 1: How do you find every licence and AI tool you pay for?
Start from the money: pull invoices, card statements and expense reports alongside the admin consoles of the tools you already know about, because a tool a team bought on its own only shows up where the payment went.
The big agreements are usually under control, and the leak sits in the long tail: the design tool a handful of people use, the AI subscription one team expensed, the trial that quietly turned into a paid plan. One IT lead we spoke to put it plainly, saying a tool that only a small group uses is the one that gets forgotten.
For each tool, write down:
- who owns it and who approves new seats
- how many seats you pay for, or how consumption is billed
- the renewal date and the notice period
- who holds each seat
Your identity provider helps with that last one. If a tool signs in through Entra ID, Okta or Google Workspace, you can see who has access, which gets you most of the way to a seat-to-person map. Tools outside single sign-on need their own export.
Step 2: How do you compare licences with actual usage?
Match each seat against activity data, from the tool's own admin console or from sign-in logs, then sort the seats by when they were last used. Anything past your threshold goes on the reclaim list.
Fair warning on the hard part: a sign-in and real use are two different things, and some tools report activity far better than others. Treat sign-in data as a first filter and check the borderline cases with the tool owner before you act on them.
It also pays to look at each tool as a whole. A tool where half the seats sit idle needs a smaller contract, while one where nearly every seat is busy might need more, and you want to know both before the renewal.
This is the step that takes the most time by hand, and the one Velory automates. As the engine that runs IT lifecycle management, Velory syncs usage against the licences you hold across your software and SaaS, AI tools included, maps each licence to a person through your identity provider, and grades every service from A to D on real activity. The idle seats arrive as a list, so nobody has to rebuild the spreadsheet every quarter.
Step 3: How do you decide which seats to reclaim?
Reclaim in order of least disruption: give idle seats to people who are waiting for one, move light users to a cheaper plan, and cancel what's left after that.
A few habits keep this from turning into a fight:
- Tell people before you remove anything, and make it easy to ask for the seat back. If someone does need it, getting it back should take a minute.
- Let the tool owner decide on borderline seats. Some tools are used once a quarter, for reporting or a campaign, and look idle the rest of the time.
- Check the contract before you count the savings. Some enterprise AI plans come with a minimum seat count, and some contracts only let you reduce seats at renewal.
On that last one: the contract decides when a reclaimed seat turns into money saved. Sometimes that's next month and sometimes it's the renewal, which is why the next step matters.
Step 4: How do you catch renewals before they auto-renew?
Put every renewal date and notice period on a calendar that IT and finance both see, and review the seat count a full notice period before the date, well ahead of the week the invoice arrives.
The number to walk in with is simple: seats you pay for minus seats anyone used. That gap is where the renewal conversation starts, and it's a figure finance can check for themselves.
Consumption-billed AI tools have no seat count to cut, so give each one an owner and a monthly budget and look at spend per team. Spend that keeps climbing without anyone being able to explain it is the AI version of an idle seat.
Step 5: How do you stop licences leaking when people leave?
Tie licence and AI access removal to the same leave date in your HR system that triggers the laptop return, so software closes when the person leaves and not whenever someone happens to notice.
Hardware tends to come back because a missing laptop is visible. A licence has nothing that forces the question, so it keeps billing until an invoice or a renewal reminder turns up. Role changes leak the same way, when someone moves team, picks up the new team's tools and keeps the old ones.
In Velory, a leaver in your HR system starts the offboarding, and the device return, the mobile plan and the software and AI licences are revoked or reassigned in the same flow, while the same kind of event provisions access for a new joiner. You shape those workflows around your own approval chains, and you can ask plain-language questions of your asset data, like which AI seats nobody has opened this quarter.
What else do IT teams ask about unused licences?
How often should we review software licences?
At least once before every renewal, a full notice period ahead. For tools billed monthly or by consumption, a quarterly look at usage and spend catches drift before it adds up.
Is SSO data enough to find unused licences?
It's a good first filter. Sign-in logs show who has access and who logged in, but logging in and using a tool are different things, and tools outside single sign-on don't show up at all. Combine sign-in data with each tool's own activity reports.
Who should own licence reclaim, IT or finance?
Both, with different jobs. IT owns the data and the process, finance owns the budget and the renewal decision, and each tool needs a named owner who makes the call on borderline seats.
How do we handle AI tools that are billed by usage?
Give each tool an owner and a budget, review spend by team every month, and treat unexplained growth the way you'd treat an idle seat. Tie access to on- and offboarding like any other software.
What's the quickest place to start?
Your three or four most expensive tools. Compare their seat counts with last month's active users and check their renewal dates, and that short list will tell you quickly whether a wider review is worth the effort.
Where do you start?
Every unused seat started as a reasonable request. The leak comes from nobody going back to check, so the fix is a routine: know what you pay for, see who uses it, reclaim in a sensible order, decide before the renewal and close access when people leave. Run it on your most expensive tools first, and when the list of tools outgrows the spreadsheet, take the product tour to see the same routine running on its own.



.jpg)
