Context

Boom Supersonic founder and CEO Blake Scholl talks with the All-In hosts about building the first privately developed supersonic jet, the public collapse of Boom's engine partnership with Rolls-Royce, and how the resulting forced pivot into building engines in-house became an unexpectedly larger business than the airplane itself. The episode matters to PMs and founders because it's a concrete case study in how a failure widely read as fatal ("people declared Boom dead") became the source of the company's most commercially validated product, and in how a specific technical reframing (boomless cruise) turned a decades-old regulatory ban into something arguably achievable within months.

The Big Idea

A partnership failure that Boom's own founder calls "one of the dumbest things I ever did," outsourcing engine development to Rolls-Royce, forced a from-scratch, in-house engine effort that turned out to have a second, larger, faster-monetizing application (behind-the-meter data center power generation) than the supersonic jet it was originally built for.

Scholl's own framing of the reversal: "in a bizarre twist of history, the thing that everyone said would kill us, that we didn't have a big company make as an engine, actually turns out to be the thing that makes a supersonic startup financially viable." The data center version of the engine, essentially the same core with the fan removed and a generator attached, can deliver 42 megawatts of power from a couple of trailers, without water cooling, because it's designed to run hot at high power for sustained Mach 1.7 flight.

Key Insights

The forced in-house pivot uncovered a second product line worth more near-term than the original one

Scholl is explicit about the sequence: after the Rolls-Royce partnership ended publicly and badly, Boom committed to building "our own engine from scratch," which meant developing genuinely new digital design and manufacturing capability rather than just replicating an off-the-shelf part. Once that engine core existed, removing the front fan and adding a rear generator converted it directly into a data center power unit, and Scholl describes the resulting demand as "tens of gigawatts" already in his inbox, ahead of the supersonic jet itself reaching commercial service. The generalizable lesson: a capability built to solve one problem under duress can reveal an adjacent, sometimes larger, market that wouldn't have been visible if the original outsourcing plan had succeeded.

A specific atmospheric technique, not new regulation, is what actually reopened supersonic flight

Boom's "boomless cruise" approach doesn't eliminate the sonic boom, it uses "the natural refractive power of the atmosphere to redirect the sonic boom upwards" so it never reaches the ground, up to roughly Mach 1.3 (about 50% faster than current subsonic flight). Scholl's framing of why this mattered regulatorily: the 1973 US ban on supersonic flight was specifically a ban on audible sonic booms reaching the ground, so a genuinely boomless technique made the ban's original rationale moot, which is why the resulting Supersonic Legalization Act passed the House and moved through Senate committee unanimously rather than along partisan lines. The lesson: sometimes the fastest path past a long-standing regulatory barrier isn't lobbying for an exception, it's a technical solution that removes the specific harm the regulation was written to prevent.

The company treats speed of iteration as more important than hitting a stated deadline

Asked directly for a date commercial supersonic flights would be available, Scholl gives a target (potentially 2030) while explicitly reframing the tradeoff: "it's more important to be fast than to be predictable... we're moving as fast as we can, and we'll make sure that it's available at the earliest date that it's physically possible." This is a specific, stated prioritization choice for an ambitious, technically uncertain program: optimize for minimizing actual time-to-outcome even at the cost of being able to commit confidently to a fixed date, rather than padding a public timeline to protect predictability.

A single viral, well-timed moment (a tweet, then a flight to DC) compressed a regulatory process from years to months

Scholl's specific timeline: Boom broke the sound barrier on a Monday, he tweeted about it, Elon Musk reposted it, he flew to Washington that night, received a White House invitation by Tuesday, had an airplane model placed in the Oval Office by Thursday, and the executive order legalizing boomless supersonic flight was signed 115 days later, a timeline he calls slow in isolation but faster than he believes it would have been under different circumstances. This is a concrete example of how a single, highly visible technical demonstration, combined with fast follow-through on building relationships in the moment, can compress a regulatory or institutional process that might otherwise take years.

Reindustrialization framing was used deliberately to justify building manufacturing capability, not just buying it

Scholl states the company's manufacturing philosophy explicitly as "the exact opposite of what you find in every legacy big company," which he characterizes as heavy outsourcing that ends up "spinning out your crown jewels." Boom's stated alternative: manufacture engine parts, including the most difficult components like turbine blades and vanes, in-house from raw materials, using what he describes as the most advanced available digital design and manufacturing tools, on the theory that inventing new manufacturing technique, not just re-shoring old techniques lost to offshoring, is what "reindustrializing America" should actually mean. This is a specific, stated position in the ongoing build-versus-buy debate for critical components: treat the in-house manufacturing capability itself as a strategic asset worth building, not just a stopgap after a partner relationship failed.

Mental Models & Frameworks

Reframe a "we have to build it ourselves" failure as a capability-creation opportunity

When an outsourcing or partnership plan for a critical component collapses, the immediate framing is usually damage control. Scholl's case suggests a more useful question to ask at that moment: what adjacent capabilities or products become possible once you're forced to build genuine in-house expertise in that component, capabilities that wouldn't exist if the original partnership had simply succeeded as planned.

Solve the specific harm a regulation targets, not just the regulation itself

Rather than treating a long-standing regulatory ban as something to lobby around or seek exceptions to, identify the specific harm the regulation was originally written to prevent (audible sonic booms reaching the ground) and ask whether a technical solution can remove that harm directly. A regulation whose original rationale has been technically mooted is far easier to get repealed with broad, non-partisan support than one you're asking to be waived despite the harm still existing.

Practical Application

After a critical vendor or partnership failure, explicitly search for a second market before just rebuilding the original plan

If your team is forced to build a capability in-house after an outsourcing plan falls through, before simply re-executing the original roadmap, deliberately ask whether the resulting capability has value outside its original intended use, following Boom's data center power business emerging directly from its forced engine effort.

When facing a long-standing barrier, ask whether the barrier's original justification can be technically removed

Before assuming a regulatory, policy, or organizational barrier requires negotiation or a special exception, check whether the specific harm or risk that justified the barrier in the first place can be eliminated through a technical or process change, which can convert an adversarial ask into a broadly agreeable one.

State explicitly whether your team is optimizing for predictable timelines or for minimized total time

For any ambitious, technically uncertain initiative, decide and communicate explicitly whether the priority is hitting a stated deadline reliably or minimizing actual time-to-outcome even if that means less certainty about the date, since these two priorities call for different planning, communication, and risk-tolerance choices, and conflating them tends to produce both a missed deadline and unnecessary internal pressure.

Bottom Line

Blake Scholl's account of Boom Supersonic's engine crisis shows that a partnership failure forcing a company to build a critical capability in-house can uncover a second, valuable business that wouldn't have existed otherwise, and that removing a regulation's original justification through a genuine technical fix, rather than lobbying around it, can turn a decades-old, seemingly permanent barrier into something a divided Congress passes unanimously.