The United States Navy has laid out its technology priorities for the coming years, with its chief technology officer making clear that the branch is rethinking how it identifies and funds innovation. TechCrunch spoke with Navy CTO Justin Fanelli about a strategy that leans on co-investment alongside venture capital rather than bearing the cost of early-stage research alone, and that frames the military as a partner to the startup ecosystem rather than a patron funding work from scratch.
To understand why this matters, it helps to understand how unusual this posture is by historical standards. For most of the twentieth century, the Defense Department was the primary engine of foundational technology research in the United States. The internet, GPS, and touchscreen interfaces all carry fingerprints of defense funding at their origins. The arrangement was straightforward: the military had problems, it funded research to solve them, and commercial applications followed later as a kind of byproduct. That model worked when the Pentagon could credibly claim to be operating at the technological frontier.
That claim is harder to make today. Commercial technology, driven by enormous private capital flows and intense competition among hyperscalers and well-funded startups, now routinely outpaces what any government laboratory can develop on its own timeline or budget. The result has been a years-long reckoning inside the defense establishment about where the military's leverage actually lies. The answer an increasing number of officials have landed on is procurement power and operational scale rather than basic research funding.
Fanelli's comments to TechCrunch reflect that shift in explicit terms. Co-investing alongside venture capital means the Navy enters the picture after private investors have already placed early bets, reducing the branch's exposure to the highest-risk phase of technology development while preserving its ability to shape what gets built and, crucially, to become a customer once a technology matures. This is a meaningfully different posture from programs like DARPA, which were designed precisely to fund work too speculative for private investors to touch. The suggestion here is that for a wide range of technologies the Navy cares about, private capital is now willing to go first.
The recently disclosed deal TechCrunch highlighted — a roughly 562 million dollar contract for autonomous refueling — illustrates where that logic leads in practice. Autonomous systems that can refuel naval vessels without human intervention address a genuine operational constraint: refueling at sea is dangerous, personnel-intensive, and limits operational tempo. That a contract of that scale exists signals that at least some autonomous technology has matured to the point where the Navy is willing to commit serious procurement dollars. For the startup and venture community, a deal of that size functions as a proof point that defense contracts in this space are real and reachable, not just theoretical.
The wish list Fanelli described to TechCrunch spans areas that have become something close to a standard inventory for any serious technology institution right now: artificial intelligence, quantum computing, and presumably adjacent areas like autonomy and advanced communications. The fact that the Navy is publishing this list openly is itself part of the strategy. Defense acquisition has historically been opaque to founders who lack connections to the procurement world, and that opacity has pushed talent and capital toward consumer and enterprise technology even when defense problems were technically interesting. Making the wish list legible is an attempt to lower that barrier.
The likely consequences run in several directions. For founders building in AI and autonomy, explicit Navy interest functions as a market signal with real money behind it. Defense is not a simple customer — the contracting process is notoriously slow and complex, and the regulatory and classification environments are demanding — but for companies already navigating that world, confirmation of priorities at the CTO level provides useful direction. For venture firms with defense-adjacent portfolios, co-investment from the Navy represents not just capital but a pathway to one of the more durable customers a technology company can find.
For the broader defense industrial base, the shift carries some tension. Traditional prime contractors have long served as the intermediary layer between the Pentagon and innovative smaller firms, often acquiring startups or subcontracting to them. A model in which the Navy co-invests directly alongside VCs and maintains its own technology wish list could compress that intermediary role over time, or at least change the terms on which primes engage with the startup ecosystem.
What to watch for next is whether the co-investment model produces contracts at the pace its logic implies, or whether institutional friction inside the Navy's acquisition bureaucracy slows the pipeline from promising startup to funded program. The gap between a CTO's stated priorities and what actually gets bought has historically been wide in defense. Watching how many of the companies that receive co-investment signals eventually close meaningful procurement deals will be the real measure of whether this represents a genuine structural shift or a sophisticated form of window shopping.
