The End of Seat-Based SaaS?
New Models: From Seats to Outputs
- Labor- or Task-Based Pricing: Charge for the amount of work the AI agent performs, similar to an hourly rate or per unit of output. “An AI agent performs a certain amount of work, and you pay for [the] time or units it took to do that work,” Levie explains. This treats AI as a workforce, aligning price with workload accomplished: a fair trade in theory for both customer and provider.
- Outcome-Based Pricing: Charge for a defined outcome, say, an AI agent resolved 100 customer support tickets or processed 1,000 invoices, rather than for usage per se. As Levie notes, this makes the value obvious: you pay when the AI actually accomplishes something for you. Some early SaaS AI offerings already work this way, charging a few dollars per conversation handled rather than a flat fee, and as the underlying AI gets cheaper to run, the vendor’s margins improve while the price per outcome can stay the same, so efficiency gains accrue to the provider rather than the customer.
- Cost-Plus (Consumption) Pricing: Charge based on the AI’s underlying compute costs, with a markup, for instance by the number of API calls, tokens processed, or CPU hours consumed. This is transparent (the customer pays roughly for resources used) and feels logical to technical buyers, but it doesn’t tie directly to business value: it’s closer to utility pricing, and a thin margin on compute may not sustain high profitability long-term. Many generative AI services already use a form of this today, such as OpenAI charging per 1,000 tokens, so it’s common at the API level even if it won’t be the whole answer.
- Unlimited Subscription (AI-as-a-Service Seat): Levie describes this as offering “AI Agents with unlimited work tied to a seat”: a flat per-user (or per-“agent”) fee granting unlimited use, basically an all-you-can-use plan for each licensed user or agent. This is simple and familiar to buyers, and works well where many end-users each benefit from AI assistance (enhancing a whole sales team, for example), but it breaks down if only a few people use the AI to generate outsized output: you’d be “giving up too much value” in low-seat, high-usage cases. In my opinion, this model might survive in hybrid form (a base seat fee plus overage charges), but by itself it doesn’t fully capture the value an unleashed AI can create.
The Conundrum: Value vs. Predictability
- Defining Outcomes and Units: What counts as a “successful outcome” for AI? In some domains it’s clear (e.g. a customer service query resolved by an AI agent), but in others it’s fuzzy. An outcome-based deal could invite disputes (was the result truly achieved to the client’s satisfaction?), especially if AI’s work quality varies. Likewise, if pricing by tasks or time, how do we count and normalize those units across different contexts? The industry is still figuring out the right unit of measurement for AI work. Business leaders like Levie openly ask: should we charge per action? per outcome? or something entirely new? The winners of this transition will be those who invent intuitive metrics that customers accept as fair value for AI-driven results.
- Customer Budgeting and Predictability: Traditional SaaS subscriptions gave enterprise buyers cost certainty: a fixed annual license count. Usage-based pricing can introduce volatility. CIOs and CFOs worry about getting a surprise bill when AI usage spikes. “People get annual budgets and cannot tolerate variability,” notes one CEO, cautioning that a sudden jump in AI agent activity could burn through budget in weeks. Early adopters of cloud consumption models learned this the hard way, and AI could repeat it. In fact, IDC’s research finds that many enterprises “look for predictability” and thus favor subscriptions or at least tiered plans that cap the risk of runaway costs. Vendors will need to balance usage-based fairness with safeguards (e.g. usage caps, enterprise volume discounts, or hybrid plans) to make pricing predictable and aligned with value.
- Scaling Costs and Margins: For SaaS companies, AI features can be expensive to run: think of all those GPU-heavy computations. If you stick to flat per-seat pricing while users offload tons of work to AI, your cloud costs could skyrocket and erode margins (the “AI margin trap”). On the flip side, if you charge purely by consumption, you risk commoditizing your offering or scaring off customers with volatile bills. Some experts suggest hybrid models will emerge, combining cost-based transparency (so customers see the resource costs) with performance-based fees or outcome bonuses, so the provider is rewarded when the AI delivers big wins for the client without making costs too opaque. Transparency will be key: as Levie emphasizes, vendors that offer clear, predictable pricing and demonstrable outcomes will have the edge, and no one wants to see a mysterious 10x jump in their invoice and not know why.
- New Usage Patterns: Agentic AI also changes who or what is using the software. We might have scenarios where an AI agent itself is the primary user of a SaaS API (with minimal human involvement), essentially a software-to-software interaction. SaaS providers may end up selling more to algorithms than to people! This raises questions: do you count an AI agent as a “seat”? (Probably not meaningful.) Do you license an enterprise for a certain number of concurrent AI agents or workflows? Or do you abstract away the user count entirely and just charge for outcomes? These are uncharted waters. Levie points out that technically there’s “little difference between having 100 agents complete one action a minute vs 1 agent completing 100 actions a minute.” Charging per agent process might therefore be moot. The value is in the volume and quality of work done, not the number of bots or users in the system.