Subscribe • Previous Issues
Integration Is the New Moat: Moving Beyond the LLM
The AI Agent Conference in New York was one of the better events I’ve attended to get a read on what’s actually happening with enterprise AI. The formal sessions were great, but the hallway conversations was where I got the inside scoop. The consistent message: deploying AI agents is much harder than most organizations expect, and the reasons are rarely the ones they anticipate. What follows is my attempt to distill what I heard into a practical view of why enterprise agents are so hard to deploy.
Reading on a regular basis? Consider becoming a paid supporter 🙏
The first barrier is integration. In one enterprise after another, agents run into older CRMs, finance systems, document stores, and homegrown tools that were never designed for autonomous software. What looks like a wiring problem usually isn’t. A logistics company built a capable agent that fell apart the moment it had to touch their order management system, a decade-old platform never designed to be queried by software making autonomous decisions. The agent wasn’t broken. The process it was dropped into was. The worst failures are often the ones that stay hidden. A financial services firm ran an agent successfully in its test environment for months, only to discover during a quarterly audit that production CRM records had silently stopped updating. No error, no alert, just bad data accumulating for three months. Teams that treat integration as a technical handoff rather than a workflow redesign problem consistently get stuck at the same wall.
The data situation compounds this at every layer. Enterprise knowledge doesn’t live in clean, queryable databases. It lives in Confluence pages nobody maintains, Slack threads from two years ago, and the heads of three people who’ve been at the company long before the current CTO arrived. One study found that more than a quarter of agent deployment failures trace directly to critical knowledge that was never captured anywhere a system could reach. When agents fail on company-specific terminology, like non-standard product codes or internal procurement shorthand, the instinct is to upgrade to a more powerful model. That instinct is almost always wrong. The fix is domain-specific examples and better knowledge capture, not a bigger model. And underneath all of it, security cannot be an afterthought. Agents need governed, scoped access to data, with proper permissions and audit trails built in from the start. Without that foundation, even a well-integrated, well-trained agent is a liability waiting to surface.
Agents Don’t Fix Broken Processes, They Find Them
But even when integration is solid and data is in order, most deployments hit a third wall that almost nobody budgets for: the organization itself. Agents do not arrive as neutral software upgrades. They ask people to change how work is routed, approved, measured, and owned. In a hospital system, that might mean deciding whether an agent can prepare a prior authorization packet before a clinician reviews it. In an industrial manufacturer, it might mean exposing the informal workaround a plant manager has used for years because the official process is too slow. In an insurance operation, it might mean discovering that no one can explain who is accountable when an agent recommends a coverage decision that later gets challenged. These are not edge cases. They are the work.
This is why early agent projects often fail in a way that is politically expensive. A weak first deployment does not just miss a KPI. It convinces managers, operators, and risk teams that the whole category is immature or unsafe. The harder second attempt, the one that would involve process audits, clearer ownership, better evaluations, and serious change management, may never get funded. In practice, deploying agents means changing the organization while the organization is still running. That is slower and messier than a demo, but it is also where the real implementation work begins.
Compounding all of this is a talent problem with no clean solution. Deploying agents at scale requires people who understand process design, LLM behavior, systems integration, and organizational change, all at once. That combination is genuinely rare, and companies that hire for one or two of those skills and assume the rest will follow are setting themselves up for the same failure pattern, just with different symptoms.
Agents Are Implemented, Not Installed
The real implementation work isn’t getting an agent to run correctly in isolation. It’s getting the agent to run correctly inside a live organization, where the work is distributed across roles, the accountability is murky, and the processes were designed around human judgment calls that nobody ever wrote down. What looks like an AI project is usually a process redesign project with an AI component attached. The companies that figure this out early tend to scope their first deployments around a specific, broken workflow rather than a whole function or department. Not “automate the sales team,” but “automate the part of lead qualification that requires pulling the same three fields from two systems and writing the same email 200 times a week.” That narrower target is less exciting to demo but far more likely to survive contact with the organization. Enterprise agents are not installed. They are stood up, governed, monitored, and gradually expanded.
The implementation gap has also created a staffing model that most organizations haven’t fully absorbed yet. The most effective deployments involve a dedicated operational owner for each agent in production, someone who sits at the intersection of the business workflow and the technical system, and who can tell the difference between an agent that’s working and an agent that’s producing plausible-looking output that nobody has actually verified. Some vendors have formalized this with embedded specialists, technical product managers or forward-deployed engineers whose job is to live inside the customer’s workflow until the deployment actually holds. Without that kind of ownership, agents in production become side projects maintained by whoever built the prototype, and the research bears this out: organizations that skip dedicated ownership are dramatically more likely to face failures that require rolling the whole thing back. The talent profile this requires doesn’t map cleanly onto any existing job title, which is part of why so many companies are either building it from scratch or outsourcing it to implementation specialists who’ve learned these lessons on someone else’s dime.
Integration Is the New Moat
The next durable advantage in enterprise agents will not come from picking a cleverer model. It will come from making agents usable inside messy, specific, high-stakes workflows. A legal team does not need a model that can sound like general counsel in the abstract. It needs a system that can find the right contract, apply the company’s negotiation playbook, respect approval thresholds, and leave a clean audit trail. A customer support operation does not gain much by giving every human agent a better copilot. It gains real leverage by redesigning the service so routine cases resolve end to end, with people handling the work that requires judgment, empathy, or escalation.
A manufacturer running fragmented ERP, procurement, and plant systems will not close the competitive gap by waiting for larger models. It will close the gap by modernizing the connective tissue of the business. The raw intelligence of foundation models is becoming a commodity faster than most people expected. What remains scarce is the integration depth, the governed data access, the workflow redesign, and the operational ownership that make agents actually hold in production.
That gap is also a market. Vendors, integrators, and internal transformation teams that can do the unglamorous work, connecting legacy systems, capturing institutional knowledge, building evaluation frameworks, managing the organizational change, are sitting in front of a real and durable opportunity. The distance between what foundation models can theoretically do and what enterprises can actually deploy is not closing on its own. The companies that treat integration, governance, and workflow redesign as the product rather than the plumbing will be the ones that turn agents from demos into operating leverage.
The Three Pillars Behind DeepSeek’s $51.5B Premium
