How Outcome Pricing Changes the Scope of an Engagement

Outcome pricing looks like a sales decision until you read what it does to the scope. The moment you get paid on a result, every failure, every retry and every argument about what counts as “done” comes out of your margin.

When is it too early?

The first engagement of a new kind shouldn’t be priced on the outcome, because neither side can predict the result. Use a flat fee for a short sprint. Once the pattern is proven and your evals make the outcome boring, price the outcome. Outcome pricing on your first engagement is gambling. On your fifth it’s arithmetic.

Keep that flat fee small, but never free. A customer with no money at stake gives you no counterpart, no urgency and no proof that anyone will pay. Founders resist this because agents make a working pilot cheap to build, but your cost was never the scarce part. The buyer’s attention, their data access and the hours of the person who checks the output are what a pilot spends, and a free pilot spends them with nobody accountable for the result. Here’s a simple structure, with made-up numbers. You’re aiming at a $48,000 first year. The six-week pilot costs $6,000, credited in full if the contract is signed within 30 days of the review. The buyer risks little, and someone with a budget had to approve it, which is the point.

The definition is the contract

Vendors in customer service define the word “resolved” very differently. Whoever writes the definition decides what counts. So an outcome price forces the exit criterion into the scope: the number, its baseline, the definition, the proof and the owner. It forces honest scoping, because neither side can stay vague and still get an invoice out.

Split the fee, and tie the split to your theory

If the only payment arrives on the number the CFO cares about, you’re financing the customer’s year and carrying risks you can’t control: a pricing change, a product bug, a reorganization on their side. Nobody can run six-week sprints on fees that arrive four quarters later.

I’d split it in three: a fixed fee for the sprint, an outcome fee on the number you can actually move in weeks, measured against a comparison group, and a smaller holdback at a later review if the money moves the way your written theory predicted. Suppose the leading number moves and the lagging one doesn’t. The theory tells you which arrow broke, and that’s the agenda for the next conversation, where a single all-or-nothing fee would have made it a dispute.

1. Fixed feeFor the sprint
2. Outcome feeOn the number you can move in weeks, against a comparison group
3. HoldbackSmaller, at a later review, if the money moves the way your theory predicted

What to put in the scope

• The fixed fee, the outcome fee and the holdback, each tied to a number and a date.
• The definition of the number, in one sentence both sides have read.
• What the customer owes you for the price to hold: access, a sponsor, same-day answers.

Part of what you’re pricing is whether the customer’s team can run the thing after you leave. That belongs in the wider scope, and it’s where I’d spend the next hour.

I wrote more on this in Charge for the Pilot, and Write Down the Day It Ends and How to Define the Outcome a Forward-Deployed Team Is Paid For.