What is an outcome agreement?
An outcome agreement is a business outcome that buyer and seller have both signed: a milestone or result that the two sides co-authored, and that the customer then countersigned — identity-assured and recorded immutably — so that downstream systems can rely on it as a fact rather than a claim. It is the atomic unit of a system of evidence: not a task someone ticked, not a note a rep wrote, but a statement of what is true that both parties put their name to.
Three properties make an agreement an outcome agreement. It is bilateral — the vendor can never confirm it alone; the customer's act completes it. It is identity-assured — the confirmation records how the confirmer was authenticated. And it is load-bearing — the health signal reads it, the renewal case is built on it, and it survives the signature into the customer-success phase of the account.
The reason
Why it exists
B2B revenue runs on claims: the rep asserts the deal is on track, the CS platform infers the account is healthy, the QBR deck says the value arrived.
Each of those is one side talking to itself. When the renewal call comes, nobody can point to the moment the customer agreed the promised value was delivered — because that moment was never captured as a record. The outcome agreement exists to capture exactly that moment, in a form software can trust.
It also changes what an AI layer can safely do. An assistant reasoning over one-sided claims amplifies the claims; an assistant reasoning over countersigned outcomes is grounded in what both parties accepted as true. That grounding is what lets a drafted renewal case or a risk verdict cite evidence rather than vibes.
Often confused with
How it differs from the adjacent instruments
A mutual action plan task
A MAP tick is a coordination signal: anyone on the plan can make it, and usually nothing downstream relies on it. An outcome agreement is countersigned, identity-assured, and consumed downstream.
An e-signature
An e-signature executes a contract at the deal's edges. An outcome agreement confirms a value outcome during the relationship — quarter after quarter.
A success plan
A success plan is the vendor's internal document about the customer. An outcome agreement is a shared record with the customer.
Questions
Frequently asked
Who can confirm an outcome agreement?
Only the customer's side. The vendor marks its own work complete, but a milestone is confirmed only by the customer, through the customer's own secure link. The one case where a vendor's click completes a confirmation is on the value statement, when the vendor accepts wording the customer proposed themselves.
Can an outcome agreement be edited after it's confirmed?
Not quietly. The history of changes is append-only, and the database itself refuses an edit to a past entry. A customer can withdraw a confirmation, and that withdrawal is added as a new, visible entry.
How is the customer's identity assured?
Every confirmation records how it was authenticated — secure-link possession by default, with an emailed one-time code available as a step-up the vendor's team can require.
Enforced, not just promised. The guarantees behind these terms (append-only records, the records-nothing buyer lane, the buyer-side firewall) are enforced in our system and checked by automated tests. Read the live trust protocol
Try it from your customer's side
A real room with the attestation layer, no credit card. Your own accounts follow a 30-minute scope meeting.