Pricing model
Per-seat pricing model
Per-seat pricing charges per active user inside a customer's account. It is the dominant B2B SaaS model and the most-attempted indie SaaS pricing model — but works only for products where multi-user collaboration is core to the value.
Verified · editorial policy
How the model works
Customer pays $X per seat per month. Adding teammates increases the customer's bill. Removing teammates reduces it. Pricing scales with team size; revenue scales with both customer count AND average customer team size.
Best for
Collaborative products where multiple team members get value (project management, design tools, internal-tooling platforms). Products where each user generates measurable individual value. Mature SaaS where customer companies have stable team structures.
Worst for
Solo-user products (forms, calendars, individual analytics). Products where 'one person can do the work but others want to look'. Products with high seat-creep churn (teams adding then removing seats monthly).
Unit-economics implications
- ARPU varies wildly by customer team size. A 5-seat customer and a 50-seat customer have 10x different revenue but similar support cost.
- Expansion revenue is built in — customers grow seats organically as their team grows.
- Churn risk is per-seat, not per-customer. Customers can downgrade by removing seats without canceling.
- Sales cycle lengthens at higher seat counts — 50-seat deals require procurement review at the customer.
Common implementation mistakes
- Per-seat pricing on solo-user products. If one person can do the work and others just want visibility, per-seat creates resentment and incentivizes shared logins.
- Identical per-seat price regardless of role. Read-only seats often deserve lower pricing than active-user seats.
- No minimum seat count. Customers buy 1 seat to test, then never expand. A 3-seat minimum forces the collaboration value.
- Counting inactive users as billed seats without warning. Triggers churn the moment the customer notices.
Positioning trap to watch
Per-seat pricing on a product where multi-user value is weak creates resentment and reduces total revenue. Customers find ways around it (shared logins) and the per-seat math breaks. If your product can be used productively by one person, per-seat is almost always the wrong model.
Pricing teardowns of products using this model
Frequently asked
- Should the first seat be free?
- Sometimes yes, as a freemium hook for the team. Free first seat + paid second seat onwards forces the team-conversion conversation. Works for products where individual use is partial-value and team use is full-value.
Other pricing models
Diagnose the page, then pick the model
Pricing model is downstream of positioning. The free diagnostic labels which Brunson failure mode your page hits; the right pricing model follows from the positioning.