The Outcome Measurement Agreement: Designing Result-First Contracts
Type: media · article
Stage: Stage 3: Pricing Proof
Difficulty: advanced
A guide to charging per verified business result — resolved tickets, qualified leads, completed workflows — rather than per seat or per month. Includes the contractual foundations, strategic positioning, and risk/reward tradeoffs of outcome-based pricing.
Overview
Outcome-based pricing is the highest-trust and highest-stakes pricing model available to a SaaS founder. Instead of charging for access to the product, you charge for the business result the product delivers. The customer pays when a ticket is resolved, a lead is qualified, a contract is signed. The alignment is nearly perfect — when the product works, you get paid. When it doesn't, you don't. This model is increasingly available as AI-driven products create verifiable, measurable outputs that didn't exist in traditional software.
The results-based reframe
Traditional SaaS pricing charges for inputs: access to a platform, a number of seats, a volume of API calls. The customer is paying for the right to use the product — not for the value the product delivers.
Outcome-based pricing charges for outputs: the thing that actually happened as a result of the product working.
Examples of measurable outcomes:
• A support ticket resolved without human intervention
• A qualified sales lead that meets the agreed ICP criteria and books a meeting
• A contract review completed within the agreed turnaround time
• A reactivation email campaign that results in a recovered churned customer
• A compliance document that passes review on first submission
The shift from input to output changes the entire commercial relationship. The customer is no longer managing a tool — they're purchasing a verified business result. You are no longer a vendor — you are a partner whose revenue is tied directly to the customer's success.
This is why advanced founders are moving in this direction: the pricing model tells a fundamentally different story about the relationship, and that story commands higher contract values, longer retention, and more expansive budget access.
The Outcome Measurement Agreement
The contractual foundation of outcome-based pricing is the Outcome Measurement Agreement (OMA) — a document signed before the contract begins that defines exactly what counts as a valid, billable result.
The OMA must specify:
• The outcome definition — precisely what event constitutes a billable result. 'A resolved support ticket' is not specific enough. 'A support ticket where the customer did not reply within 24 hours after the AI response, with no escalation flag triggered' is specific enough.
• The measurement method — how the outcome is tracked, who has access to the tracking data, and what happens if the measurement system fails
• The attribution window — if the customer does multiple things in parallel with your product, which outcomes are attributable to you and how is this calculated?
• The dispute resolution process — what happens when the customer disputes an outcome count? What data wins?
• The exclusions — outcomes that don't count: test tickets, internal-only tickets, tickets triggered by the vendor's own systems
Without an OMA signed before the commercial relationship begins, outcome-based pricing devolves into disagreements about what was delivered. The OMA is not optional — it's the mechanism that makes the model workable.
Strategic positioning
Outcome-based pricing changes how you appear in a customer's internal budget conversation.
Seat-based pricing: 'We're spending $X/month on this tool.' The customer evaluates you against other tools in the same budget category. You compete on features and price.
Outcome-based pricing: 'We're spending $X per resolved ticket, and our ticket resolution rate with this vendor is 87%.' The customer evaluates you against the cost of the outcome you're replacing (human agents, manual review, outsourced services). You compete against the alternative cost of the result.
The ROI narrative in a sales conversation:
• Old model: 'Our platform costs $2,000/month. Here are the features you get.'
• New model: 'We charge $3 per resolved ticket. Your current cost per ticket with your support team is $18. At your current volume of 2,000 tickets/month, you're spending $36,000/month for outcomes we can deliver for $6,000/month — and our escalation rate is under 13%.'
The second conversation positions you as a strategic partner with a verifiable financial argument. The buyer's manager can approve it in 10 minutes. The first conversation requires a committee and a three-month evaluation.
Risk and reward tradeoffs
Outcome-based pricing is not without structural risk. The founder must be prepared for:
• Revenue fluctuation — if the customer's volume drops (seasonal, structural, or due to their own business changes), your revenue drops with it, even if the product is working perfectly. Build this variability into your financial model: what does your revenue look like at 50% of expected volume? 25%?
• Value attribution complexity — in any real business environment, multiple factors affect outcomes. Your AI resolved the ticket, but the customer's help center documentation was also improved last quarter. How much of the improvement is yours? Attribution disputes are the most common friction point in outcome-based contracts.
• Product reliability requirements — when you charge per outcome, every product failure is a direct revenue loss, not a customer experience problem. Your reliability standard must be higher than a seat-based product's, because the consequences of downtime are immediate and quantifiable.
• Scope creep in outcome definition — customers will frequently test the edges of the OMA, attempting to count outcomes that were excluded or disputing outcomes that should count. The OMA must be specific enough to resolve these disputes without renegotiation.
The founders who succeed with outcome-based pricing are those who have enough data about their product's reliability and outcome rates to price the model sustainably before offering it — not those who adopt it as a sales tactic without the operational foundation to deliver it.