AI AgentsResearch & InsightsAI for Business

AI Agents Put $234B of Enterprise Software at Risk

Gartner says AI agents could put up to $234 billion of application software spending at risk by 2030. Here is how pricing is moving from seats to outcomes and a five-question checklist for your next renewal.

Toolbit AI - Team
4 min read
AI Agents Put $234B of Enterprise Software at Risk

On July 1, 2026, Gartner said AI agents could put up to "$234 billion in application software spending at risk by 2030," as reported by CIO. That figure is exposure, not a forecast of lost revenue, so the practical move is to check each seat-based contract before it renews.

  • What changed: Gartner put a ceiling on how much software spend agents could shift away from per-person licenses.
  • Who's affected: founders, PMs and buyers who renew seat-based SaaS contracts.
  • What to do: run the five-question checklist below before your next renewal.

Up to $234B is exposed by 2030, not lost

Gartner calls this agentic arbitrage: agents programmed to complete tasks across multiple systems bypass user interfaces, per Channel Dive. The $234 billion is an upper bound for 2030, about 20% of enterprise SaaS spend, according to Channel Dive's summary of Gartner. Gartner itself frames the shift calmly: "This is less an apocalypse and more of a metamorphosis," per CIO.

The core idea is simple. George Brocklehurst, a Gartner managing VP, put it this way via CIO: "You are no longer buying software primarily for people; you are increasingly buying it for agents." When an agent does the clicking, a price set per human login looks harder to justify.

Treat vendor claims with care. Channel Dive reports that Gartner estimates about 70% of agents on the market are "agent-washing," meaning existing features relabelled as agents.

Pricing is moving from seats to outcomes

Vendors are starting to charge for work done instead of people logged in. The old and new models count different things:

Per-seat pricingAgent pricing
Unit chargedHuman loginsConversations, outcomes or usage
AssumptionOne person uses one licenseAn agent works without a single user
What you forecastHeadcountVolume of tasks

Two published prices show the shift. Agentforce pricing lists $2 per conversation, or Flex Credits at $500 per 100,000. Each Agentforce action costs 20 credits, about $0.10. Fin pricing is $0.99 per outcome, charged once per conversation. An outcome means the customer confirms it is resolved, asks for no further help, or Fin completes a workflow.

Agentforce charges $2 per conversation while Fin charges $0.99 per outcome, so the two prices count different units and cannot be compared directly

These units differ, so $2 versus $0.99 is not like for like. Agentforce bills each conversation; Fin bills each outcome. Seat models are also losing share: a Pilot study cited by Pickaxe found seat-based pricing fell from 21% to 15% of SaaS companies in 12 months. Hybrid pricing rose from 27% to 41% in the same study. Pickaxe does not state the study's sample size or dates.

Renew, shrink or renegotiate: a five-question checklist

Before any seat-based contract renews, answer these five questions:

  1. Who logs in? Count active human users against paid seats.
  2. What do agents do inside it? List tasks an agent now completes without a person.
  3. Does the vendor offer usage or outcome pricing? Ask for it in writing, with the unit defined.
  4. What exactly counts as a billable unit? Get the definition, as Intercom publishes for Fin outcomes.
  5. Who owns the agent's permissions? No named owner means no renewal yet.
Keep seats when people still work in the tool daily, shrink when seats exceed active users, renegotiate when an agent does most of the work, and pause when no one owns the agent's permissions

In short, keep seats when people still work in the tool daily, and shrink when seats outnumber active users. Renegotiate when an agent does most of the work, and pause until someone owns the agent's permissions. Gartner's advice, via CIO, fits here: "Scrutinize the contract as much as you scrutinize the technology."

Agents need a permission owner

An agent that acts across systems needs a person accountable for what it may touch. Before you scale one, write down which systems it can read and change. Then note which actions need human approval and where its actions are logged.

Building it yourself? Our guide to governed multi-agent workflows shows approval gates and tool allowlists in practice. The same questions apply to agents inside a workspace and to voice support agents.

Still unconfirmed

  • Gartner's full release: the July 1, 2026 page blocked our fetches, so quotes here come via CIO and Channel Dive.
  • The 40% figure: Enterprise DNA reports agents in a projected 40% of enterprise apps by end of 2026. That is a Gartner forecast from August 2025, not a measurement, and we could not read the original.
  • Other vendors' rates: Sierra publishes no prices, so we left it out.

For picking the model behind an agent, see our model comparison of ChatGPT, Claude and Gemini.

Share this article

Related articles

Continue exploring similar guides and insights