Your Org Chart Is a 160-Year-Old Workaround

The org chart dates to 1855, when Daniel McCallum mapped the New York and Erie Railroad. The push for formal structure started earlier, after a deadly 1841 collision on the Western Railroad. Two thousand years of organizational design all solved the same problem: how do you coordinate people when no single human can hold the whole operation in their head at once?

Roman legions solved it with centurions and cohorts. Prussian generals solved it with a dedicated staff layer. American railroads imported the model in the 1840s and corporate America copied it into the org charts we still use. Departments, layers, managers, reporting lines. The entire architecture was a workaround for one constraint: human span of control.

Your AI agents do not have that constraint.

And yet most revenue organizations are building their AI strategy on top of the same tree-shaped structure designed for the limits of 1856. They are adding agents to a hierarchy. They are automating the workaround.

In March, Jack Dorsey and Sequoia's Roelof Botha published "From Hierarchy to Intelligence" at Block. This page covers what it means for a revenue org.

What the end of hierarchy means for your revenue motion

The Block argument is precise. Hierarchy existed because information had to route through humans, and humans have limits. A leader can reliably coordinate three to eight direct reports, so you build layers. Decisions travel up, instructions travel down, and each layer pre-computes enough to keep the layer above it from drowning in noise.

That structure has one fundamental cost: speed. Every layer a decision touches adds latency. Every handoff between functions loses fidelity. Every status meeting and alignment session exists because information could not get from where it lived to where it was needed without a human carrying it there.

AI doesn't augment your company. It reveals what your company actually is.Jack Dorsey and Roelof Botha, From Hierarchy to Intelligence

If your company is a slow information routing system dressed in a modern tech stack, AI makes that visible. It does not fix it.

The revenue motion is where this shows up most clearly. Marketing builds positioning. It travels through brand review, then messaging alignment, then enablement, then rep training, then a QBR, then a field feedback loop that takes two quarters to close. By the time intel from a lost deal reaches the person who could update the positioning, six months of campaigns have already been built on stale assumptions.

The org chart is becoming an operating system: a design for how context moves between people and agents, how decisions get made, and how handoffs happen across roles. Block stripped their structure to three role types. Individual contributors who build. Directly Responsible Individuals who own specific outcomes for 90-day windows. Player-coaches who build and develop people at the same time. No permanent middle management. The intelligence layer now does the coordination work that middle managers did.

Coinbase capped management at five layers below the CEO in May 2026, abolished what their memo called pure managers, and stood up AI-native pods including, in their words, potentially one-person teams directing fleets of agents. On May 7, 2026, Cloudflare cut about 1,100 roles, roughly 20 percent, and said internal AI usage rose more than 600 percent in the prior three months.

Two front-page restructurings in three days, both pointing at the same shape. Fewer layers, smaller teams, agents doing the coordination work humans used to do. The shift is coming. Design toward it now, or the org chart becomes your most expensive technical debt.

The graph model applied to revenue

The Block architecture has three components: a company world model, a customer world model, and an intelligence layer that composes capabilities into solutions and delivers them proactively. For a revenue organization, this maps directly.

Your company world model

Your ICP definition, positioning, competitive intelligence, win/loss patterns, and product roadmap, maintained as a single source of truth that every person and every agent pulls from. Most revenue motions drift because the company world model lives in six tools, owned by six people, and has never been treated as one canonical document.

Your customer world model

The proprietary signal layer built on your own customer data: usage patterns, deal history, conversation transcripts, expansion signals, churn indicators. Dorsey is explicit about what makes this defensible: what does your company understand that is genuinely hard to understand, and is that understanding getting deeper every day? For a B2B revenue org, the equivalent is the corpus of every deal you have run, every call recorded, every objection handled, every outcome measured. Most companies have this data. Almost none have organized it as a world model.

Your intelligence layer

