Free guide · Buying an outcome
Outcome-Based Service Buying Checklist
Use this worksheet when a supplier proposes charging for a result rather than another software seat. Define the result before comparing prices. A reported activity—such as a closed ticket—is not automatically a successful outcome.
Fill in the buying brief
Business outcome: [what changes for the customer] Unit counted: [what triggers payment] Starting baseline and measurement period: [source and dates] Success threshold: [observable quality and time standard] Exclusions and exceptions: [what does not count, and why] Reopened or corrected work: [how counted and who pays] Human review: [which cases require a person] Evidence and reporting: [records buyer can inspect] Data, access and security boundaries: [what supplier can use] Price and volume assumptions: [including minimums and overages] Dispute and exit process: [how errors are resolved] Owner: [who signs off on the definition]
Questions to ask the supplier
- What precisely counts as a completed outcome, and who verifies it?
- How is quality measured, not just volume or speed?
- What happens when the work is reopened, reversed or needs correction?
- Which exceptions go to a human, and how quickly?
- What evidence can we inspect for any disputed result?
- What work remains with our team, and what expertise does the supplier provide?
- How do price, minimum volume and risk compare with a subscription or internal process?
Worked help-desk example
A proposal charges per “resolved request.” A weak definition counts every closed ticket. A stronger draft definition counts a request only when the customer's issue is addressed, the resolution is recorded, and the customer does not reopen it within the agreed review window. Exclude duplicates and tickets closed without a response. Route account-access exceptions to a person. The buyer and supplier must agree on the window, evidence and dispute process before any price comparison is meaningful.
Compare options on the same basis
| Criterion | Outcome-based service | Software seats / current process |
|---|---|---|
| Total expected cost, with volume range | ||
| Quality standard and evidence | ||
| Exceptions and human work | ||
| Reopened work and disputes | ||
| Data access and exit risk |
Decision check: Can you explain the measured result, inspect the evidence, and calculate a plausible cost under low and high volumes? If not, clarify the offer before buying.