Case note
Unused AI plans, overlap, and limit-driven routing
A practical buyer question: are we paying for unused or overlapping AI plans, and is work being routed by limits rather than by fit?
Three patterns show up in finance and usage records, and they are easy to miss if you only look at one vendor dashboard.
First, seats or licenses with no activity in the period your records cover. A seat that still appears on an invoice without usage is a fact about the seat row, not a judgment about anyone who holds it.
Second, overlapping plans: two tools that do the same job for the same cost center, both invoiced, with no record of which work goes where. Overlap becomes a problem when nobody can say what each plan is for.
Third, limit-driven routing. A rate limit or quota is hit, so traffic fails over to another model or vendor. That may be the right operational choice. It is the wrong silent choice if the fallback is a poorer fit and nobody inspects the route.
Synthetic example. A cost center carries two writing assistants and a general model plan. The seat export shows seats with no calls. Usage moves to a fallback model at the same timestamps as rate-limit events. The records show unused seats, overlapping plans, and routing that followed a limit. This illustration is not customer data.
What to inspect
- Seat and license exports joined to usage, at seat or team level, not as a ranking of individuals.
- Invoices and plan names across vendors, mapped to cost centers (Sales, Finance, Engineering, Customer Support).
- Rate-limit, quota, and similar limit events in provider logs, with the model or route used next.
- Spend exports for the same period, so billed usage can be attributed to a plan and a route.
Do not multiply unused seats by a list price to invent an avoided-cost figure. What you do about an unused seat is a separate decision.
For work that may not need a new agent at all, see When an existing tool beats an AI agent. For why activity views are not the same as attributable spend, see Why AI ROI beats dashboards and proof.
One next action
Export seats and invoices for every AI tool in scope. Mark seats with no activity in the period, list plans that serve the same job in the same cost center, and list where a recorded limit was followed by a fallback route.
If you want those spend and seat rows inspectable with lineage, Overdrive helps you maximize your AI spend from inside your AI assistant. It is a remote MCP server with OAuth sign-in, and it works today in Claude, ChatGPT, and Grok Bot (setup steps). Start with a labeled sample pack and expand the lineage on each figure. Using Overdrive with your own company data is still in security review. The plan is for you to connect the tools you already use instead of uploading files, and those connectors are not available yet.
Claims and caveats
- This post claims that unused seats, overlapping plans, and limit-driven routing are visible in invoices, seat exports, and usage logs, and that they should be reported as records rather than as an avoided-cost estimate.
- It does not claim that unused seats should be removed, or that overlap is always excess. It reports no counts, rates, or money figures, and it does not rank people.
- The short illustration is a synthetic example. It is not customer data and it is not a result.