Seat-based pricing charges customers based on how many people use the product. Each user occupies a "seat," and the customer pays per seat. It is one of the most established pricing models in SaaS because it scales naturally with the customer's organization: as their team grows, their bill grows proportionally.
How seat-based pricing works
A plan defines a number of included seats at no additional cost, plus a per-seat price for any seats beyond that. The customer pays the plan's base price upfront at the start of each billing period, and extra seat charges are calculated based on their actual usage.
For example, a plan at $99/month with 5 included seats and $25 per additional seat works like this: a customer with 3 users pays $99. A customer with 8 users pays $99 plus $75 for the 3 extra seats, totaling $174/month.
Advance charge and true-up
Seat-based pricing uses a hybrid billing approach. The base price and included seats are charged in advance at the beginning of each period. Extra seats beyond the included amount are trued-up, meaning the actual count is measured and charged either during the period when seats are added or at the end of the billing cycle.
This hybrid approach matters because seat counts change mid-cycle. A customer might add 3 team members on day 10 and remove 1 on day 20. The billing system needs to handle these changes with proper proration rather than waiting until the end of the period to reconcile everything.
When to use seat-based pricing
Seat-based pricing works best when each user represents meaningful value. Collaboration tools, project management software, CRMs, and communication platforms all benefit from this model because adding a user directly increases the value the customer gets from the product.
It is also the right choice when your costs scale with users. If each seat consumes infrastructure resources like storage, compute, or API calls, seat-based pricing aligns your revenue with your costs.
Seat-based pricing is less appropriate when not all users engage equally. If a customer has 50 seats but only 10 are active daily, they may feel they are overpaying. Products with highly variable usage per user are often better served by usage-based billing models.
Pros and cons
Seat-based pricing is predictable for both the vendor and the customer. Customers can forecast their bill based on headcount, and vendors can forecast revenue based on seat counts across their customer base. This predictability makes budgeting and financial planning straightforward on both sides.
Revenue expansion happens organically. As the customer's company grows, their seat count grows, and their bill increases without any sales effort. This built-in expansion is one of the most powerful aspects of seat-based pricing.
The downside is that it can create resistance to adoption within organizations. If the budget holder pays per seat, they may limit who gets access to control costs. This slows down product adoption and can push users toward workarounds like sharing login credentials. Some companies address this by offering viewer or read-only seats at lower prices or for free.
Hybrid models
Many SaaS products combine seat-based pricing with other models. A common pattern is charging per seat for the base product and adding metered billing charges for consumption features. For example, a project management tool might charge $15/seat/month with an additional $0.01 per API call for integrations.
Another hybrid approach includes a generous number of seats in the base plan and charges per seat only beyond that threshold. This removes friction for small teams while still scaling revenue with larger organizations.
How Commet handles seats
Commet treats seats as a feature type within its plan system. Each plan defines the number of included seats and the per-seat overage price. When a customer adds or removes seats through the SDK, Commet calculates prorated charges automatically. Seat changes mid-cycle are reflected in the next invoice with precise proration down to the day, so customers are charged fairly for exactly what they used.