Impulse Space Is Building the Trucking Network for Low Earth Orbit

The launch market solved one hard problem: getting to orbit is now routine enough that ride-share manifests fill up months in advance. But orbit is not a single place. Low Earth orbit, sun-synchronous orbit, medium Earth orbit, geostationary transfer orbit — these are distinct destinations, separated by significant delta-v, and most launch vehicles deliver payloads to one of them and stop there. The payload that needs to end up somewhere else has to figure out the rest on its own.

That gap is the market Impulse Space is building into.

What Impulse Space Is Building

Founded by Tom Mueller — SpaceX’s first propulsion engineer and the person most responsible for the Merlin and Draco engine families — Impulse Space is developing in-space transportation vehicles, commonly called orbital transfer vehicles or OTVs. The company is working on two: Mira, a smaller vehicle designed for rapid, responsive in-space maneuvering in LEO, and Helios, a larger, high-energy vehicle capable of transfers to GEO and beyond.

The business model is essentially last-mile logistics for space. A customer launches their satellite on a rideshare, the satellite separates into a standard parking orbit, and Impulse’s OTV meets it there and delivers it to its operational orbit. For commercial satellite operators, this eliminates the need to carry large propulsion systems on the satellite itself, which either reduces mass or frees that mass for payload. For the market overall, it decouples launch vehicle selection from final orbit — you can book the cheapest or fastest ride to LEO and still end up exactly where you need to be.

The in-space transportation market is early. But the trajectory is clear: as launch costs continue to fall, the bottleneck in commercial space operations shifts from getting off the ground to getting where you actually need to go once you’re up there. Impulse is positioning itself at that bottleneck.

The Engineering Challenge Is Harder Than It Looks

Building an OTV sounds like a focused problem — propulsion, guidance and navigation, power, structure. But the requirements environment for an OTV is fundamentally different from a satellite or a launch vehicle, and that difference creates a specific engineering discipline challenge.

A satellite is designed for one mission. Its requirements are defined early, frozen relatively quickly, and the system is built to those requirements. A launch vehicle is more complex, but it also has a defined payload envelope — the rocket doesn’t care what’s inside the fairing. An OTV sits in the middle of these two paradigms and inherits the hard parts of both.

Every Impulse mission is different. The payload changes. The departure orbit changes. The target orbit changes. The timeline changes. And because the OTV is providing a service to a customer’s hardware, the interface requirements — mass, power, communications, separation mechanisms — change with each customer. The propulsion system has to be designed to handle a range of delta-v budgets across a range of payload configurations. The guidance, navigation, and control system has to execute orbital mechanics that are specific to each mission profile. And every time a customer updates their satellite design, Impulse’s requirements may need to update in response.

This is not a static requirements problem. It is a continuously evolving one, and the evolution is often driven by external factors the engineering team does not fully control.

Why Document-Based Requirements Management Breaks Here

Traditional requirements management in aerospace runs on documents. A requirements specification gets written, reviewed, baselined, and placed under configuration control. Change requests go through a formal process. Traceability is maintained in a requirements traceability matrix — typically a spreadsheet or a database table — that links requirements to design artifacts and test cases.

This process was designed for programs with long development timelines, stable contracts, and well-defined interfaces. It works reasonably well when the requirement set is large but static.

For Impulse, the problem is that requirements are not stable across the mission portfolio. A change to Helios’s propellant load affects delta-v performance, which affects the range of missions Helios can serve, which affects what customer interfaces the vehicle needs to support, which affects GNC modes, which may feed back into structural loads. These relationships are real, they are bidirectional, and they matter. A document-based system captures what the requirements say at a point in time. It does not make the dependencies between requirements visible, and it does not update when something changes upstream.

When you are designing a vehicle that will fly different missions for different customers, you need to understand the impact of a requirement change immediately, not after a configuration management cycle.

A Live System of Record for Propulsion and Mission Systems

Impulse Space uses Flow Engineering as a live shared system of record for their propulsion and mission systems work. Flow Engineering is an AI-native requirements management platform built for hardware and systems engineering teams, structured around graph-based models rather than documents. Requirements, design decisions, verification activities, and the relationships between them are all nodes in a connected model — which means when something changes, the downstream effects are visible immediately rather than discovered later in a design review.

For a team managing OTV requirements that span propulsion chemistry and performance, GNC algorithms and mode logic, and mission-specific customer interface definitions, the ability to trace a requirement change through all three domains simultaneously is not a convenience. It is a prerequisite for working at the pace the market demands.

The live, shared nature of the system matters as much as the graph structure. OTV development involves propulsion engineers, GNC engineers, systems engineers, and mission designers working in parallel. When a customer payload spec changes, the mission design team needs to understand the GNC implications, the propulsion team needs to know if the delta-v budget is still achievable, and the systems team needs to see whether interface requirements are still consistent. If those teams are working off different document versions, the integration risk accumulates silently until it surfaces at a review or, worse, during test.

A shared model means everyone is working against the same state of the system. Flow Engineering’s approach — keeping requirements alive and connected rather than archived in documents — fits the operational tempo of a startup building hardware for a multi-mission service model.

What the In-Space Logistics Market Demands From Systems Engineering

The in-space transportation market will not be won on propulsion performance alone, though propulsion clearly matters when Mueller is your founder. It will be won on the ability to execute missions reliably, repeatedly, and against changing customer requirements without large operational overhead.

That is a systems engineering problem as much as it is a hardware problem. The companies that will dominate this market will be the ones that can rapidly assess whether a new customer’s payload is compatible with their vehicle, understand what mission-specific requirements need to be generated or modified, and verify that the modified configuration meets performance and safety requirements — all on a timeline that fits a commercial launch schedule.

The traditional aerospace requirements process, built around formal reviews and document cycles measured in months, cannot support that cadence. The engineering discipline required here looks more like the software-influenced, model-based approach that has emerged in the new space industry over the past decade, applied to a domain — in-space propulsion and orbital mechanics — where the physics is unforgiving and verification matters.

Impulse is not the only company working in this space. Momentus, D-Orbit, and Exolaunch all offer in-space transportation or mission extension services. Each has its own approach to the vehicle design and the business model. What differentiates the serious contenders from the early-stage ventures will increasingly be operational reliability and the ability to serve a diverse customer set at scale — both of which depend on engineering process, not just engineering talent.

An Honest Assessment

Impulse Space has legitimate technical credibility. Mueller’s propulsion background is not symbolic; it directly informs the engine development work that makes high-energy OTV missions plausible at the cost points the commercial market can absorb. Mira has flown. Helios is in development. These are not paper vehicles.

The systems engineering challenge they face — requirements that span multiple coupled subsystems and change with each customer mission — is one of the genuinely hard problems in commercial space. It is not a problem that gets solved by hiring more engineers. It gets solved by building the right infrastructure for managing how those engineers’ work connects.

The choice to use a connected, AI-native system of record rather than a document-based one reflects a clear-eyed view of what the mission tempo requires. In a market where launch cadence is accelerating and customers expect their payloads delivered to precise orbits on schedule, the engineering backend has to match the pace of the commercial frontend. Static documents do not move fast enough. Live models do.

The in-space logistics market is not hypothetical anymore. The infrastructure to serve it is being built right now, and Impulse Space is one of the few teams with the propulsion expertise and the engineering discipline to build it at the level of reliability the market will eventually demand.