AI & Automation

The Agents Multiplied, the Connections Didn't

Standing up AI agents is not the same as connecting them — and the gap between the two is where the returns leak out.

← Back to Blog

New 2026 research keeps surfacing the same quiet surprise. Enterprises have raced to stand up AI agents — a dozen or more running in a single organization is now ordinary — and yet a large share of them, by several accounts roughly half, aren't connected to anything beyond the narrow task they were dropped into. The intelligence arrived on schedule. The wiring didn't.

More agents is not more autonomy

It's easy to read a rising agent count as progress. It usually isn't. An agent that can't reach the systems where the relevant facts actually live is an island — it can reason beautifully about whatever is in front of it and nothing about what isn't. Deploy ten more of those and you haven't built an autonomous operation; you've built ten more islands, each confidently acting on a partial view.

This is the part the agent count hides. The hard problem in a document-heavy operation was never "can software take the next action." It was "does the software taking the action know what's already true everywhere else." Adding agents answers the first question and leaves the second one exactly where it was.

The old silo problem, with a faster clock

For years the cost of disconnected systems was mostly absorbed by people — a coordinator on the phone reconciling what two systems disagreed about, an email forwarding a status that one party couldn't see in the other's software. Slow, but human-paced, and a person could catch the obvious errors before they propagated.

An agent removes the person and keeps the disconnection. Now the same gap gets crossed at machine speed, without the pause where someone would have noticed the number didn't match. A disconnected agent doesn't just fail to help; it can act on a stale or partial fact faster than anyone can intervene, and then hand its output to the next agent as if it were settled. Fragmentation didn't go away. It got a faster clock and fewer witnesses.

Why wiring each agent to each system doesn't scale

The instinct is to close the gap one integration at a time: connect this agent to that system, then the next, then the next. It works for the first few and then collapses under its own arithmetic. Every agent that needs to see every system is another brittle, point-to-point connection to build and maintain, and the count of those connections grows far faster than the count of either agents or systems. You end up maintaining a thicket of bespoke links, each one a place the whole thing can quietly break.

Worse, those links usually try to copy data from one place to another so the agent has something local to read — which reintroduces the oldest problem in multi-party work. Now there are two copies of the fact, they drift, and no one knows which the agent acted on.

Connect once, to a shared layer

The alternative is to stop wiring agents to systems and wire everything to a connective layer instead. When each party's system of record connects once to a neutral layer that moves structured facts — status, milestones, document references — every agent reads the same current picture through that one connection, rather than each agent negotiating its own fragile path to each system.

This is what Veritas by ATG is built to do. It doesn't replace anyone's software and it doesn't become a second master copy of the data; each party keeps its own archive, and only the facts that need to travel do. An agent working against that layer isn't guessing from a stale local copy — it's acting on what's true now, across company lines, which is the only ground on which autonomy is safe to grant.

The order that actually matters

The headline number to watch isn't how many agents a business is running. It's how many of them can see past their own task. An agent on a connected layer compounds — every new one inherits the same shared picture and adds to it. An agent on a fragmented stack just adds another island to a map that was already too fragmented to navigate. Connect first, and the agents multiply into something. Skip it, and they multiply into noise. That ordering — connect, then automate — is the whole of the thesis, and this year's research is simply the bill coming due for ignoring it.

If you're adding AI agents faster than you're connecting the systems they need to see, that's the gap Veritas and ATG Consulting exist to close — connect first, so the automation has something solid to stand on.

Start a project