Stoke Space: Full Rocket Reusability Drives Space App Store Moment

Stoke Space's quest for fully reusable rockets reveals a fundamental tension in innovation: the allure of immediate progress versus the enduring advantage of tackling foundational, difficult problems. This conversation with co-founders Andy Lapsa and Tom Feldman isn't just about rocket science; it's a masterclass in systems thinking applied to the hardest of engineering challenges. They expose how conventional industry wisdom, focused on incremental first-stage reuse, leaves the most critical and expensive component--the second stage--to be discarded. The hidden consequence? A bottleneck that stifles the very ubiquity and diversity of space applications that could define the next era of human endeavor. Anyone building a complex, long-term technical product will find profound lessons here on the strategic value of embracing upfront difficulty for delayed, but ultimately dominant, payoff. This is for founders and engineers who understand that true breakthroughs often lie in the unglamorous, unaddressed complexities others ignore.

The Unseen Bottleneck: Why Second-Stage Reusability is the Real Frontier

The rocket industry, much like many tech sectors, has a compelling narrative of progress. We celebrate the visible milestones: the successful launch, the first stage landing softly back on Earth. This has indeed been transformative, scaling the industry from a handful of launches to around 150 annually. But Andy Lapsa and Tom Feldman of Stoke Space cut through the industry's self-congratulatory buzz to highlight a critical, often overlooked, truth: the real barrier to a ubiquitous space economy isn't just getting to orbit, it's getting back reliably and affordably.

Their focus on full reusability, specifically targeting the second stage capsule, is a direct challenge to conventional wisdom. While the first stage endures the rigors of atmospheric ascent, the second stage faces a far more brutal reentry, traveling at 17,000 miles per hour and enduring temperatures exceeding 2,700 degrees Fahrenheit. This isn't a minor engineering hurdle; it's a multi-million dollar component that, until now, has been treated as a disposable luxury.

"The second stage goes the rest of the way to orbit typically rockets are thrown away completely in the last few years the industry has shown the ability to reuse the first stage which has been transformative... but the second stage is still thrown away on every single mission."

-- Tom Feldman

The implication is stark: by leaving the second stage disposable, the industry has artificially capped its own growth. The current launch cadence, dominated by constellations like Starlink, leaves little room for new applications or diverse payloads. Stoke Space’s strategy, therefore, isn't just about building a better rocket; it’s about fundamentally altering the economic and operational calculus of space access. They are betting that solving this seemingly intractable problem--the brutal reentry of the upper stage--will unlock an "iPhone app store moment" for space, where entirely new categories of innovation become possible precisely because the cost and availability barriers are removed. This requires a long-term vision, understanding that the immediate pain of solving reentry heat and deceleration will yield a massive competitive advantage in the years to come.

The Backyard Forge: How Obsession with Iteration Builds Unassailable Moats

The origin story of Stoke Space is a testament to the power of embracing difficulty and prioritizing rapid iteration from day one. Lapsa and Feldman didn't just have an idea; they had a conviction born from their experience at Blue Origin that full reusability was achievable and necessary. Yet, they faced the daunting reality of starting from scratch, with no established network and the looming shadow of a global pandemic. Their initial approach was a masterclass in lean, hardware-centric development, eschewing theoretical perfection for tangible progress.

Their early days, testing a prototype engine in a shipping container in Tom Feldman's backyard, highlight a core principle: speed of iteration is paramount in complex hardware development. Instead of waiting months for external suppliers, they built their own test stands, their own tooling, and crucially, their own manufacturing capabilities. This allowed them to shrink iteration cycles from months to days.

"The speed at which you can iterate becomes fundamentally important to your ability to do the hard thing as quick as possible... if you can't make parts yourself then your iteration cycles dependent on a out of house supplier."

-- Andy Lapsa

This isn't just about efficiency; it's about building a strategic moat. By controlling their entire development and manufacturing pipeline, from engine components to avionics, Stoke Space gains an unparalleled ability to learn and adapt. When an engine fails--an inevitable part of rocket development--they can diagnose, redesign, fabricate, and retest with a speed that outpaces competitors reliant on external vendors. This rapid feedback loop, fueled by their own infrastructure and a culture that embraces testing over perfect analysis, is the engine of their progress. It’s a strategy that requires significant upfront investment and a tolerance for immediate, visible "work" (welding, testing) with no immediate external validation, a discomfort that shields them from competitors who might opt for less demanding, less effective approaches.

The Software Bridge: Architecting for the Future, Not Just the Present

A surprising insight from the conversation is the critical role of software, not just in the rocket's flight, but in the very fabric of Stoke Space's operations and scalability. As Lapsa and Feldman articulate, the journey from a backyard garage operation to launching government payloads or even humans is fraught with painful transitions. This bridge, they argue, is often built with software.

The core challenge for a reusable rocket company is not just launching, but the complex logistics of turnaround: maintaining parts, scheduling preventative maintenance, and understanding the service life of components. This requires a level of data management and operational intelligence far beyond that of expendable rockets.

"We want to build is a vehicle that's going to go to orbit fly around and come back again and and we want to turn that thing around as fast as possible and go again and again and again... Did it work well? How long have the parts been in service? When do I need to go and do preventative maintenance?"

-- Andy Lapsa

Stoke Space's decision to build their own operational software, "Boltline," from the outset is a strategic move to manage this complexity. This internal tool allows them to integrate data from manufacturing, testing, and eventual flight operations, providing a unified view of their entire system. It’s a proactive approach, anticipating the needs of a high-cadence, reusable launch system rather than retrofitting solutions later. This early investment in software infrastructure not only streamlines current operations but lays the foundation for future scaling, enabling them to manage a fleet of rockets with efficiency and foresight. It’s a clear example of how investing in the less glamorous, but fundamentally enabling, systems (like software for operations) creates a durable advantage that compounds over time, allowing them to manage the complexity that would overwhelm less prepared organizations.

Key Action Items

• Embrace the "Second Stage" Problem: Identify the most difficult, often discarded, but critical component of your product or service. Focus R&D and strategic investment here, even if it means slower initial progress. (Longer-term investment, pays off in 3-5 years).
• Build Your Own Iteration Engine: Invest in internal capabilities for rapid prototyping, testing, and manufacturing. Reduce reliance on external suppliers for core development loops to accelerate learning. (Immediate action, pays off in 6-12 months).
• Develop Operational Software Early: Don't treat software as an afterthought for complex hardware. Build integrated systems to manage maintenance, logistics, and performance data from the outset. (Immediate action, pays off in 12-18 months).
• Quantify Reusability Value: Clearly define and communicate the economic and operational benefits of reusability (or your equivalent) beyond immediate cost savings, focusing on increased access, new applications, and market expansion. (Immediate action, ongoing).
• Practice Hearing "No": Cultivate resilience in fundraising and business development by expecting and learning from rejections, particularly when pursuing unconventional or technically challenging ventures. (Immediate action, ongoing).
• Invest in Foundational Technology: Prioritize deep technical challenges (e.g., high-performance engines, robust heat shields) that, while difficult, offer significant long-term competitive advantage and unlock future possibilities. (Longer-term investment, pays off in 2-4 years).
• Plan for Failure as a Learning Opportunity: Design processes and infrastructure that allow for rapid analysis and iteration following failures, rather than treating them solely as setbacks. (Immediate action, ongoing).