There is a second-order problem the build-vs-buy framing usually misses. It is not just that homegrown platforms become maintenance burdens. It is that AI tooling has democratized building to the point where organizational coordination collapses.
At Yum Brands — 50,000+ restaurants, roughly 8,000 engineers across Pizza Hut, Taco Bell, KFC, and other brands — the AI team is watching this play out in real time. Because AI tools now allow non-engineering teams to build functional products, teams across all brands are independently spinning up AI-powered projects. The problem is not that the products are bad. The problem is that five teams build the same integration aggregator without knowing it, and nobody discovers the duplication until they present to leadership a month or two later.
As one lead engineer described it to me: "Things are just going a little too fast. Because now everybody thinks they're an engineer, there's just so much slop. Leadership is having a hard time getting actual deliverables because people keep shifting their objectives because AI is allowing them to finish things so quickly."
This is the coordination tax nobody budgeted for. In the old world, building was slow enough that coordination happened naturally — you could not waste months of engineering time without someone noticing. In the new world, a team can build a million-dollar product in weeks, and the organizational processes designed to prevent duplication were built for a slower cadence. When everyone can build, nobody knows what has already been built.
This is a hundred-million-dollar problem at Yum's scale, and it is a governance problem that tooling created. A centralized agent platform with cross-team visibility stops being a developer productivity tool and starts being the coordination layer that prevents millions of dollars of duplicated effort. I've argued separately that internal tooling has a twelve-month shelf life — the coordination layer is the part that has to outlast the tools that ride on top of it.
Sources
Related Essays
When Building Is Cheap, Coordination Breaks
Three brand teams in the same Fortune 50 build the same aggregator without talking. AI lowered the cost of building, and the budget process that used to coordinate everyone disappeared with it.
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
- AI tooling has democratized building to the point where organizational coordination collapses. Five teams build the same integration aggregator, and nobody finds out until they present to leadership.
- The old build cadence was slow enough that coordination happened naturally. The new cadence outruns the processes designed to prevent duplication.
- A centralized agent platform with cross-team visibility stops being a productivity tool and becomes the coordination layer. That is a hundred-million-dollar problem at enterprise scale.
FAQ
What is the coordination crisis?
AI tooling lets non-engineering teams build functional products in days. That speed has outrun the organizational processes designed to prevent duplicate work, so multiple teams now ship the same product independently before anyone notices.
How big is the financial impact?
At a company with thousands of engineers across multiple brands, duplicated AI projects can easily reach a hundred million dollars in wasted effort per year. That makes coordination — not productivity — the durable platform value.