Seat-based pricing works well when the number of people using a product is a reasonable guide to its value. It is familiar to buyers, easy to budget and relatively simple to administer.
Agents complicate that relationship. One person can supervise several workflows, while other tasks run without someone opening the application. A customer may get more work done without adding users. The provider may also incur more cost serving those workflows, even though its license revenue stays the same.
I expect this to put pressure on per-seat pricing, particularly for software that can complete a defined task. I also expect seats to remain useful where people spend time collaborating, reviewing work or using the product directly. A single pricing model is unlikely to fit both kinds of use well.
What could the customer pay for?
I find it useful to separate four options. Each measures a different thing, and each puts some risk on the customer or the provider.
Work performed
A vendor can charge per task, action or unit of processing time. That gives buyers a connection between activity and cost, and it works for tasks that can be counted consistently.
The difficulty is deciding what counts. A short document and a complex contract may both be one task, but require very different effort. Charging for every retry can also make the customer pay for the system’s mistakes. The unit needs to be understandable before the work begins and auditable afterward.
An agreed outcome
Outcome pricing charges for a result, such as a resolved support request or a processed invoice. It can make the value easier to understand, provided both parties agree on what completion means.
Intercom’s pricing combines seats for human users with outcome billing for its Fin agent. Its outcome definitions show why the detail matters: a resolution can include an explicit confirmation or an assumption based on the customer not asking for more help. A buyer needs to understand that definition before treating the billable count as a measure of customer satisfaction.
The same issue appears in other domains. Was an invoice processed if a person later had to correct it? Was a sales lead qualified if sales rejected it? Outcome pricing moves some of the discussion from procurement into the design of the service itself.
Consumption
A vendor can charge for resources used, such as tokens, API calls or compute time, usually with a margin. This makes operating cost easier to relate to revenue and can be appropriate for infrastructure or flexible development platforms.
It gives the customer a less direct connection to business value. A long, unsuccessful run may cost more than a short, successful one. Buyers also need enough visibility to understand why usage changed. A consumption model therefore needs estimates, budget controls and a way to investigate unusually expensive work.
A subscription with included use
A flat fee per user, agent or organization remains attractive because it is easy to buy and plan around. It can work well where usage is reasonably bounded or where customers value access as much as individual outputs.
Unlimited use is harder to price when a small number of people can generate a large workload. The vendor has to absorb that variation, limit it through the contract, or charge overages. A base subscription with included usage may be a workable compromise, but the limits should be clear enough that customers can forecast the bill.
Predictability still matters
It is easy to argue that customers should pay for the value they receive. Agreeing on that value is harder, especially before a system has been used for long enough to establish a baseline.
A buyer has an annual budget and needs to understand what happens if adoption succeeds. Doubling useful output may be welcome; an unexpected invoice is still a problem. Usage alerts, spending limits, volume commitments and clear overage terms can make a variable model manageable.
For vendors, the corresponding question is whether revenue covers the cost of delivering the result. That includes failed attempts, human review, support and integrations as well as inference. Lower model costs may improve the margin on a fixed outcome price, but those savings do not automatically reduce the rest of the delivery cost.
A hybrid model can share these risks. A platform fee covers access and a baseline service, while usage or outcome charges grow with the work. I would judge it by how well a customer can explain a bill and predict the next one, rather than by how novel the model sounds.
Counting agents is unlikely to be enough
Agent count has some of the same weaknesses as seat count. One agent running frequently can perform more work than many agents running occasionally. Parallelism, retries and the way a developer divides a workflow can change the number of agents without changing the result the customer receives.
Concurrency may still be a useful capacity limit. It is a less convincing measure of business value. A pricing model should not encourage customers to reorganize identical work purely to avoid an arbitrary billing unit.
This matters for smaller companies, too. A small team may be willing to spend substantially more on software if it completes valuable work they otherwise could not take on. The opportunity is real, but it depends on the work being useful and reliable. A hypothetical saving in headcount is not enough to establish the price.
The product has to support the promise
If a vendor sells completed work, the product needs to show what happened, how completion was assessed and what needs human attention. Buyers need a route for challenging errors and understanding failures. These capabilities are part of what makes an outcome commercially credible.
The business case should also use the customer’s baseline. Time saved is valuable when the organization can use that time, improve service or avoid an expense. It does not always turn into an equivalent cash saving. The same care applies to revenue claims: the software may contribute to a sale without being responsible for the whole result.
I would start with a narrow workflow, agree on the unit and measure the cost and quality of delivering it. Then test whether customers understand the price and whether the provider can sustain it. Seats, consumption and outcomes can coexist. The useful model is the one that reflects how the customer uses the service without making either side carry risks they cannot see.
