Glossary
Seat
A seat is one named person's access under a plan, the unit software has been sold in for decades and the one AI pricing fits least comfortably.
In plain terms
You buy a number of them and assign each to a person. It is the unit almost all business software has used, it is easy to budget and easy to audit, and everybody understands it. The awkwardness with AI tools is that a seat measures people while the underlying cost is driven by use, and one person can consume vastly more than another without anybody doing anything unusual.
Why it matters
Because the unit shapes behaviour, usually in the wrong direction. Where access is counted per person, the instinct is to limit who gets one, which is the opposite of what an organisation wants from a tool that only pays back through use. Teams end up rationing the cheap part while the expensive part, the consumption, is unaffected by the rationing.
How it works
A seat is a licence to a named individual, not a concurrent slot. Two people cannot share one by taking turns under most agreements, and the reassignment rules matter more than they look: whether a seat can move to a replacement immediately, monthly or not until renewal decides whether the count reflects your organisation or your history.
The unit and the cost driver point in different directions for AI tools. A seat prices a person, while what the vendor pays for is what that person asks the system to do, and the gap between a light and a heavy user of the same tool is large. That mismatch is why a seat is often paired with an allowance rather than sold alone, and asking what a seat actually includes is the way to find out whether yours is.
Partial users are where seat pricing is least satisfactory. Someone who needs a tool twice a month costs the same as a daily user, so those people are the first to be denied access, and they are frequently the ones for whom a small amount of use would have been most valuable. The pattern is predictable enough to be worth watching for.
The count is also an administrative artefact rather than a fact about the organisation. Leavers who were never removed, duplicates from a reorganisation and speculative allocations all inflate it, and a review before a renewal is one of the few reliably worthwhile exercises in this area.
What the count reflects
Seen in the wild
A team plan for an assistant where each person needs their own named access rather than a shared login.
ChatGPTA CRM offering a small number of free named users, which is a seat count used as the boundary of a free tier.
AttioA workspace where AI is added per member, so the count follows the existing membership rather than who uses the AI.
Notion AI
Common misconceptions
People assume
A seat can be shared if we take turns.
In fact
Most agreements name an individual and prohibit exactly that, and it is one of the few terms vendors check. What some products do offer is reassignment, which is a different arrangement with its own timing rules, so the question to ask is how quickly a seat can move rather than whether two people can use one.
People assume
Fewer seats means lower cost.
In fact
Lower licence cost, and for AI tools the licence is often not the largest part. Where consumption is charged separately, restricting who has access limits the cheap component while leaving the expensive one to whoever remains. It also suppresses exactly the light, occasional use that would have been inexpensive.
Telling them apart
Seat vs Usage
Seat
Counts people. Predictable, easy to audit, indifferent to how much they do.
Counts work. Tracks value more closely, harder to forecast.
If adding a person changes the bill and adding work does not, you are on seats.
Questions
- Can a seat be reassigned?
- Often, and the timing is the part worth checking: immediately, at the next billing period, or only at renewal. That single term decides whether your count tracks the organisation you have or the one you had, and it is easy to miss because it reads as administrative detail.
- How should we decide how many we need?
- Start from who the tool is for rather than from a budget, then review the count at renewal against who actually used it. Both directions of error are common: paying for leavers who were never removed, and denying access to occasional users whose small use would have been the cheapest value available.
- Why do AI tools combine seats with allowances?
- Because a seat prices a person and the vendor's cost follows what that person does, and those diverge widely. The combination gives the buyer a predictable base and the vendor protection against a heavy user, which is a reasonable compromise even though it makes comparing two plans harder.
Key takeaways
- A seat names an individual; it is not a concurrent slot.
- The unit counts people while the cost follows use, which is the core mismatch.
- Rationing seats limits the cheap part and suppresses valuable occasional use.
- The count drifts with leavers and reorganisations; review it before renewal.
Last checked July 2026