Per-User Pricing

Key Takeaways

  • Per-user pricing, also called per-seat pricing, ties a customer’s bill directly to the number of users with access to the product.
  • It is easy to understand, predictable to invoice, and scales naturally as a customer’s team grows, which makes it a common starting point for SaaS companies.
  • The main drawback is that it can discourage customers from adding users, creating a ceiling on account expansion and net revenue retention.
  • Variations such as per-active-user pricing and tiered seat models address some of those limitations while preserving the simplicity of the core model.

What Is Per-User Pricing?

Per-user pricing is a billing model where a SaaS company charges a fixed rate per user, per billing period. If the rate is $30 per user per month and a customer has 20 users, they pay $600 per month. Add five more users and the bill increases proportionally.

The model is also referred to as per-seat pricing, since each user occupies a “seat” on the account. The terms are interchangeable in most SaaS contexts.

Per-user pricing is one of the most widely adopted models in B2B SaaS, particularly for collaboration tools, CRMs, project management platforms, and productivity software where each individual user has a distinct login and workflow. Salesforce, HubSpot, and Microsoft 365 are well-known examples. For a broader look at how per-user pricing fits among other models, see Maxio’s ultimate guide to software pricing models.

 

How Per-User Pricing Works

The mechanics are simple. A vendor sets a price per user per month or per year. The customer’s invoice reflects the number of active seats on their account at billing time. If users are added mid-cycle, most billing systems prorate the charge for the remainder of the period.

There are a few common variations:

  • Standard per-user. Every named user on the account is billed at the same rate, regardless of how frequently they log in.
  • Per-active-user. Customers are only billed for users who were active during the billing period. This removes the friction of adding users to the account since dormant users do not increase the bill.
  • Tiered seat pricing. The per-user rate decreases as the number of seats increases. A company with 5 users might pay $40 per seat, while one with 50 users pays $25. This makes the model more competitive at higher volumes and rewards growth.
  • Role-based pricing. Different user types are priced differently. An admin seat might cost more than a read-only or viewer seat. This lets vendors capture more value from power users while reducing the barrier to adding light users.

 

Example: A project management tool charges $25 per user per month. A team of 10 pays $250. When the team grows to 15, the bill becomes $375 with no renegotiation required. The vendor’s revenue scales automatically with the customer’s headcount.

 

Strengths and Limitations

Per-user pricing is widely used because it is simple to explain, simple to invoice, and easy for customers to forecast. But it carries trade-offs that become more visible as a SaaS company scales.

Strengths Limitations
Simple to communicate and sell Can discourage customers from adding users to avoid a higher bill
Predictable revenue as seat count grows Does not reflect differences in how much value different users extract
Easy to invoice and reconcile Customers may share logins to minimize seat count
Scales naturally with customer team size Expansion revenue depends on headcount growth, not product value
Customers can forecast their own costs easily May underperform flat-rate in low-seat, high-usage scenarios

 

Why Per-User Pricing Matters for SaaS Finance Teams

For finance and RevOps teams, per-user pricing is straightforward to model and report on. Seat counts change predictably, invoicing is consistent, and revenue recognition is generally simpler than with usage-based models. But there are a few dynamics worth monitoring.

  • Seat count is a leading indicator of account health. Teams adding users are growing into the product. Teams reducing users may be signaling risk. Tracking seat movement alongside churn and net revenue retention gives a cleaner picture of account trajectory than revenue alone.
  • Expansion revenue has a ceiling. Unlike usage-based models, where revenue can expand as customers use more of the product, per-user pricing only grows when seats are added. If customers hold seat counts flat, ARR from those accounts stagnates.
  • Proration requires clean billing infrastructure. Mid-cycle seat additions and removals create partial-period charges that need to be calculated accurately and reflected in MRR reporting. Manual handling of proration at scale introduces reconciliation risk.

 

How Maxio Helps

Maxio supports per-user and per-seat billing natively, including proration for mid-cycle seat changes, tiered seat pricing, and role-based pricing configurations. Finance teams can track seat counts alongside MRR and ARR metrics in a single system, with automated invoicing that accounts for upgrades, downgrades, and mid-term changes without manual reconciliation.

For companies moving from per-user toward hybrid or usage-based models, Maxio supports the transition without requiring a rebuild of billing infrastructure. See Maxio’s usage-based billing overview for more on how the two models can coexist.

 

Frequently Asked Questions

What is per-user pricing in SaaS?

Per-user pricing is a billing model where customers pay a fixed rate for each user who has access to the product, typically billed monthly or annually. It is also called per-seat pricing.

What is the difference between per-user and per-active-user pricing?

Standard per-user pricing charges for all named users on an account, regardless of whether they log in. Per-active-user pricing only charges for users who were active during the billing period. The active-user model reduces the friction of adding new users since dormant accounts do not contribute to the bill.

What are the main drawbacks of per-user pricing?

The biggest drawback is that customers may limit the number of users they add to control costs, which caps expansion revenue for the vendor. It also does not reflect differences in how much value individual users extract from the product, and it can incentivize credential sharing to reduce seat counts.

How does per-user pricing affect MRR and ARR?

MRR and ARR from a per-user account change whenever seats are added or removed. Mid-cycle changes create prorated charges that need to be reflected accurately in revenue reporting. At scale, managing this manually introduces reconciliation risk.

When does per-user pricing stop making sense?

Per-user pricing can become limiting when product value does not scale linearly with team size, or when customers hold headcount flat but extract significantly more value over time. In those cases, a usage-based or hybrid model may capture revenue more accurately.

 

Related SaaSpedia Terms

Term Why It’s Relevant
Annual Recurring Revenue (ARR) Per-user pricing directly affects ARR. Seat additions drive expansion ARR; seat reductions can signal contraction. Tracking both alongside account health gives a more complete picture.
Monthly Recurring Revenue (MRR) Mid-cycle seat changes create prorated MRR movements that need to be captured accurately. Clean MRR reporting depends on billing systems that handle proration automatically.
Churn Seat reductions are an early indicator of potential churn. Finance teams monitoring seat count trends alongside churn metrics can identify at-risk accounts sooner.
Net Revenue Retention Per-user models grow NRR through seat additions. If customers hold headcount flat, NRR from those accounts will not improve without a pricing model change or upsell.
SaaS Subscription Models Per-user pricing is one of several subscription model options. Understanding how it compares to flat-rate, tiered, and usage-based models helps with pricing strategy decisions.
Value-Based Pricing Per-user pricing is not always aligned with the value a customer receives. Value-based pricing offers an alternative framework where price reflects outcomes rather than headcount.
Customer Acquisition Cost (CAC) In a per-user model, CAC-to-LTV ratios improve as seat counts grow within an account. Expansion from existing customers is generally less expensive than acquiring new ones.

 

Related Maxio Content

Article What it covers
Ultimate Guide to Software Pricing Models Covers per-user pricing alongside flat-rate, tiered, usage-based, and value-based models, with guidance on when each makes sense for SaaS companies.
Understanding Enterprise Pricing Models Covers per-user and per-active-user pricing in the context of enterprise SaaS, including how customers respond to seat-based cost structures.
Usage-Based Pricing: Definition, Benefits, and Implementation A useful counterpart to per-user pricing, covering how usage-based models work and when they capture revenue more effectively than seat-based approaches.
Guide to SaaS Pricing Models: Strategies and Best Practices Practical guidance on selecting and evolving a pricing model, including the role of per-user pricing in early-stage and scaling SaaS businesses.