The Navy Just Dropped 12 SBIR/STTR Topics and a Counter-Unmanned Air Systems CSO for FY26 Release 3 — Quantum Battlefield Dominance, Applied AI, and Contested Logistics Frame the Pre-Release. Here Is What the June 24 to July 22 Window Means for Defense Tech Founders.

On June 3, 2026, the Department of the Navy pre-released its Fiscal Year 2026 Release 3 SBIR and STTR solicitation, featuring twelve conventional Broad Agency Announcement topics and a single Commercial Solutions Opening area of interest focused on Counter-Unmanned Air Systems. The release frames the topics under three Navy critical technology areas — quantum and battlefield information dominance, applied artificial intelligence, and contested logistics — which together describe the strategic mission space the Navy is asking small businesses to address. The proposal submission window opens June 24, 2026, and closes July 22, 2026 at noon Eastern. The technical questions cutoff is June 23. Naval Air Systems Command and Naval Sea Systems Command are hosting a joint Counter-UAS webinar on June 16, 2026.

The Release 3 topic mix is unusual for the FY26 Navy cycle. The three critical-technology framings are familiar from the Navy's prior public documents, but the specific topics under each framing are unusually concrete and unusually well-aligned with commercially available technology. The Counter-UAS Commercial Solutions Opening is the most strategically significant single addition — it routes around the conventional SBIR Phase I gate and lets the Navy contract with companies that have existing commercial Counter-UAS systems on terms more favorable than the standard SBIR vehicle. For small businesses that have been building in the Navy adjacency, Release 3 is the most direct path into Navy contracting that the FY26 cycle has offered to date.

This piece walks through the twelve conventional topics, the Counter-UAS CSO, the three critical-technology framings, the June 23 / June 24 / July 22 timeline, and how Navy-adjacent small businesses should think about positioning for the window.

The 12 Conventional Topics: A Reading

The twelve conventional BAA topics span sensor management, maritime surveillance, satellite imagery, weapon systems modernization, embarked data, satellite communications, signals intelligence, target discovery, predictive tracking, zero-trust data, secure tasking of commercial assets, and terminal defense.

Adaptive Sensor Management. The topic asks for software and algorithm work that lets Navy sensor networks dynamically reallocate sensing resources across changing mission contexts. The space includes multi-sensor scheduling, sensor handoff under degraded communications, and cross-domain sensor coordination. Companies with prior commercial work on sensor orchestration in autonomous systems, in industrial sensing, or in space situational awareness should find the topic accessible.

Anomalous Behavior Detection and Alerting for Congested Maritime Environments. This is a maritime domain awareness topic with an applied AI framing. The Navy is asking for systems that identify anomalous vessel behavior in high-traffic littoral environments where the conventional rule-based maritime traffic monitoring approaches break down. Companies with prior work on behavioral analytics, AIS data processing, or maritime intelligence have a direct path in.

Gun Weapon Systems Ammunition Handling and Controls Modernization. This is a hardware modernization topic with an embedded controls dimension. The Navy is asking for ammunition handling system upgrades and the associated control software for legacy gun weapon systems. The topic is narrower than the other Release 3 topics and favors companies with established defense hardware experience.

High-Throughput Embarked Data Transfer. This is a data infrastructure topic — moving large data volumes off ship in low-bandwidth and contested communications environments. The space includes adaptive compression, intelligent prioritization, edge-to-cloud architectures, and resilient transport protocols. Companies with prior commercial work on bandwidth-constrained data transfer, satellite data systems, or edge computing pipelines have a path in.

Intra-Satellite Communications. This is a space communications topic focused on communication between satellites in a constellation, not satellite-to-ground. The technical space includes optical inter-satellite links, RF cross-links, and the protocol layers that support both. Companies in the new-space communications sector with active product development should find the topic well-fitted.

Long-Range Listening Device. This is a signals intelligence topic with an unusual framing — the Navy is asking for systems that detect and characterize signals at significantly extended ranges relative to current capability. The topic favors companies with established signals processing expertise and RF systems engineering capability.

Multi-Band Approach to Target Discovery. This is a sensor fusion topic combining data from sensors operating across multiple RF and electro-optical bands to detect and characterize targets that are difficult to find in any single band. Companies with prior multi-modal sensor fusion work, particularly in defense or autonomous-vehicle contexts, have a clear path.

