Category: Market structure

Value is accruing to vertically integrated players and to open-standard specialists. Everything in between is getting compressed, and it is remarkably easy to end up there by accident.

Download the paper (PDF) Download the infographic

There are two places to stand in AI infrastructure right now, and a large uncomfortable space between them.

At one end is vertical integration. Own the silicon, the system, the interconnect and the software, publish the reference architecture, and you capture the whole margin stack. You also capture something more valuable than margin, which is the authority to decide which suppliers exist. When you set the envelope, every other company in the value chain is designing to your document.

At the other end is the open-standard specialist. You are the best available answer to one physics problem, you are trivially integrable into anybody’s design, and you win by being specified rather than by being sold. Your moat is not scale or relationships. It is that replacing you means accepting a worse answer to a problem the customer cannot avoid.

The middle is where most companies actually are: competent, broad-line, differentiated by coverage and relationships rather than by architecture. It gets compressed from above by integrators who set the specification and from below by specialists who own a physics problem. The symptoms are recognizable long before anyone names the cause. Average selling prices flat or declining while volume grows. More bids, longer bids, more of them won on price. A roadmap that has become a list of customer requests. Engineering capacity consumed by variants rather than by advancing a position.

The cooling market ran this pattern in public over about three years. Nearly every independent direct-liquid-cooling specialist of consequence was acquired, and it is worth reading that two ways at once. The specialists had built positions defensible enough to be worth buying, which is the specialist end working. And the acquirers were broad-line industrials paying large multiples to get out of the middle, which is the middle end failing. Both halves of the barbell were visible in the same transaction.

The same structure shows up on the demand side. A hyperscaler designing its own accelerators, its own racks and its own cooling is vertical integration. A neocloud betting the company on one workload profile is a specialist. A regional colocation operator with a general-purpose story, a diversified tenant base and no structural advantage in power or thermal is in the middle, and is currently discovering what that costs when tenants with gigawatt appetites start asking questions about interconnect queues.

What makes the middle dangerous is that you get there through a sequence of individually defensible decisions. Add a product line adjacent to the core, because the customer asked and the engineering is mostly done. Take the high-volume commodity business, because the factory has capacity and the contribution is positive. Hire more coverage rather than resourcing a co-design capability, because coverage shows up in the forecast this quarter and capability shows up in eighteen months. None of those is a mistake in isolation. Taken together over four years they are a strategy, and it is the one nobody chose.

Picking an end costs something real, which is why so few companies do it. Vertical integration requires capital and the willingness to compete with your own customers. Specialization requires refusing revenue, which is much harder than it sounds in a board meeting: turning down adjacent business that would dilute the one thing you are best at, and accepting a smaller addressable market in exchange for pricing power inside it. A company that says it is a specialist while accepting every order that arrives is in the middle.

The test I would apply is a single sentence. Can you name the one physics problem you are the best available answer to, without using the words solutions, platform, or end-to-end? If not, you are in the middle, whatever the strategy document says. And if you can, the follow-up is whether your compensation plan, your engineering roadmap and your hiring pattern all point at that one problem, or at the broad middle your revenue currently comes from.

Moving from the middle toward the specialist end is a two-year operational exercise and it does not start with positioning. It starts with the engineering roadmap, because the only credible specialist claim is a measured one, which means funding the test data that proves your advantage on the specific problem you have chosen and declining the variant requests that would consume the same engineers. Then the target list narrows, usually by more than anyone is comfortable with: a specialist sells into the layer where its problem is decided, which is frequently a shorter list of accounts than the sales organization currently carries. Then compensation has to stop rewarding the revenue you are trying to exit. Companies routinely do the first step and none of the others, which produces a technically excellent company with a sales force still selling breadth.

The investor read of all this is worth knowing if you ever intend to raise or be acquired. Acquirers in this market are not paying for revenue multiples, they are paying for position at the constraint, which is why specialists with modest revenue have been bought at prices that look absurd against their income statements and why broad-line businesses with more revenue have not. If your plan is to be acquired, the asset you are building is a defensible answer to a named problem, and diversifying revenue to look safer actively reduces what you are worth.

