OmniFit logo OmniFit English notes for AI creators and operators
Blog
News + business model

If the AI fails, you do not pay

đź“… Published: September 2, 2026

OpenAI is reportedly letting some big customers pay only when the AI actually completes the job. That sounds like a pricing tweak. It is bigger than that. If this model spreads, software stops getting paid for seats and tokens and starts getting paid for finished work.

OpenAI Outcome-based pricing SaaS AI agents
YouTube thumbnail for Bret Taylor of Sierra speaking about AI agents and outcome-based pricing
Hero thumbnail from Stripe and Cheeky Pint's interview with Bret Taylor of Sierra on AI agents and outcome-based pricing.
What changed

A reported OpenAI pilot shifts payment from model usage toward completed outcomes, at least for some large customers.

Why it matters

AI agents break the old seat-based logic. Buyers want to pay for solved work, not for raw activity.

What gets harder

Vendors now own more delivery risk, and both sides must agree on how to measure and attribute success.

The shift

This is not just a new billing line

According to The Information, as summarized by The Decoder, OpenAI has started offering some large customers a pay-only-when-the-AI-works arrangement for certain tasks such as customer support. OpenAI has not made a broad public product announcement around this model, so the safe read is that this is a reported commercial experiment, not a universal pricing reset.

Plain English:

If an AI agent handles a lot of work but creates no real business result, more buyers now want that failure to be the vendor's problem, not the customer's cloud bill.

Why seat pricing weakens

AI agents do not behave like human seats

Old SaaS pricing worked because one employee usually mapped to one account, one workflow, and a fairly stable amount of usage. Agents break that logic. One agent can work across many channels, run around the clock, and replace slices of work that used to belong to several people. Once that happens, buyers stop asking how many seats they need and start asking what the system actually completed.

That is why the fight is moving from access pricing to performance pricing. Seats made sense when software mainly exposed an interface. Tokens made sense when vendors wanted to meter model activity. But customers increasingly care about a third question: did the AI resolve the ticket, generate the lead, or finish the task?

This did not start with OpenAI

Outcome pricing was already spreading

OpenAI is not inventing the model from scratch. Sierra already markets outcome-based pricing directly on its homepage with the promise that customers “only pay for the value Sierra delivers.” The Decoder also points to other vendors moving the same way, including Salesforce-linked examples and coding tools that are willing to attach credits or guarantees to delivered value.

That is the real signal here. The industry is slowly giving up the comfortable idea that software deserves payment simply because it was used. More vendors are being pushed to prove that their AI actually finished the work in a measurable way.

The hidden cost

Vendors now eat more of the failure risk

Outcome pricing sounds great for customers because it pushes some operational risk back to the seller. If the agent fails, the vendor may still pay the compute bill, the support cost, and the implementation overhead while collecting less revenue. That creates a stronger incentive to improve reliability, guardrails, and task design instead of optimizing only for activity metrics.

In other words, the model does something healthy: it ties AI quality to revenue quality. A vendor that ships flaky agents can no longer hide as easily behind big usage numbers.

What gets messy

The hardest part is not billing. It is attribution.

Stripe's guide on outcome-based pricing makes the catch very clear. You have to define the unit, measure it with evidence, write exclusions and edge cases into the contract, and agree on how disputes will be handled. That sounds administrative, but it is the whole game.

A resolved support ticket is relatively easy to count. Revenue lift is not. If sales rise after an AI rollout, how much came from the model, how much came from better timing, and how much came from the rest of the business? Without shared rules, “pay on results” quickly turns into “fight over the spreadsheet.”

Why creators and small tool teams should care

This changes how AI products will be packaged

Even if you are not buying an enterprise support agent, this trend matters. It pushes the whole market toward a tougher standard: software should be paid for the value it creates, not just for turning on the meter. For creator tools, that could mean more pricing built around finished edits, approved assets, booked meetings, delivered clips, or recovered support tickets rather than raw generations or seat counts.

That will not kill seat pricing overnight. Hybrid models will remain common. But the direction is clear: AI software is being forced to act less like a landlord and more like a contractor.

Bottom line

The rent era is under pressure

The reported OpenAI move matters because it attacks the oldest comfort in software: getting paid before the customer sees clear value. If AI agents keep taking over real tasks, buyers will push harder for pricing that follows results, not just usage. The winners will be the vendors that can define the outcome cleanly, deliver it reliably, and prove it happened.

That is a much harder business than selling seats. It is also a more honest one.

Sources

Read the primary materials and supporting report

The Decoder: OpenAI starts charging some customers only when its AI actually works

Accessible report summarizing The Information's claim that OpenAI has started offering some large customers pay-only-when-it-works terms.

Sierra homepage

Used to verify Sierra's public outcome-based pricing language: customers only pay for the value Sierra delivers.

Stripe: Outcome-based pricing — a guide for businesses

Used to verify the implementation challenges around measurement, attribution, contracts, and dispute handling.

Stripe and Cheeky Pint: Bret Taylor of Sierra on AI agents, outcome-based pricing, and the OpenAI board

Companion context video used for the hero thumbnail and embed.