Can't a large company hire Arco or a similar studio to fix their operations?

They can hire consultants. They cannot implement the results. Autonomy requires the removal of human-in-the-loop dependencies — and for a large corporation, removing those dependencies means dismantling the management tiers, approval chains, and coordination roles that define the organisational structure. Most boards will not authorise the scale of reconstruction required. The ones that do typically find that the change management cost exceeds the efficiency gain — because the legacy workforce is still there, drawing salary, while the autonomous systems are being built alongside them. Arco builds new companies instead of fixing old ones. The no-MVP principle and the no-legacy principle are the same decision.

Isn't a large incumbent's data an advantage over a new entrant?

Only if the data is clean, structured, and accessible to agents. Most incumbents have fragmented legacy systems — data spread across ERP platforms, spreadsheets, email threads, and institutional knowledge held in individual employees’ heads. An agentic system cannot operate on data it cannot read deterministically. Arco builds businesses with structured data layers from day one, which means our data is an operational asset rather than a retrieval problem. The incumbent’s years of data are largely inaccessible to the agents that would make use of them.

Why does Arco focus on replacement rather than disruption?

Disruption implies changing the market — convincing customers to adopt a new behaviour, a new product category, or a new way of thinking about a need. Replacement implies delivering the exact same value the customer already pays for, through a structurally superior operational architecture. Arco does not need to change the customer’s mind. We need to be the more efficient choice in a market where the incumbent is paying 20–30% of its operating budget to coordinate itself. That gap funds our margin. The customer gets the same outcome for less, or a better outcome for the same price. The incumbent loses on cost structure, not on product.

What specific industries have the highest Legacy Liability?

The highest concentrations are in labour-intensive service sectors where the delivery of value requires high volumes of human handoffs: logistics brokerage, back-office compliance, professional services coordination, high-volume document processing, and insurance claims handling. In each of these industries, the core workflow has not changed materially in twenty years — it has only become more expensive as headcount has grown to manage complexity. These are the markets where the Human-to-Logic ratio is most heavily skewed toward human labour, and where the Coordination Tax embedded in the incumbent’s cost structure is the largest. They are the primary targets for autonomous reconstruction.

Is AI transformation ever successful for incumbents?

Occasionally, at the margins. The most successful cases involve firms that used AI to redesign workflows entirely rather than layer technology onto existing ones — which is precisely what McKinsey’s research on high-performing AI organisations identifies as the differentiator. But even in those cases, the structural constraint remains: the organisation still employs the people whose roles are being redesigned, and the political cost of full reconstruction is rarely paid. The result is partial autonomy — faster processes, somewhat lower headcount, the same underlying dependency on human coordination for anything that requires a judgment call. Partial autonomy is not autonomy. It is the incumbent’s ceiling.

How does Legacy Liability affect an incumbent's ability to compete on price?

Directly and permanently. If 20–30% of an incumbent’s operating budget is consumed by the Coordination Tax, that cost is embedded in every price they charge. A competitor with an Operational Drag ratio below 5% — Arco’s architectural target — can price below the incumbent’s cost base and still generate a superior margin. The incumbent cannot match that price without eliminating the coordination overhead that generates it, which it cannot do without the organisational reconstruction it will not authorise. Legacy Liability is therefore not just an operational problem. It is a permanent pricing disadvantage against any competitor that built correctly from the start.

Legacy Liability: Why Incumbents Can't Adapt

Size is no longer a moat. It is a weight. Legacy Liability is the structural condition of a business that has grown too dependent on human-centric coordination to rebuild itself without dismantling the organisation in the process. For the modern incumbent, legacy infrastructure is a liability that prevents adaptation. Most large enterprises are currently attempting to “AI-transform” their operations — but you cannot transform a structure built on the assumption of human-centric labour. You can only replace it.

Corporations optimise for continuity — Arco optimises for replacement.

The Sunk Cost of Human Capital

The conventional defence of the incumbent is scale. Large enterprises have distribution, brand, regulatory relationships, and institutional knowledge that a new entrant cannot easily replicate. These are real advantages — and they are precisely what makes the incumbent impossible to reform from the inside.

The primary obstacle for a large enterprise attempting autonomous transformation is not technology. It is the existing organisational chart. A traditional firm is a collection of human handoffs, status meetings, and middle-management layers designed to coordinate those handoffs. Each of those layers represents a budget line, a headcount, a set of job titles, and a reporting structure. Removing them is not an engineering decision. It is a political one — and most boards lack the stomach for it.

When these firms attempt to implement agentic AI, they try to fit the agent into an existing human role. This is a category error. A high-speed agent placed into a low-speed human workflow is throttled by the slowest link in the chain. The incumbent ends up paying for both the expensive human overhead and the new technology, without achieving the structural decoupling of headcount from revenue that autonomy requires. The result is “AI-assisted” inefficiency — faster inputs, same bottlenecks.

