When payment depends on the result, vague outcomes and shared dependencies stop being footnotes and become commercial liabilities.

Outcome-based pricing always sounds attractive in the meeting.

The customer says, “If you believe in the result, put some of your fees at risk.”

The supplier says, “Absolutely. We’re confident.”

Procurement smiles. Sales feels progressive. Everyone congratulates themselves for aligning incentives.

Then somebody eventually asks the awkward question:

Who actually controls the outcome?

I’ve worked around enough large deals to know that outcome-based pricing is not simply about transferring risk to the supplier. It exposes where the risk was hiding all along.

Imagine a managed-services provider agreeing to reduce critical incidents by 30%.

The supplier can improve monitoring, strengthen problem management, automate recovery, and clean up operational procedures. Fair enough.

But the customer still controls application funding, change approvals, technical debt, business priorities, and several third-party vendors. One aging application continues failing because modernization was deferred. Another supplier introduces unstable releases. The customer repeatedly postpones permanent fixes because the workaround appears cheaper this quarter.

Critical incidents do not fall by 30%.

Now the commercial meeting gets interesting.

The customer says the outcome was missed. The supplier says the conditions required to achieve it were never provided. Procurement points to the contract. Delivery points to the dependency log. Sales looks around the room as if hoping to discover an emergency exit behind the presentation screen.

The pricing model did not align everyone. It gave everyone a more expensive argument.

You cannot sell ownership of an outcome without understanding who controls the conditions that produce it.

This is also where buyer psychology matters.

Outcome-based pricing feels safer because the customer believes payment is connected to performance. The supplier may see it as a way to demonstrate confidence and separate itself from competitors. Both sides can become emotionally attached to the elegance of the model before confronting the messiness underneath it.

But organizations do not produce outcomes through contract language.

They produce outcomes through decisions, behaviours, capabilities, systems, and dependencies—many of which sit outside the supplier’s authority.

That does not make outcome-based pricing a bad idea. I actually think it can create better commercial relationships when it is designed honestly.

The real conversation is not, “How much supplier revenue should be at risk?”

It is:

What exactly is the outcome? What is the starting baseline? Which party controls which levers? What must the customer do? What happens when another vendor causes the failure? How will improvement be measured? And what should happen when both sides outperform the target?

Those questions are not contractual fine print. They are the operating model behind the price.

A good outcome-based agreement should create shared focus and shared reward. A weak one becomes a traditional contract wearing an innovation nametag.

Sales leaders therefore need to resist the temptation to use outcome language merely to make the proposal sound commercially bold.

If the sales team cannot explain how the outcome will actually be produced, governed, measured, and influenced, it is not offering confidence.

It is offering optimism with a penalty clause.

Outcome-based pricing does not eliminate risk. It makes the risk measurable—and sends the bill to whoever misunderstood it.

If you’re exploring outcome-based commercial models and want to pressure-test where the value, control, and risk really sit, reach out. I’m always happy to have the conversation.