#414 How SpaceX Works

What It Covers

Max Olson's introduction essay for his forthcoming book *SpaceX Foundation* analyzes why SpaceX launched more mass to orbit in 2025 than every other provider combined, breaking down the three mutually reinforcing systems — cost strategy, engineering methodology, and culture — that competitors cannot replicate individually.

Key Questions Answered

• •The Idiot Index: Raw materials represent only 2% of a rocket's cost, meaning 98 cents of every dollar goes to process overhead, supplier markup stacking (15–30% per tier), and expendable hardware. Identifying this ratio — what Elon calls the idiot index — is the starting point for any first-principles cost reduction effort in capital-intensive manufacturing.
• •Vertical Integration as Cost Capture: SpaceX builds 80% of its hardware internally — engines, avionics, structures, software — collapsing multi-tier supplier chains. A NASA study estimated Falcon 9 development cost $440M versus $1.3–4.4B using traditional contractors. Vertical integration also compresses iteration cycles from multi-year supplier retooling to weeks within the same building.
• •Standardization Creates the Volume Flywheel: SpaceX publishes a fixed Falcon user's guide; customers adapt satellites to the rocket, not the reverse. Building 40 identical Falcon 9s annually creates automotive-style manufacturing learning curves impossible at single-digit launch cadences. Reusing the same physical boosters 20-plus times adds an operational learning curve steeper than the manufacturing one.
• •Fail Fast With Tiered Risk Profiles: SpaceX separates development risk from operational risk explicitly. Dragon crew vehicles carry maximum safety margins. Falcon 9 allows landing failures but not ascent failures. Starship development treats explosions as precision data points. This structure lets one organization run aggressive iteration and conservative operations simultaneously without cultural contradiction.
• •Tip-of-the-Spear Resource Allocation: When Starship was bottlenecked on Raptor engine production, SpaceX redirected company-wide resources — daily executive updates, memos, personnel — exclusively to that constraint until resolved, then shifted focus to the next limiter. This practice of identifying the single binding constraint and applying disproportionate resources prevents effort diffusion across secondary problems.