The argument against. Barbells are not permanent, and the middle is not worthless. Scale, service coverage, supply reliability and financial durability all live there, and in a supply-constrained year those are worth a great deal of money. A specialist with superior physics, one factory and no second source will lose to an adequate incumbent who can actually ship and can pass a supplier audit. The barbell describes where margin is accruing, not where revenue is. A company can be profitably in the middle for a long time. What it cannot do is be in the middle and also expect the pricing power that belongs to the ends.

Whoever solves the scarce resource holds the pricing power. The scarce resource keeps changing, and commercial organizations are slow to follow it.

A data center is a machine for turning a constrained resource into computation. The interesting question in any given decade is which resource is actually constrained, because that is where the profit pool sits. And the answer has changed roughly every fifteen years for as long as there have been data centers.

In the mainframe era the constraint was physical: conditioned floor space, raised floor, machine-room real estate, and the enormous capital cost of the box that sat on it. Through the eighties and nineties it became processor performance, and the margin moved to whoever could put more instructions per second in front of a customer. In the 2000s it became bandwidth and interconnect. That is the era I came up in, and it is worth remembering how completely it dominated the conversation: dense wavelength division multiplexing and intelligent optical switching existed because moving data between places was the wall everything else hit. Then virtualization and utilization had their turn. Now the constraint is power and heat, and it is not close.

Each of those transitions relocated the profit pool, and the companies with pricing power in one era rarely held it in the next. Not because they got worse at what they did. Because the constraint moved out from under a commercial organization that had been carefully optimized for the previous one. Sales coverage, partner programs, engineering investment and compensation plans all get built around the thing that was scarce when they were designed, and they are the slowest part of a company to change.

The clearest evidence that the current constraint is thermal and electrical is not a market forecast. It is what large, diversified industrials have been willing to pay. Eaton acquired Boyd’s thermal business in a deal valued around $9.5 billion, closing in March 2026. Ecolab acquired CoolIT for roughly $4.75 billion. Schneider took Motivair, Trane took LiquidStack, Daikin took Chilldyne, Flex took JetCool. Inside about three years, nearly every independent direct-liquid-cooling specialist of any consequence was bought. Nobody pays those multiples for a component line. They pay them for a position at the constraint, and they pay them when they have concluded the position will not be available later.

Market sizing corroborates without proving. Dell’Oro has the data center liquid cooling market reaching roughly $7 billion in manufacturer revenue by 2029, from something on the order of $2 billion as of early 2026. A market on that trajectory, with no vendor holding a commanding position in it, is a market where position is still purchasable, which is exactly the condition that produces an acquisition wave.

The more useful question is where the constraint goes next, and the direction is consistent: down the stack, toward the package. It has already moved from the room to the row to the rack, and it is now moving from the rack to the board and from the board to the package and the die. Each step down shortens the list of people who can solve it and raises what solving it is worth. It also changes who the buyer is. Room-level problems are bought by facilities and operations. Package-level problems are decided by thermal and package architects, eighteen months before anyone issues a purchase order, and they are not reachable through the channels that worked at the room level.

That gives any company in this market three questions worth asking at every planning cycle, and they are more uncomfortable than they look.

Which layer of the stack are you selling into, and is it where the constraint will be in twenty-four months? Plenty of companies are selling competently into the layer where the constraint used to be, and reporting the resulting margin compression as a pricing problem.

Is your differentiation a property of the current constraint or the previous one? Broad coverage, service footprint and integration breadth were decisive when the problem was the room. They are much less decisive when the problem is a temperature gradient across a substrate.

And who has pricing power in your value chain today? If the answer is the layer above you, you are a supplier to the constraint rather than the holder of it, and no amount of sales effort changes that. Changing it requires owning a different problem.

The argument against. The obvious counter is that constraints get relieved rather than relocated. If eight-hundred-volt DC distribution, better microchannel cold plate design and warm-water operation together buy the industry another five years of headroom at the rack level, then the thermal window stays open longer and the shift to the package slips. That is a real possibility and anyone selling on an inflection should hold an explicit view on what would delay it. The honest version of this thesis is not that the package layer is inevitable next year. It is that the constraint is moving, the direction is legible, and a commercial organization built for the last position will be late to the next one whether it arrives in 2028 or 2033.

The version of this idea that is worth anything is not a slide with four eras on it. It is the habit of asking, every planning cycle, whether the thing you are best at is still the thing your customers cannot get enough of.