SaaS pricing is shifting from seats to usage — here's what's actually changing

Per-seat pricing has been the default SaaS billing model for two decades, but its dominance has been eroding steadily since the 2022-2024 spending correction, when buyers started pushing back hard on paying for unused licenses. OpenView Partners, whose annual SaaS Benchmarks survey has tracked pricing-model adoption since 2021, has documented the shift year over year: usage-based pricing in some form has grown from roughly a third of SaaS companies earlier in the decade to a meaningfully larger share today, with hybrid models — a base subscription plus usage-based components — emerging as the most common landing point rather than a full move to pure consumption pricing.\n\nAI features are accelerating the shift rather than starting it. Flat per-seat pricing was already a poor fit for products where usage varies enormously between customers; it's an even worse fit for AI features where the vendor's own underlying compute cost scales directly with how much a customer actually uses the feature. That's pushed even seat-pricing loyalists like several major CRM and productivity vendors toward bundling a base AI allotment into existing tiers and charging separately for usage beyond it — a hybrid structure rather than a wholesale repricing.\n\nThe practical risk on the buyer side is bill unpredictability: usage-based and hybrid AI pricing has produced a rise in surprise overage charges as procurement and finance teams accustomed to flat per-seat costs get used to forecasting consumption instead. Vendors that pair usage pricing with clear usage dashboards and spend alerts are seeing meaningfully better renewal and expansion outcomes than those that don't, according to multiple industry surveys tracking the category through 2025 and into 2026.\n\nFor SaaS pricing teams: the near-term move isn't necessarily to abandon per-seat pricing, which still works well for products with steady, predictable usage per user. It's to build the metering and reporting infrastructure now, even if you stay on a subscription model today, because retrofitting usage tracking after a pricing change is far harder than building it in from the start.