What AI tools actually cost a team
Nobody escalates a twenty dollar decision, which is exactly why these things are priced at twenty dollars.
The short answer
AI spend accumulates through two channels that behave differently: per-seat subscriptions that spread by word of mouth and are never removed, and usage-based API billing that has no fixed number to notice. Most teams cannot state their monthly total, and it is nearly always higher than they guess.
The formula
subscription cost = seats x price per seat, per tool
wasted seats = seats not used in the last 30 days x price per seat
true monthly = active subscriptions + usage-based billing
cost per unit = true monthly / units produced (tickets, documents, images)
Cost per unit is the figure that turns a scary total into a decision. Without it there is no way to distinguish a rising bill that is a problem from one that is evidence of adoption.
Worked example
A twelve person team with a general assistant at $30 a seat, two overlapping writing tools, and an API workload:
assistant: 12 seats x 30 = 360, but 4 unused = 120 wasted
writing tool A: 8 seats x 45 = 360
writing tool B: 6 seats x 40 = 240 (overlaps A)
API workload = 388
total = 1,348 a month
unused seats + the duplicate tool = 360 → 26.7% of spend
$1,348 a month, of which $360 buys nothing. That is $4,320 a year, and no single decision in the chain was large enough for anyone to question.
Why per-seat pricing accumulates quietly
Adoption spreads by recommendation, which is what you want, and removal never spreads at all. Someone leaves and their seat stays. Someone stops using a tool and nobody notices because the invoice does not change.
Annual plans hide it for longer. A tool paid annually disappears from monthly review entirely and resurfaces eleven months later as a renewal nobody has thought about.
The API line behaves completely differently
Usage-based billing has no number to notice until the invoice. It can be stable for months and then triple because a feature shipped, traffic grew or a loop retried, with no decision behind the change.
This is the one to put a hard cap on rather than an alert. It is also the one to measure per unit, because the total on its own tells you nothing about whether the increase was good news.
The audit that takes an hour
List every tool, its cost, its seats, and when each seat was last active. The last column is where the money is, and most teams find between a quarter and a third of seats are dormant or duplicated.
Duplication is the common finding rather than extravagance. Two writing assistants because different people chose differently. Three transcription services. A specialised tool bought for something the general assistant already does.
None of this is an argument for cutting. Some of these tools return many times their cost, which is the reason to know the number rather than a reason to skip knowing it.
What this leaves out
- Prices are illustrative. Per-seat AI pricing moves quickly and enterprise agreements differ substantially from list.
- Assumes seat activity is measurable. Not every tool exposes it, and the ones that do not are the ones most likely to be carrying dormant seats.
- Excludes the compute cost of self-hosted models, which trades a subscription for infrastructure and staff time.
Common questions
- How much should a team spend on AI tools?
- There is no benchmark worth quoting, because it depends entirely on what the tools replace. The answerable question is cost per unit of work produced, and whether that number is falling as adoption rises.
- Should we standardise on one tool?
- Usually yes for overlapping general-purpose tools, where the duplication is pure cost. Less so for genuinely specialised ones, where forcing a single tool creates workarounds that cost more than the licence saved.
- How often should we audit this?
- Quarterly is enough for subscriptions and monthly for usage-based billing, because they drift at completely different speeds. Tying the subscription review to a calendar reminder is what stops it becoming an annual surprise.
Spreadsheets that do this
The formulas above, already built and checked — so you fill in your numbers rather than the arithmetic.
Related guides
Last reviewed 22 August 2026