Optimizing Satellite Imagery Across Commercial Vendors. This is a tasking and analytics topic that lets the Navy treat the commercial satellite imagery market as a single resource pool — automatically tasking the optimal vendor for each collection requirement and integrating imagery across vendors with different formats, resolutions, and revisit cadences. Companies in the geospatial software, imagery analytics, or commercial satellite tasking space should look at the topic carefully.

Predictive Movement for Object Oriented Tracking. This is an applied AI topic focused on predicting the future trajectories of tracked objects in real time. The topic intersects with autonomous vehicle motion prediction, maritime traffic prediction, and air traffic prediction. Companies with prior work on trajectory prediction in any of those adjacencies have a path in.

Real-time Zero Trust Data and Access Control for Combat Systems. This is the most strategically interesting topic in the release. The Navy is asking for zero-trust architectures applied to combat system data — meaning identity-based authorization, continuous validation, and microsegmentation that work in the real-time-constrained environment of combat systems. The topic intersects with the broader Department of War zero-trust roadmap and with the cybersecurity maturity model certification framework. Companies with prior commercial zero-trust deployments should expect the topic to be highly competitive.

Secure Tasking of Commercial Assets. This is a tasking and security topic about how the Navy can task commercial satellite, sensing, and communications assets in a way that does not reveal Navy operational intent. The technical space includes blind tasking protocols, cover-traffic generation, and obfuscation layers.

Terminal Defense Weapon System Coordinator. This is a fire control and weapon system integration topic about coordinating multiple terminal defense weapons against incoming threats. Companies with prior weapons integration or fire control software experience have the most direct path.

The mix favors software-forward companies. Eight of the twelve topics are dominated by software, algorithms, or data systems. Three are sensor-and-software hybrids. One — Gun Weapon Systems Ammunition Handling — is primarily hardware. The mix signals where the Navy thinks the highest-leverage small business contributions are: applied AI, sensor fusion, secure data systems, and tasking and orchestration.

The Counter-UAS Commercial Solutions Opening

The Counter-Unmanned Air Systems Commercial Solutions Opening is structurally different from the twelve conventional BAA topics. A Commercial Solutions Opening is a procurement vehicle that lets a Department of War buyer contract with companies that have an existing commercial product, on terms more flexible than the conventional Federal Acquisition Regulation contracting vehicles. The CSO does not require the company to perform the standard Phase I feasibility work — it lets the Navy go directly to a follow-on contract for a commercially proven Counter-UAS system.

The June 16 NAVAIR/NAVSEA webinar is the gate. Companies with commercial Counter-UAS systems should register for the webinar, attend, and engage with the program managers presenting. The CSO will likely have a tighter timeline than the conventional BAA topics and a more constrained pool of competitive companies — Counter-UAS is a small, well-known commercial market, and the Navy will know most of the players going in.

The strategic significance of the Counter-UAS CSO is that it signals a shift in how the Navy is thinking about Counter-UAS acquisition. The conventional path — open a Phase I topic, run an eighteen-month feasibility cycle, then a twenty-four-month Phase II development cycle, then a Phase III transition — does not match the operational tempo of the Counter-UAS threat. The CSO route lets the Navy buy what already works. For commercial Counter-UAS companies, the CSO is the most direct path to a meaningful Navy contract that the FY26 cycle has offered.

The Three Critical Technology Framings

The Navy explicitly groups the Release 3 topics under three critical technology areas. The framings are not just organizing labels — they signal where the Navy is willing to fund follow-on Phase II and Phase III work, which is where the meaningful contract value sits.

Quantum and Battlefield Information Dominance. This is the broadest of the three framings and covers the sensing, signals, and data topics. The "quantum" qualifier in the framing is partly aspirational — quantum sensing and quantum communications are early-technology lines, and few of the Release 3 topics actually involve quantum hardware. The "battlefield information dominance" qualifier is the operative one: the Navy is asking for systems that give its forces an information advantage over peer adversaries in contested environments. Companies positioning under this framing should explicitly tie their technical narrative to the information-advantage thesis.

Applied Artificial Intelligence. This is the framing under which the anomalous behavior detection, predictive movement, multi-band target discovery, and satellite imagery optimization topics sit. The Navy is asking for AI systems that work in operational environments — meaning real-time constraints, degraded inputs, and adversarial conditions. The framing intersects with the broader Department of War AI strategy and with the work the Chief Digital and AI Office is funding. Companies under this framing should expect heightened evaluation of the model robustness, the inference latency, and the operational concept of how the AI system would be used by sailors.