The system that routes the right capability to the right moment without a human carrying the information. A competitive signal reaches the rep while the deal is still live. A churn risk reaches customer success before the renewal conversation. A positioning gap reaches the CMO from deal-loss data.

Cognition's Devin went from about $1 million ARR in September 2024 to about $73 million in June 2025. These are production results from organizations that stopped automating hierarchy and started replacing it.

Companies stuck at Level 2 of the AI maturity curve are using AI to accelerate the people they have, and headcount still roughly tracks revenue. Organizations at Level 4 have decoupled the two. Headcount and revenue are no longer the same line on the same graph.

Teams that keep the tree will lose slowly at first, then fast, to teams that run a graph.

The migration for leaders who are not starting over

Nobody is suggesting you fire your team and rebuild from scratch. Run the migration one step at a time. Here is how revenue leaders inside existing hierarchies start moving without blowing up what works.

Step 1: Map your information routing costs

Before redesigning anything, audit where coordination work actually lives. Build a coordination map: read the org as a flow of context, decisions, handoffs, and judgment. Ask three questions across every function.

1. Where does status get reported, and who carries it?
2. Where does context get explained at handoffs, and how much fidelity is lost?
3. Where do decisions wait for a human when the information needed already exists somewhere in the system?

In most revenue orgs the answers cluster in three places: the marketing to sales seam at MQL to opportunity, the sales to customer success seam at close to onboarding, and the loop between customer outcomes and product or positioning updates. Those three seams cost you the most, and they are where the first agents should go.

Step 2: Build your company world model before you deploy agents

The most consistent failure mode is deploying agents on top of weak context. You cannot get graph-model performance out of a hierarchy-model data architecture. Your world model has four components: one canonical ICP definition with a single owner and update cadence, one source of truth for positioning and messaging with clear versioning, one competitive intelligence layer with a structured refresh cycle, and one corpus of deal data organized as a queryable knowledge base rather than a folder.

Most organizations already have all of this. It is in six places, owned by different people, with different conventions and different update frequencies. The migration uses the data you have, consolidated into a structure an agent can use.

Step 3: Replace coordination roles with outcome owners

The Directly Responsible Individual model is the most misread part of the Dorsey and Botha essay. It restructures accountability. A DRI owns a specific outcome for a defined window, 90 days in Block's example, with authority to pull from any capability layer to deliver it.

For a revenue org that looks like a DRI who owns churn in a specific segment for Q3, with authority to pull from marketing, sales, and customer success to move the number. That DRI operates across the seams that currently require multiple managers to coordinate. The AI handles the coordination work. The human handles the judgment work.

Gartner warned on May 5, 2026 that AI layoffs may free budget without delivering returns. The organizations seeing real ROI invest in the skills, roles, and operating models that let humans guide and scale autonomous systems. The goal is the right people with clear accountability, supported by agents doing the coordination that used to require layers.

Step 4: Identify your economic graph

Block's defensibility argument anchors on one question: what does your company understand that is genuinely hard to understand, and is that understanding getting deeper every day? For a B2B revenue org, the answer is almost always some combination of conversation intelligence from every customer interaction you have recorded, deal data showing which patterns predict wins and losses in your specific market, and usage data showing how customers actually use the product versus how they said they would during the sales cycle.

Most revenue organizations have this and treat it as a reporting asset. Organizations moving toward the graph model treat it as a compounding strategic advantage and build the intelligence layer on top of it. Every quarter it gets richer, and the gap widens against the competitor still pulling their ICP from a generic market research deck.

Plan for three quarters

The architecture shift is a quarter. Building the world model is a quarter. Standing up the DRI layer and letting agents carry the coordination work is another quarter. Three quarters to go from hierarchy to the early stages of a graph model, without a single layoff required, and without losing the institutional knowledge your people carry.

Most revenue organizations today have roughly 18 months before the gap between graph-model and hierarchy-model competitors becomes structurally insurmountable. The leaders who act in the next two quarters will be talking about this from the position of having shipped.