The U.S. Navy spends around $150 billion annually on technology and equipment, and its chief technology officer is now publishing a roadmap to help startups and investors figure out where that money will flow in the coming years. Justin Fanelli, the Department of Navy's CTO, shared an updated list of technology priorities this week in an interview with TechCrunch, speaking from his phone while literally sprinting to catch a classified flight with an undisclosed destination. Over the past three and a half years, he's worked to reshape how the Navy buys from private companies, moving away from what he calls a "spaghetti chart" of entry points toward a more streamlined funnel where successful firms get pulled into the Navy's technology base as enterprise services.
The Navy's updated priority list breaks into five areas: applied AI for tasks like sensor fusion, targeting, and autonomous operations; quantum information science for navigation and secure communications; advanced networking to move data across degraded connections; electromagnetic spectrum operations that adapt in contested conditions; and digital engineering tools like open APIs and zero-trust architecture. Recent purchases illustrate the shift in practice. The Navy awarded a $562 million contract this month for the MQ-25 Stingray autonomous refueling drone, bought edge compute hardware from Armada, brought in Gecko Robotics for inspection work, and tapped Domino Data Lab to run its machine learning pipeline. In one case Fanelli highlighted, the Navy replaced a defense contractor's delayed shipboard camera system with commercial cameras and software from Applied Intuition, shaving roughly four years off the timeline and expanding deployment to more vessels than originally planned.
The stage at which the Navy enters has shifted markedly. "We mostly buy Series D through F type companies," Fanelli told TechCrunch, explaining that the Navy used to fund its own early-stage research to cover the seed-through-Series-B gap but is now trying to hand that responsibility to commercial investors instead. He described the Navy's approach as "co-investment," where it waits for companies to mature a product on their own before purchasing it, rather than funding early research directly. Taking an equity stake remains rare, he noted, and represents the most aggressive version of that strategy. The priorities document, vetted by unnamed venture investors before release, exists partly to fulfill what Fanelli calls the Navy's responsibility: if it won't fund early-stage work itself, it must "cast a cleaner signal" for private capital to follow.
The approach reflects a broader shift in how defense procurement works when budget cycles span years and new tools only survive if they replace something already being paid for. Fanelli explained that promising technologies most often fail inside the Navy not for technical reasons but budgetary ones—a system only sticks around if it "turns off" an existing line item. Buying decisions run through a small source selection committee rather than the sprawling review process outsiders might imagine, a structure Fanelli said is meant to keep decisions merit-based rather than layered with approvals. The updated priorities come with a caveat: the memo notes they're not funding commitments, don't rank individual programs, and "will change based on emergent, near-term, and long-term needs." Instead, the list functions as a roadmap companies and investors can plan around, so capital deployed today has somewhere to land inside the Navy in a couple of years. For founders and funders in defense tech, the signal is deliberate—and it's growing louder each year Fanelli sends it. The real test, though, will be whether venture-backed companies can navigate the tension between rapid iteration and the kind of long-term budget displacement the Navy requires to make new capabilities permanent.