Key milestones in NASA’s Artemis moon program

Artemis II is scheduled for April 2026 as a roughly 10-day crewed lunar flyby with four astronauts (Reid Wiseman, Victor Glover, Christina Koch, Jeremy Hansen); Artemis I completed a 25-day uncrewed test flight in November 2022. NASA selected SpaceX’s Starship as the first commercial lunar lander and added Blue Origin as a second provider in 2023, but technical, cost and COVID-related delays pushed timelines (the crewed landing was previously delayed to 2027). In 2026 new NASA Administrator Jared Isaacman overhauled the program, scrapping the Lunar Gateway and adding an extra crewed mission to build operational experience ahead of a future surface landing.

Analysis

The programmatic pivot toward surface-focused architecture materially changes the vendor win-set: primes and midsize subsystem suppliers that specialize in surface power, thermal, ISRU (in-situ resource utilization) and ruggedized edge compute should see a compressed, higher-value procurement cadence over the next 1–3 years. That concentrates award timing and increases the premium on companies that can deliver COTS-to-flight heritage with short lead-times and low up‑front NRE; expect smaller suppliers with flexible manufacturing to command 10–20% price concessions versus traditional long‑cycle contractors.

Boeing’s exposure to large, single-vehicle integration work is now a source of convex downside: delays or scope reductions on monolithic programs translate to multi-quarter revenue vacuum without easy replacement, while modular suppliers (including compute and electronics hosts) can pick up incremental share quickly. Conversely, LMT/NOC are positioned to capture steady systems-integration and surface-habitat subsystem roles where program managers prefer stable control and proven supply chains, implying defensible multi-year revenue streams with lower execution beta.

The biggest non-obvious second-order is compute and data-center hardware demand tied to mission simulation, flight autonomy, and ground-in-the-loop ops — a procurement bucket that flows to high-density, ruggedized server vendors and could add a discrete 5–10% revenue tail for those suppliers if even a handful of contracts are awarded. Key risk windows are concentrated around near-term flight tests and follow-on award cycles; a high-profile technical success materially re-rates exposure to modular subsystem vendors, while a failure or political budget reprioritization would quickly re-price primes with single-program concentration.

Key Decisions for Investors

• Pair trade (12–24 months): Long NOC + LMT (equal notional, total 6–8% portfolio tilt) vs Short BA (50% notional of combined long). Rationale: capture stable systems-integration wins vs BA’s single-program integration risk. Target: 20–30% upside on long leg if award cadence materializes; downside: ~12–15% on budget shock—hedge short with 6–9 month calls.
• Event hedge (3–6 months): Buy near-term BA puts (1–3 month) into major mission test windows to protect portfolio exposure. Rationale: program test failures compress BA multiple quickly; cost of puts is expected to be modest vs one-off downside. Risk/reward: limited premium vs asymmetric downside protection.
• Convexity play (9–24 months): Long SMCI equity or buy deep‑out‑of‑the‑money 12–18 month calls (target 2–3x notional of expected contract upside). Rationale: capture on-board and ground compute contract wins; if awarded, upside >30% vs drawdown 20–25% if no awards. Position size: small, hit-oriented (1–2% portfolio).
• Selective long LMT (12–18 months): Buy 12–18 month calls or a modest overweight in cash for steady exposure to habitat/subsystem awards; target total return 15–25% if procurement flows as expected, with downside capped ~10–12% in a budget shock scenario—use trailing stop or hedged collar if conviction is low.