⚠ The Customer Learns the JobHigh threat

Co-design is intimate work. Marvell engineers spend years inside a customer's architecture, and both sides emerge knowing more than they did. Only one of them is the customer.

That is the structural problem with selling this way. A hyperscaler that has been through two accelerator generations with an outside partner has watched the floorplanning, the memory interface decisions, the SerDes trade-offs and the tape-out discipline at close range. It can hire against that knowledge, and it can run the next competition as a far better-informed buyer. The relationship that produced the revenue also produced the customer's ability to negotiate it down.

This is not hypothetical. The next generations of Amazon's Trainium are reported to have moved to Alchip¹, a design-services firm that competes on execution and price rather than on the depth of the relationship. Whatever the specific reason, the outcome is the one this page warns about: an incumbent partner did not hold the socket.

The number that would falsify the co-design thesis is retention across a node transition. If Marvell holds programs through the move to a new process — where the architecture genuinely changes and every assumption is reopened — the relationship is doing the work. If it loses them there, then what Marvell sells is a service, and services are re-bid.