Seat-based SaaS pricing is under pressure from AI economics. Here is the full spectrum from traditional subscriptions to outcome-based models — and what it means for every company buying or building software today.
“If an AI agent can do the work of three support reps, why would you keep paying for three seats?” That question is no longer hypothetical. Seat-based SaaS pricing — the dominant model for the last two decades — is under serious pressure. Not from a startup or a pricing consultant, but from the basic economics of AI.
For most of the SaaS era, software has been sold like an American buffet. You pay a flat fee per seat per month. Within that, you can use as much as you want. No usage caps, no metering, no surprises on your invoice.
This model drove massive adoption. It removed friction. It made budgeting simple. And it worked for a long time.
But it also created a hidden subsidy. Your power users — the ones logging in daily, running complex workflows, consuming real compute — pay the same flat rate as the person who logs in once a month. The heaviest users get the most value per dollar. The lightest users quietly subsidize them.
This dynamic was fine when the marginal cost of serving another user was close to zero. But AI changed the math. Every AI-powered feature carries real compute costs: inference tokens, API calls, GPU time. A flat per-seat fee can no longer absorb that. SaaS companies are being forced to rethink how they charge — and software buyers need to understand what is coming.
Seat-based pricing: a subscription model where cost is determined by the number of user accounts (“seats”), regardless of how much each user actually uses the software. Dominant for two decades, now declining as AI agents replace human seats.
What is replacing the buffet is not a single new model. It is a spectrum. Think of it as five rungs on a ladder, moving from the most abstracted pricing to the most aligned with actual value delivered.
| Pricing model | What you pay for | Predictability | Value alignment |
|---|---|---|---|
| Traditional SaaS (per seat) | Access — number of users | High | Low |
| Micro usage-based | Consumption — tokens, API calls, compute | Low | Medium |
| Value usage-based (credits) | Meaningful work units | Medium | Medium-high |
| Micro outcome-based | Measurable steps toward results | Medium | High |
| Full outcome-based | Actual results delivered | Low–Medium | Very high |
Rung 1: Traditional SaaS (per seat, per month). This is the model everyone knows. You are paying for access. The number of users determines the price. Whether those users are active or inactive, productive or idle, the bill stays the same. It is simple and predictable — and it is declining. According to Growth Unhinged’s 2025 State of B2B Monetization report, seat-based pricing dropped from 21% of SaaS companies to 15% in just twelve months.
The reason is straightforward: AI agents do not need seats. A company that once required 50 Salesforce logins might now need 15, with AI handling the rest. Salesforce’s own Agentforce and Data 360 products hit nearly $1.4 billion in combined ARR, growing 114% year-over-year — while simultaneously cannibalizing their seat-based revenue.
Rung 2: Micro usage-based pricing. Instead of paying a flat fee, you pay for what you actually consume: CPU time, API calls, tokens processed, data stored. AWS popularized this model for infrastructure, and it is now spreading into application software. The appeal is obvious — you only pay for what you use. But it introduces unpredictability. Enterprise buyers routinely report unexpected charges from consumption-based AI pricing.
Rung 3: Value usage-based pricing (credits). This is the middle ground. Instead of metering raw compute, you are charging for a meaningful unit of work — something that clearly matters to the customer, even if it is not the final outcome. The PricingSaaS 500 Index found that 79 companies now offer credit-based models, up 126% year-over-year. HubSpot, Salesforce, Figma, and Adobe have all adopted credit structures. Credits give customers more transparency than a flat seat license while being easier to implement than pure outcome pricing.
Rung 4: Micro outcome-based pricing. A micro outcome is not the ultimate business result, but it is a measurable step on the path to it. In sales and marketing, leads are the clearest example. A booked meeting, a verified contact, a scored prospect — these are micro outcomes on the path to a closed deal. The customer is not buying the activity. They are buying a step closer to the result they actually want.
Rung 5: Full outcome-based pricing. You pay only when the software delivers the actual result you are looking for. Intercom charges $0.99 per AI-resolved support ticket. Their Fin AI agent has processed over 40 million resolved conversations with a 67% resolution rate and is approaching $100 million in annual recurring revenue, growing at roughly 3.5x year-over-year. Zendesk charges $1.50 to $2.00 per automated resolution. Salesforce prices its Agentforce on completed actions, not human seats.
Gartner projects that by 2030, at least 40% of enterprise SaaS spend will shift toward usage-, agent-, or outcome-based pricing. Chargebee’s 2025 State of Subscriptions Report found that 43% of companies already use hybrid models, with adoption projected to hit 61% by the end of this year.
Why this matters for buyers: Outcome-based pricing shifts risk from the buyer to the vendor. If the AI does not resolve the ticket, Intercom does not get paid. That is a fundamentally different deal than paying $150 per seat per month regardless of whether the software actually does what you bought it to do.
Fraction’s senior engineers can help you scope AI projects with transparent story-point pricing — so you pay for output, not hours.
Scope Your Project for FreeFree and instant. No call required.
Outcome-based pricing sounds ideal in theory. In practice, two challenges keep it from being a universal solution.
The first is attribution. Did the AI close the sale, or did the rep’s follow-up email? Did the fraud detection platform catch the attack, or did the internal security team flag it? When outcomes depend on multiple systems and human actions, determining who or what deserves credit gets complicated fast.
The second is predictability. Enterprise buyers need to set budgets. If pricing is purely variable, finance teams cannot forecast spend. This is why hybrid models are growing faster than pure outcome-based ones. A common structure: a predictable monthly platform fee for access and core features, with outcome-based charges layered on top when AI delivers measurable results above a baseline.
Most companies are not choosing between per-seat and outcome-based pricing. They are combining them. And that is probably the right answer for most buyers, at least for now.
The pricing spectrum above applies to software products. But the same forces are reshaping how technology services get priced — from dev shops and agencies to legal and consulting firms.
Services have historically lived in the hourly world. The worker does the work, the client gets billed for the hours. It is a form of usage-based pricing: however many hours are consumed, mark them up, and that is the invoice. This model has always had an uncomfortable misalignment. The client’s goal is the output. The provider’s revenue is tied to the input. Faster delivery means less money for the provider. The incentives work against each other.
AI is making that misalignment impossible to ignore. According to Jellyfish’s 2025 State of Engineering Management Report, 62% of engineering teams report at least a 25% productivity increase from AI tools, with deeply engaged teams seeing 30–50% faster throughput. If a strong engineer augmented by AI can produce in two hours what used to take eight, hourly billing makes no sense for either side.
The traditional alternative is the fixed bid: a flat price to deliver an entire project. Fixed bids give the client cost certainty — but providers pad estimates to account for overruns, bug fixes, and scope changes. That padding can be significant, sometimes doubling the real cost.
The middle ground is pricing per unit of work rather than per hour or per project. In software development, that unit is the story point: a standardized measure of task complexity. Story-point pricing works like slicing the fixed bid into thin, individually scoped increments. Each task gets estimated and priced before work begins. The provider does not need to pad a massive lump-sum estimate because the risk is distributed across many small, well-defined units. The client gets transparency into what each piece of work costs and can prioritize accordingly.
AI makes this model more practical than it used to be. The same AI that is good at writing code is also effective at reading task descriptions, assessing complexity, and estimating effort — automating and standardizing what used to be manual and inconsistent.
These pricing models are at different stages of maturity. Traditional per-seat SaaS still dominates by installed base. Hourly billing still dominates in services. But the trend lines are unmistakable. Usage-based pricing is mainstream. Credits are proliferating. Outcome-based pricing is live in production at some of the largest software companies in the world.
Here is what has not changed: the fundamental question for software buyers is still whether a given tool or service delivers value that justifies its cost. What is changing is that the cost structure is becoming more transparent and more aligned with actual value delivered.
For companies evaluating software investments today, the practical takeaways are straightforward. First, look at how your vendors are pricing AI features. If they are bundling AI into existing seat licenses, that will not last — expect pricing changes. Second, understand what pricing model aligns with how you will actually use the product. If you are buying a tool for its AI automation capabilities, a per-seat model is probably overcharging you for idle seats and undercharging you for compute. Third, negotiate with the new models in mind. Credits, usage tiers, and outcome-based components are all levers that did not exist in most SaaS contracts two years ago.
And if you are buying development services, ask the same question: are you paying for hours, or are you paying for output?
At Fraction, we charge $149 per story point, scoped before development begins, with a structured breakdown so you know exactly what you are paying for before you commit. AI helps automate the estimation process, which means tighter scoping and less padding. The engineer gets compensated for completing tasks, not for logging hours. The client pays for output, not input. As AI reshapes the economics of both building and buying software, that alignment between cost and value becomes more important, not less.
The buffet era is not over yet. But the menu is changing. The companies that understand the new pricing landscape — whether they are buying software products or development services — will make better decisions, negotiate better contracts, and avoid locking themselves into models that will not survive the next two years.
AI agents can do the work that used to require multiple human seats. When software replaces headcount, charging per head stops making sense. A company that once needed 50 Salesforce logins might now need 15, with AI handling the rest. The result is that seat-based pricing creates a structural misalignment between what buyers pay and what they actually consume.
Usage-based pricing charges for what you consume — API calls, tokens, compute time. Outcome-based pricing charges only when the software delivers a measurable result, such as a resolved support ticket. Usage-based pricing aligns cost with consumption but not necessarily with value. Outcome-based pricing aligns cost directly with value delivered, shifting risk from the buyer to the vendor.
Credits are a middle-ground pricing mechanism that charges for meaningful units of work rather than raw compute or final outcomes. They give customers more transparency than a flat seat license while being simpler to implement than pure outcome-based models. The PricingSaaS 500 Index found 79 companies now offer credit-based models, up 126% year-over-year, with HubSpot, Salesforce, Figma, and Adobe all adopting credit structures.
It is live in production at some of the largest software companies in the world — Intercom charges $0.99 per AI-resolved support ticket and Zendesk charges $1.50 to $2.00 per automated resolution. But attribution complexity and the need for predictable budgets mean most companies are adopting hybrid models: a platform fee for core access plus outcome-based charges on top when AI delivers measurable results above a baseline.
Services that bill by the hour face the same misalignment as seat-based SaaS. AI is divorcing hours from output in knowledge work — a skilled engineer augmented by AI can produce in two hours what used to take eight. The emerging alternative is per-unit-of-work pricing: in software development, that unit is the story point, scoped and priced before work begins, so the client pays for output rather than input.
First, examine how your vendors are pricing AI features — if they’re bundling AI into existing seat licenses, expect pricing changes. Second, understand which pricing model aligns with how you’ll actually use the product. Third, negotiate with the new models in mind: credits, usage tiers, and outcome-based components are all levers that didn’t exist in most SaaS contracts two years ago. And if you’re buying development services, ask whether you’re paying for hours or for output.
Praveen Ghanta is a five-time founder and serial entrepreneur. He is the founder of DevHawk.ai, an AI-powered engineering management platform, and Fraction.work, which connects fast-growing companies with top fractional tech and growth marketing talent. Previously, he founded HiddenLevers, a risk analytics platform for wealth management that he bootstrapped from inception to acquisition by Orion Advisor Solutions in 2021, serving thousands of advisors and $600B in assets. He earlier founded SmartWorkGroups, acquired by Intralinks in 2000.
Connect on LinkedIn →Describe your software or AI project. Get a full scope with story-point pricing, sprint estimates, and a downloadable plan in minutes. No calls, no waiting.
Scope Your Project for FreeWorking on a data strategy? Talk to a Fraction CTO. → Book an intro call
