Outcome-Based Pricing: The ACV Minimum Threshold
- Cormac Repman

- 1 day ago
- 3 min read
I've been pricing consultants and service platforms for years, but I only recently learned when outcome-based pricing actually breaks down. It's simpler than I thought: if your customer's annual contract value doesn't hit $30k, you can't make the unit economics work on a performance model.
Here's what I mean. I work with a platform that charges based on qualified meetings booked. We have customers paying percentage of revenue or flat rates per booking. Sounds aligned, right? Customer wins more business, we win more fees. But I watched two things happen this month that forced me to rethink this entirely.
First, we booked 4 qualified meetings for one customer last month and 1 for another through a traditional competitor. That's a 4x performance gap. The customer was ready to drop the competitor. But when I looked at the economics, it fell apart. The customer generating 4 meetings a month is paying us roughly 15% of gross bookings. At their average deal size, that's hitting $8,600 monthly. Even strong performance wasn't hitting $30k annually.
The second thing was platform load. We have 77 active users now and the system is struggling. Trellis is lagging, kicking users out mid-workflow. Every new customer we add increases infrastructure cost, support overhead, and incident risk. For a customer generating $8k monthly revenue, that math gets thin fast. By the time we factor in onboarding, customer success, and the technical debt of one more user on the system, we're either breaking even or losing money.
This forced me to think differently about customer economics. The customers who actually make outcome-based pricing work are the ones doing $30k to $50k plus annually with us. At that scale, our per-customer infrastructure cost is noise. Their success metrics are measurable enough that the performance incentive actually drives behavior. We can afford dedicated support. The platform handles their load without growing team costs.
Below that threshold, I've realized traditional licensing is the better model for everyone. I'm not saying that cynically. I'm saying it mathematically. If a customer is generating $8k to $15k annually with us, they're better off on a flat license fee. They know their costs upfront. We know what we're making. We both have room to invest in the relationship. There's no weird incentive misalignment where we're tempted to optimize for the metrics that look good on a board rather than the outcomes the customer actually needs.
The hard part is saying no to revenue that looks good in the short term. When a new prospect comes in generating $10k to $12k of monthly volume, the outcome-based pitch looks appealing. But I've learned that's where things break. You end up with a customer on a model that doesn't have positive unit economics. You're perpetually watching the clock, hoping their volume increases, rather than building a sustainable business with them.
The lesson applies beyond SaaS. Anyone selling on performance, commission, or usage-based models should audit their customer base. Ask yourself: which customers are actually above the threshold where this model makes sense? For the ones below it, you might find that a simple annual fee actually builds better relationships and eliminates the financial drag.
I'm not saying outcome-based pricing is wrong. I'm saying it has a floor. Below $30k, it's a trap for both sides. Once I started moving smaller customers to traditional pricing, everything got simpler: clearer unit economics, better retention, fewer late-night alerts about system load. The outcome-based deals became a premium offering for customers where we could actually invest properly.
That's the real alignment. Not a model that technically works, but a model where everyone wins without having to gamble.

Comments