Future of SaaS
The agent pricing reckoning
Per-seat licensing assumed software helps a person work. Agents do the work. Four billing models are now fighting to replace the seat, and three of them will lose.
- Author 01
WebTechOS Editorial
- Published 02
2026-08-12
- Read 03
8 min
Software has been sold by the seat for twenty years because the seat was a reasonable proxy for value. One person, one licence, one set of work that person could now do faster. The proxy held as long as the software needed a human driving it.
Agents break the proxy. When the software does the work rather than accelerating a person doing it, the number of humans with logins stops correlating with anything. A support team that resolves forty percent of conversations automatically does not need forty percent fewer seats — it needs the same seats and a different invoice.
The four contenders
Per-resolution pricing, which Intercom has pushed hardest, charges for a successful outcome. It aligns vendor and customer incentives more honestly than anything else on the table, and it makes budgeting genuinely difficult. A product incident that triples conversation volume triples the bill in the same month the team is least able to absorb it.
Per-execution pricing, n8n's model, charges once per workflow run regardless of depth. It is the customer-friendly choice and the reason n8n has taken so much share from per-task competitors, but it caps vendor revenue exactly where value is highest — the complex, deep workflows customers would pay far more for.
Credit systems, used by Clay, Relevance AI, YourGPT and most no-code agent builders, are the most common and the least loved. They price genuine underlying variability, which is defensible. They also make it nearly impossible for a buyer to forecast a bill before committing, which is why every review of every credit-priced tool contains the same complaint.
Consumption pricing on tokens or compute is the most honest and the least commercial. It works for infrastructure, where buyers are engineers who can model it. It fails for business software, where the buyer wants a number to put in a budget.
The winning model will not be the fairest. It will be the one a finance team can forecast.
What buyers should do now
Model your expected volume against each shape before comparing headline prices. The same workflow can differ tenfold between a per-task and a per-execution vendor, and the direction of that difference depends entirely on how many steps your workflows have.
Negotiate caps rather than rates. On outcome and consumption pricing, a ceiling that converts overage into a lower marginal rate is worth more than a discount on the base price, because it removes the tail risk that makes these models frightening.
Instrument your own usage independently of the vendor's dashboard. Every disputed bill in this category comes down to a definition — what counts as a resolution, an operation, a credit — and the customer who measured it themselves has a materially better conversation.
WebTechOS accepts no payment for coverage, placement or scores. Where a piece references pricing, it reflects published list rates at the date shown.
Keep reading
All insights →Why most agent projects fail in month three
The demo works. The pilot works. Then something changes upstream, nobody notices for two weeks, and trust never comes back. A field guide to the failure that kills more agent projects than capability ever has.
SaaS InsiderThe consolidation nobody predicted
Unbundling was supposed to be the permanent condition of SaaS. Instead, buyers spent two years cutting vendor counts, and the tools that bundled well are winning categories they were not supposed to.
Customer Support TechCustomer support after deflection stopped being the metric
Containment rates became contractual, and then immediately stopped being interesting. What replaced them says more about where support tooling is headed than any product roadmap.