How to Identify Unused AI Seats Before Renewal

A renewal notice arrives with 400 AI seats, a larger annual commitment, and a familiar question from finance: who is actually using these licenses? To identify unused AI seats accurately, you need more than a last-login report. You need to reconcile procurement records, identity data, product activity, and the business purpose behind each seat.

That distinction matters. Removing every account that has not logged in recently can disrupt a legitimate workflow or eliminate access just before a project starts. Leaving every assigned seat untouched turns a small licensing decision into recurring, unowned spend. The objective is not to cut access indiscriminately. It is to establish which seats are active, necessary, and owned before the next invoice locks in another term.

Why unused AI seats are harder to spot than they look

Traditional SaaS license reviews usually begin with a simple assumption: one user, one license, one product. AI tools complicate the picture. An employee may have a company-provided seat in one application, access to another through a bundled productivity suite, and a separate account purchased on a corporate card. Meanwhile, engineering may consume a vendor's API through a shared platform account rather than individual seats.

These are different cost types and should not be managed as one problem. A named-user subscription is a fixed commitment. API consumption is a variable expense. Both belong in an AI spend program, but the evidence required to manage them is different. A seat can be unused even when the vendor bill is predictable. An API account can look quiet at the user level while supporting a production agent serving thousands of internal requests.

The second challenge is ownership. The procurement system may list an executive sponsor, while the actual users sit across sales, product, legal, and customer support. If no department owns the renewal decision, no one has an incentive to challenge the count. Finance sees a vendor invoice. IT sees identities. Neither view alone answers whether 400 seats remain justified.

Define what counts as an unused AI seat

Do not use a single inactivity threshold as your definition. A better approach is to classify seats into operational categories, then set an action for each category.

1. Unassigned seats

These are the clearest candidates for removal. They appear on the vendor contract but are not assigned to an active employee or approved contractor. Check for pending invitations and recently provisioned accounts before reclaiming them, but an unassigned seat should not survive a renewal without a documented reason.

2. Assigned but never activated

A user may have accepted a license but never completed meaningful setup or used a core feature. This often points to overprovisioning during a broad rollout. It can also reveal weak enablement: a team received access but never received a use case, training, or manager direction.

The financial action depends on the cause. If the tool has no identified business use, reclaim the seat. If the use case is valid but adoption failed, the department should explicitly decide whether to fund training and retain a smaller pilot group. Passive retention is not a strategy.

3. Inactive seats

An inactive seat has historical activity but no meaningful recent use. The appropriate lookback period depends on the role and workflow. Thirty days may be adequate for a daily assistant used by customer support. Ninety days may be too aggressive for legal, finance, or strategy teams that use an AI application around monthly close, quarterly planning, or specific transactions.

Measure meaningful activity rather than only a login event. A login can be a password reset, a browser session, or a user checking whether access still works. Look for actions that reflect value: completed workflows, created projects, analyzed documents, or use of the product's primary function.

4. Low-use but business-critical seats

Some seats should remain even with sparse activity. An incident-response lead, an executive assistant supporting board materials, or a specialist who uses a tool for occasional high-value work may have a legitimate need. These exceptions should be named, owned, and reviewed - not treated as vague justifications for keeping a full population of dormant accounts.

Build an evidence-based review process

The most reliable seat review joins four data sources: the contract or invoice, the vendor's seat roster, the company's identity directory, and product-usage data. Each source corrects a blind spot in the others.

Start with the commercial baseline. Capture committed seats, billing cadence, renewal date, true-up terms, unit price, renewal notice deadline, and whether unused seats can be reduced mid-term. A company that starts this review two weeks before auto-renewal may identify waste but still be unable to act on it.

Next, export the seat roster with user email, license type, assignment date, last activity, and administrator status. Normalize email addresses against the identity directory. Duplicate aliases, employees who have left, contractors whose engagements ended, and users transferred to other departments often appear only after this comparison.

Then ask departments to validate the gray area. Do not send a generic message asking managers whether they "need" their licenses. That question almost always produces a yes. Send a short list of named users with a clear status: no activation, no activity in 90 days, or no matched active identity. Ask the manager to choose one of three actions: retain with a business reason, reassign, or remove.

This turns the review into an accountable decision. It also creates an audit trail that explains why the company retained exceptions and who approved them.

Assign the financial impact to an owner

A reclaimed seat is more than a usage metric. It changes a future commitment, and that change should be visible in departmental reporting. If a central IT budget pays for every AI subscription, business teams may have little reason to right-size their allocations. If every seat is charged directly to a department without a shared governance process, teams may evade controls by purchasing outside approved channels.

A practical middle ground is showback first, then chargeback where the organization is ready. Showback reports the cost of assigned seats to each cost center without moving the expense. Chargeback records the allocation in the financial system so the receiving department carries the expense in its budget.

For example, assume an annual AI subscription costs $120,000 for 300 seats, or $400 per seat. After a review, 45 seats are unassigned or inactive without a valid exception. Reducing the renewal to 255 seats lowers the annual commitment by $18,000. If the remaining seats are allocated by employee department, finance can book the expense using an allocation schedule rather than leaving the entire amount in a central software account.

A simplified monthly entry might debit Sales AI Software Expense $4,000, Product AI Software Expense $3,000, and Finance AI Software Expense $1,500, while crediting a central IT clearing account for $8,500. The exact accounts depend on the chart of accounts and accounting policy, but the principle is consistent: the operational roster should support the financial record.

Avoid false savings that create more cost

Seat reduction has trade-offs. If you cut below actual demand, employees may share accounts, buy unapproved subscriptions, or lose access during critical work. Those outcomes create security, compliance, and forecasting problems that are more expensive than a handful of unused licenses.

Keep a small, explicit buffer only when the business case supports it. For a fast-growing team with regular onboarding, a limited pool of unassigned seats may reduce administrative friction. The pool should have an owner, a target size, and a monthly aging report. An unassigned seat held for six months is not a buffer. It is unused capacity.

Also separate adoption decisions from entitlement decisions. A low adoption rate may mean the product is poorly matched to the team, not that every individual employee should be pushed to use it. Measure outcomes where possible, but do not manufacture utilization merely to justify a contract already signed.

Make seat hygiene part of AI financial operations

A one-time cleanup produces savings once. A repeatable control prevents the same waste from returning. Establish an owner for each AI vendor, require a cost center or project code when a seat is assigned, and run a monthly exception report for unassigned, inactive, and departed-user seats.

Quarterly reviews work well for most organizations, with an additional review 90 to 120 days before a major renewal. The renewal review should combine seat data with broader AI spend: fixed subscriptions, API usage, gateway costs, and cloud AI services. That is the point where finance can compare committed access with actual operational demand and update the forecast.

Meridian is designed for this broader Agent FinOps work: connecting AI spend to teams, agents, and projects so operational usage can support allocations, chargebacks, and finance-ready records. But the underlying discipline applies regardless of tooling. Every AI cost should have an owner, a measurable basis for allocation, and a documented reason to continue.

The most useful question is not, "Can we remove licenses?" It is, "Can we explain every license we plan to renew?" When finance and technology can answer that question with evidence, AI adoption becomes easier to fund - and far easier to govern.