1. The Human Bottleneck Nobody Wants to Talk About
If you watch the 1988 action film Die Hard through a corporate lens, the actual villains aren't just the thieves—it's the LAPD chain of command. While one guy on the inside actually solves the problem, the management outside (Deputy Chief Robinson and the FBI) spend the entire crisis holding meetings, following rigid protocols, and actively making the situation worse. It is the ultimate display of organizational latency.
Look at any large corporation for long enough and you notice something uncomfortable: most of what happens in the middle of the org chart is not decision-making—it is coordination.
The modern corporation is throttled by the biological limits of its own workforce. Humans are, at the risk of sounding rude about our own species, high-latency routers. When a market shifts, it takes days—sometimes weeks—of cross-departmental alignment, Zoom meetings, PowerPoint decks, and coffee-machine hallway diplomacy for a mid-sized company to react. In between, we sleep, get distracted, form opinions about office snack policy, and run into cognitive biases that no amount of leadership training seems to fully patch out. There is an entire economy of team-building offsites, executive coaches, and quarterly all-hands meetings whose main job is to translate one PowerPoint deck into a slightly different PowerPoint deck, built specifically to compensate for these limits. It works, more or less. It just works slowly.
If you look at a company the way a systems engineer looks at a distributed system, most middle management is not doing knowledge work at all. It is running an internal routing protocol—making sure Team A knows what Team B is doing, translating priorities between departments, and turning strategic ambiguity at the top into an actionable ticket at the bottom.
The reason we tolerate the latency of that routing protocol is that we have never had a viable alternative. Software has, historically, been either (a) too dumb to make judgment calls, or (b) too disconnected from the operational surface to actually execute on them.
Both of those constraints are now, quietly, being lifted—accelerated by advances in 2026, where AI agents are shifting from simple assistants to autonomous decision-makers embedded in everyday operations.
A note before we go further: None of this is an argument that humans are or should be replaced wholesale. It is an argument that a specific layer of the org chart—the coordination layer—is a strong candidate to function in a software-native way. Everything above and below that layer changes shape, but does not disappear.
2. From Cost Centre to Revenue Centre
Today, running an AI agent looks like an expense. Every ReAct loop burns tokens, every tool call spins up GPU cycles, and finance signs off on the bill because the alternative is paying a human to do the same work more slowly.
This is about to change now. In 2026, we're seeing the first wave of truly autonomous agents that don't just cut costs—they generate revenue.
Algorithmic trading desks at hedge funds have been running autonomous, revenue-generating loops for close to two decades. They just don't call them "agents" because the marketing budget is spent on being taken seriously. E-commerce platforms already run automated repricing and inventory reordering on top of predictive analytics—the polite phrase for "the software has been quietly rearranging the store while you were asleep." The shape of a system that owns a P&L target and executes on it is not new. What is new is that reasoning models can now sit at the top of that loop and make the kind of nuanced decisions that older systems could not.
As reasoning models mature and tool-use protocols stabilise—Anthropic's Model Context Protocol (MCP) is a key standard bearer in 2026—companies are starting to hand agents autonomous budget authority. Give an agent an objective like "optimise European supply-chain routing margins," a set of real-world tools, and enough monitoring, and it stops being an assistant. It becomes a revenue-generating node.
At that point, the agent is not a cost. It is a business unit.
And that is the moment the org chart starts to bend.