Outcome pricing forces agent scope

LangChain published a conversation with Sierra's head of product, and the part worth stealing has nothing to do with prompts. Sierra — described as serving most of the Fortune 20 with customer-facing agents, a coverage claim I can't independently verify — prices some of its agents by outcome: you pay when the agent achieves the valuable thing. And the discussion draws a sharp line inside that model: a high-value outcome like a completed sale is priced as an outcome; a commodity action like a balance lookup is not pretending to be one.

Everyone reads outcome pricing as a commercial innovation. I read it as an architecture review with an invoice attached — because look at what a vendor must be able to do before it dares bill a single outcome.

It must define success precisely enough that a customer will pay against the definition — "resolved the ticket" with an explicit standard for resolved, not "had a nice conversation about it". It must attribute the outcome to the agent — did the agent close the sale, or did the customer arrive already decided? It must handle exceptions — the return, the reopened ticket, the chargeback — because charged outcomes that un-happen become refund disputes. And it must attach evidence to every line item, because enterprise finance does not pay invoices that say "trust us, 4,100 resolutions."

Now notice: every one of those four is a thing your agent program should have anyway, and almost certainly doesn't. Pricing just makes them non-optional. That is why the discipline transfers even where no invoice will ever exist. An internal agent whose success cannot be defined separately from its activity — conversations held, messages sent, tasks touched — is unbillable, and unbillable is a synonym for unimprovable: if you cannot say what a success is, you cannot count them, compare versions, or decide whether the thing earns its costs.

The scope pressure is the healthy side effect. Ambiguous, sprawling agent mandates — "help customers with whatever they need" — are precisely the ones where success is undefinable, so outcome pricing quietly forbids them. The vendor is pushed toward narrow, measurable, high-value work, which is — not coincidentally — where agents actually succeed today. The same podcast's title thesis, that the best agents are simpler than you think, is the same force viewed from the build side.

At work, the diagnostic I now run on any agent proposal, internal or vendored, is what I've started calling the invoice test: write the imaginary invoice. One line per outcome type, a unit price, and the evidence you would attach to defend each line to a hostile CFO. A product owner who cannot draft that invoice — who can only list activity metrics, conversation volumes, or "engagement" — does not yet have an agent product. They have a chatbot with ambitions. On one engagement this year, the exercise took ninety minutes and deleted two-thirds of the proposed agent's mandate; what survived was the narrow slice with definable outcomes, and it shipped, and it worked, and everyone involved would call that a success — measurably, for once.

Steal the Sierra split too: sort your agent's actions into outcomes (rare, valuable, chargeable-in-principle) and commodities (frequent, cheap, table stakes). Fund and evaluate the two differently. The commodity tier is judged on cost and latency; the outcome tier on definition, attribution, exceptions, and evidence. Mixing them is how dashboards end up celebrating ten thousand balance lookups while the sales the agent was hired for go unmeasured.

If you couldn't bill it, you can't improve it — write the invoice first, even when nobody will ever pay it.