The model is straightforward: pick a plan, count users, multiply. That simplicity is why it dominated B2B SaaS for two decades, and why it is now under pressure from usage-based alternatives and AI tools that cut the number of seats a team actually needs.
Per-seat pricing is a SaaS model where the invoice scales directly with the number of users, or seats, who have access to the product. Each active account adds a fixed monthly or annual fee, so a team of ten pays ten times what a team of one pays at the same tier. It is the classic B2B default because it is simple to quote, simple to forecast, and lines up with the way enterprise procurement already buys software.
What per-seat pricing actually is, why it took over B2B SaaS, and the pressures bending it today.
Per-seat pricing charges a flat recurring fee for each user granted a login. Ten users means ten seats on the invoice. Each seat typically unlocks the same feature set at a given tier, so cost scales linearly with headcount rather than with activity, outcome, or data volume inside the product.
A rep can price a deal on a single phone call: pick the tier, count the users, read the number back. Procurement sees a predictable annual cost tied to headcount they already track in HR systems. The simplicity made per-seat the default B2B motion for CRMs, help desks, project tools, and most office software.
Seat counts move slowly, so revenue is a stable number across the year. Finance teams can model next year's ARR by projecting headcount growth times the price card. That predictability is why boards and investors still prefer per-seat businesses when they value a company, even as the model shows its age.
A seat on the invoice is a seat whether the person logs in daily or once a quarter. Dormant licenses add up fast in large orgs, and buyers notice. The invoice stays flat during slow quarters when headcount holds, which feels unfair to a finance leader cutting other costs.
When seat prices climb, teams quietly share credentials to avoid buying more licenses. The behavior violates most terms of service and breaks audit logs, but it is widespread enough that vendors build detection systems. Shared logins are the clearest market signal that per-seat pricing has been stretched past its fit.
AI tools let a smaller team cover work that previously required more people, which cuts the headcount that drives seat counts. A sales org that runs leaner because of AI buys fewer seats of every tool it uses. The pricing model that depends on growing headcount is being squeezed by the technology that cuts headcount.
Every per-seat plan is built from the same handful of parts. Vendors call them different things, but once you can read the shape you can read any seat-based pricing page in the category.
Each tier has a per-seat rate quoted monthly or annually. The rate rises with the feature bundle, so a basic seat is cheaper than a professional seat is cheaper than an enterprise seat. Annual billing almost always carries a discount off the monthly rate to reward committed revenue.
Many plans enforce a minimum seat count, especially at higher tiers. The floor filters out small accounts that would carry a lot of support cost at a tiny invoice, and it gives the sales motion a known starting price. Minimums usually scale up with tier so the enterprise plan starts at a higher floor.
Buyers who add seats at volume typically negotiate a lower effective rate. Discounts kick in at tier breakpoints like fifty, one hundred, and five hundred seats, and the published list price is rarely what a large customer actually pays. The discount structure is the hidden half of every per-seat price card.
Mature products split seats by role: a full seat for an active user, a lighter seat for a read-only viewer, and sometimes a free seat for a guest or external collaborator. Role tiers let the vendor sell into orgs where only part of the headcount needs full access, which is nearly every org past the first fifty people.
Most per-seat SaaS runs on an annual contract, with monthly billing available at a premium. The annual term locks revenue, simplifies renewal, and gives procurement a single approval moment per year. Mid-term seat adds are usually co-termed so the whole account expires on the same date.
Most contracts allow adding seats mid-term at the same rate, prorated. Removing seats mid-term is almost never allowed, which is the asymmetry buyers complain about most. True-downs happen at renewal, which is why finance teams audit license usage in the weeks before every contract comes up.
Per-seat pricing did not become the default by accident. It survived two decades of pricing experiments because it solves real problems for both sides of the deal, especially in the enterprise motion where fit with procurement matters as much as fit with the end user.
Price times users equals invoice. A rep can quote a deal in a sentence, a buyer can approve one in minutes, and the finance team can audit it in a glance. The simplicity cuts sales cycle time and reduces the surface area where a deal can stall waiting for pricing questions to resolve.
Enterprise procurement is built around fixed POs and headcount-based planning. Per-seat pricing maps cleanly onto both. The procurement team can approve a known annual spend tied to a known seat count, which is the shape they are already running for every other SaaS line in the budget.
The customer tells the vendor how fast they plan to hire, and the vendor can forecast the account's revenue trajectory with reasonable confidence. The vendor's own revenue forecast then rolls up as a sum of account forecasts, which is why per-seat businesses have cleaner financials than usage-heavy peers.
A fixed seat count puts a ceiling on the support load the vendor has to plan for. Each seat is a predictable amount of training, onboarding, and ticket volume. Capacity planning on the support team becomes a headcount problem instead of a traffic forecasting problem, which is simpler to run.
When a customer grows its team, the account grows automatically. The land-and-expand motion in per-seat SaaS does not require a product change, a usage spike, or a new negotiation. It only requires the customer to hire, and the account manager to notice. Expansion is a conversation about headcount, not consumption.
A small team with a handful of users pays a small invoice, which keeps the model accessible to new buyers. Flat pricing would overcharge the two-person startup. Pure usage pricing would feel arbitrary. Per-seat lands in a middle that most small teams can swallow without a finance review.
The model is under more pressure than it has ever been. Buyers have gotten sharper, AI has cut headcount, and competing pricing shapes have shown what alternatives look like. The pains below are the ones every per-seat vendor is hearing from customers right now.
In a large org, half the seats on a tool often go unused in any given month. Buyers can see that in their own usage reports, and the invoice looks worse every time they open it. Dormant seats are the loudest complaint in every per-seat renewal, and the one vendors have the least good answer for.
When a seat is too expensive relative to how often it gets used, teams share credentials. The practice shows up on audit logs as impossible travel and simultaneous sessions. Vendors build detection to catch it, buyers resent being policed, and the whole exchange poisons trust that per-seat pricing depends on.
AI tooling lets a smaller team do what a larger team used to do. A sales org that writes drafts, scores leads, and triages inboxes with AI needs fewer reps, which means fewer seats of every tool the reps use. The pricing model is pinned to the headcount curve that AI is actively flattening.
A seat that generates ten million in pipeline costs the same as a seat that generates nothing. Buyers see the mismatch and ask for pricing that reflects value delivered, not just access granted. The model treats every user as equal, when in reality the top performer is worth ten times the average.
Modern work includes partners, contractors, and customers in the same workflows. Per-seat pricing was designed for employees with full access, and it struggles to price external users who need a view but not a license. Teams end up buying full seats they do not need or routing collaboration outside the tool entirely.
The average mid-market org runs more than a hundred SaaS tools. Every one of them wants a seat per employee. The compounding cost per headcount has become its own finance problem, and procurement teams are increasingly ruthless about cutting seats or consolidating onto fewer platforms.
Strkr tracks the users who matter, surfaces dormant seats before renewal, and lets revenue teams compare per-seat, tiered, flat, and usage motions on the same customer record. One tool, one record, one pricing conversation.
Flat pricing charges one fixed fee for the whole account, regardless of how many users log in. Per-seat pricing charges a fee for each user, so a team of fifty pays fifty times what a team of one pays at the same tier. Flat is simpler for the buyer and caps the vendor's revenue per account, while per-seat scales revenue with the customer's headcount but adds a cost penalty for inviting more users.
The two terms are used interchangeably in most SaaS pricing pages. Per-seat and per-user both describe a model where the invoice scales with the number of licensed accounts in the product. Some vendors prefer per-user because it emphasizes the human, and some prefer per-seat because it emphasizes the license. The mechanics on the invoice are identical.
Tiered pricing is about which feature bundle the account buys, like basic versus professional versus enterprise. Per-seat pricing is about how many users within that tier the account is paying for. The two usually combine: a plan has a tier that sets the feature set and a per-seat rate inside that tier. A customer picks a tier first and a seat count second.
Per-seat pricing is simple to quote, maps cleanly onto enterprise procurement, and produces the predictable annual revenue curve that investors and boards reward. The model also captures natural expansion as customers hire, without requiring the vendor to renegotiate. Those strengths are why most B2B SaaS still defaults to per-seat even as usage-based alternatives have gained ground.
A dormant seat is a licensed user who rarely or never logs in but still appears on the invoice. In a large org, dormant seats often reach thirty to fifty percent of the total license count. They are the loudest complaint in per-seat renewals because buyers can see the gap between what they pay and what they use, and they usually push to true down at the next renewal cycle.
A shared login is one set of credentials used by more than one person to avoid paying for additional seats. The practice violates most terms of service and breaks audit trails, but it spreads when seat prices climb past what casual users feel is fair. Shared logins are the clearest signal that per-seat pricing has stretched past its fit, which is why vendors build detection systems and offer cheaper viewer tiers.
AI tooling lets a smaller team do work that previously required more people, which cuts the headcount that drives seat counts. A sales org running leaner because of AI buys fewer seats of every tool it uses. The pricing model is pinned to a headcount curve that AI is flattening, which is why more vendors now offer hybrid plans that mix a seat base with usage components or value-based packaging on top.
Per-seat pricing is a poor fit when usage varies widely within an account, when the value delivered has no relationship to headcount, when guest and external collaboration is central to the product, or when the buyer explicitly wants pricing that scales with outcomes. Products in those shapes usually move to usage-based, tiered, or hybrid pricing where the invoice tracks something other than the user count.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
