73% of SaaS Vendors Are Abandoning Per-Seat Pricing - Here's Why It Matters

73% of SaaS Vendors Are Abandoning Per-Seat Pricing - Here's Why It Matters 73% of SaaS Vendors Are Abandoning Per-Seat Pricing - Here's Why It Matters Austen August 31, 2026 · 6 min read Three-quarters of the SaaS industry is rewriting its pricing playbook right now, and most aren't ready for what comes next. February 2026 wasn't kind to software companies. The SaaS index shed $285 billion in a matter of weeks, and it wasn't because of a recession or some macro shock [6] . Public markets simply looked at per-seat pricing models and decided they didn't reflect reality anymore. When Publicis Sapient announced it was slashing traditional SaaS licenses by roughly 50% and replacing them with AI tools, it sent a signal: enterprise buyers are done paying for seats that don't capture value [8] . I've been watching this unfold from inside the developer world, and honestly, the speed caught even the cynics off guard. Per-seat pricing made sense when software mapped neatly to humans doing work. But that relationship is broken now, and vendors are scrambling to figure out what comes next. The math stopped working Here's the problem in one sentence: when one user with an AI agent does the work of five people, charging per seat punishes the customer for being efficient and punishes the vendor for delivering that efficiency [1] . It's a pricing model that literally disincentivizes the product improvement both sides want. GitHub Copilot is the poster child for this. A developer with Copilot writes code faster, catches bugs earlier, ships features in half the time. But under traditional per-seat SaaS logic, GitHub would make less money as teams shrink from 50 engineers to 10 while their actual software consumption grows 10x [6] . That's not sustainable, and investors figured it out before most founders did. Enterprise procurement teams picked up on this even faster. They're not stupid. If AI tools let them consolidate licenses while maintaining or improving output, why would they keep paying for "shelf-ware" they don't need? [3] The February repricing wasn't a panic; it was a correction. What's replacing it (and why it's messy) The 73% of SaaS companies rebuilding their pricing are converging on three models, though most are hedging with hybrids [6] [7] . Usage-based pricing ties cost to actual consumption: API calls, compute hours, tokens processed. It feels fair to buyers because they pay for what they use. But it creates chaos for vendors trying to forecast revenue. Your NRR becomes unpredictable, your COGS swing wildly, and CFOs lose the clean ARR narratives Wall Street loves [2] . Outcome-based pricing charges for results delivered rather than seats or usage. Close a deal, process an invoice, resolve a ticket. This sounds great until you hit the attribution problem: who gets credit when an AI agent, a human, and three integrations all touch the same outcome? There's no standard contract language for this yet, and disputes are starting to pile up [4] . Hybrid models try to split the difference with base fees plus consumption tiers. Flexera calls this the "hybrid era" because most companies aren't confident enough to go pure consumption [7] . I think they're right, but hybrids introduce their own complexity around billing logic and customer communication. The problems no one's solved Here's what keeps me up at night: we're redesigning the economic foundation of software before we've figured out the operational details. Attribution is the big one. If you're charging based on outcomes and an AI model screws up, who's liable? The vendor whose AI generated the output? The customer who approved it? The infrastructure provider running the compute? We don't have legal frameworks for this [4] . Forecasting is another mess. Per-seat models were predictable. You knew churn rates, expansion patterns, cohort behavior. Usage-based pricing turns your P&L into a weather forecast. One customer's workload spike can swing your monthly numbers by 30%, and good luck explaining that variance to your board [2] . And there's a darker angle most founders won't say out loud: this transition favors incumbents with diversified revenue streams. If you're a $10 million ARR startup betting everything on per-seat licenses, you can't afford to experiment with consumption models while your cash flow craters. Public companies with balance sheets can. That's going to reshape which companies survive this decade. What this means for you If you're building or buying software right now, assume per-seat pricing is already dead for anything touching AI. The 73% figure isn't a trend; it's a migration that's mostly finished at the strategic level, even if implementation is lagging [6] . For vendors: start modeling your unit economics under usage-based assumptions yesterday. Even if you're not ready to flip the switch, you need to know what your margin structure looks like when revenue becomes variable. For buyers: push for consumption models, but read the fine print around liability and attribution. The contracts being written right now are first drafts, and nobody's sure what happens when they break. The SaaS pricing model that defined the last 20 years is gone. What replaces it is still being written, and the companies that figure out the attribution and forecasting problems first are going to own the next decade. Sources [1] r/SaaS on Reddit: Seat-based pricing is dying [2] The Death of Per-Seat Pricing: What It Means for Your SaaS P&L [3] Reasons Companies Are Transitioning From Seat-Based Pricing [4] Per-Seat to Outcome-Based Pricing: Why SaaS Billing Is Changing [6] Death of Per-Seat Pricing: 73% of SaaS Rebuilding [7] From seats to consumption: Why SaaS pricing has entered its hybrid era [8] The 3 New Pricing Models in B2B Austen View more posts → Published with Austen — goausten.ai