Component sellers still organize around server OEMs, because that is where the purchase order comes from. The decision moved upstream and most commercial teams have not followed it.
Ask a thermal, power or interconnect company where its opportunities live and you will get a list of server OEMs. That is not irrational. The purchase order does eventually come from an OEM or a rack integrator. But the decision that determines whether you can win has usually been made a layer above, in a document published by a silicon vendor, months before anyone in sourcing has heard your name.
What changed is that silicon vendors stopped shipping chips and started publishing rack-scale architectures. When a vendor releases a rack-scale reference design, it is not a product announcement. It is a specification of the thermal, mechanical, electrical and serviceability envelopes that every OEM and ODM building that platform will design inside. Heat removal per rack, coolant flow rate, connector and quick-disconnect approach, tray geometry, busbar cooling, service access. By the time an OEM is collecting quotes, the architectural questions have been closed for two quarters and the remaining conversation is about price and lead time.
The two models in the market are not equivalent, and confusing them costs new entrants a year. Some vendors maintain a recommended or approved vendor list for their rack-scale platforms. Getting onto that list is a qualification campaign run against the silicon vendor, not a sales campaign run against the OEM, and it is typically a year of validation work before a quote is even possible. Others publish an open specification. AMD’s Helios is the current reference case: built on the Open Compute Project’s Open Rack Wide with DC-MHS, UALink and UEC, seventy-two accelerators per rack across eighteen compute trays, on the order of 245 kW of heat removal at roughly 385 litres per minute, blind-mate quick disconnects, liquid cooling carried through the busbar. HPE came in as first major OEM partner and Schneider announced a validated Helios reference design in July 2026.
The commercial significance of that difference is hard to overstate. An open specification with no closed thermal vendor list attached is the one rack-scale architecture where the thermal decision is genuinely contestable on merit. A closed list is a gate you queue for. If you are a specialist with better physics and no incumbency, the open architecture is where twelve months of effort can actually change an outcome, and the closed one is where twelve months of effort buys you the right to compete later.
Timing is the second thing most plans get wrong. OEMs begin thermal design on a platform roughly twelve to eighteen months before it launches, which means the decisions for platforms shipping in 2028 are being made right now. When someone in this business says a sales cycle is twelve to eighteen months, that is not a hedge or a pessimistic forecast. It is the length of the design cycle, and a pipeline built on shorter assumptions is a pipeline that will be rebuilt from zero every two quarters.
The third thing, and the one that quietly consumes the most time, is geography. Architecture, mechanical execution and supplier qualification frequently sit in three different places, and often on different continents. A platform’s thermal architecture may be set in Texas while the mechanical execution and thermal qualification sit in Taipei, with the supplier audit run by a group that reports somewhere else again. By 2024, something like two-thirds of global AI server design contracts sat with Taipei ODMs. A warm relationship with a US-based OEM account team is not access to the people who lock a thermal envelope, and discovering that after eight months of pleasant meetings is one of the most common ways a design-in effort fails.
There is a diagnostic for all of this that takes an afternoon. Go through every active opportunity and record one field: was it entered at the architecture layer or the sourcing layer? If sourcing dominates, you are not losing on price. You are arriving after the decision, and the loss is being recorded in your own CRM as a price loss, which is precisely why it never gets fixed. Price losses get escalated to finance. Timing losses would get escalated to whoever owns coverage, if anyone ever labelled them correctly.
Buying access at the architecture layer requires the only currency that works there, which is a testable answer to a problem the customer has already written down. A model of their package. A test vehicle report. Published data. A paper in the right technical program. Architects will give time to someone who might reduce their risk, and they will give none at all to someone who wants to introduce a product. Enthusiasm, relationships and executive sponsorship are all useful later, and they buy nothing at this gate.
The argument against. None of which means the sourcing layer is the wrong door. For a mature product line with real volume, the OEM sourcing organization is exactly the right buyer, and a company that treats every opportunity as an architecture campaign will starve a business that needs revenue this year. The distinction worth holding is whether you are selling into a platform decision or a component decision. They sit at different layers, they are made by different people, and they are frequently funded out of different budgets. The mistake is not choosing one. It is running both through the same motion and wondering why the forecast keeps missing.