When Your Support Software Gets Arbitraged Away by AI, What’s Left?
Gartner dropped a number recently that should make every enterprise software vendor sweat: $234 billion in software spend is at risk of being “arbitraged away” by AI agents by 2030. They’re calling it agentic arbitrage — the phenomenon where an AI agent can log into your tool, do the work, and move on, making the tool itself unnecessary.
Most vendors are responding with the usual playbook: announce AI features, ship a chatbot, rebrand the product page. That’s not going to save them. Because the question isn’t whether your software has AI. The question is whether your software requires a human to be present in a way that an agent cannot replicate. That’s a very different bar.
Here’s the brutal truth: most enterprise support software fails that test. And the tools that pass it aren’t the ones with the best AI roadmap — they’re the ones anchored to something an AI agent can’t reach into without eyes.
What “Agentic Arbitrage” Actually Means for Software Vendors
Agentic AI software isn’t just automation. It’s a new class of agent that can navigate interfaces, read data, trigger actions, and close loops — without a human touching the keyboard. An agent doesn’t need your CRM’s UI if it can talk to your CRM’s API. It doesn’t need your ITSM portal if it can open tickets, route them, and resolve them through structured calls. The agent is the user now.
Arbitrage, in the Gartner sense, means the software gets bypassed entirely. You’re paying for a platform whose entire value proposition — organizing information, routing workflows, presenting data — is now something an agent handles natively. The software becomes middleware at best, and overhead at worst.
The vendors most exposed are the ones whose value lives in the interface. Dashboards. Unified inboxes. Reporting layers. Ticket queues. When an agent can read and write to the underlying data directly, the interface is dead weight. And once the interface is dead weight, so is the license fee.
The Categories Most at Risk When AI Does the Work Itself
Let’s be specific. The support software categories most vulnerable to agentic AI arbitrage share one trait: their core value is information organization and routing.
CRMs are the clearest case. A well-prompted agent with API access can pull customer history, log interactions, update contact records, and draft follow-up emails without a human ever opening Salesforce. The CRM doesn’t disappear — but the number of seats you need drops to near zero.
ITSM platforms face the same pressure. If an agent can triage an incoming ticket, match it to a known resolution pattern, assign it or close it, and update the status — you’ve replaced the tier-1 support workflow without touching ServiceNow’s UI.
Knowledge base tools are next. Their value was always search and retrieval. That’s table stakes for a language model.
Traditional helpdesk software — the kind built around queues, macros, and canned responses — was already losing to better AI-native alternatives. Agentic AI just accelerates the timeline.
These are tools built for human operators who needed software to organize complexity. When the operator is an AI agent, the organizing layer is redundant.
What Survives the Arbitrage Wave
Not everything collapses. Some software survives because it’s doing something fundamentally different from information management — something that requires presence, not just data access.
The surviving category isn’t about having better AI. It’s about being irreplaceable because of the physical-world constraint. Tools that exist at the boundary between the digital system and the physical environment — tools that require seeing, not just reading — can’t be arbitraged away by an agent operating on structured data.
Think about what an AI agent actually has access to: text, records, logs, APIs. What it doesn’t have is a live camera feed from a customer’s device, showing you the actual broken thing in real time. What it can’t do is guide a field technician’s hands through a repair by seeing what the technician sees.
That’s the wedge. Not AI features. Physical-world irreplaceability.
You Can’t Replace Eyes With a Language Model
The diagnostic problem in hardware support, field service, and technical troubleshooting isn’t data retrieval. It’s visual interpretation. A customer says “the machine is making a noise and there’s something leaking near the back panel.” A language model with access to your ticket history can’t tell you whether that’s a loose fitting or a cracked housing. A technician with eyes on the situation can.
This is where tools like Viewabo sit in a fundamentally different risk category. Remote visual support — the ability to open a live video session with a customer, see their environment through their phone camera, and diagnose in real time — cannot be replicated by an AI agent reading structured data. The unstructured visual signal is the product. And that signal requires a human eye and a live camera, not an API endpoint.
Agentic AI software is extremely good at tasks that can be expressed as: read data → apply logic → write output. It is useless at tasks that require: observe physical environment → interpret ambiguous visual signal → guide physical intervention. Those tasks are immune. Not because AI can’t analyze images — it can — but because getting the image in the first place requires a live human on the other end of a camera, in the physical space where the problem exists.
No agent can get eyes on a customer’s broken piece of equipment without a human holding a phone. That dependency doesn’t go away. It’s not a technical limitation to be engineered around. It’s structural.
The Support Stack That’s Actually Built for What Comes Next
So what does this mean practically for how you build or buy a support stack?
First, be honest about which of your current tools will survive the next three years. If the core value proposition is “organizing and routing information that a human needs to act on,” that tool is in trouble. Not because it’s bad software — but because the human-in-the-loop is being automated out of the picture.
Second, double down on the physical-world interface. The tools that survive are the ones that live at the point where digital information hits the physical environment. Remote visual support, AR-guided assistance, live diagnostic sessions — these are not features you bolt on. They’re the core. If your support workflow still requires a human to physically see something before a resolution is possible, you need the infrastructure to make that visual connection fast, clear, and documentable.
Third, stop evaluating software by its AI feature list. Every vendor is going to claim AI-native everything. The right question is: does this tool do something that an AI agent operating on structured data cannot do by itself? If the answer is no, the clock is running.
The $234 billion at risk isn’t at risk because AI is smarter than your software. It’s at risk because the work those tools were built to organize is being consumed directly by agents who don’t need the organizing layer. What’s left — what’s genuinely defensible — is the part of support that requires a human to be physically present, holding a camera, seeing the problem.
That’s not a small niche. That’s the hard part of support that has always been hard, and that no amount of agentic AI will make easy.