Skip to main content

Outcome-based pricing acceptance criteria, refunds and exceptions

Outcome-based pricing acceptance criteria: define finished and who confirms it, when a result reverses, what never bills, and who owns every exception case.

Michael Houck7 min read

Outcome-based pricing acceptance criteria come down to 4 clauses you write before the first invoice: what counts as finished and who confirms it, when a finished job reverses and gets credited back, which attempts never bill, and who owns the cases that fit none of those rules. Intercom's published terms for Fin, its AI support agent, answer the first 3 directly and show what clause 4 looks like in practice, which makes them the clearest worked example I've found of what a billable finished job has to include.

Picking the unit is the easy part

Choosing to charge for the finished job is a decision you make once. In Software vs. Services on November 8, 2026, I wrote that Intercom is already selling the work, charging for each resolved conversation instead of each seat, and that software which owns the outcome gets to charge against the payroll budget. I made the same case earlier in Outcome-Based Selling on June 16, 2026: charging per result moves the risk to the vendor, and buyers say yes faster.

The work starts after that yes. Intercom's pricing team wrote on May 20, 2026 that Fin's pricing metric is the outcome, and that a small change in how you define the metric can completely change how customers experience value. Your delivery lead is the person who lives with that definition every day, so this page is written to be forwarded to them.

Clause 1: what counts as finished, and who confirms it

Intercom's help article on Fin outcomes, checked November 21, 2026, counts a resolution in 2 ways: the customer confirms the answer helped, or the customer leaves after Fin's last answer without asking for more help. Intercom calls the second one an assumed resolution, and it bills.

The same Intercom help article, checked November 21, 2026, draws the edge of silence carefully. If Fin asks a clarifying question and the customer never replies, nothing bills, because Fin's last message was a question instead of an answer. Responding to a greeting doesn't count either.

Your contract needs the same 3 lines:

  • the finished state, written so both sides can check it;
  • who confirms it, and how long they have to do it;
  • what silence means, both after you deliver and after you ask the customer for something.

Clause 2: when a finished job comes back

A result that holds for a day and then fails isn't the result the customer paid for. Intercom's help article, checked November 21, 2026, says that if a customer returns to a resolved conversation asking for more help, that resolution is deducted and not charged, even across billing periods.

That one sentence is Intercom's answer to the refund question: a reopened resolution is deducted from the bill. Your contract has to say which remedy you owe when a finished job reverses, a credit on the bill or cash back, and it has to say:

  • what counts as the same job coming back, as opposed to a new job;
  • how long the reopen window lasts;
  • whether a credit can land on a later invoice than the original charge.

Leave any of those out and every reopened job turns into a negotiation.

Clause 3: what never bills

Intercom's help article, checked November 21, 2026, says Fin never charges for an outcome that didn't happen: if the customer asks for a human, or a configured Procedure fails to finish for any reason, there's no charge. Escalations triggered by Fin's default behavior or by workspace-level rules don't bill either. The same article carves out one exception to the human-request rule: if the customer asks for a person while the collect information setting is on, then goes inactive without giving that information, the conversation is still marked resolved and billed.

The same Intercom article draws one line that's easy to miss. A handoff the customer configured on purpose, where a Procedure is set up to end by passing the conversation to a teammate or a workflow, does bill, because the customer defined that handoff as the finished result. A failed attempt and a designed handoff can look identical in a log. The contract is where you tell them apart.

Clause 4: who owns the exceptions

Some cases fit none of the first 3 clauses. Intercom's help article, checked November 21, 2026, spends a full FAQ on one of them: a teammate joining a conversation Fin already answered. If the customer got an answer and didn't ask for more help, it still counts as resolved and bills; if Fin said it had no answer and a teammate stepped in, it doesn't.

