THE CASE AGAINST VERTICAL INTEGRATION

Vertical integration was not SpaceX's strategy so much as its necessity. In the early years, there was no reliable supply chain for the components a private launch company needed at the prices it could afford. Building in-house was not a philosophy but a workaround that happened to work exceptionally well.

The aerospace industry read this as a blueprint. The lesson seemed obvious: control your supply chain, control your costs, control your schedule. A generation of launch startups absorbed this logic and began building engines, avionics, and structures under one roof before they had launched anything at all.

The problem is that vertical integration requires scale to justify itself. When SpaceX was building Merlin engines in-house, it was also flying them dozens of times a year. The fixed costs of internal manufacturing dissolve into a high launch cadence. For a startup flying twice a year, those same fixed costs are ruinous.

A more honest reading of the SpaceX story is that vertical integration was one of several advantages operating simultaneously, and that it became beneficial only after the company had already achieved meaningful scale. The companies now attempting to replicate the model without the volume are not following a proven strategy. They are hoping the sequence does not matter. It does.