The technical challenges of background agents are solvable. The organizational challenges are harder.
When AI lowers the cost of building something to near zero, every team builds. Marketing builds an internal tool. Operations builds an integration. Three different brand teams within the same company build the same aggregator. No one finds out until the quarterly review.
This is not a technology problem. This is a coordination problem that technology made worse. When building was expensive, the cost itself was a coordination mechanism — you had to get budget approval, which meant someone asked whether anyone else was already doing this. When building is cheap, that natural check disappears.
The fix is not to slow building back down. The fix is to build coordination systems that match the new speed. Visibility into what every team is shipping. A universal log of every agent action. Shared context across functions so the third team to build an aggregator at least starts from the first team's work. Governance that surfaces overlap before it becomes waste.
I've argued that the bottleneck has moved from generation to review, and the same shift is happening at the organizational level. The enterprises that figure out AI operationalization will not be the ones with the best models or the most tokens. They will be the ones that build organizational systems — visibility, governance, shared context — that match the speed of AI-assisted development. The agent mesh is not just a technical architecture. It is an organizational one. Build the org chart for it before the duplicate aggregators bury you.
Related Essays
The Coordination Crisis AI Tooling Created
When everyone can build, nobody knows what has already been built. Five teams independently spin up the same Slack bot, and the duplication goes undetected for months.
You Need a Directory of Agents
Companies have directories of employees. They have no equivalent for the agents doing real work. Every agent should be inspectable, auditable, and correctable.
The IKEA Effect Is Real for Agent Tooling
People pay 63% more for furniture they assembled themselves. The same dynamic governs agent platforms — developers who build their own agents care about them and keep improving them.
Key takeaways
- When building was expensive, the cost itself was a coordination mechanism — budget approval forced visibility.
- When building is cheap, that natural check disappears and three teams ship the same integration aggregator without ever meeting.
- The agent mesh is not just a technical architecture. It is an organizational one.
FAQ
Why does cheap building create coordination problems?
Marketing builds an internal tool. Operations builds an integration. Three different brand teams build the same aggregator. No one finds out until the quarterly review. When budget approval was the gate, someone always asked whether anyone else was already doing this. That gate is gone.
How do enterprises fix the coordination problem?
Build organizational systems that match the speed of AI-assisted development — visibility, governance, shared context, a universal log of every agent action. The fix is not to slow building down. It is to give leaders a way to see what is being built across the organization.