Intercom's help article shows what these cases look like; it doesn't publish who rules on a disputed charge. That part is my recommendation: write the exception owner into the contract by name or role, with how fast they rule and where the customer sees the ruling. The Sell the work skill ends on this step, owning the exceptions, after you've picked the job, defined one finished unit and priced it. Run it before you write these clauses so the unit you're defining is one you can afford to deliver.

Deciding who absorbs an ambiguous case is the hard call in this contract. My view is that the seller should expect to absorb most of them, because the seller chose to carry the risk when it priced per result. In The 5 Levels of Work in October 2025, I wrote that hiring people who solve problems on their own doesn't excuse you from knowing what's going on in your business. The exception log is how you know.

A completion and reversal sheet to send your delivery lead

Copy this into the contract appendix and the delivery runbook, and keep the 2 in sync:

  1. The finished unit, in one sentence a customer could check without asking you.
  2. Who confirms it, how, and the deadline for confirming.
  3. What silence means after delivery, and what silence means after you ask a question.
  4. The remedy for a reversed job (a credit on the bill or cash back), the reopen window, what counts as the same job, and whether credits cross billing periods.
  5. Attempts that never bill: failures, customer requests for a person, your own escalation rules, plus any stated exception (such as a customer who asks for a person and then never answers your follow-up).
  6. Handoffs that do bill, because the customer designed them as the finished result.
  7. The exception owner, the response time for a disputed charge, and where the ruling is recorded.
  8. The share of jobs that hit item 4 or item 7 last month, reviewed with the delivery lead.

Item 8 is an early warning, not a margin check. When the share of reopened or disputed jobs rises, read those cases and find the cause: the acceptance wording, the delivery itself or the billing. Then fix that rule or process, and recheck what you keep from each finished job against what it costs to deliver, redo and argue about. In 5 AI-Native Metrics to Track on August 4, 2026, I described intervention rate as the percentage of agent outputs that need a human correction. Track it next to item 8, because a disputed charge and a corrected output are different problems.

Where this doesn't apply

Outcome pricing needs a result both sides can check. If the work mostly rests on human judgment the customer can't verify, such as strategy or creative direction, a milestone fee or a retainer is easier to defend than a per-result price with a long exception list.

It also costs margin before it earns it. Intercom CEO Eoghan McCabe said on The Cognitive Revolution in October 2025 that he was told Fin would cost $1.21 per resolution at launch, priced it at $0.99 anyway and took a hit on each one before getting to software-level gross margins. Credits for reversed jobs come out of the same margin, so price the reopen window in before you sell it.

This page is about contract design, not legal advice. Have counsel read the refund and credit language before it goes in front of a customer.

The buyer on the other side may be an agent as well. In Agents Are Your Customers Now on October 25, 2026, I wrote that the done-for-you option on a founder friend's pricing page was the one I'd actually pay for. That's the kind of offer these clauses protect.

GTMnow's February 2026 interview with Intercom president Archana Agrawal covers how Intercom restructured its product, pricing and go-to-market around Fin and what it takes to price software on outcomes, according to the video's YouTube description:

Frequently asked questions

What counts as an outcome in outcome-based pricing?

Whatever the contract says counts, so write it down before the first invoice. Name the finished state, who confirms it, and what happens when the customer goes quiet instead of confirming.

How do refunds work with outcome-based pricing?

The contract has to say. Intercom deducts a resolution from the bill when the customer returns to the same resolved conversation asking for more help, even across billing periods. Write down whether you credit or refund a reversed job, and how long the reopen window lasts.

Do you charge for failed attempts under outcome-based pricing?

You shouldn't. Separate a failed attempt, which never bills, from a handoff the customer configured on purpose, which can bill, and list both in the contract so neither side has to argue about it later.

Write clause 4 first, because it's the one you'll need in month 2. To pick the finished job and price it before you write any of them, get the free Sell the work skill, and for one essay every Sunday on building leverage in your life and work, get the Sunday issue.

Get the next one.

One essay every Sunday on how to build leverage in your life and work.