The question in the topic title is the wrong shape. An agent can already book a meeting, file a ticket, and draft a refund. That is not the same as replacing Salesforce, SAP, or the ledger those clicks used to touch.
The useful split in 2026 is four jobs: record the fact, click through the interface, act across systems, and stand behind the action when it is wrong. Mix those jobs and you get a slide that says "AI agents will replace the apps we use today." Keep them separate and you can ask who still gets paid — and who still gets sued.
This post is a map of those jobs. It is not a eulogy for SaaS, and it is not a product roundup.
What "replace the app" actually means
Three different systems get lumped together.
1. The system of record. The row in the CRM, the invoice in the ledger, the ticket in the queue. Someone — or something — still has to write a durable fact somewhere a later audit can find. Agents do not abolish that. They change who types.
2. The click-path. The seat. The dashboard, the five-tab workflow, the training course on "how we use the tool." This is the part Gartner is actually pricing. If an agent can complete the work without a person opening the UI, the vendor that sold seats for that UI is the one exposed.
3. Liability. When the agent refunds the wrong customer or emails the wrong contract, who answers? A demo that "just works" is not an operating model. A named reviewer with a budget on irreversible actions is.
If you mix those three, you get hype. If you keep them separate, you can ask a better question: did this system change what got stored, what got clicked, or only who got blamed?
The money is on the seat, not the database
Gartner's 1 July 2026 number is the honest one, not a vibe. Up to $234 billion of enterprise application spending is exposed to what it calls agentic arbitrage between now and 2030 — about 20% of enterprise application SaaS spend by the end of the decade. Agentic arbitrage is not "the ERP vanished." It is an agent finishing a job across CRM, billing, and ticketing so a person never opens those three screens.
George Brocklehurst, managing vice president at Gartner, put the pricing argument in one sentence: you are no longer buying software primarily for people; you are increasingly buying it for agents. For two decades software was judged on interface — usability, workflow, training. When the primary user is an agent, that depreciates. Outcomes bypass the UX. The link between user growth and revenue growth breaks.
That is a seat problem. It is not "apps are over." Gartner itself calls the shift a redefinition of "SaaSpocalypse": disaggregation, a metamorphosis, not a funeral. Incumbents who keep selling dashboards and seat packs are the ones in the blast radius. Incumbents who sell the record plus the agent layer are trying to collect on both sides.
Adoption is loud. Deployment is not.
Agentic AI sat at the Peak of Inflated Expectations on Gartner's 2026 Hype Cycle. The 2026 CIO and Technology Executive Survey is the split to keep: 17% of organizations have deployed AI agents; more than 60% expect to within two years — the steepest intent curve in that survey. Most of what is live is narrowly scoped (coding, support, ops). Fully autonomous agents are not ready for the majority of enterprise use cases. Intent is not a production system.
McKinsey's State of AI 2026 survey is the buy-vs-build tell. 32% of respondents said their organization decided against buying one or more software products or features because they could be built internally with agentic coding tools. That is not "the CRM died." That is a feature that used to be a purchase order turning into a repo. Large firms (over $1 billion revenue) report 40% scaling AI agents, up from 27% a year earlier. Smaller firms are flat at 22%. The agent layer is concentrating where there is already a platform team.
A year earlier, in a Gartner survey of IT application leaders, only 12% strongly agreed that agents would replace applications inside two to four years. Believe the strongly-agreed number, not the keynote.
Incumbents are not waiting to be replaced. They are buying the agent.
Salesforce is the worked example, not the victim. Agentforce reached $1.2 billion ARR in Q1 FY27 (+205% year on year). In June 2026 it agreed to buy Fin (the Intercom rebrand) for about $3.6 billion — a support agent Salesforce could not ship fast enough on its own. By Q2 it was reporting Agentforce ARR above $1.5 billion. That is an incumbent attaching an agent layer to a system of record it already owns. It is the opposite of "apps went away."
Do not treat vendor resolution rates as audited truth. Treat the deal as the signal: the company that sells the CRM is paying billions so the click-path can live somewhere else, on top of the same record.
Four jobs, keep them separate
A short test for any "agents will replace the apps we use today" pitch:
1. Record. Does a durable fact still have to land in a system someone can audit? Yes. An agent that never writes a record is a chat window. 2. Click. Can the job be finished without a human opening the UI? For a growing slice of support, scheduling, and coding chores: yes. That is the $234 billion. That is the seat. 3. Act. Can the loop call more than one system without a person tabbing between them? This is the actual agent. It is also where most pilots stay narrow. 4. Stand behind it. When the refund is wrong, who is on the ticket? A 17% deployment rate with 60% intent is a governance backlog, not a replacement wave.
The software lesson is the same as a review budget on irreversible publishes. Fully automatic is a demo. An unlabeled loop that can email a customer is still a loop.
What to do with this if you buy or build software
If you buy software: stop counting only seats. Ask which jobs still need a named person in the UI, which jobs an agent can finish against the API, and who is paged when the agent is wrong. Adding "AI features" to a dashboard you already hated is how you spend more for the same click-path.
If you sell software: the interface is no longer the product. The record, the permissions, and the audit trail are. If your revenue assumes a human in every workflow, Gartner's 20% is aimed at you.
If you build agents: log the action (what changed, in which system, under whose budget), not the vibe. Put a review budget on anything that can move money, mail, or access. Do not call a click-path killer "a replacement for the app" when the app is still the database.
What not to do
Do not say "agents replaced apps" because 32% of survey respondents skipped a software purchase. Do not say "SaaS is dead." Do not treat a 60% intent figure as a 60% deployment figure. Do not quote a vendor's ticket-resolution percentage as a census.
The apps we use today were never one job. Agents took the click. The record got more expensive, because it now has to prove it was not just a loop.
No comments:
Post a Comment