Contested Logistics. This is the framing for embarked data, intra-satellite communications, secure tasking, and high-throughput data transfer. The Navy is asking for the data and communications infrastructure that supports operations when conventional logistics paths are contested or denied. The framing connects to the broader Navy investment in distributed maritime operations and in the agile combat employment concepts that the Navy has been refining over the past three years.

For small business founders, the framings are a strategic positioning aid. A pitch that ties technical work explicitly to one of the three framings, and that articulates how the technology contributes to the framing's operational mission, is materially stronger than a pitch that only describes the technical innovation. The evaluators are looking for both — the technical credibility and the mission relevance.

The June 23 / June 24 / July 22 Timeline

The compressed window — June 24 proposal opening, July 22 closing — gives companies roughly four weeks to write, internally review, and submit a proposal. The June 23 technical questions cutoff is the operational constraint: any question to the topic point of contact must be submitted by June 23, and answers are typically posted within a few days. Companies should review the topic descriptions immediately on June 4 and submit any clarifying questions through the conventional channel by mid-June to allow time for the answer to be posted and incorporated into the proposal.

The four-week proposal window is tight by SBIR standards but typical for Navy Release cycles. Companies that wait until July to start the proposal will struggle to produce a competitive submission. The most successful Navy SBIR competitors begin proposal preparation on or before pre-release — they have a topic-specific draft started by mid-June, an internal review cycle complete by early July, and a final submission ready by mid-July with a week of buffer.

The technical questions cutoff is also a signaling channel. Topic point-of-contact program managers track which companies are asking questions, what the questions are, and how the questions tie to the topic's underlying mission. Companies that ask substantive, technically credible questions — questions that demonstrate they have already done the basic research on the topic and are now drilling into a specific operational assumption — are positioning themselves positively for the eventual evaluation. Companies should not ask questions that they could have answered themselves with a careful reading of the topic description.

Positioning Notes for the Navy Cycle

Three positioning notes for companies new to Navy SBIR.

First, Navy SBIR has a longer cycle than DARPA or NSF SBIR. The proposal-to-award timeline can run six to nine months from submission. Companies should plan their cash runway accordingly and should not count on Navy SBIR award funds for cash flow needs in calendar Q4 2026 even if the proposal is submitted in July.

Second, the Navy is more transition-focused than NSF and is more comparable to DARPA on the transition emphasis. Phase II and Phase III contracts are where the meaningful contract value sits, and they are awarded preferentially to companies that have credible Phase III sponsor commitments — meaning a Navy program of record that has indicated intent to transition the technology. Companies pursuing Navy SBIR should be working the sponsor relationship from the Phase I proposal forward, not waiting until Phase II to start.

Third, the Navy values commercial dual-use heavily. The most successful Navy SBIR companies have credible commercial markets in addition to the Navy market, which insulates the company from any single Phase III transition risk and which signals to evaluators that the company will survive the inevitable program-of-record turbulence. Companies that are exclusively Navy-focused should think carefully about whether the long Navy cycle and the Phase III transition risk are compatible with their capital structure.

The recent Department of War SBIR/STTR FY26 deep dive on the Public Law 119-83 ART program is at Granted Blog, and the NSF SBIR/STTR restart deep dive is at Granted Blog. Companies pursuing the Navy Release 3 window should consider how it fits into a broader federal SBIR portfolio that increasingly rewards companies pursuing multiple agencies in parallel.

What to Watch After July 22

Two things to watch after the July 22 closing. First, the evaluation tempo — whether Navy program offices stay on the standard six-to-nine-month award cycle or whether the Counter-UAS CSO awards move faster because of the commercial-product nature of the procurement. The CSO timeline will signal how the Navy is thinking about urgency on Counter-UAS. Second, the topic concentration in Release 4 and subsequent FY27 releases — whether the Navy continues to weight applied AI and contested logistics over conventional sensor and weapon system topics, which will signal where the FY27 capital is flowing.

The June 24 to July 22 window is open. Companies that have been building in the Navy adjacency should treat the window as a four-week sprint with high stakes on the proposal quality. The Counter-UAS CSO is the highest-leverage single opportunity in the release for companies with existing commercial Counter-UAS systems. The conventional twelve topics favor software-forward small businesses with credible defense mission framing and prior commercial validation.