The MultiDomain Operations Gap: Where Defense Tech Investors Should Actually Be Looking

Multi-domain operations get a lot of air time in Pentagon strategy documents. They get far less serious attention from venture investors, most of whom treat MDO as buzzword wallpaper rather than a genuine investment signal.

That's a mistake worth examining.

The U.S. military's stated goal with MDO is straightforward: operate across land, sea, air, space, and cyber simultaneously, with enough speed and integration that adversaries can't respond effectively. The problem is that each of those domains runs on different data protocols, different classification levels, different program offices, and different procurement timelines. Synchronizing them in real time is less a software problem than an organizational physics problem, and the DoD has been mostly losing that battle.

Where does that leave investors?

The Integration Layer Is Where the Money Is

Most defense tech startups pitch point solutions: a better drone sensor, a faster satellite communications terminal, a more accurate positioning system. Those are real products with real customers. But the compounding failure in MDO isn't capability, the U.S. military has extraordinary individual capabilities in every domain. The failure is translating those capabilities into coordinated action faster than an adversary can exploit the seams.

That translation problem requires software that can ingest data from radically different sources (many classified at different levels), reason over it in something close to real time, and surface actionable output to commanders who have seconds to decide. Startups working on cross-domain data fusion, low-latency edge AI inference, and secure multi-level communications are sitting in exactly this gap.

Palantir built a substantial portion of its early DoD business on this thesis, though it came at it from an intelligence angle rather than a tactical operations angle. The opportunity now is more granular: purpose-built systems for specific joint force integration problems that are too narrow for a prime contractor to prioritize but too consequential for the military to ignore.

The Procurement Mismatch Is Actually an Opportunity

Here's the uncomfortable reality about MDO investment: the programs that need the technology don't always have budgets aligned to buy it. Joint all-domain command and control (JADC2) is the DoD's umbrella initiative to solve exactly this problem, but JADC2 is not a program of record with a clean acquisition path. It's a concept being executed through a loose collection of service-specific programs, the Army's Project Convergence, the Air Force's Advanced Battle Management System, the Navy's Project Overmatch.

For a startup, that means no single customer to land. You need relationships across multiple services simultaneously, which is expensive and slow.

The smarter play is startups that have identified one of these service programs as a primary beachhead and built their product to interoperate with the others through open standards (specifically, the DoD's push toward MOSA, the Modular Open Systems Approach). Win one service program with a compliant architecture, and you have a credible path to the others without a full re-engineering cycle.

graph TD
    A[Startup Product] --> B(Primary Service Beachhead)
    B --> C{MOSA-Compliant Interface}
    C --> D[Army: Project Convergence]
    C --> E[Air Force: ABMS]
    C --> F[Navy: Project Overmatch]
    C --> G[SOCOM / Other Combatant Commands]

This architecture is what good MDO-focused startups should be building toward. Investors should be asking for it explicitly in diligence.

What Diligence Actually Looks Like Here

Vetting an MDO-adjacent startup requires different questions than a typical defense tech deal. A few that matter:

Does the product operate at classification levels below Secret? Unclassified or CUI-level systems can be deployed, iterated, and sold across allied networks. Secret-only systems create FOCI and export control headaches from day one.

Who is the end user, and have they tested it in an operationally realistic environment? A lot of MDO-adjacent startups have impressive lab demos and zero field validation. Joint exercises like Project Convergence Capstone events exist precisely to test this integration. Has the startup participated?

What happens when the network goes down? Resilience at the edge is non-negotiable for any MDO system. Startups that assume persistent connectivity are building for the wrong threat environment.

None of these questions are exotic. But they filter out a significant portion of pitches that look promising on a slide deck and fall apart against actual operational requirements.

Why Now

The 2022 National Defense Strategy named China as the pacing threat and explicitly tied readiness to multi-domain integration. That political commitment is starting to show up as real budget, the FY2026 defense budget proposal included substantial increases for JADC2-related efforts, and the services are under real pressure to show convergence progress.

Startups solving MDO integration problems have a window where demand is genuine, competition from primes is limited (they're too slow and too siloed), and the DoD's appetite for non-traditional vendors is higher than it's been in decades.

The opportunity isn't in any single domain. It's in the space between them.