Pricing pattern
Per-seat pricing
Fixed price per user per month. The dominant collaborative-SaaS pattern (Slack, Notion, Linear, GitHub). Predictable for procurement, aligns revenue with team size, but breaks when teams game it via shared logins or when usage varies wildly across users.
Verified · editorial policy
TL;DR
As of , the short version is: Fixed price per user per month. The dominant collaborative-SaaS pattern (Slack, Notion, Linear, GitHub). Predictable for procurement, aligns revenue with team size, but breaks when teams game it via shared logins or when usage varies wildly across users.
Per-seat pricing TL;DR
- Pattern
- Per-seat pricing
- TL;DR
- Fixed price per user per month. The dominant collaborative-SaaS pattern (Slack, Notion, Linear, GitHub). Predictable for procurement, aligns revenue with team size, but breaks when teams game it via shared logins or when usage varies wildly across users.
- When it works
- When the product is genuinely collaborative – each user gets distinct value from their own account. When team size correlates with willingness-to-pay (5-person team can afford less than 50-person team). When procurement processes prefer predictable seat-based billing. When the product has a per-user view/state/dashboard.
- When it backfires
- When users can share accounts without losing value (single login for a 5-person team). When the product has heavy active users and many passive users (some users use 95% of features, others log in monthly) – per-seat overcharges the passive cohort. When team growth slows revenue growth.
- Last verified
- May 20, 2026
The mechanics
Price stated as $X per user per month. Total bill = $X × number of users. Annual discount (15 to 25%) usually offered. Often combined with feature tiers ($X / user / month for Standard, $Y / user / month for Plus).
Where you see this in the wild
Slack
Pro $7.25/user/month, Business+ $12.50/user/month. Classic per-seat with feature tiers stacked.
Linear
Standard $8/user/month, Plus $14/user/month. Clean per-seat with annual option.
Notion
Plus $10/user/month, Business $18/user/month. Per-seat plus per-tier.
Figma
Professional $15/editor/month, Organization $45/editor/month. Per-seat with 'editor vs viewer' distinction.
Fit assessment
When it works
When the product is genuinely collaborative – each user gets distinct value from their own account. When team size correlates with willingness-to-pay (5-person team can afford less than 50-person team). When procurement processes prefer predictable seat-based billing. When the product has a per-user view/state/dashboard.
When it backfires
When users can share accounts without losing value (single login for a 5-person team). When the product has heavy active users and many passive users (some users use 95% of features, others log in monthly) – per-seat overcharges the passive cohort. When team growth slows revenue growth.
The Brunson lens
Per-seat pricing maps the offer onto an axis the buyer already understands (team size). The Brunson lens question: does each seat get a distinct Stack? If the answer is 'yes, each user has their own dashboard / settings / output' the per-seat model fits. If the answer is 'one team shares one workspace' the pattern is fighting the actual usage and buyers will resent it.
Common implementation mistakes
- Per-seat for a product that doesn't have per-user value. Buyers create one shared login; ARPU collapses.
- No 'viewer' tier (free or cheap). Forces companies to either pay full price for read-only users or block them from the tool – usually they block.
- Per-seat plus per-feature plus per-usage. Three-dimensional billing is impossible to forecast and slows enterprise sales.
- No volume discounts at 50+ seats. Enterprise procurement demands them; not offering them costs deals.
- Per-seat at very low price points ($1–$3/user/month). Doesn't justify the procurement overhead for buyers; doesn't generate enough revenue per account.
Questions founders ask about per-seat pricing
What's a good per-seat price point?
$8 to $25/user/month is the sweet spot for most B2B SaaS. Below $8 procurement friction outweighs revenue; above $25 buyers start scrutinizing per-user value. Outside that band requires very specific positioning.
Should I offer a viewer-only tier?
Yes, free or very cheap. Forces full-pricing on read-only users blocks them from the tool, which kills viral growth. Free viewer tiers are a network-effect lever.
How do I handle seasonal team-size fluctuations?
Bill on monthly average users with end-of-month true-up, OR offer 'admin can add/remove seats anytime, pro-rated'. Buyers hate annual commits for fluctuating team sizes; flexibility wins enterprise.
Related Brunson terms
Now diagnose your own pricing page
Patterns are the structure. The free 90-second Launch Diagnostic checks whether your pricing page is being read as Wrong Person, Weak Offer, or Weak Belief – the upstream diagnosis that determines whether any pattern works.