For most of defense technology history, building for both commercial and defense markets was a strategic mistake. The markets had different requirements, different procurement timelines, different product specifications, and different cultures. Companies that tried to serve both typically did neither well — they got stuck in no-man's land where their product was too specialized for commercial buyers and too slow and insufficiently ruggedized for government buyers.
That dynamic is changing. And understanding why it's changing — and where the change is real versus where it's still marketing — is the core of how we think about dual-use investment.
Why the Old Separation Made Sense
The commercial-defense separation was never arbitrary. It reflected real product and market differences.
Commercial technology buyers optimize for unit economics, user experience, and time to deployment. Defense buyers optimize for reliability under stress, interoperability with existing systems, and survivability in operational environments. The environmental and performance specifications for military systems — MIL-SPEC — exist because commercial products routinely fail in the conditions military equipment has to operate in. A laptop that works in an air-conditioned office building doesn't necessarily function after a transport aircraft decompression event at altitude or in a desert environment with significant vibration and sand ingestion.
Add to that the structural differences in procurement: commercial SaaS sales cycles measured in weeks or months versus defense procurement cycles measured in years. The commercial playbook of iterating fast, releasing often, and adjusting based on user feedback is incompatible with programs of record that lock requirements years before deployment.
What's Changed
The separation is eroding in specific technology domains. Not universally — a fighter jet fire control system and a consumer app are still different businesses — but in software-intensive applications, the convergence is real and investment-relevant.
Machine learning infrastructure. The compute and software infrastructure underlying AI systems is functionally identical in commercial and defense applications. The same training pipelines, inference optimization techniques, and model evaluation frameworks apply whether you're optimizing an ad targeting algorithm or a sensor fusion system for autonomous vehicles. Companies building best-in-class ML infrastructure can sell to both markets from a common technology base.
Geospatial analytics. Location intelligence, mapping, and geospatial analysis tools built for commercial applications — logistics optimization, supply chain management, infrastructure monitoring — translate directly to defense applications at the software layer. The data sources differ; the analytical capabilities don't. Companies in this space have demonstrated that the same core product, with different data access and user interface configurations, can serve commercial and military customers.
Cybersecurity. The threat landscape for commercial enterprises and defense contractors is increasingly similar in kind if not in sophistication. Zero-trust architectures, vulnerability management, and threat intelligence products built to commercial standards meet or approach the requirements for non-classified defense environments. The CMMC framework has explicitly designed itself to align with commercial cybersecurity standards rather than creating a completely separate government regime.
The Investment Case
Genuine dual-use companies have a specific financial advantage over pure-play defense companies: they can generate commercial revenue on commercial sales timelines, which funds the development and business development work required to win government contracts. This compresses the capital requirement for reaching a self-sustaining revenue position.
It also provides structural resilience. A company with commercial revenue isn't existentially dependent on a single government program decision or budget cycle. Defense-only companies that get a key contract cancelled face a potential revenue cliff that dual-use companies can manage through commercial business.
We've observed, across our portfolio, that the companies with commercial revenue tend to negotiate better government contract terms. They have alternatives. They can walk away from bad deals. That negotiating position produces better outcomes — financially and operationally — than companies that need any contract they can get.
Where It's Still Hard
Dual-use isn't magic. The domains where it genuinely works are defined by software intensity and standards convergence. In hardware-intensive domains — physical weapons systems, specialized vehicles, advanced sensors — the specifications diverge enough that a common product serving both markets remains difficult to execute.
There's also a strategic coherence requirement that gets underestimated. "Dual-use" is only a real thesis if the technical differentiation that makes you valuable in the commercial market also makes you valuable in the defense market. Companies that frame themselves as dual-use primarily to attract a broader set of investors — rather than because their core technology genuinely crosses over — tend to underperform in both markets.
When we evaluate dual-use companies, we ask specifically: does the same IP, the same team, and the same product roadmap serve both markets, or do you functionally need separate businesses? The answer to that question determines whether dual-use is a strength or a distraction. For the companies where it's genuinely a strength, it's one of the most attractive investment structures in the defense tech landscape.
