AI does not mean the end of SaaS subscriptions, but it weakens the logic of charging only per user. When software performs work rather than merely helping an employee, pricing increasingly moves toward usage, measurable outcomes or a hybrid of the two.
The classic SaaS model offered predictability: a fixed monthly fee per seat and high gross margins. AI changes both sides of that equation. Inference and compute create variable costs for the vendor, while the customer may use the product to reduce labour, increase throughput or remove an entire manual workflow.
As a result, the commercial conversation moves from “Which features are included?” to “What economic result did the product create?”
Why the old pricing logic is under pressure
AI has different delivery economics
Traditional software can serve an additional user at a very low marginal cost. An AI agent consumes models, infrastructure and monitoring every time it works. AlixPartners estimates that variable margins for agentic AI can be materially lower than for traditional SaaS. A vendor therefore needs pricing that scales with real consumption and cost.
Customers want a financial value story
A CFO can defend a budget more easily when the contract connects to hours saved, write-offs reduced, revenue added or risk removed. A list of features is not enough when an AI project competes with many other transformation initiatives.
Three pricing models that can coexist
- Usage-based: payment per task, document, minute, token or transaction.
- Outcome-based: payment tied to verified savings, revenue or another business KPI.
- Hybrid: a platform fee that covers availability and support, plus a variable component for usage or outcomes.
Pure outcome pricing sounds attractive, but it is not appropriate everywhere. The vendor may not control market demand, staffing decisions or the quality of the customer's data. A hybrid structure usually allocates those risks more realistically.
How unit economics changes
CAC may remain high because enterprise sales still requires discovery, security review, integration and a pilot. LTV becomes more dependent on demonstrated effectiveness. Gross margin depends on model and infrastructure costs. Forecasting becomes harder because revenue and cost can both vary with usage.
The product team therefore needs a commercial measurement layer:
- A clear baseline before implementation.
- Two or three metrics that both parties can audit.
- A BI dashboard or independent measurement process.
- Rules for seasonality, external shocks and changes in customer behaviour.
- Cost controls for model usage, retries and human review.
What to do before offering outcome pricing
First, choose a result that is close enough to the product's actual influence. “Increase company profit” is too broad; “reduce manual processing time per invoice” is measurable. Second, run the pilot with the future pricing metric already instrumented. Third, write the baseline and exceptions into the contract before the result is known.
Outcome pricing is particularly powerful for a younger vendor entering an enterprise account. “If we do not create the agreed value, the variable fee is zero” can reduce buyer risk. But the promise works only if the vendor understands the customer's economics and can survive variance in payment timing.
Further reading: AlixPartners on AI SaaS pricing and its analysis of usage- and outcome-based models.