Founders ask Collective 54 this 9 times in our records, and 6 of those were in 2026. The measurement half is where most attempts fail, and it has to be settled before the pricing is offered.
Outcome-based pricing is one of nine revenue sources available to a boutique firm, and it has a specific character: it aligns the firm with the client, and it is usually uncapped. If you produce a result you get paid, and there is a great deal of upside. If you fail you do not, and there is a great deal of downside.
That asymmetry is the whole design problem. Hourly billing caps your upside and protects you. Fixed bids reward you for getting efficient. Outcome pricing does something different: it converts your delivery quality directly into revenue, which is excellent if your delivery is standardized and dangerous if it is not.
So the first honest question is not how to design the pricing. It is whether your delivery model is consistent enough to bet on. A firm whose project-level results vary widely is not ready, and the pricing will expose that faster than anything else you could do.
The single most useful constraint: tie the price to a metric the client already tracks.
The SBI example is instructive. In that market, project success was measured by revenue per sales head. Clients already watched that number, already had a baseline for it, and already believed it mattered. The firm stopped charging fees and asked for a percentage of the gain. Those projects became the home runs.
Notice what made it work. Nobody had to be persuaded that the metric was the right one. Nobody had to build reporting for it. Nobody had to negotiate what counted, because the client's own system had already answered that.
If you have to teach a client a new metric in order to price against it, you have added a second sale to the first one, and you will lose both more often than you win them.
Three questions have to be answered in writing before the engagement starts, and the order they are asked in is the order they will hurt you.
What exactly is the number, and where does it come from? Name the system of record. Name who pulls it. Name the definition, including the edge cases. A metric that lives in a spreadsheet someone maintains by hand is not a measurement basis, it is a future argument.
What is the baseline? Measured over what period, on what basis, agreed by whom. Baselines set retroactively are always contested, because by then both sides know which direction the answer needs to go.
How is attribution handled? This is where most arrangements break. The client will run other initiatives during your engagement. The market will move. A competitor will do something. If the contract does not say how the gain is apportioned, the conversation at settlement will be about everything except your work.
Collective 54 asks a blunt screening question about this: can you prove direct attribution of results in your engagements? If the answer is no, outcome pricing is not the right revenue source for that service, whatever its appeal.
In an Era 3 firm, economics are modeled before commitment rather than discovered after. That means, for this pricing model specifically: select the value metric the price is tied to, choose the model, model expected and acceptable margins, forecast cost to serve across human, AI and tooling components, and test sensitivity to discounting and scope creep.
Two practical points follow.
First, set a floor. Pure contingency means you fund the delivery and the client funds nothing, which puts your working capital behind their outcome. A base fee that covers cost to serve, plus a share of the gain above the baseline, keeps the alignment and removes the existential risk. This is a departure from the purest form of the model, and it is the version most boutique firms should actually run.
Second, run the downside case honestly. If the outcome does not land, what does that engagement cost you, and how many of those can you carry at once. A firm with strong cash flow per partner can absorb a bad one. A firm already tight on working capital cannot, and should not take the bet regardless of how good the upside looks.
Do not convert the book. Pick the engagement type where your delivery is most standardized and your results are most repeatable, and run it there first.
The SBI sequence is worth following as a pattern. That firm started on hourly billing, hit the ceiling, added fixed bids and lost money on the first few because the scoping was poor, improved at scoping and watched profitability rise as costs fell against fixed prices, and only then added performance fees. The mix settled at roughly one-third retainers, one-third fixed bids and one-third performance-based fees.
The ordering is not incidental. Fixed bids teach you to scope accurately, and accurate scoping is the prerequisite for knowing what an outcome engagement will cost you to deliver. Firms that jump from hourly straight to outcome pricing are pricing a cost base they have never had to measure.
Also run at least three revenue sources. A single source concentrates your volatility, and outcome pricing is the most volatile of the nine. It belongs in a mix, not as a replacement.
Pricing decisions are hypotheses, and they have to be tested continuously by linking the quoted price to delivered effort, realized margin and client satisfaction. For outcome pricing, three things are worth watching specifically.
Delivery effort against the assumption. Outcome engagements invite scope expansion, because both sides want the number to move and neither is watching the hours. Detect when delivery effort diverges from what the price assumed, and detect it early.
Exception frequency. Record every deviation from the standard structure so that one-time arrangements do not quietly become the norm. Exceptions are signals rather than failures, but only if someone is counting them.
Whether the metric is still the right one. Client priorities move. A metric that was strategic at signing can be background noise eighteen months later, and a share of a number nobody cares about is worth less than the fixed fee you gave up.
There is a reason this question is getting asked more now, and it is not only that founders read about it.
AI makes marginal cost non-linear and decouples value creation from time spent. That breaks the logic of hourly billing in an obvious way and makes outcome pricing look like the natural destination, because outcome pricing is the model least attached to effort.
That reasoning is right, with one caution. When delivery gets dramatically faster, the gap between what you charge and what it costs you widens, and firms that have not governed their pricing give that gap away without noticing: passed to clients unintentionally, eroded through discounting, absorbed by scope expansion, or hidden inside packaging drift. Outcome pricing protects against some of that by decoupling price from effort. It does not protect against a client who watches your delivery time collapse and renegotiates the share.
Decide in advance what you will say when that conversation happens.
If you cannot prove attribution, do not use this model. There is no version of it that survives an unprovable claim, and attempting it damages an otherwise good relationship at exactly the moment you are asking to be paid.
If your delivery is not standardized, fix that first. Project-level variability that is survivable under fixed fees becomes an existential problem when your revenue depends on the result.
If you are within a year of a sale, be careful. Buyers underwrite demonstrated, durable performance, and revenue from a model with two quarters of history reads as an unproven experiment rather than a margin gain. Uncapped upside also increases the variability of reported earnings, which is not what a buyer is looking for in the period they are examining most closely.
And if the client is a first-time buyer of your firm, outcome pricing is the wrong instrument for that engagement. It requires shared trust in a measurement process, and you have not established any.
Settle measurement before you design the price. Tie it to a metric the client already tracks, name the system of record, define the baseline in advance and write down how attribution will be handled when other things also move the number, because attribution is where these arrangements break. Apply the screening test honestly: if you cannot prove direct attribution, this is the wrong revenue source for that service. Then model the economics before you offer them, forecasting cost to serve and testing sensitivity to discounting and scope creep, and set a floor fee that covers cost to serve rather than running pure contingency, so that alignment does not mean your working capital funds the client outcome. Roll it out narrowly, on the engagement type where your delivery is most standardized, and follow the sequence that works: get accurate at fixed-bid scoping first, because that is how you learn what an outcome engagement actually costs you. Keep at least three revenue sources in the mix, since this is the most volatile of the nine. And once it is live, watch delivery effort against the assumption, count your exceptions, and re-check that the metric still matters to the client.
The metric, and it should be one the client already tracks. When SBI moved to performance fees, project success in that market was measured by revenue per sales head, a number clients already watched, already had a baseline for and already believed mattered. The firm stopped charging fees and took a percentage of the gain, and those projects became the home runs. Nobody had to be persuaded the metric was right, nobody had to build reporting, and nobody had to negotiate what counted. If you must teach a client a new metric to price against it, you have added a second sale to the first.
Attribution. The firm picks an outcome it can influence but not prove, discovers this during the engagement rather than before it, and ends up arguing with an otherwise satisfied client. The client will run other initiatives while you work, the market will move, and a competitor will act. If the contract does not say how the gain is apportioned, the settlement conversation will be about everything except your work. Collective 54 screens for this directly: if you cannot prove direct attribution of results, outcome pricing is the wrong revenue source for that service.
Usually not. Pure contingency means you fund the delivery while the client funds nothing, which puts your working capital behind their outcome. A base fee covering cost to serve, plus a share of the gain above an agreed baseline, keeps the alignment and removes the existential risk. Model the downside honestly too: if the outcome does not land, know what that engagement costs you and how many you can carry at once. A firm with strong cash flow per partner can absorb one. A firm already tight on working capital should not take the bet however good the upside looks.
Narrowly, on the engagement type where your delivery is most standardized. Follow the sequence that worked at SBI: hourly billing first, then fixed bids, where the first few lost money because the scoping was poor, then improved scoping and rising profitability as costs fell against fixed prices, and only then performance fees. The mix settled near one-third retainers, one-third fixed bids and one-third performance fees. Fixed bids teach accurate scoping, and accurate scoping is how you learn what an outcome engagement costs to deliver. Keep at least three revenue sources, because this is the most volatile of the nine.
Sources: Greg Alexander, The Boutique: How to Start, Scale, and Sell a Professional Services Firm (Advantage, 2020), chapter 4 for the nine revenue sources available to a boutique firm, for performance-based contracts aligning firm and client interests while remaining usually uncapped in both directions, for the screening question on whether direct attribution of results can be proven, for the rule of thumb to run at least three revenue sources, and for the SBI evolution from hourly billing through fixed bids, including losing money on the first fixed bids through poor scoping, to performance fees tied to revenue per sales head, a metric clients already tracked, settling at roughly one-third retainers, one-third fixed bids and one-third performance-based fees; chapter 15 for pricing as the quickest route to scale, for matching pricing strategy to business strategy, and for price versioning; chapter 12 for cash flow per partner and cash flow per project, and for the commercial photography firm whose project-level cash volatility revealed a delivery model that was not standardized and therefore not scalable. Greg Alexander, The AI-Native Boutique Firm (Advantage Books, January 2027), specifically The AI Pricing Manager for pricing as a governed system rather than a periodic decision, for the way AI makes marginal cost non-linear and decouples value from time spent, for the finding that efficiency gains leak through unintentional pass-through, discounting, scope expansion and packaging drift when pricing is not governed, for treating pricing decisions as hypotheses tested by linking quoted price to delivered effort, realized margin and client satisfaction, and for exception tracking so that one-time decisions do not become invisible norms; and The AI Service Design Manager for Category 4 Commercial and Pricing Design, including selecting the value metric pricing is tied to, choosing the pricing model, modeling expected and acceptable margins, forecasting cost to serve across human, AI and tooling components, and testing sensitivity to discounting and scope creep.
Collective 54 is the private community for founders and executives of boutique professional services firms between $5M and $50M in revenue. Members work these answers against their own numbers.