Information Used to Need People to Move It. Now It Doesn't.

Think about your last week. How many meetings existed primarily to move information from one group to another? A status update. A handoff. A briefing. A review where one team reported what they had done to another team that needed to know. Count them. They are probably most of your calendar.

Now think about why those meetings exist. Not why each individual one is on the calendar, but why the category exists at all. The answer is the same across almost all of them: information needed a human to carry it. The engineering team could not automatically share context with the product team, so someone scheduled a sync. The CEO could not read the raw operational data, so someone packaged it into a report. The legal team needed to understand what sales had agreed, so someone held a handoff.

Every meeting, every layer of management, every operations function that primarily coordinates rather than builds: these are all solutions to the same underlying problem. Information needed people to move it. That constraint is lifting. And when it lifts, everything built around it becomes optional.

Why Hierarchy Exists

The org chart was invented in 1855 by the New York and Erie Railroad. It was one of the first organisations that needed to coordinate thousands of people across distances too large for direct communication. The solution: nested hierarchies with named individuals at every node, passing orders down and sending information back up.

This was not a choice between good and bad structures. It was the only available technology for the coordination problem. Information had to travel through humans because humans were the only available relay mechanism.

The same logic applies to every layer of management ever added since. Middle managers do not exist because they are inefficient. They exist because someone had to translate between the strategic layer and the execution layer. That translation requires proximity, which requires people.

What Changes When Information Moves Itself

Here is the same scenario with agents.

A customer complaint arrives. An agent reads it, cross-references the customer's account history, identifies it as a pattern seen in 14 other tickets this month, flags it as an emerging product issue, drafts a resolution for the support team, and sends a summary to the product team's shared system. All within minutes.

The CEO queries the live company state Monday morning: three emerging customer pain points, ranked by frequency and revenue at risk, with draft responses already prepared. Total latency: minutes, not weeks. No meetings. No packaging. No relay.

This is not speculation. Cloudflare CEO Matthew Prince described exactly this: "Internal audit previously picked a handful of business risk areas to scrutinize each quarter. Now we're moving to a system in which every business risk is audited continuously." Not faster audits. Continuous audits. Qualitatively different.

"Internal audit previously picked a handful of business risk areas to scrutinize each quarter. Now we're moving to a system in which every business risk is audited continuously." — Matthew Prince, CEO, Cloudflare

What Remains When the Relay Is Gone

This is the important question. If agents handle information relay, what do the humans do?

Three categories remain irreducibly human.

• Judgment Decisions where the right answer is not deterministic. Where context matters in ways that cannot be fully specified in advance. Where the decision-maker has to own the outcome and be accountable if it is wrong. Agents can surface the information, assemble the context, and present the options. The decision and its ownership stays with a person.
• Relationships The customer who needs a person on the phone, not a resolution. The partnership that requires trust built over time. The employee who is struggling in ways that do not show up in the data. Agents can flag these. They cannot replace them.
• Creating Building products, selling ideas, designing systems. Work that produces something new rather than routing or measuring something that already exists. This is what compounds. This is where the value is going.

The Cloudflare CEO's observation points at exactly this: AI is not coming for builders or sellers, but it is coming for measurers. Builders create. Sellers connect. Measurers relay. The relay is what is changing.

The Uncomfortable Audit

Take any function in your company. Map what each person in it does. Sort the activities into three buckets:

The relay bucket is the portion that agents can handle. In most organisations, it is the largest bucket in operations, finance, compliance, and middle management layers. It is not the largest bucket in engineering, sales, or senior leadership.

This is not an exercise in identifying who to let go. It is an exercise in identifying where to deploy agents first, so that the people currently in the relay bucket can move into the creating and connecting buckets.

Building the First Relay Agent

The relay that is most automatable is almost always the one that meets three criteria.

• High volume. Volume means agents earn their cost quickly. A relay that happens twice a year is not where you start. A relay that happens hundreds of times a day is.
• Clear rules. Agents need to know what "correct" looks like. If the relay involves judgment calls every time, it is not the first target. If it follows a defined process with consistent inputs and expected outputs, it is.
• High latency. The longer information takes to reach the right person, the more valuable it is to speed it up. The relay that produces 4-to-8-week lag is the one that, when replaced, changes how the company operates visibly and immediately.

The First Build maps one of these relays, replaces it with an agent, and measures the result. Not in theory. In production, on live data, with real latency reduction visible within two weeks.

The Install builds the relay replacement function by function across the whole company. Each sprint shortens one information journey that currently requires a meeting or a management layer.