Outcome pricing sounds simple in a sales conversation: you pay for the result, not the hours. Writing a contract that actually survives contact with a real project is where most outcome-priced engagements quietly turn back into day-rate ones.
Key takeaways
- An outcome contract needs four things to hold up: a testable definition of done, a milestone schedule tied to that definition, a change-of-scope clause, and an exit gate.
- The change-of-scope clause is where most outcome contracts fail — without it, every scope conversation becomes a renegotiation of the whole price.
- "Testable" means a third party could check it without asking the vendor to explain themselves. If it needs a conversation to confirm, it is not a definition of done.
- An exit gate that lets you leave with what you have paid for, cleanly, is what makes the other three clauses credible.
Clause one: a definition of done you didn't have to write yourself
Most disputes on outcome-priced work are not about price. They are about whether the outcome was actually delivered. A definition of done that says "a working checkout flow" is not a definition of done — it is a discussion waiting to happen. A workable one specifies the test cases, the performance bar, and who runs the check. If your vendor is proposing the definition of done, read it as carefully as the price, because it is doing more work than the price is.
Clause two: milestones tied to that definition, not to time
A milestone schedule that pays out on dates is a day-rate contract wearing an outcome-contract's clothes. A real outcome milestone pays out when the definition-of-done tests pass, whenever that happens. This sounds like a small distinction. It changes who carries the risk of an underestimate — and it is the single easiest thing to check in a proposal before you sign it.
Clause three: the change-of-scope clause, where most contracts actually break
Scope changes on every real project. An outcome contract without a clear, pre-agreed mechanism for handling that turns every change request into a full renegotiation, because the original price was calculated against a scope that no longer exists. The clause needs to say, in advance: how a change is proposed, how its impact on price and timeline is assessed, and who has to agree before it takes effect. Get this wrong and you end up back on a de facto day rate, just with extra paperwork — because every conversation about a new requirement becomes a conversation about the whole engagement.
Clause four: an exit gate that costs you nothing to use
The clause that makes the other three credible is the one nobody wants to talk about at signing: what happens if you want to leave. A real exit gate lets you stop after any completed milestone, take what you have paid for in a usable state, and walk — without penalty clauses designed to make leaving more expensive than staying. If a vendor is confident in their delivery, an easy exit gate costs them nothing. If they resist including one, that tells you something about how confident they actually are.
What this looks like in practice
Every outcome contract we write includes all four clauses as named, separate sections — not folded into general terms where they are easy to skim past. If a vendor's proposal is missing the change-of-scope clause specifically, ask for it before you ask about price. It is the clause that determines whether the price you are being quoted is the price you will actually pay.
Outcome-priced from day one
See what this would cost at Effektiv pace.
Pick a project that finished or stalled. Show us a quote you've received or an invoice you've paid. We'll price the same scope on outcomes, not hours.