The structural problem with paying for effort rather than results is one that Charlie Munger, Vice Chairman of Berkshire Hathaway, identified as a universal law of organizational behavior: “Show me the incentive, and I will show you the outcome.”
When a provider is paid by the hour, the incentive is to fill hours. When a provider is paid per agent, the incentive is to maintain headcount. Neither of those incentives points in the same direction as the brand’s: keep customers, grow revenue and reduce the cost of doing both. But the growing interest in a better model has produced confusion about what outcome-based contracting is, how it works and what it requires.
Outcome-based pricing vs. an outcome-based operating model: Not the same thing
These two concepts are often used interchangeably, but they shouldn’t be.
Outcome-based pricing changes what you pay for. Results-based financing provides a useful discipline for this distinction: it makes some portion of payment contingent on the achievement of predefined and independently verified results, rather than simply reimbursing inputs or activities. Outcome-based operating models change how the work gets done in order to produce the result you’re paying for. One is a formula, and the other is a redesign of agent behaviors, workflows, governance structures and how performance gets measured in real time.
As Ryan Holder, VP of Account Management at Foundever and one of our most experienced practitioners in this space, puts it: “Outcome-based pricing is not monolithic. You have to look at it with nuance based on the nature of the business, what you’re trying to solve and what the model then becomes.”
There’s also a more fundamental definitional problem: a KPI is not an outcome. A KPI measures activity or performance — FCR, CSAT or AHT. An outcome is the business result those metrics are meant to predict: subscriber retention, revenue protected, churn reduced or lifetime value grown. KPI-based contracts capture what already happened. The behavior that changed the score happened weeks ago, before it showed up in the metric, leaving no practical window to intervene.
CX-industry analysis describes a clear shift in BPO contracting from agreements centered on hours worked or resources allocated toward arrangements measured against specific business results, including revenue, cost and customer-experience outcomes. It also notes that this transition calls for more collaborative relationships, flexible contract structures and robust performance monitoring, not simply a new pricing formula.
What has to change before an outcome-based model can work
The sequence is everything. Before a contract can express outcomes, an operation has to be redesigned to produce them. And this has to happen from both sides of the relationship. There should be a level of shared visibility into what the operation is doing, a willingness from both parties to redesign how work flows and a mutual commitment to owning what the results will become.
That redesign moves through five phases:
1. Define the outcome clearly, then trace it back to behavior. The assumption that “if we improve first contact resolution, everything else will follow” is common — and costly. As Ryan says, “You can still resolve a problem and give a poor experience. For example, resolution can go up while satisfaction stays the same. The outcome has to be clearly defined, and the specific behaviors that drive it have to be identified first. Making the operational truth visible is sometimes the hardest part of the conversation. It requires the client to open up their data and their assumptions, and the partner to be honest about what the operation can and cannot support.”
2. Redesign workflows around the outcome. Most CX workflows are engineered to handle volume: to reduce handle time, minimize cost per contact and process interactions as quickly as possible. Outcome-based operations require something different: routing logic, escalation paths, and agent guidance that reflect what creates value for the customer, not just what reduces cost for the operation.
3. Build governance on leading indicators, not lagging metrics. Leading indicators measure the conditions and behaviors that predict the outcome before it’s visible. Lagging metrics — such as CSAT, FCR and NPS — tell you what happened. Leading indicators give you a window to change what happens next. Real-time measurement of agent behaviors is the foundation of this model.
4. Align incentives at every level. What agents are rewarded for internally has to connect directly to what generates value under the commercial model. When internal incentives point in a different direction than the contract, the commercial model will pull in one direction while the operation runs in another.
5. Write the contract. It should express what the operating model delivers and how risk is shared between both parties.
Signing the contract is not the end of the process. It’s the start of a continuous cycle of measuring, adjusting and holding each other to account for what the model was designed to produce.
The outcome-based partnership trap: When metrics get gamed
When commercial stakes are attached to a specific measure, there will always be pressure to reach that measure by whatever path is available. For example, a three-day resolution target can be “achieved” by telling a customer to call back in four days. A CSAT score can be influenced through behaviors that have nothing to do with delivering a better experience. There are ways to game the system.
The more defensible approach is to attach the operating model to the behaviors that drive the outcome, not just the outcome itself. “If you can identify the specific actions that are structurally predictive of the result you want, and build governance around measuring those behaviors in real time, you create a model that’s harder to game and more likely to sustain,” says Ryan.
Readiness is key, too. “There needs to be a level of maturity and stability in the business so that you can baseline and understand what is achievable and then build upon that,” says Ryan. “If there’s a lot of variability in the data, it’s very difficult to create and drive an outcome-based model.”
Outcome-based results for a telecoms sales program
In a telecoms inbound sales program, one of Canada’s largest telecommunications providers and Foundever had a structural misalignment: compensation rewarded agent availability, not the quality of what they produced. Both parties knew the arrangement wasn’t aligned to the outcomes that mattered.
The decision was made to shift to an outcome-based structure, one where Foundever’s compensation was tied directly to sales per activated unit. But at the outset, conversion rates were sitting at just 11%, and an operational analysis revealed the root cause: agents were handling a high volume of low-intent interactions that drained capacity and diluted conversion metrics. Under an outcome-based model, that call mix would make the operation financially unviable.
So, before the contract could work, the operation had to change, and that change had to be built together. Foundever and the client redesigned the program jointly across four dimensions:
- Call routing and intent filtering: Intercepting low-intent interactions before they reached the sales floor, reserving the queue for customers with genuine buying intent
- Workflow redesign: Freeing agents to focus fully on revenue-generating conversations
- Collaborative governance: Daily performance management cadences and calibration sessions with client stakeholders
- Incentive alignment: Linking associate rewards directly to outcome achievements
The conversion rate more than doubled, rising from 11% to a sustained 23%. The operation completed a full transition from hourly billing to a performance-based structure, creating a scalable framework that both the client and Foundever could build on.
The contract set the terms, and the redesigned operation delivered the results.
Three questions to ask before you pursue an outcome-based contract
Not every organization is ready for this model. Knowing where you stand before entering the contract conversation is key. Before the contract conversation begins, here are three questions you should ask:
Are we ready to redesign how we operate, or are we hoping a new pricing structure will solve an operational problem? Pricing changes don’t resolve process problems. A broken escalation path or a rigid workforce management system will undermine the model regardless of how the contract is written.
Do we know what drives our desired outcome in our specific environment? What, with our customers and our product, are the behaviors and conditions that predict the result we care about?
Are we prepared to govern in real time? Outcome-based models require operational visibility that many organizations don’t currently have, such as live dashboards, leading indicator tracking and weekly root cause analysis. If your governance rhythm is quarterly, the infrastructure won’t support what the contract requires.
Outcome-based contracting is a different kind of relationship altogether, one where both parties share visibility into what the operation is doing, both parties commit to redesigning how it works and both parties own what it produces. It requires trust, transparency and a willingness to redesign the partnership itself.
Redesigning a commercial model is one of three challenges showing up consistently across CX organizations right now. Download “The CX complexity guide” to see how 221 leaders across eight industries are tackling attrition, AI and cost pressure.