Seat-Based Billing
Also known as: Per-User Billing, Per-Seat Pricing, User-Based Subscription
Seat-based billing charges customers per user account, so revenue scales with how many people on their team need access to your product.
Definition
Seat-based billing is a subscription model where you charge a flat fee per user (or 'seat') on a customer's account each billing cycle. If a customer adds five users at $30/seat, they pay $150 that month; if they remove two, the next invoice reflects three seats.
Operators use seat-based billing for products where value scales with team size — collaboration tools, CRMs, helpdesks, project management. Your billing engine tracks active users, prorates additions and removals mid-cycle, and adjusts the next invoice automatically.
It's distinct from usage-based billing (which meters consumption like API calls or storage) and flat-rate billing (one price regardless of users). Many modern SaaS plans combine seat-based pricing with usage tiers or feature gates for hybrid monetization.
Why It Matters
Seat-based pricing creates predictable, expansion-friendly revenue. When a customer hires, your ARR grows automatically without a new sales cycle — net revenue retention often runs above 110% on healthy seat-based products. It's also the easiest model for buyers to forecast, which shortens procurement cycles.
Ignoring seat hygiene quietly destroys margin and trust. If your system doesn't prorate accurately, customers dispute invoices and churn. If you don't deprovision inactive users on downgrade, you under-bill. If you don't surface seat utilization, customers buy fewer seats than they need and stall expansion.
Examples in Practice
A 40-person agency uses a project management tool at $25/seat. They onboard a new account team of six mid-month; the billing engine prorates the partial month, charges the difference on the next invoice, and updates the renewal baseline from 40 to 46 seats.
A SaaS sales team running a CRM negotiates a 25-seat contract at a discounted rate. The vendor's billing platform enforces the seat cap, blocks the 26th invite, and triggers a sales notification to upsell additional seats rather than silently overage-charging.
A 200-person support org uses a helpdesk priced per agent. During a seasonal ramp, they add 30 contractors for 60 days. Seat-based billing handles the temporary expansion, then auto-removes those seats when contractors are deprovisioned in the identity system.