The Coordination Tax They Cannot Delete

The fatal flaw of the large enterprise is the Coordination Tax — the internal spend required simply to keep the organisation aligned.

The McKinsey Global Institute found that the average knowledge worker spends 28% of the working week managing email and a further 20% searching for information and tracking down colleagues — nearly half the working week consumed before a single unit of output is produced.

Gary Hamel’s research published in Harvard Business Review quantifies the budget consequence: excess management overhead in large firms consumes up to 30% of operating costs — structural spend that produces no output, only alignment.

In a legacy service business, both measurements point to the same liability: the time lost to internal communication is the margin consumed by overhead rather than output. It is the cost of the organisation managing itself. That cost has not diminished.

Miro’s 2025 Momentum at Work report found that 79% of knowledge workers cite constant emails and messages as their primary maintenance burden, spending three hours on coordination for every one hour of productive output.

Microsoft’s 2024 Work Trend Index confirmed that 68% of workers feel overwhelmed by the pace and volume of work, with 60% of time in productivity tools consumed by email, chats, and meetings — leaving only 40% for the work that actually produces output.

The Coordination Tax is not a 2012 observation. It is the current operating condition of most large enterprises.

An incumbent cannot delete this tax. Doing so would require deleting the very departments and hierarchies that define the company. The middle-management layer that coordinates the coordinators is not a inefficiency that can be quietly removed — it is a structural feature of how the business was built. Every attempt at “digital transformation” runs into this reality: the technology is straightforward; the organisational surgery is not. They are trapped by their own success.

Consider a large logistics firm. It employs hundreds of coordinators whose job is to match freight with carriers, resolve exceptions, and manage customer relationships. These roles exist because the workflow was designed for humans — the data is fragmented, the systems do not talk to each other, and every exception requires a human judgment call. An AI assistant speeds up the email. It does not remove the email. The Coordination Tax persists because the human-in-the-loop dependency persists. The only way to eliminate it is to rebuild the workflow from scratch — which is precisely what Arco does instead of transforming an existing business.

This is why the markets Arco targets are the ones where incumbents have been accumulating this liability for decades. The longer a firm has run on human-centric coordination, the deeper the structural debt — and the wider the gap between what the incumbent charges and what an autonomous competitor needs to charge to generate the same margin. That gap is the Operational Arbitrage. The incumbent created it. Arco captures it.

Arco does not wait for incumbents to digitally transform. We wait for their Coordination Tax to become so high that they can no longer compete on price or speed. Then we move in — not with a better product, but with a structurally superior cost base.

The Operator's Verdict

The incumbent’s advantage — scale, distribution, brand, institutional knowledge — is also its anchor. The same size that made it dominant makes it structurally resistant to the reconstruction that autonomous architecture requires. Every consultant hired to accelerate the transformation runs into the same wall: the organisation cannot be made autonomous without first being made smaller, and no board votes for that.

You cannot fix a legacy business by adding agents to it. You can only win by building a business that does not have legacy to begin with.

Related Operational Memos

Memo #01: Automated vs. Autonomous — Why the incumbent's focus on automation is a strategic dead end.

Memo #02: What We Mean When We Say Agentic — How agentic architecture eliminates the human-in-the-loop dependencies that define Legacy Liability.

Memo #03: Overhead Is a Design Choice — The Coordination Tax in detail — and how Arco designs it out from day one.

Memo #05: Markets That Work — How Arco identifies the incumbent markets where Legacy Liability has created the largest Operational Arbitrage.

KEY TAKEAWAY

What is Legacy Liability and why can't incumbents eliminate it?

Legacy Liability is the structural condition of a business that has grown too dependent on human-centric coordination to rebuild itself without dismantling the organisation. The primary expression of Legacy Liability is the Coordination Tax: the McKinsey Global Institute found that knowledge workers spend 28% of the working week on email and 20% searching for information — nearly half the working week lost before any productive output is possible. Hamel and Zanini’s Harvard Business Review research calculated that excess bureaucracy costs the US economy more than $3 trillion annually in lost output. Miro’s 2025 Momentum at Work research confirms the pattern holds: 79% of knowledge workers spend three hours on coordination for every one hour of productive work. Incumbents cannot delete this tax without deleting the management layers that define the company. True autonomy requires a clean-sheet build. Key metric: 28% + 20% of the working week lost to email and information search (McKinsey Global Institute, 2012); $3 trillion in annual lost output from excess management (Hamel & Zanini, HBR, 2016); 79% of knowledge workers overwhelmed by coordination tasks (Miro, 2025); 60% of productivity tool time consumed by communication rather than creation (Microsoft Work Trend Index, 2024).