title: 'AI Decisions Are Pricing Decisions' tagline: "Every model swap, prompt change, and workflow tweak is a pricing decision. Most builders aren't measuring it. Their customers are paying for it." description: "AI vendors pass internal cost decisions to customers via token pricing. Outcome pricing is the only model that delivers per-customer pricing consistency." publishedAt: '2026-05-20' updatedAt: '2026-05-21' author: 'Blaise Albuquerque' authorRole: 'Founder, Bear Lumen' category: 'insights' tags: ['ai-pricing', 'outcome-based-pricing', 'unit-economics', 'cost-to-serve', 'pricing-strategy'] featured: true reviewed: true voice: manifesto
AI decisions are pricing decisions.
Every model swap, every prompt change, every new feature, every workflow tweak shifts your unit economics. Sometimes it's things outside of your control. Sometimes it's just the inherent nondeterministic nature of AI.
Either way, most companies cannot tell you by how much. The pricing conversation has become the most ambiguous part of an AI investment that is otherwise run with rigor.
That is not a small gap that can continue to be ignored. It's the gap that's festering.
A shift no one priced for
We've all heard this conversation. For two decades, the SaaS pricing model assumed a stable consumer: a human, sitting at a dashboard, clicking.
Cost-to-serve was bounded by what a human could do in a day. Seat pricing worked because seats were a proxy for that bound.
That assumption is now wrong, and most products are still priced as if it were true.
The new consumer is largely not a human at a dashboard. Or at least, that's the direction companies are working towards.
The new consumer is an agent acting on behalf of a human. The agent does the expensive preparation work.
It calls APIs, runs CLIs, and queries MCPs (Model Context Protocol servers that expose tools to agents). It sets up notifications, configures tooling, and arranges preferences so outcomes or decisions can be made.
Sometimes that agent belongs to the provider. Other times it belongs to the customer. Either way, the customer consumes the outcome.
This isn't the future. This is 2026, and it's the direction nimble companies are building towards.
These agentic sessions, called copilots, prepare outcomes or decisions for a human to approve or not depending on the impact. Every customer support AI drafts responses a human sends after verifying the outcome against the artifact evidence.
Every sales AI prepares lists of humans to reach out to and the copy to use, which aggregates personalization. The hybrid pattern exists already.
However, the granular cost per customer driving that outcome is less clear.
The cost shape that broke the model
Picture a customer support AI product. The vendor ships a quality improvement: better reasoning, sharper sentiment analysis.
The resolution accuracy moves from seventy-five percent to eighty-five percent. That's a real product gain.
However, the token consumption to deliver each resolution doubles.
Now consider the customer in this scenario. Their support queue didn't grow.
They're processing the same number of inbound issues this month as last. Their behavior didn't change, their staff didn't change, their workflows didn't change.
Yet the bill doubled.
A few days before the cycle closes, they get a notification that they're near their limit. It's too late and too vague to act on.
They can't tell why the bill went up. They can't tell whether the new accuracy is worth the new cost.
They can't tell whether this is a one-time spike or the new baseline. They're not pricing-fluent, and frankly, they shouldn't have to be.
Now ask the obvious question: who pays for the difference?
In every AI product priced per token, the answer is the customer. The vendor made a product decision to improve quality.
The provider the vendor builds on charges more for the better reasoning. The vendor forwarded the difference.
The customer absorbed it. The customer experienced the decision as a billing surprise rather than as a product improvement.
This is what's happening across the AI software industry right now. Vendors are running quality experiments, swapping models, tuning prompts, expanding context windows, adding retries.
Each one of those decisions is a pricing decision the customer never consented to. The customer is eating the cost of someone else's reckless adoption of AI.
Cursor learned this the hard way. When it switched its Pro plan to token-based billing in mid-2025, users who budgeted $20/month saw invoices hit $60 to $100. One five-person team spent $4,600 in six weeks.
The customers hadn't changed their behavior. Cursor had changed its math, and the customers absorbed the difference.
And the customer can't walk away. The feature is now load-bearing for their business.
So they pay. They expense the surprise bill. They notice it.
They post a review that says the pricing is opaque and the bills are unpredictable. They tell their network.
Then the next quarter, the vendor ships another improvement. The bill spikes again.
The customer pays again, because they still can't drop the product. But the next review is sharper, and the next renewal conversation is more skeptical.
This is how trust compounds in the wrong direction. The customer hasn't yet churned. The reputation has.
The pricing model that breaks centuries of business practice
Step back and consider what this is, structurally. For most of commerce, when you buy something, the price is known before the transaction.
A rubber ducky costs ten dollars. You buy a hundred ducks, pay a thousand dollars, paint them, sell them in your store for thirty each.
The math works. The business works.
Usage-based AI pricing breaks that contract. Today's rubber ducky costs ten dollars.
Tomorrow's costs a hundred, because a caching issue spiked the token usage required to deliver "one ducky." The duck is identical.
The price is ten-times-higher because of something happening inside the vendor's infrastructure that the customer has no visibility into and no agency over.
Now try to run a store on that. Try to set a retail price on your painted ducks when the wholesale price of an unpainted duck swings ten-times week to week.
Try to forecast next quarter. Try to tell your investors what your gross margin will be.
You can't, because the input cost isn't a price anymore. It's a roulette wheel that the vendor spins on a schedule you can't see.
The same thing happens further up the supply chain. Consider a woodcrafter who buys raw materials from a producer.
The producer ships wood at varying prices. The variance isn't supply and demand. It's decisions inside the producer's workshop the woodcrafter never sees.
The producer might call this "transparent pricing" because every gram of wood is metered and itemized. But to the woodcrafter, transparency without consistency is a tax dressed up as a meter.
The producer's internal decisions become the woodcrafter's external margin problem.
Centuries of commerce solved this problem by stabilizing the unit of trade. You buy a ducky for ten dollars.
You buy a board-foot of oak at six dollars. You buy a kilowatt-hour at fifteen cents.
The unit is known, the price is known, and the buyer can build a business on top of it. Per-token AI pricing reverses that.
The unit floats. The price floats. The customer absorbs the float.
That's why this has to change. Companies building AI products need per-customer pricing transparency that delivers consistency to the customer.
The vendor takes on the variance internally. The customer sees a stable price for the outcome they actually care about.
That's the goal.
Customers don't want transparency. They want consistency.
Half the pricing industry is selling transparency as the answer. Per-token meters, real-time dashboards, line-item invoices.
However, none of that is what the customer actually wants. The customer wants a bill stable enough to budget against.
Think about how you'd feel if your electric bill came with a per-electron line item. You wouldn't feel informed. You'd feel taxed.
Token pricing is the vendor's unit of measurement sold to the customer as if it were their own. It's easy for the vendor because tokens are how the provider bills them.
It's hard for the customer because they have to do conversion math to figure out what they actually bought. Worse, when the vendor's model changes shift that math, the customer has no idea whether they got a worse deal or a different product.
Consistency is what trust is built on. A customer who can predict the cost of using your product next quarter trusts you.
A customer who can't is a customer who's shopping for an alternative even when they like the product.
Here's the contrast in one table:
| Pricing model | Who absorbs the variance? | Customer can budget? | Vendor IP exposure |
|---|---|---|---|
| Per-token | Customer | No (token-to-outcome ratio is unstable) | Required for any real transparency |
| Per-outcome | Vendor | Yes (price per resolved ticket, drafted brief, etc.) | Stays internal |
There's also a reason most vendors don't provide real transparency into how tokens are spent. The transparency would expose the workflows that make the product good.
The prompts. The retry logic. The context strategies. The model selection rules.
These workflows are the product. They're the IP. A customer who can see how each token was used can reverse-engineer most of how the product works.
Per-token pricing forces an impossible choice. The customer experiences opacity as risk transfer.
The vendor experiences disclosure as IP loss. There's no middle ground at the token layer.
"We'll add a better cost dashboard" doesn't solve this, because the unit of measurement is the IP itself.
Outcome pricing dissolves the paradox. The unit becomes a plain-language customer-facing artifact: a resolved ticket, a drafted email, a qualified lead, a generated brief.
The cost to produce that outcome stays opaque on the vendor side, where it belongs. The customer gets consistency. The vendor keeps the IP.
It's the only model that satisfies both parties.
Who absorbs the variance?
Here's the test every AI pricing model should pass.
When your product decisions shift cost, who absorbs the variance?
If you change a model and your customer's bill goes up, that's risk transfer. Not pricing.
If you tune a prompt that adds tokens and your customer's bill goes up, that's risk transfer. Not pricing.
If your internal workflow improvement raises latency and adds retries and your customer's bill goes up, that's risk transfer. Not pricing.
The product mistake belongs to the builder. The bill shouldn't.
This is the integrity test, and it's also the fairness test. A builder who absorbs variance is acting in good faith.
A builder who passes it through is asking the customer to insure the builder against the builder's own decisions. That's not a pricing model.
That's a transfer of risk dressed up as a meter.
What builders need to do
Three things.
Price the outcome, not the work
What does your customer actually buy? A resolved ticket. A drafted email. A built dashboard. A qualified lead. A generated brief. A completed workflow.
That's the unit. Price that.
The variance in producing it is your problem to manage, not your customer's.
Own the margins
Owning margins means knowing what each outcome costs you to produce under current model conditions. And knowing how that cost is moving over time.
It means absorbing the variance from your AI decisions on your own P&L (profit and loss).
It means saying no to product decisions that would compromise unit economics, even when they'd be otherwise interesting.
Invest in instrumentation that tracks pricing impact per AI decision
This is the part almost nobody is doing. Every AI decision should be measurable as a pricing decision.
When you swap a model, your dashboard should show you the per-outcome cost shift across every customer segment.
When you tune a prompt, you should see the cost-per-completion delta.
When you ship a feature, you should know which outcomes it added and what each one costs to produce.
Without that instrumentation, you're running an AI business by intuition. That's the same as running it blind.
The market has spent eighteen months arguing about which pricing model is right. Seats, usage, credits, outcomes.
However, the answer is downstream of one decision the builder has to make: are your customers going to pay for the variance of your AI decisions, or are you?
If your answer is "the customer," you're not in a pricing conversation. You're in a risk-transfer conversation.
Why I'm writing this
I'm building Bear Lumen because the instrumentation layer I just described exists in disjointed forms and is largely incomplete.
Billing platforms like Lago, Metronome (now part of Stripe), and Orb capture the wallet. They tell you what to invoice. They don't tell you what each invoice cost you to deliver.
Observability platforms like Helicone, Langfuse, and Arize trace per-request cost. They tell you which API call cost what. They don't tell you which customer outcome that call was producing.
There's no single tool for product, finance, and engineering to come together on. Existing tools have gaps.
The AI building conversation I'm hearing describes challenges all companies are having. Industry voices like Anh-Tho Chuong at Lago, Steven Forth on pricing innovation, and Rob Litterst at Good Better Best each describe a piece of the same elephant from different angles.
However, almost none of them have named the underlying problem this directly. The customer is paying for the vendor's product decisions.
The unit of measurement (the token) is also the IP. No amount of "better transparency" will fix that.
Bear Lumen measures cost-to-serve outcomes for your users, products, and features. Not just tokens. Not just requests. Not only traces.
The thing you need for driving your pricing strategy. The cost of producing each thing the customer actually values, attributed to the customer who consumed it, grouped by the product or feature that produced it.
The dataset everyone's been pricing against without ever measuring it.
That's the instrumentation layer. It's the prerequisite for outcome pricing, which is the prerequisite for the kind of accountability this post is arguing for.
Your AI product decisions are pricing decisions.
Are they benefiting your customer, or hurting them?
Are you making them with integrity and fairness?
Are your customers actually happy with the way you are pricing your product?