“Rolls-Royce has charged airlines per flying hour (not per engine) since 1962. What is new in 2026 is that the same logic can now be applied to knowledge work, public services, and software delivery. The technology barrier has dissolved.”
The service economy has operated on a simple premise for a century: you pay for hours, seats, and licences. AI has broken that premise. The question is not whether your business adapts; it is whether you move before or after the erosion of margins begins.
The time-based model has a structural defect that AI has just made visible
The time-and-materials contract, the per-seat licence, and the annual managed services retainer share a common flaw: they decouple price from value. A vendor earns the same revenue whether the work produces a ten-times return or a marginal improvement. The client carries all execution risk. Renewal conversations are based on relationship and inertia, not on demonstrated performance.
For decades, this worked because there was no practical alternative. Outcomes were difficult to define, harder to measure, and impossible to attribute cleanly. Providers could reasonably argue that results depended on client-side factors they did not control.
AI has dismantled each of those objections in turn. Agentic systems can now execute complex, multi-step workflows autonomously. IoT instrumentation and digital twin platforms provide continuous, auditable operational data. Machine learning can isolate the contribution of an intervention from confounding variables with statistical rigour. The measurement problem: the technical excuse that kept time-based billing in place no longer holds.
Gartner projects that AI-native companies are scaling 40% faster than traditional SaaS providers. The structural reason is not that they have better technology. It is that they have better commercial alignment: they sell results, not access. Revenue scales with customer value creation, not with headcount or licence count. That alignment is an asymmetric competitive advantage — and it is compounding.
Who is most exposed
Four categories of business that cannot afford to wait
Not every business faces equal urgency. The following categories face existential pressure from the OaaS transition, not incremental disruption.
Professional services and consulting firms billing by the hour or day are acutely vulnerable. When an AI agent can execute in hours what a team of analysts required weeks to produce, the value of the time itself approaches zero. The only defensible commercial position is to contract for the quality and impact of the analysis — not the hours consumed producing it. Firms that resist this transition will face a stark choice between margin compression and client loss.
Managed service providers operating on resource-based retainers — particularly in IT operations, cybersecurity, and infrastructure management — are already under pressure. Clients are beginning to ask why they pay a fixed monthly fee regardless of incident frequency, threat prevention performance, or uptime achievement. Outcome-contracted MSPs — who charge per threat neutralised, per percentage point of uptime guaranteed, per recovery time objective met — are demonstrating superior client retention and stronger renewal pricing.
Software vendors with per-seat SaaS models face the most technically immediate threat. When an AI agent can perform the work of multiple human users on a single licence, seat-based pricing becomes structurally indefensible. The vendor’s own product success undermines its revenue model. The transition to outcome-based pricing is not a preference — it is a survival requirement.
Government technology suppliers and system integrators operating in Asia and the Middle East face a different but equally significant pressure. National transformation programmes — from Saudi Vision 2030 to Singapore’s Smart Nation initiative to India’s digital public infrastructure — are increasingly specifying measurable citizen outcomes, not technology deliverables. A supplier that cannot contract against operational KPIs will not win the next generation of public sector mandates.
The transition framework
Moving from time-based to outcome-based: the structural differences
The transition is not a pricing exercise. It is a reconfiguration of the commercial model, delivery architecture, and organisational incentive structure. The following table frames the substantive differences between the two operating states.
How to transition
A four-phase approach to frictionless model migration
The most common failure mode in OaaS transitions is attempting to move directly from time-based pricing to pure outcome pricing without the intermediate infrastructure. This produces measurement disputes, provider cash-flow crises, and client distrust. The correct approach is a staged migration that builds contractual confidence incrementally.
Phase 1
Instrumentation and baseline establishment
Before any outcome can be contracted, it must be measurable. This phase focuses entirely on establishing the pre-intervention baseline: identifying which operational metrics are available, which require new instrumentation, and what their current state is. This is not yet an outcome contract; it operates under the existing time-based or access-based model. The output is a documented baseline, an agreed attribution methodology, and a shortlist of contractable outcome units. Client and provider co-design this framework; shared ownership of the measurement methodology is the primary friction-reduction mechanism.
Phase 2
Hybrid model introduction
The two-part tariff is introduced: a base fee that covers the provider’s fixed delivery costs plus a variable outcome component that captures a portion of the verified performance improvement. The base fee is set to protect the provider’s floor revenue during model maturation. The outcome variable is initially modest — typically 15–25% of the total contract value — but establishes the measurement cadence, reporting infrastructure, and dispute-resolution process in a low-stakes environment. Clients experience a direct link between payment and performance for the first time without bearing full implementation risk.
Phase 3
Outcome-led contract transition
As measurement confidence and outcome data accumulate, the variable component becomes dominant. The base fee reduces to a platform and monitoring cost; the outcome variable rises to 60–80% of the total contract value. Performance floors are introduced, where minimum outcome rates below which the provider is not paid, alongside performance ceilings that cap client cost during exceptional performance periods. This protects both parties and prevents the contract from becoming economically unsustainable in either direction. Attribution models are stress-tested against real data from the hybrid phase and refined where needed.
Phase 4
Mature OaaS contract
The contract operates primarily on outcome-linked revenue. The base fee, if retained, covers only the provider’s irreducible fixed costs. Annual renegotiation is triggered by performance data, not by relationship management. The provider’s competitive position is now based entirely on demonstrated outcome delivery, not on methodology presentations or credential submissions. This is the sustainable long-term state and the one that generates the highest client retention, strongest renewal pricing, and most defensible margin for providers who execute it well.
Reducing friction in practice
The five decisions that determine whether a transition succeeds or stalls
Most OaaS transitions fail not because the model is wrong, but because specific structural decisions are made incorrectly or deferred until after conflict emerges. The following five decisions must be resolved before any outcome contract is signed:
Outcome unit selection: Choose the metric that scales directly with client value. If the product works twice as well, the client should receive approximately twice the value and pay approximately twice as much. Proxy metrics — API calls, queries, model inferences — are usage pricing in disguise. 2.
Attribution methodology: The causal logic linking the intervention to the outcome must be agreed upon before deployment, not negotiated after data is visible. Pre-agreed statistical methods, independent audit provisions, and data ownership arrangements prevent the most common source of disputes. 3.
Floor and ceiling provisions: Pure outcome contracts with no floor are not commercially sustainable for providers. Minimum commitments protect provider cash flow during ramp-up. Caps protect clients during periods of exceptional performance. Both sides require these structural protections for the contract to be renewable. 4.
Client-side data obligations: Outcome contracts must specify the client’s obligations: data quality thresholds, system availability requirements, process compliance expectations. If the client’s operational behaviour degrades the outcome, the provider cannot bear the financial consequence under a pure outcome model. 5.
Exit and data portability: When the provider controls both the AI system and the measurement infrastructure, the client’s switching cost becomes structurally high. Exit provisions — data export rights, model handover obligations, transition support — must be contractually specified at inception, not at termination.
What OaaS does not solve
OaaS is not a universal remedy. For new products without operational history, the baseline problem is real and not trivial to resolve. For outcomes with long measurement horizons, such as population health improvement, long-term infrastructure resilience, and decade-scale urban transformation, payment cadence and outcome realisation are structurally misaligned in ways that require bespoke financial structuring, not simply a different contract template.
The model also does not eliminate delivery risk; it simply reassigns it. Providers who underestimate the cost of delivering outcomes at contracted performance levels will erode margin faster under an outcome model than under a time-based one. The transition requires genuine confidence in delivery capability, not just commercial optimism.
And for clients, outcome contracts are not a substitute for governance. Regulators will hold the contracting organisation accountable for decisions made on its behalf, regardless of whether those decisions were made by an AI agent under an OaaS arrangement. Accountability does not transfer with the outcome contract.