Glossary
Per-seat pricing
The bill tracks headcount, which is only a proxy for value received.
Definition
Per-seat pricing is a model in which a customer pays a fixed fee for each named user per billing period, regardless of how much any of them uses the product. The model descends from per-user software licensing, and it dominates business software because it is simple to quote, simple to forecast, and grows automatically as a customer's headcount grows.
- Also called
- Per-user pricing
- Unit
- A named user per period
- Vendor benefit
- Predictable, forecastable revenue
Why it became the default
Per-user licensing predates SaaS: on-premise software was sold in user counts long before anything was rented monthly. Subscription software inherited the unit because it solved a real problem. Pricing needed a number that a buyer could count, a salesperson could quote, and a finance team could forecast, and headcount is the only such number every company already knows.
The model is also the reason collaboration software is priced the way it is. Value in a workspace tool rises with the number of people in it, so the seat is a rough proxy for value delivered, and a legitimate one for most of the product's history.
Where the proxy breaks
Occasional users
The finance manager who opens the tracker twice a month costs the same as the engineer living in it. Teams respond by not buying seats for people who should have them, which quietly damages the product's usefulness.
Multiplication across tools
Four per-seat tools at $10 to $20 each is $40 to $80 per person per month before anyone has done any work. The unit is the same in each, so the count multiplies rather than adds.
Growth taxes collaboration
Adding a contractor, a client or a temporary reviewer has a price, so organisations exclude people from the system of record to avoid the line item.
AI does not fit the unit
AI features cost the vendor money per use, not per user, so they arrive as per-seat add-ons that overcharge light users and undercharge heavy ones. The unit stopped matching the cost structure.
Commonly confused with
| Term | What it means | The difference |
|---|---|---|
| Per active user | Charges only for users who used the product in the period | A meter on activity. Rarer, because it makes vendor revenue less predictable. |
| Concurrent-user licensing | A pool of simultaneous sessions shared across many people | Common in on-premise and specialist tools; the seat is not tied to a person. |
| Tiered pricing | Price bands by feature set or company size | Often combined with seats. Tiers decide what you get; seats decide how many pay for it. |
| Platform fee | A flat charge for the account regardless of users | Headcount-independent. Sometimes paired with a usage meter in hybrid models. |
The alternative Polaris uses
Polaris charges nothing per seat and nothing for the software: unlimited humans, tasks, workstreams and docs, with the Chief of Staff included in every organisation. Revenue comes from delivered work at roughly two dollars per human-equivalent hour, itemised on a work log you can challenge.
The consequence worth stating plainly is that adding a person to Polaris costs nothing, so there is no financial reason to keep anyone outside the system of record.
Related terms
Usage-based pricing
The bill follows consumption, which cuts both ways for buyer and vendor.
Tool sprawl
The expensive part is not the licences. It is that nothing is authoritative any more.
Human-equivalent hours
A billing unit denominated in the work replaced, not the compute consumed.
Per-seat pricing and usage pricing charge for different things
One model prices access. The other prices output. Almost every argument about software cost is really about which of those you are buying.
Tool stack cost for a 10-person team
The size where the free tiers run out on all three products at roughly the same time.
What your work stack actually costs
Sixteen pages of pricing arithmetic you can check yourself, with the billing basis named on every row.
Questions people ask
+Why do most SaaS companies still price per seat?
Because it is legible and forecastable for both sides. A buyer can compute next year's bill from next year's hiring plan, and a vendor can model revenue from customer headcount. Those are real advantages that no consumption meter matches.
+What is the true cost of a per-seat stack?
Multiply the number of people by the sum of the per-seat prices of every tool they need, then add the AI add-ons that are now sold on top of each. A ten-person team on four mid-tier tools is typically paying several hundred dollars a month before a single task is completed.
+Are AI seats the same as software seats?
Structurally yes, economically no. A software seat costs the vendor almost nothing to serve, so an unused seat is pure margin. An AI seat carries real inference cost per use, which is why per-seat AI pricing is unstable and why so many AI products have moved to credits or meters.
Related
Usage-based pricing
The bill follows consumption, which cuts both ways for buyer and vendor.
Tool sprawl
The expensive part is not the licences. It is that nothing is authoritative any more.
Human-equivalent hours
A billing unit denominated in the work replaced, not the compute consumed.
All-in-one workspace
One data model behind documents, tasks and conversation, instead of three products and a pile of integrations.
Per-seat pricing and usage pricing charge for different things
One model prices access. The other prices output. Almost every argument about software cost is really about which of those you are buying.
Tool stack cost for a 10-person team
The size where the free tiers run out on all three products at roughly the same time.
The cost of AI subscriptions for a team
Five figures a year at fifty people, and no shared record of what any of it produced.