Customer outcomes framework
Definition
Customer outcomes framework
A customer outcomes framework is the agreed way of naming what a customer is actually buying, how that result is measured, and how commercial terms attach to it. It describes the goal, not the data behind it or the activity that produces it.
Keep that line clean — a scoring practice tells you how an account is doing against a goal, while the framework is the document that says what the goal is and who agreed to it.
Most disputes in outsourcing start here. Both sides measured diligently, but nobody wrote down, in advance, which result the money was actually buying.
Key takeaways
- The framework names the outcome, its measure, its baseline and the commercial consequence of missing it.
- Outcomes are results the customer wanted anyway, not activity volumes a supplier finds easy to count.
- Every outcome needs one owner on each side and one agreed source of truth for the number.
- Review the framework yearly, because an outcome that no longer matters still shapes behaviour.
How it works
You start from the result the customer is buying, then work backwards. Name the outcome in plain words, agree the measure and its baseline, set the review rhythm, and decide what happens commercially when the number moves either way.
| Layer | Example | Who owns it |
|---|---|---|
| Activity | Calls handled per hour | Supplier operations |
| Output | Tickets resolved first time | Supplier and client jointly |
| Outcome | Repeat contacts avoided per customer | Client business owner |
| Commercial | Fee adjustment tied to the outcome | Both sides, in the contract |
The measurement layer usually lands in the service level agreement (SLA), which is where a framework becomes enforceable rather than aspirational. The SLA carries the number; the framework explains why that number was chosen.
Baselines decide everything — an outcome measured against a flattering starting point rewards nobody, and an outcome with no baseline at all turns the first review into a negotiation.
Agree the data source in the same sentence as the measure. Two sides reading one outcome off two different systems is the most reliable way to lose a year to reconciliation.
Consequences need the same care. Service credits outsourcing terms are the usual mechanism, though credits punish misses without rewarding the overshoot that an outcome framework is meant to encourage.
Mapping helps. A business capability model shows which internal capability each outcome depends on, which stops a supplier being held to a result that three other teams control.
Translate the outcome into something measurable at the work face. Critical to quality attributes do that job, turning a broad promise into the handful of characteristics an agent can influence on a single contact.
Regulated buyers have a further obligation. OCC Bulletin 2023-17, issued on 6 June 2023, sets out interagency guidance on managing third party relationships for banks and federal savings associations.
Public sector frameworks follow the same logic — the US Office of Personnel Management publishes guidance offering a strategic approach to managing human capital in federal agencies, built around stated results rather than activity.
Finally, prove the framework pays. A straightforward cost benefit analysis against the previous arrangement keeps the conversation about value rather than about unit rates.
Write the customer outcomes framework before the pricing, not after. Once a rate card exists, every outcome discussion collapses back into a conversation about unit cost and headcount.
Review cadence belongs in the framework too. Quarterly for the numbers, yearly for whether the outcome still describes what the business is actually trying to achieve.
Suppliers should push for this as hard as buyers do. An outcomes framework is the only durable defence against being judged on a result that three other teams control.
Examples
Outcome definitions differ by sector, because the result being bought differs. Banks buy reduced risk, retailers buy repeat purchase, healthcare payers buy resolution without rework, and technology buyers buy uptime the user can actually feel.
Banking collections. The outcome is not calls made; it is sustainable repayment arrangements that are still being honoured ninety days later. That single change of measure rewrites how a supplier staffs and coaches the floor.
Retail customer service. The outcome is repeat contact avoided, not average handle time. Suppliers paid on handle time have every reason to close a contact early and see the same shopper again next week.
Health insurance administration. The outcome is a claim resolved correctly the first time, measured on a sample audited by the payer. Accuracy beats speed, and the framework has to say so explicitly.
Technology support. The outcome is uptime experienced by the end user, measured from the user’s device rather than from the supplier’s monitoring console. Where the measure sits changes the behaviour it rewards.
The pattern across all four is the same — write the measure from the customer’s side of the desk, because anything taken inside the supplier’s own systems drifts toward what the supplier controls.
Related terms
- Revenue share model: one commercial structure for tying a supplier’s reward to an agreed outcome.
- Strategy implementation: the delivery work that an outcomes framework is supposed to point in one direction.
- Service level agreement (SLA): the contractual home of the measures a framework defines.
- Critical to quality: the attributes that translate a broad outcome into something a team can influence daily.
- Cost benefit analysis: the check that an outcome is worth what it costs to pursue.
FAQ
How is an outcome different from an output?
An output is something the supplier produces, such as a resolved ticket. An outcome is the change the customer wanted, such as not having to make contact again at all. Outputs are easier to count, which is why contracts drift toward them.
How many outcomes should a framework carry?
Three to five. Beyond that, teams stop prioritising and the framework becomes a reporting pack nobody reads before the meeting. Rank them, so everyone knows which one wins when two conflict.
Who owns an outcome?
One named person on each side. The client owns the business result, the supplier owns the contribution it controls, and both sign off the same measure.
Can outcomes be written into a contract?
Yes, and they should be. Tie a defined share of fees to the agreed measure, and state the data source and audit method in the same clause. Agree in advance who arbitrates a disputed number.
When should the framework be reviewed?
Review it yearly and after any major change in strategy. An outcome that has stopped mattering still drives behaviour until somebody formally retires it.
Browse Outsource Accelerator’s outsourcing guidance before you commit a framework to contract.
Independent
