Outcome-Based Pricing Sounds Fair. In Practice, It's Just Penalties with Better Marketing.

Why would a partner invest in helping you improve your business when the primary benefit to them is less work or lower margin?

That's the question nobody in outsourcing is asking out loud. The industry has spent two decades talking about partnership, innovation, and shared success. The contracts tell a different story.

The FTE-based model is breaking down. Everyone knows it. Clients want vendors who bring AI, analytics, and transformation, not just bodies and SLA compliance. Vendors are being asked to take on more risk, invest more capital, and deliver more sophisticated outcomes than any hourly rate was ever designed to support.

So why isn't the new model working?

Because we're trying to solve a new problem with the old mindset.

What "outcome-based" looks like in practice.

I was advising a US client negotiating a large outsourcing contract. The client wanted to move to per-call pricing, and specifically, they only wanted to pay for first-contact resolutions. Repeat calls from the same customer within a defined window would not be reimbursed. The logic was straightforward: if the agent resolved the issue the first time, there wouldn't be a repeat call.

Fair thinking. But here's what the contract didn't account for.

What if the repeat call happened because the client's own field service team failed to fix the problem, not because the agent gave a wrong answer? The customer calls again. The agent handles it perfectly. But under this model, the vendor absorbs the cost of a failure they had no part in creating.

Same engagement. Same client. They also wanted the vendor to invest in voice and chat AI agents. But here's the catch: they wouldn't pay for interactions handled by AI. The vendor would fund the technology, absorb the implementation cost, take on the risk of a new platform, and receive nothing for every call the AI successfully resolved.

When I pushed back, the client's response was direct: "This is what the vendor needs to deliver if they want the business."

That's not outcome-based pricing. That's risk transfer with a partnership label on it.

The other side of the table.

I've also been the vendor in this conversation. A different client, a different contract — but the same fundamental dynamic.

The client wanted flexibility. They asked us to staff above our WFM forecast — to carry a cushion of agents beyond what the data said we needed, available on demand when volume spiked. We absorbed that cost. Agents on the clock, waiting.

The pricing still had to come down. And if we missed our committed hours, by even one hour in a month, there was a penalty. No margin of error. But if we delivered hours above commitment? No credit. No acknowledgment. No upside.

Full downside. Zero upside. And the base rate still had to decrease.

I've sat in both rooms. The mindset is the same in both of them: transfer the risk to the vendor, keep the reward on the client side, and call it a partnership.

Why vendors stop innovating.

Here's what nobody says publicly because it sounds self-serving — but it's true.

When a vendor delivers results under an outcome-based contract, clients renegotiate pricing down. The vendor hit the target. Costs came down. CSAT went up. So the client asks for a lower rate in the next cycle. The vendor never recaptures the investment. Never earns the premium that justified taking the risk in the first place.

Apply the same logic to your vendor relationship. If the results are there, the investment should follow. If the only response to a vendor delivering results is to reduce what you pay them, you've designed a system that punishes success. And vendors learn quickly. They stop taking risks. They stop investing. They do what the contract requires and nothing more.

That's how the old model reproduces itself inside a new pricing structure.

What the contract of the future actually requires.

This is not a vendor problem or a client problem. It's a design problem. And fixing it requires both sides to change.

For the model to work, four things have to be true.

First, KPIs need to be tied to causal factors that the vendor can actually control. Penalizing a vendor for repeat calls driven by your broken field service process is not outcome-based pricing. It's misdirected accountability. If you want shared risk, start with an honest assessment of who owns what.

Second, there has to be a defined investment and recovery period. Vendors need fair time to recoup both successful and unsuccessful innovation bets. AI implementation, process redesign, technology integration — these are not free. If you want a vendor to invest, build the recovery window into the contract. Not as a favor. As a condition of the risk you're asking them to take.

Third, risk has to be symmetric. Penalties for missing must be matched by real upside for exceeding. Not a thank you. Not a conversation about the next contract cycle. Actual financial upside built into the current agreement. If you're not willing to write that clause, you're not actually offering outcome-based pricing.

Fourth, the vendor needs access to the data and decisions that drive the outcome. You cannot hold a partner accountable for results they don't have the visibility or authority to influence. If the systems are broken, fix them first. If the data isn't shared, share it. If the decisions are made above the vendor's head, don't put the outcome in their contract.

The mindset shift that makes all of this possible.

The old model was built on a simple premise: keep the vendor hungry, keep the penalties sharp, and competition will drive performance. That model had a logic to it when the work was transactional, the switching costs were low, and the ask was labor at a price.

That's not the ask anymore.

Today, clients need vendors who will invest in AI, build industry-specific expertise, redesign processes, and take accountability for outcomes that span technology, people, and operations. That level of commitment doesn't come from a vendor who is one rebid away from losing the business. It comes from a partner who has enough confidence in the relationship to take real risk.

The clients who figure this out first will have a significant advantage. Not because they'll pay more. Because they'll get more — more innovation, more accountability, and more of their vendor's best thinking applied to their hardest problems.

The question worth asking before your next contract negotiation is not "how do we protect ourselves if they underperform?" That question will always get answered. The question that changes the outcome is: "Have we designed this contract so that our partner can actually win?"

If the answer is no — you're not doing outcome-based pricing. You're doing penalties with better marketing.

In your current outsourcing relationships, is the contract designed for your vendor to succeed — or just to protect you if they fail? Tell me on LinkedIn. I read every comment.