Modern Pricing & UBB
February 26, 2026 saas

When Seat Pricing Actually Makes Sense (A Defense)

Seat pricing has become the pariah of the SaaS pricing world. Every conference talk, every pricing blog, every VC memo is telling you to switch to usage-based. And for many products, they're right. But there's a contrarian case to be made for seat pricing that the industry is currently too excited about UBB to make clearly: in the right context, seat pricing is not just defensible — it's the optimal choice.

This isn't an argument that seat pricing is universally good. It's an argument that the framework matters, and that blindly switching to usage-based because it's the current fashion is as wrong as blindly staying on seats because it's what you've always done.

When Collaboration Is the Core Value

Seat pricing wins decisively when the product's core value is the network of people using it together. Google Workspace. Slack. Notion. Figma. The value of these products is specifically, fundamentally the fact that your whole team uses them. More users means more collaboration channels, more shared documents, more real-time co-editing. The value scales with seats because the product value scales with seats.

For these products, usage-based pricing would be bizarre. "You paid for 10 API calls to the Slack API today" is meaningless. The value isn't in API calls — it's in the team being on the same platform, reading the same channels, reacting to the same messages. You're not buying compute. You're buying team coordination. And team coordination is measured in people, not events.

SBI's 2024 pricing research identifies collaboration tools as the clear category where per-seat pricing consistently outperforms usage-based alternatives, with higher NRR and lower churn than comparable tools that have attempted consumption-based transitions. The reason: customers of collaboration tools evaluate their spend relative to the number of people who benefit, not the number of interactions generated.

When Usage Is Uniform Across Users

Seat pricing works well when usage patterns across individual users are relatively uniform — when the 10th user consumes roughly as much as the 1st. This is characteristic of tools where the primary workflow is the same for everyone: a CRM that every sales rep uses the same way, a project management tool where every team member creates similar numbers of tasks, an HR platform where every employee processes their own data.

When usage is highly variable — some users consuming 100x what others consume — seat pricing creates subsidization dynamics that eventually produce churn. Your power users feel like they're paying the same as light users, your light users feel fine, and at renewal time the power users will either lobby for a higher-complexity renegotiation or find a usage-based alternative. Usage-based pricing converts that implicit tension into explicit economics that both parties can reason about.

Kyle Poyar's Growth Unhinged analysis identifies the usage variance test as the key diagnostic: if your 90th percentile user consumes more than 5x what your 10th percentile user consumes, seat pricing will create enough internal pricing pressure that it becomes worth the operational cost of switching to usage-based. Below 5x, seat pricing captures value adequately.

When Procurement Needs Predictability

Enterprise procurement teams have a strong preference for predictable costs. This isn't irrational — it's how large organizations budget software. IT departments forecast annual software spend, allocate budgets, and manage vendor relationships around contracts with known values. A pure consumption model requires a consumption forecast before procurement can approve the budget, and consumption forecasts for new software are inherently uncertain.

For products sold into highly structured enterprise procurement processes — government contracts, financial services compliance software, healthcare IT — seat pricing often closes faster and at higher TCV because procurement can sign a known number. The usage-based alternative requires a procurement education cycle that can add months to the sales process. For products with long sales cycles and large initial deal sizes, that time cost is real.

The Framework

Before switching from seat to usage-based, run these three tests:

  1. Collaboration value test — Is the product's primary value in the network of users, or in the outcomes individual users generate? If network, seats. If outcomes, usage.
  2. Usage variance test — Is your 90th percentile user consuming more than 5x your 10th percentile user? If yes, usage-based is worth the operational overhead. If no, seats capture value adequately.
  3. Procurement friction test — Are your target customers in procurement environments that require predictable spend? If yes, seat pricing (or seat pricing + committed spend hybrid) is likely optimal. If no, usage-based can be introduced without significant sales cycle cost.

The right pricing model is the one that aligns with how your customers experience value, how your cost structure works, and how your customers' procurement functions operate. Seat pricing, executed well, is a clean model that your customers can explain to their CFO without a calculator. That's not nothing.

Sources

← Seats & Per-User · All posts