Result-Oriented Pricing
Definition
Result-Oriented Pricing
Result-oriented pricing sets a price against a required end state rather than against the activity used to reach it. The specification comes first and the price follows it, which is the reverse of how most contracts are actually built.
The distinction matters because a requirement written in hours can only be priced in hours — rewriting it as a result is what makes any other model available.
Public procurement has treated this as doctrine for years. Federal buyers are told to describe work in terms of results rather than methods, and everything downstream follows from that instruction.
Where it goes wrong is measurement — a result nobody can observe without a meeting is not a result, it is an opinion with a delivery date attached.
Key takeaways
- The requirement is written as a required end state, not as a method or an hour count.
- Measurable standards and a surveillance method must accompany every stated result.
- The buyer gives up control of how the work is done, which not every buyer can accept.
- Weak results specifications produce disputes at payment time, not at signature.
How it works
Three artefacts do the work: a statement of required results, measurable standards attached to each, and an agreed method for checking them. Missing any one turns the arrangement back into an hourly contract with extra paperwork.
The federal instruction is explicit. Buyers must “describe the work in terms of the required results rather than either ‘how’ the work is to be accomplished or the number of hours to be provided”.
Standards come next, and the same rules require “measurable performance standards (i.e., in terms of quality, timeliness, quantity, etc.) and the method of assessing contractor performance against performance standards”.
Consequence is the third leg. A fixed-price services clause lets the buyer “reduce the contract price to reflect the reduced value of the services performed”, which is the enforcement mechanism behind the specification.
| Requirement written as | What it enables | What it prevents |
|---|---|---|
| Hours of effort | Hourly or FTE pricing | Any transfer of delivery risk |
| Tasks completed | Unit or transaction pricing | Rewarding a better method |
| Results achieved | Fixed, outcome or incentive pricing | Buyer control of method |
| Business outcomes | Gain share, outcome pricing | Use where attribution is unclear |
The table is the practical point. Buyers who want outcome pricing but keep writing task lists are asking suppliers to price a risk the specification never transferred.
Surveillance then has to be proportionate — a monthly sample against stated standards works, while inspecting every item rebuilds the supervision cost the model was meant to remove.
Examples
Results-first specification changes what can be bought, and it exposes buyers who were never really willing to let go. These four cases show the difference between a genuine result and a relabelled task list.
A government agency specifies a records service as a required accuracy and turnaround standard. Suppliers bid different methods, and the winning one automates a step the agency had not considered.
A manufacturer writes a maintenance requirement as equipment availability rather than as a visit schedule. Planned visits fall, availability rises, and the supplier keeps the benefit of its own method.
A retailer specifies results but retains approval over staffing, tooling and process. Suppliers price it as an hourly contract, because that is what it actually is.
An insurer writes results with no surveillance method attached. Payment disputes begin in month three, and both sides end up arguing from different spreadsheets.
Related terms
Result-led contracting is described with several labels that sit at different points in the process. The entries below separate the specification from the payment mechanism it makes possible.
- Result based outsourcing: the delivery model, where this entry covers the pricing that follows.
- Outcome based pricing: pays when a business outcome occurs, which needs this specification first.
- Statement of work (SOW): the document where results or methods actually get written.
- Key performance indicator (KPI): the measurable standard attached to each result.
- Milestone based pricing: pays on accepted deliverables rather than on a standing service result.
- Service level agreement compliance: the surveillance record that proves a result was met.
- Transformational outsourcing: where results specification matters most, because the method should change.
FAQ
How is this different from outcome based pricing?
This is about how the requirement is written; outcome based pricing is about when money changes hands. You need the first before the second is possible.
What makes a result measurable?
An observable standard with a number and a method of checking it. If confirming the result needs a discussion, it is not yet a standard.
Does the buyer lose control?
Of method, yes, and that is the trade. Buyers who retain approval over staffing and process have not transferred anything and should not expect result pricing.
How much surveillance is enough?
Proportionate sampling against the stated standards. Full inspection rebuilds the oversight cost the specification was written to remove.
Can existing contracts be converted?
Usually only at renewal. Rewriting a task-based schedule into results mid-term changes the risk balance, and suppliers will reprice accordingly.
What happens if a result is missed?
The contract should already say. A price reduction reflecting the reduced value of the service is the standard remedy in public contracting.
Find providers who will bid against a results specification in the Outsource Accelerator directory.
Independent
