Your sales team just closed your first outcome-based deal. Everyone is celebrating. But someone on the finance or product team is quietly panicking — the contract terms require measurement, verification, and settlement capabilities the company doesn't have. The next 30 days will determine whether this deal is a win or the beginning of a disaster.
Week 1 — Lock the specification
Translate the signed contract into an operating specification. What outcome is being measured? What evidence qualifies? What's the baseline? What exclusions apply? What's the pricing formula? What's the dispute resolution path?
The contract likely has gaps in each of these — gaps that need to be filled before measurement begins. Fill them now, in writing, with the customer's agreement. Gaps that feel harmless in Week 1 become disputes in Week 12.
Week 2 — Establish baselines
You cannot measure improvement without a baseline. Week 2 is about establishing the baseline from the source systems agreed in the contract. This is also when you discover whether the data you need actually exists and is accessible.
It frequently doesn't. The customer's CRM doesn't have the field you need. The measurement event hasn't been tracked historically. The system doesn't have API access. You need to know this in Week 2, not Week 6.
Week 3 — Build the measurement pipeline
Connect to the customer's systems. Configure the data ingestion. Normalize the incoming events. Run a test measurement against a known time period to validate the pipeline. Document what you're measuring and how.
The documentation matters. When a dispute arises — and it will — the documented pipeline is the evidence that the measurement was done correctly. Without it, every dispute is a credibility contest.
Week 4 — Ship verification and settlement
Apply the count/no-count rules from the specification. Run a full cycle on test data. Produce a sample settlement statement. Review with the customer's finance team.
Make sure both sides see the same numbers and agree on the methodology. Only then does the deal go live. This conversation — "here's how we'll count outcomes, here's how we'll invoice" — is one of the most valuable conversations in the early customer relationship. Do it before the first invoice, not after.
What breaks most often
- The baseline takes longer than expected because the data isn't where you thought it was.
- The measurement methodology has ambiguities that require customer conversations you didn't plan for.
- The customer's IT team is slow to grant data access. Start this conversation in Week 1, not Week 3.
- The pricing formula in the contract has edge cases nobody thought about. Run a test cycle before go-live to find them.
Why 30 days is possible
Most companies think standing up outcome infrastructure takes months. Using Acretix's Launch Studio compresses the timeline because the patterns are reusable. The first mapping to a customer system takes 15–20 hours. The fifth mapping takes 3–5 hours. The infrastructure you build for the first deal becomes the infrastructure that makes every subsequent deal faster.
Your first deal is your pilot
Ship it well and everything downstream is easier. Ship it badly and you lose the customer and damage the reputation of outcome pricing internally. The 30 days of careful work that make the first deal clean are worth more than the revenue from the deal itself.