Skip to content

Podcast

#414 How SpaceX Works

Founders

Source ↗ ← All highlights
  • The 2008 Near Death And Flight 4 Turnaround
    • SpaceX almost died after three Falcon 1 failures and had funds for one try in 2008, then Flight 4 succeeded and NASA awarded a $1.6B cargo contract six weeks later.
    • That near-death forcing function turned into a defining company milestone and runway extension. Transcript: Max Olson Three Falcon 1 explosions between 2006 and 2008. By September 2008, SpaceX had funds for exactly one more attempt, and Tesla was weeks away from bankruptcy. Elon was borrowing money for rent. Then it worked. Flight 4 succeeded, and NASA’s $1.6 billion cargo contract followed six weeks later. (Time 0:03:02)
  • Atoms Are Cheap Process Is Pricey
    • SpaceX optimized for lowest cost to orbit by asking what rockets should cost from first principles, not accepting industry prices.
    • Elon found rocket materials were ~2% of price, revealing 98% went to process, markups, and custom designs to attack. Transcript: Max Olson What SpaceX has done more than anything is minimize the cost of getting things to space. The vision is humanity expanding across our solar system, but the lever is the cost of moving mass from Earth’s surface to orbit and beyond. Everything else, the launches, the landings, the reuse, serves that goal. When you study how companies hold advantages over time, consistently being the low-cost provider might be the hardest to maintain. The reason is that it has to be baked into everything you do. It cannot be an initiative or an afterthought. It has to shape how you design products, structure the company, and choose what to build. And as you’ll see in the book, it all started from the earliest days. Before starting SpaceX, Elon wanted to get to Mars, but he didn’t set out to build a rocket manufacturer. In 2001, he tried buying Russian ICBMs to get there, but the Russians quoted him ridiculous prices. So he famously reframed the question from first principles. What is a rocket made of? Aerospace grade aluminum alloys plus some titanium, copper and carbon fiber. And then I asked, what is the value of those materials on the commodity market? (Time 0:04:49)
  • Make Yourself The Supplier
    • Vertical integration captured the process tax by making ~80% of hardware in-house so SpaceX avoided supplier margin stacking.
    • NASA estimated Falcon 9 development cost ~$440M versus 3–10x with traditional contractors, showing the leverage. Transcript: Max Olson Once SpaceX concluded that atoms were cheap and process was expensive, vertical integration followed almost inevitably. That’s a great line. SpaceX concluded that atoms were cheap and process was expensive, and so therefore vertical integration followed almost inevitably. The next subheading talks about this, becoming your own supplier. If materials are cheap and the tax is all process and overhead, you need to control the process to capture the savings. You cannot negotiate your way to a 10x cost reduction with suppliers who have profits baked in at every tier. So SpaceX became its own supplier. By building 80% of its hardware internally, engines, structures, avionics, software, and key ground systems, SpaceX collapsed the traditional aerospace stack. They outsource raw materials and commodity parts and make everything else themselves. That’s something SpaceX didn’t originally set out to do, one engineer noted, but was driven by suppliers’ high prices. This wasn’t an ideological commitment to doing everything in-house. It was the result of suppliers repeatedly quoting prices and timelines incompatible with SpaceX’s cost targets. The benefits compound. When several tiers each add 15% margin, total cost multiplies through the layers. A NASA study found SpaceX developed Falcon 9 for roughly $440 million. (Time 0:09:35)
  • Force Customers To Standardize To Gain Scale
    • Build a standardized platform customers must adapt to so you unlock manufacturing volume and learning curves.
    • SpaceX forced customers to design to Falcon specs (bolt circles, connectors), turning rocket into a Model T produced in volume. Transcript: Max Olson The only way to get volume is to standardize, build a common platform that customers have to adapt to. The existing approach was bespoke vehicles per mission, custom adapters, mission-specific modifications, multiple vehicle families. This optimizes each mission at the expense of manufacturing scale. SpaceX bet the opposite, that cost savings from standardization would exceed the value of customization. Yes, customers wanted custom solutions, but they wanted low prices even more. Force them to choose, and they will adapt. The Falcon 9 became the industry’s Model T, one rocket built in volume. Same nine Merlin engines on the first stage, same vacuum Merlin on the second. Same structure, same diameter, same aluminum, lithium alloy, same welding methods, same avionics, same ground systems. Even Falcon Heavy is just three Falcon 9 first stages strapped together with a shared upper stage. A scaled variant from the same core, not a new vehicle. SpaceX published a Falcon User’s Guide, which defined bolt circles, electrical connectors, and fairing environments. Customers designed to SpaceX’s spec instead of demanding customizations. Satellite orbits adjusted to Falcon performance curves. (Time 0:12:36)
  • The Cost Flywheel Is Systemic Not Singular
    • Three interlocking choices—first principles design, vertical integration, and standardization—create a reinforcing flywheel that makes each flight cheaper.
    • Lower prices gain market share, volume lowers cost, enabling reuse and faster learning. Transcript: Max Olson You can probably see why all three tactics were necessary. First principles identified the waste. Vertical integration provided the control to eliminate it. Standardization allowed the volume to make that control profitable. Without all three, the system breaks. They work together so that each flight makes the next one cheaper. (Time 0:15:11)
  • Use Reality As Your Primary Validation Tool
    • SpaceX uses rapid build-test-learn instead of exhaustive up-front analysis, treating failures as data to discover real-world interactions.
    • Prototypes and flights reveal emergent behaviors that models miss, accelerating design maturity. Transcript: Max Olson If the strategy is to rethink everything from first principles, how do you actually execute that without major consequential failures? The standard answer is to analyze exhaustively before building. So he’s going to describe the standard answer, and I love how he talks about SpaceX literally inverted this. Traditional aerospace follows this path religiously. A NASA report on the Commercial Crew Program noted that Boeing utilizes a well-established systems engineering methodology, targeted at an initial investment in engineering studies And analysis to mature the system design prior to building and testing. Must be really fun to read these kind of reports. Plan extensively, freeze requirements early. Minimize test failures. This is the measure twice, cut once approach. SpaceX inverted this. Here’s the problem with the traditional approach. You can’t think your way to perfect solutions for problems you don’t fully understand. That’s another bar. You can’t think your way to perfect solutions for problems you don’t fully understand. Your model is always wrong in the ways you don’t know yet. Complex systems have emergent behaviors that only appear when the pieces are actually bolted together. This is the paradox of first principle design. If you’re questioning every inherited assumption, which you should, you’re venturing into territory where analysis alone can’t tell you what works. The physics might be known, but how the physics will interact with your specific materials, your specific manufacturing tolerances, your specific assembly process, that’s not Something you could derive from first principles. That’s something you have to discover. And so what SpaceX does instead is they use reality as their validation tool. The alternative is to use reality as your primary validation tool. SpaceX focuses on rapidly iterating through a build, test, learn approach that drives modifications towards design maturity. (Time 0:16:33)
  • Increase Production Rate To Accelerate Iteration
    • Raise production rate so you can afford many hardware-rich iterations and push prototypes to failure.
    • Choosing stainless steel for Starship and in-house Raptor output made cheap, fast builds and sacrificial tests feasible. Transcript: Max Olson Iteration only works if you can afford many attempts. This is where SpaceX’s hardware-rich approach becomes essential. This is what Elon says about this. A high production rate solves many ills. He has said this repeatedly. He continues, any given technology development is how many iterations do you have and what’s your time and progress between iterations. So if you have a high production rate, you can have a lot of iterations. You can try a lot of different things. If you have a small number of engines, then you have to be much more conservative because you can’t risk blowing them up. SpaceX builds many cheaper prototypes, hardware-rich fleets of test articles. They’d rather have 10 rough versions to blow up than one polished version they’re flayed to break. This can lead to specific design decisions like using stainless steel for Starship, which is cheap, easy to weld, and can be welded in a tent, by the way, instead of carbon fiber, which Is expensive and requires giant autoclaves. Vertical integration really helps enable this. When you own the factory, you can build fast without waiting on vendors. When you own 3D printing capability, you can produce parts on an ad hoc basis. When you can manufacture Raptor engines at high volume, losing one to a test failure doesn’t set you back months. (Time 0:21:29)
  • Design Culture To Enable Your Strategy
    • Hire and shape people to fit the operating system you need; culture is the mechanism that lets tactics function.
    • SpaceX recruited missionaries with Mars vision, forcing prioritization and attracting engineers willing to fail visibly. Transcript: Max Olson An engineering process that treats failure as data only works if the engineers themselves believe it. A system that pushes to the edge of what’s possible only survives if the people doing the pushing can handle the intensity. The practices described here are the mechanism, but they’re powered by something else entirely. And that goes to his next subheading, which is the people. And so Max writes back to my original point, the practices I’ve described so far aren’t secret. So why can’t others just copy them? The standard answer is organizational inertia, bureaucracy, risk aversion, etc. And yet there’s true to all of these, but it’s not the whole story. The answer is that strategy doesn’t exist in isolation. The same playbook in a different environment would produce different results or nothing at all. You can’t copy strategy without transplanting the conditions that make them work. A fail fast culture needs people willing to fail visibly. A first principles approach requires people willing to question experts. Skip level truth seeking requires people willing to deliver bad news directly to the CEO. The variable I’ve been circling around is people, not in the bland HR sense of our people are our greatest asset. In the structural sense, who shows up, what they believe, and what behaviors they’re willing to accept from each other. (Time 0:24:21)
  • Hammer The Tip Of The Spear
    • Attack the single biggest constraint relentlessly and escalate blockers until resolved to unlock downstream progress.
    • Elon focused company resources on Raptor production when it bottlenecked Starship, shifting priorities until throughput increased. Transcript: Max Olson The first one, meme number one, tip of the spear focus. Always identify and attack the biggest limiter. Don’t spread effort across secondary problems. Laser in on the single constraint that if removed would unlock everything downstream. That is true at every level. Each SpaceX site has a single dominating objective to simplify prioritization. A NASA manager who visited SpaceX observed that when a new problem appears, it looks like a flash mob in the hallway. When a system-level bottleneck is identified, it gets disproportionate resources. When Starship development was bottlenecked on Raptor engine production, that became the company’s focus. Not propellant loading, not heat shields, not launch infrastructure. Raptors. Elon gave it absolute focus, daily updates, memos to the company, resources redirected from elsewhere. Once engine production broke through, attention shifted to the next constraint. The limiter always gets the hammer. Meme number two, push through roadblocks. A roadblock isn’t a reason, it’s a problem statement. You’re either clear it or you escalate it until someone does. Admitting you’re blocked isn’t shameful at SpaceX. It’s expected. Hiding a blocker is what gets you in trouble. As one engineer described it, solving blockers move the needle forward on several projects. The cultural expectation is honesty about what’s not working and the relentless effort to fix it. That’s another good line. I gotta repeat that. (Time 0:32:06)
  • Question Requirements And Delete Parts
    • Treat every requirement as a hypothesis to interrogate and delete unnecessary complexity aggressively.
    • Grid fins dropped folding mechanisms after sim showed fixed fins acceptable—“the best part is no part.” Transcript: Max Olson Design something, throw it over the wall, and let someone else figure out how to actually make it at spacex the person who drew the bracket is the person who welds it meme number four question Requirements every constraint customer regulatory internal is treated as a hypothesis to interrogate not a fact to accept this is the embodiment of first principle thinking here’s An example falcon 9’s grid fins were originally designed to fold like traditional aerospace grid fins. The folding mechanism reduced drag during ascent, which seemed obviously necessary. SpaceX questioned whether it was worth the mass and complexity. Simulations showed fixed fins were acceptable, so they deleted the mechanism entirely. This is what Elon said. The best part is no part. The best process is no process. Engineers are explicitly told that requirements from quote unquote smart people are the most dangerous because nobody thinks to question them. Every requirement must have an owner, a specific person who can defend why it exists. If the owner can’t explain it or the original reason no longer applies, that requirement gets deleted. This turns into Elon’s now well-known rule. If you are not adding back at least 10% of the requirements you deleted, you aren’t deleting enough. (Time 0:34:20)