Per-Seat Pricing

Overview

Per-seat pricing charges customers based on the number of users on their account. $X per user per month. Revenue scales linearly with team size. It’s one of the most common SaaS pricing models and one of the most debated — because it directly taxes the adoption you’re trying to maximize.

The AI era is accelerating this debate. When AI agents consume your product alongside humans, counting “seats” becomes less meaningful. Many companies are migrating toward usage-based or hybrid models for this reason.

When It Works

• Collaboration tools. Products where every team member needs their own account — Slack, Figma, Linear, Notion. The value scales with team size, and per-seat pricing captures that
• Clear per-user value. Each user gets a distinct workspace, data, or permissions. The product is genuinely more useful (and more costly to serve) with more users
• Sales-led B2B. Enterprise buyers understand per-seat pricing. Procurement teams can model costs against headcount projections. It maps cleanly to budget planning
• Land-and-expand strategy. Start with 5 seats, grow to 50, then 500. Per-seat pricing turns product adoption into automatic revenue expansion without renegotiation
• Combined with tiered pricing. Starter at $10/seat, Pro at $25/seat, Enterprise at $50/seat. Tiers gate features, seats gate scale. This is the dominant B2B SaaS pattern

When It Breaks

• It punishes adoption. Every new user is a cost increase. Teams share logins, limit invitations, and resist onboarding new members. You’re creating friction against the behavior that makes your product stickier
• Not all seats are equal. An admin who logs in daily and a viewer who checks a dashboard once a month pay the same price. This feels unfair and erodes trust
• AI agents break the model. If an AI assistant uses your API on behalf of a team, is that a seat? If 3 humans and 12 agents use your product, per-seat pricing doesn’t map to value anymore
• Low-seat-count customers are unprofitable. A team of 2 paying $10/seat is $20/month. The support and infrastructure cost may exceed the revenue. Flat-rate pricing with a minimum is often better for small teams
• Enterprise negotiations kill the simplicity. Large deals always involve volume discounts, committed seats vs. active seats, and true-up clauses. The “simple” per-seat model becomes a negotiation framework

Real-World Patterns

Per-seat pricing dominates:

• Team collaboration — Slack, Notion, Figma, Asana, Monday.com
• Sales and CRM — Salesforce, HubSpot (Sales Hub), Pipedrive
• Dev tooling — GitHub, GitLab, Jira
• Design and creative — Figma, Canva for Teams

The emerging shift: several high-profile products have moved away from per-seat. Figma introduced organization-wide pricing. Some dev tools now offer flat-rate team plans instead of per-seat. The trend is toward models that don’t penalize adding users.

Implementation Notes

• Define what a “seat” is. Active user? Invited user? User who logged in this month? This distinction matters for billing accuracy and customer trust. Most companies bill on provisioned seats, not active users — but communicate this clearly
• Offer seat tiers, not just seat count. Admin vs. member vs. viewer at different price points reduces the “all seats cost the same” problem. Viewers at $0 or a reduced rate encourages broader adoption
• Handle seat changes mid-cycle. Adding seats mid-billing-period requires proration. Removing seats raises the question: refund, credit, or apply at next renewal? Decide this upfront
• Set a minimum. Don’t sell 1-seat plans unless you’re targeting solopreneurs. A 3-seat or 5-seat minimum ensures baseline revenue per account
• Annual commitments with seat true-ups. Enterprise deals typically commit to a seat count annually, with quarterly or annual true-ups for additional seats. Your billing system needs to support this

Supported By

Per-seat pricing is natively supported by all major billing platforms:

• Stripe — quantity-based subscriptions where quantity = seat count. Proration, mid-cycle changes, and metered seat tracking all supported via API
• Chargebee — per-seat plans with add-on seats, tiered seat pricing, and automated proration. The most feature-rich option for complex seat-based billing
• Recurly — seat-based subscriptions with add-on management and dunning per account
• Paddle — per-seat subscriptions with MoR tax handling. Supports seat quantity changes via API
• Dodo Payments — subscription billing with seat-based configuration via API

Verdict

Per-seat pricing is the right model for products where each user gets distinct, measurable value and team adoption is the primary growth vector. It’s predictable, easy to explain, and maps to enterprise procurement. But it creates a real tension: you want maximum adoption, and your pricing model makes adoption more expensive. If you’re seeing customers limit invitations, share accounts, or resist onboarding — the model is working against you. Consider hybrid pricing with a platform fee plus reduced per-seat rates, or explore usage-based models if your product’s value is better measured by what people do than how many people are there.