From Builders to Orchestrators

The era of Scale is ending. The middle layer of the enterprise — the armies of Builders and PMs who kept the factory moving — is collapsing. What replaces it is not more people. It is a different structure entirely.

To understand where software is going, you have to look at what was scarce in the previous eras. The architecture of the industry (and our careers) has always been defined by the Core Constraint.

• In the Mainframe Era, the constraint was Access. Hardware was the bottleneck, and the customer was held captive by the physical machine.
• In the SaaS Era, the constraint was Engineering Capacity. It took two years to build a platform and one year to build a GTM motion. That head start was the moat that created the distribution structure.

To build anything meaningful, you needed armies of developers (to build) and Product Managers (to align everyone on what was being built) just to keep the factory moving. Progress was a function of Scale - how many people you could hire and coordinate.

That era is ending.

As I argued in The AI-Driven Software Revolution, the marginal cost of creation is collapsing toward zero. Features can be prototyped in hours. Interfaces can be spun up in a weekend. What once required a Two-Pizza Team now fits inside a single person's context window.

We are moving from an era of Scale ("How many people do you have?") to an era of Agency ("How much leverage does one person have?").

This forces a fundamental rethinking of the org chart. The middle layer - the mediators who translate intent into tickets - is collapsing. As I see it, the new firm is unbundling into three specific pillars: The Builders, The Orchestrators, and The Relationship Owners.

1. The Builders (The Auto Factory)

For the last twenty years, software development was a craft. It was closer to hand-assembling a luxury car. Every line of code was placed by a human hand.

In the AI era, software development is increasingly becoming a Robotic Assembly Line. The Builder no longer manually tightens every bolt. The AI does the heavy lifting of generating the boilerplate, the logic, and the tests.

The Builder's role shifts from Writer to Supervisor. Think of a modern Tesla Gigafactory. The humans aren't on the line holding screwdrivers; they are designing the jigs, monitoring the error rates, and supervising the robots.

• The Old Metric: Velocity (Story Points).
• The New Metric: Throughput and Quality Assurance (Evals).

The Engineers will absorb the technical aspects of Product Management. They define the "Evals" - the acceptance criteria that tell the AI whether the code is good. They build the System Architecture that allows the factory to run. They ensure the output is deterministic and safe. They don't just build the car but instead they design the factory that builds the car.

2. The Orchestrators (The Bakery)

If the Builders run the factory, who decides what to build? Let's view this role through the analogy of the Bakery.

In the AI era, the raw ingredients (LLMs, Compute, Infrastructure) are commodities. They are the flour and the sugar. Everyone has access to the same flour (OpenAI/Gemini/Claude). The differentiator is no longer having the technology.

Taste is the differentiator, and the Baker is what I call the Orchestrator.

In the SaaS era, we separated Product (who defined the why and what) from Engineering (who defined the how).

The Orchestrator collapses these roles. They are the First & Last Mile person. They don't just pass tickets to the factory; they configure the factory to bake exactly what the customer needs.

Orchestrators will have the following responsibilities:

• They own the P&L. They define the Outcome Metrics that drive the business model (see The Cannibalization Trap).
• They are the Solution Architect. They sit in the loop with the customer. They understand the specific, nuanced palate of the market.
• They act as the Refinement Loop. They take the raw output from the Builders' factory and refine it into a solution that sells.

If you don't have Taste, if you can't tell the difference between a generic AI response and a high-value insight, you cannot be an Orchestrator. You are just reselling flour.

3. The Relationship Owners (The Handshake)

Finally, there is the Relationship Owner. In a world of infinite AI noise, Trust becomes the scarcest asset.

These are the people who front-end the demand. While the Orchestrator ensures the solution works, the Relationship Owner ensures the customer believes in it. They handle the nuanced, human-centric touch that AI cannot replicate. They provide the Handshake that validates the transaction and own the Moral Liability when things go wrong.

The New Market Structure

This internal restructuring mirrors the external market shift. We are seeing a massive bifurcation of the software industry:

1. The Bottom: Wholesale Consolidation (The Flour Mills)

The infrastructure layer is consolidating. AWS, Azure, OpenAI - these are the massive, industrial mills providing the flour. They operate on brutal economies of scale. There will only be a few of them.

2. The Top: Hyper-Fragmentation (The Bakeries)

The application layer is exploding. Because the barrier to entry (the cost of the factory) has dropped, we will see thousands of niche Bakeries popping up. These are vertical-specific AI apps, highly tuned to specific industries (Legal, Medical, Construction, BFSI).

Conclusion: The Agent Network

But this market structure creates a new problem. In a world of ten thousand niche bakeries, how do you find the right loaf of bread?

You aren't going to download ten thousand apps or visit ten thousand websites. That friction is too high. The SaaS Era model of manually using software (browsing tabs, clicking buttons, filling forms) breaks down under this deluge of fragmentation.

This is where the interface shifts.

We are seeing glimpses of this in recent Agentic Commerce announcements. The future won't look like a cluttered home screen; it will function more like a Payment Network.

Think about your credit card. You don't sign a separate contract with every merchant. You carry one card (your Identity and Context), and it interoperates with millions of distinct Point-of-Sale terminals (the Merchants).

The Agentic Era will function on the same rails:

• The Builders (Infrastructure) ensure the rails are robust, acting like the Visa network that lets any agent talk to any other agent.
• The Orchestrators (Bakeries) build the specific "Point of Sale" agents—the specialized bots that know exactly how to price, scope, and deliver their niche service.
• The Relationship Owners (Trust) ensure that when your personal agent meets their selling agent, you trust the brand enough to authorize the trade.

The interaction moves from explicit software era to implicit agentic era.

You don't manually order Bread. Your Personal Secretary (Buying Agent) negotiates with the Orchestrator's Selling Agent in the background - matching taste, price, and logistics.

This is the architectural leap. We are leaving the Telegraph Era - where every interaction required a manual, low-bandwidth input - and entering the Orchestration Era, where the software does the connecting, and the humans simply approve or intervene for the handshake.