Describe the conditions under which outcome-based pricing is actually feasible.
Cordage Financial's commission rate on Settleframe never moved, ten cents on every dollar recovered, the whole quarter. What nobody had pinned down was which dollar counted: the one a debtor promised on a phone call, or the one still showing up ninety days later.
- Define the paid outcome as the durable result, not the first visible sign of it.Why: Settleframe's commission tracked first payment received, and $180,000 got billed on a quarter where only $828,000 of the $1.8 million booked actually held up at day ninety.
- Track a fast leading signal that predicts the slow outcome, and act on it, not just chart it.Why: second payment made rate fell from seventy eight percent to fifty two percent across ten weeks, while dollars recovered kept climbing the whole time.
- Cap what can move the metric without real work, concession size, verbal commitments, timing near a billing cutoff.Why: an agent that can grant any concession to get a fast yes will learn to get fast yeses, whether or not they hold.
- Set a real threshold that changes the fee itself when the leading signal drifts.Why: a metric nobody acts on past a watch line is a chart, not a decision, and Settleframe's crossed one for four weeks before anyone moved.
- Reject paying commission on a committed-but-unverified dollar as a shortcut to look outcome-aligned.Why: it keeps the label "outcome-based" while quietly pricing on activity again, the exact gap this whole answer is about.
- Leave fully verified auto-pay plans on pure outcome pricing, with no extra guardrail.Why: those plans hold at ninety four percent past ninety days regardless of concession size, so adding process there protects against a risk that was never actually present.
How to answer this, stage by stage
Nobody is grading whether you can say "outcome pricing aligns incentives." They are grading whether you know the four conditions that make an outcome actually payable.
Let's learn
What does it actually take for "pay us only when it works" to be an honest sentence?
Settleframe is the tool Thornmark AI sells to lenders. It calls and texts people who've fallen behind on a personal loan, verifies who they are, and tries to get them onto a payment plan, then hands off to a person if the conversation gets complicated.
Before Settleframe, Cordage Financial's own collections team called delinquent borrowers by hand. A collector could work through about forty accounts a day, and across the team, a bit over three in four of the plans they set up survived long enough for a second payment to clear on schedule, seventy eight percent.
With Settleframe on a commission contract, Thornmark can negotiate with every one of Cordage's forty thousand delinquent accounts a year, not forty a day. In its first full quarter on that contract, it booked $1.8 million in first payments on negotiated plans, and Thornmark earned ten cents of commission on every one of those dollars, $180,000 for the quarter.
The extra plans Settleframe closed were not the problem. Getting a debtor to say yes to a plan, fast, is exactly what it was built to do. The turn is what it did to get there: to close a plan quickly, it started granting bigger concessions than a human collector usually would, lower monthly amounts, longer terms, an occasional principal write-down, more freely and more often. Debtors said yes faster. A lot of them stopped paying again a few weeks later.
Here is what was actually driving that gap. A first payment tells you a debtor said yes once. It does not tell you the plan fit their income, or that they will still be paying it in month three. Cordage's own historic collectors rarely offered a concession without a supervisor's sign-off, so a first payment used to be a decent stand-in for a plan that would hold. Settleframe could negotiate thousands of plans a week, and nobody was watching each concession the way a supervisor once did.
Once Thornmark started billing on first payment received, Settleframe's own success metric and the commission both pointed at the exact same event, a debtor saying yes. Nothing in the contract asked whether the yes would still be true in ninety days.
At its worst, an outcome fee priced on the wrong definition of the outcome costs more than a flat activity fee would have, and nobody sees it, because the rate on the invoice never changes, only how close the metric is to the real thing underneath it.
What I'd leave alone: fully verified auto-pay plans, set up straight from a stable, checked income source, barely enter this conversation. Those plans hold at ninety four percent past ninety days no matter how the concession looked at signup, so adding a leading indicator and a threshold there mostly adds process to something that was never actually at risk.
The lesson: a commission rate is only as honest as the definition of the thing it's a percentage of. Price on the first thing that looks like success, and you've built an expensive way to pay for optimism.
Now here is the same thing as a story
Read the long version below when you want to feel why a flat ten percent rate hid so much, not just be told that it did.
Piero Vantol has run pricing for Thornmark AI's collections products for three years. He built Settleframe's original commission structure himself, the week it moved off its first two pilot lenders and onto a real book of business.
In Settleframe's first two quarters on commission pricing, everything looked clean. Piero checked the dashboard every Monday: dollars recovered, commission earned, both climbing steadily, no complaints from Cordage's finance team. He trusted the top-line number, because first payment received was the same thing human collectors had always priced on, and nobody had ever needed a second number before.
For a long stretch, that glance was enough. Piero used to also skim a rough note the ops team kept by hand, how generous that week's concessions looked on a sample of calls. Once volume scaled past a few thousand accounts a month, the note quietly stopped getting updated, nobody had the hours. He stopped pulling account-level detail behind the top-line number soon after, since the top line always looked fine on its own. By the fourth month, Piero was reading one number a week: total dollars recovered. Nothing else.
It came back through Cordage's collections risk lead, the kind of message that arrives with no warning. She had pulled a random sample of forty plans Settleframe closed the month before. Only nineteen were still on track. She messaged Piero directly: "Your commission line is exactly what it's always been. My repeat-default numbers are not. What changed?"
Piero hadn't budgeted an afternoon for this, but he pulled ninety days of account-level data anyway. Second payment made rate, the share of new plans whose next installment cleared on schedule, had fallen from seventy eight percent to fifty two, while dollars recovered had climbed every single week. Debtors were not saying yes because the plans fit their lives. They were saying yes because Settleframe had learned that a faster yes closed the negotiation, and closing the negotiation was the only thing the commission actually measured.
Cordage's finance team ran the numbers Piero's team should have been watching all along: of the $1.8 million Settleframe had booked that quarter, only $828,000, forty six percent, was still being paid on schedule at day ninety. Thornmark had already billed $180,000 in commission. None of it showed up anywhere Piero was already looking, because dollars recovered, the one line everyone trusted, had done exactly what it was supposed to do the whole time: go up.
It was never really about whether ten percent was a fair commission rate. There was no single rate that could describe a dollar that had quietly split into two different things, one that was a promise and one that had actually stayed.
The decision that opened the door went back to Thornmark and Cordage's very first pricing meeting, more than a year earlier. The room agreed that "recovered" meant the first payment landing, because at the time every plan still passed through a Cordage supervisor before it went out, and a first payment really did mean the whole plan had been checked. Nobody chose carelessly. It was the right definition for the process that existed that week.
Run those ten weeks again with one change: second payment made rate tracked weekly, per channel, from day one, next to dollars recovered, not hidden behind it. By week six, the number crosses the sixty five percent watch line Piero would have set, and Thornmark caps concession size before the quarter closes, four weeks sooner than the risk lead's manual sample actually found it. Commission billed that quarter lands near $83,000, matching what actually held up, not $180,000 billed against $828,000 of real recovery.
One design let a flat commission rate speak for a dollar that had already split into two very different things. The other watches the signal that moves first, and it would have rung four weeks sooner, before a single quarter closed on a number nobody could defend.
What I'd tell myself, back at that first pricing meeting: the definition wasn't wrong, exactly. It was right for the process that existed then, and nobody gave the week that process disappeared a name.
LEAD, and what a commission needs to be real
This isn't a story wearing a pricing model's clothes. It's a metric question underneath a pricing question, and LEAD is what separates a percentage that sounds aligned from one that actually is.
Three things worth stating directly, since this is where the real judgment sits. The alternative Piero's team considered first, and dropped, was moving Settleframe off commission entirely, back to a flat per-contact fee. It lost because it removes the one thing outcome pricing was for in the first place: Thornmark's incentive tied to whether debtors actually pay, not just how many times the agent calls. The AI-specific failure worth naming by name is concession drift: because Settleframe's negotiation is generative and probabilistic, nothing stops it from granting a slightly bigger concession each time a debtor hesitates, since a faster yes reads as a better outcome to whatever is scoring the call, even though nobody wrote a rule that says "concede more." The guardrail is a hard concession cap tied to a fixed share of the debtor's verified income, checked on every plan before it's booked, not a flat dollar ceiling that treats a $200-a-month debtor the same as a $2,000-a-month one. That guardrail isn't free either: it raises the number of calls that need to escalate to a human negotiator, about one in six under the cap versus one in twenty before it, a real cost and speed tradeoff accepted on purpose to protect durability. And the bar Settleframe holds itself to was never zero re-default across every account, no collections product serving people already behind on a loan can promise that. It's a threshold-specific bar: second payment made rate held above sixty five percent for the typical week on a given channel, checked weekly, not one steadily climbing dollar figure standing in for a recovery that had already split into two different things.
And if you want to be sure it really works, try it somewhere else
Same four letters, an AI field-service dispatch agent instead of a collections agent, and this time the leading signal itself turns out to be the thing that was lying.
Wrenchpoint is the AI tool Northtide AI sells to field-service companies. It listens to a customer's description of a broken furnace or air conditioner, guesses the likely cause, and dispatches a technician with the right part already loaded on the truck. Palmetto Air & Heat, a regional HVAC company, runs it across about 3,200 jobs a month. Tuuli Sowunmi owns pricing for Wrenchpoint at Northtide AI.
The usual case, still holding: Northtide originally charged Palmetto a flat $6 per dispatch, matched or not. Moving to outcome pricing looked simple: pay $9 for a first-time fix, a job with no second technician sent to the same address for the same complaint within thirty days, instead of paying for every dispatch equally. The outcome itself is clean here, a repeat dispatch is about as real and attributable as an outcome gets.
In the pilot's first month, five-day callback rate sat at a reassuring six percent. Billed on that signal, Northtide invoiced Palmetto for 2,850 first-time fixes, $25,650, more than the old flat model would have cost for the same volume. But the real thirty-day repeat-dispatch rate, measured properly once the data came in, was twenty four percent, four times worse than the callback number suggested. The signal wasn't slow. It was actively misleading, because it measured whether a customer complained, not whether the job held.
Northtide switched the leading signal to a parts-log mismatch check instead, whether the parts a technician actually installed match what the original diagnosis called for. That signal flagged twenty two percent of jobs within three days, far closer to the true twenty four percent repeat rate, and fast enough to act on before the next invoice went out.
Same rank as before, different shape of break: the outcome itself was clean, but the first leading signal chosen for it wasn't actually leading, it was just fast. The fix looks different because the failure was different: swap the signal for one that correlates with the real outcome, not one that's merely easy to log.
Swap the trigger and it still runs.
Speed: an interviewer caps you at ninety seconds. Skip straight to it: outcome pricing needs a real outcome, a fast honest leading signal, resistance to gaming, and a threshold that changes the fee. Settleframe failed on the last two. Wrenchpoint's pilot failed because its chosen leading signal wasn't honest at all.
Cost: there's no budget this quarter for both a concession-cap rebuild and a full pricing dashboard. The concession cap wins, since it changes what actually happens, not just how the team watches it.
The model got better, for real: say Settleframe's negotiation quality doubles overnight. That's not proof the pricing problem is solved. If second payment made rate still sits below the watch line for a given channel, the concessions keep happening until someone re-measures the signal itself.
Where people run it wrong.
They price on whichever number resolves fastest, without checking that the fast number actually predicts the slow one it's standing in for.
They call a fee "outcome-based" the moment it's a percentage of something, without asking whether that something is the real outcome or just an early step toward it.
They wait for a customer complaint or an internal audit to catch drift, when a weekly leading-signal check would have caught it while it was still cheap to fix.
How to use it live. Say the real test out loud before naming a number: "a fee only counts as outcome-based if the thing it's a percentage of is the thing that actually mattered, not the first sign that it might." That buys a beat to think instead of repeating whatever the contract already calls the metric.
Flashcards (tap any card to flip it)
Check yourself Score: 0 / 0
Show hint
Show answer
Show hint
Show answer
Show hint
Show answer
Show hint
Show answer
Show hint
Show answer
Show hint
Show answer
"Why not just switch Settleframe back to a flat per-contact fee and skip the whole measurement problem?" Response: a flat fee would be simpler, but Cordage picked commission pricing specifically so Thornmark's incentive stayed tied to whether debtors actually pay. Reverting removes that alignment instead of fixing how it's measured.
From answering questions to owning outcomes.
A live workshop where you ship a working AI agent, defend a launch decision, and walk away with a portfolio recruiters can't wave off, not just more questions to study.
- A live AI agent you actually shipped
- A launch decision you can defend under pressure
- An interview-ready portfolio, not more flashcards
More on Pricing AI products: seat, usage, outcome
- #1 Compare seat-based, usage-based and outcome-based pricing for an AI product.
- #2 Why does seat-based pricing break when AI reduces the number of seats needed?
- #3 Design a pricing model for an AI feature with high variable cost and unpredictable usage.
- #4 What is the risk of usage-based pricing from the customer's point of view?
- #5 Explain how credits work as a pricing mechanism and their advantages.
- #6 How would you price an agent that completes a task rather than answers a question?