DOD is not one agency. DARPA, AFWERX, USSOCOM, and Army DEVCOM each publish strategic priority documents that signal which technologies they are actively funding. If you read the DAF 7 Operational Imperatives, DARPA's S&T strategy, and USSOCOM's SOF Vision 2035, you can map your technology to the DOD components most likely to fund it, before you commit 80 hours to writing a proposal.
This guide walks through how to read those documents. It is aimed at deep-tech founders considering their first defense SBIR who have dual-use technology but no visibility into which DOD component's priorities actually match what they build.
DOD is not one agency. Stop treating it like one.
The most common mistake we see with first-time defense SBIR applicants is writing a single "DOD-ready" proposal and shopping it across AFWERX, DARPA, and Army SBIR topics. This fails because:
- AFWERX Open Topic is primarily about customer discovery. Phase I is $75K over 90 days. The proposal is evaluated on whether you can find an Air Force end-user, not whether you can finish a feasibility study.
- DARPA funds high-risk, high-reward research aligned to a specific program manager's thesis. Program managers rotate every 3-5 years, and each has a portfolio they are actively building.
- USSOCOM funds smaller Phase I awards (often $150K-$250K) focused on niche capabilities the Special Operations community needs. The proposal volume is lower, and niche technical fit matters more than scale.
- Army xTech and Navy SBIR (ONR) each have their own solicitation cadences, evaluation criteria, and priority areas.
Treating these as one "DOD" pipeline costs you time and signal. The DOD priorities keyword list that powers most grant roadmap tools is a flat union of terms like "autonomous systems" and "quantum." That union does not tell you whether to write an AFWERX proposal, a DARPA white paper, or a USSOCOM SBIR response.
What is the difference between AFWERX, DARPA, and USSOCOM?
AFWERX funds dual-use technology with a credible Air Force customer. DARPA funds breakthrough research aligned to a program manager's technical thesis. USSOCOM funds narrowly scoped Special Operations capabilities. The three use different evaluation criteria, different award sizes, and different Phase II pathways. Reading each component's strategic documents tells you which one, if any, is worth your 80 hours.
How each DOD component signals priorities
Each DOD component publishes strategic documents that signal what they are funding. Not every document matters for SBIR positioning. Here is what to read, and what to skip.
| Component | Document | Update Cadence | SBIR Relevance |
|---|---|---|---|
| Department of the Air Force | DAF 7 Operational Imperatives | Annual updates, multi-year themes | High. AFWERX Open Topic proposals should connect to an OI. |
| AFRL | Directorate research focus pages (RX, RI, RY, RW, RQ, RH, RV, RD, AFOSR) | Continuous | High for the Defense Need section. Naming a directorate is stronger than naming "the Air Force." |
| DARPA | DARPA Strategic Plan + per-office focus pages | Strategic plan updated periodically; office pages continuous | High, but DARPA has a separate SBIR cycle. Read the program manager's active portfolio pages. |
| USSOCOM | SOF Vision 2035 + annual SOF AT&L priorities | Vision is multi-year; priorities published annually | High for the specific USSOCOM SBIR topics. |
| OSD / National Defense Strategy | National Defense Strategy | Every 4 years | Low for SBIR positioning. Too high-level. |
| Army | Army Modernization Priorities | Periodic | Medium. Useful for xTech and Army SBIR topics. |
| Navy / ONR | Naval S&T Strategy, ONR thrust areas | Periodic | Medium. Useful for ONR SBIR and DON Open Topic. |
The bottom table row is important. The National Defense Strategy is not a useful SBIR positioning document. Reviewers read it as a signal you do not know the component-level documents. Citing the NDS in a Defense Need section is the SBIR equivalent of citing Wikipedia in a peer-reviewed paper. It is not wrong, but it signals you did not do the real homework.
The DAF 7 Operational Imperatives, read for startups
The Department of the Air Force publishes 7 Operational Imperatives that drive AFWERX and AFRL investment priorities. For AFWERX Open Topic proposals, connecting your technology to at least one OI is not optional. The "Defense Need" criterion on the AFWERX scoring rubric scores 1-9 based on how specifically you can articulate an Air Force capability gap. Generic warfighter framing scores in the 2-4 range. Naming a specific OI and a specific AFRL directorate scores in the 6-8 range.
What are the DAF 7 Operational Imperatives?
The DAF 7 Operational Imperatives are the Department of the Air Force's public priority framework for technology investment. They cover space resilience, air superiority, connected battle networks, ready-to-fight forces, base resilience, long-range kill chains, and readiness to transition. They shape AFWERX Open Topic scoring and AFRL research budgets. Every AFWERX proposal should connect to at least one OI explicitly.
Here is how each OI translates to startup technology domains. These are illustrative mappings, not exclusive ones.
| OI | Short name | What it means | Startup technology signals |
|---|---|---|---|
| OI-1 | Space Order of Battle | Resilient space-based capabilities; on-orbit servicing; rapid launch | Small satellites, inter-satellite communication, space domain awareness sensing, low-cost launch components |
| OI-2 | Air Superiority | Next-generation air dominance; collaborative combat aircraft; advanced sensors | Autonomous aircraft, edge-AI mission planning, advanced sensors, RF spectrum management |
| OI-3 | Connected Battle Networks | JADC2 and ABMS connectivity; decision superiority | Mesh networking, secure data fabrics, edge compute, AI/ML inference at the tactical edge |
| OI-4 | Ready-to-Fight Forces | Readiness, training, talent, medical | Synthetic training environments, human performance sensing, predictive maintenance for training aircraft |
| OI-5 | Resilient Basing | Agile Combat Employment; base resilience; distributed logistics | Microgrids, rapid airfield repair, expeditionary logistics, counter-UAS |
| OI-6 | Global Strike | Long-range fires; kill chain integration | Hypersonics, precision munitions, long-range ISR, targeting fusion |
| OI-7 | Defining Tomorrow | Rapid capability development, modular open systems | Digital engineering, modular open systems architecture, MBSE tooling |
If your technology does not obviously map to at least one OI, AFWERX Open Topic may not be a good first SBIR. That is not a judgment of your technology. It is a signal that the proposal will score low on Defense Need and cost you 40-80 hours for a low-probability outcome.
Reading AFRL directorate priorities
AFRL is the Air Force Research Laboratory, and it is organized into eight technical directorates plus AFOSR (basic research). Naming a specific directorate and a specific research focus area in your Defense Need section is one of the highest-impact moves in an AFWERX proposal.
| Directorate | Focus | Example startup technology connections |
|---|---|---|
| AFRL/RX | Materials and Manufacturing | Advanced composites, additive manufacturing, corrosion-resistant coatings, structural health monitoring |
| AFRL/RI | Information | AI/ML, autonomous systems, cyber, decision support, edge compute |
| AFRL/RY | Sensors | RF sensors, EO/IR, radar, sensor fusion, electronic warfare, passive sensing |
| AFRL/RW | Munitions | Weapon systems, seekers, warheads, targeting |
| AFRL/RQ | Aerospace Systems | Propulsion, aerodynamics, thermal management, hypersonic vehicle systems |
| AFRL/RH | Human Effectiveness | Human-machine teaming, biomedical sensing, cognitive sciences, aircrew protection |
| AFRL/RV | Space Vehicles | Satellite systems, space propulsion, space ISR, space weather |
| AFRL/RD | Directed Energy | Lasers, high-power microwaves, optics, beam control |
| AFOSR | Air Force Office of Scientific Research | Basic research across science domains (not SBIR-relevant directly) |
A fictional example. A startup building edge-AI acoustic sensing for drone detection would map primarily to AFRL/RY (Sensors) and AFRL/RI (Information), with a secondary connection to OI-5 (Resilient Basing, counter-UAS). That specific framing beats "we make AI for defense" by a factor of three on the Defense Need criterion. We have seen AFWERX proposals score 7+ on Defense Need with this level of specificity and 3-4 without it.
Reading DARPA's S&T strategy and office themes
DARPA is structurally different from AFWERX. DARPA program managers pick a technical thesis and build a portfolio of programs around it. Your SBIR proposal or BAA white paper is evaluated on whether it fits that program manager's portfolio.
What does DARPA fund?
DARPA funds breakthrough research with high technical risk and high potential payoff. It funds across six technical offices: BTO (biological), DSO (defense sciences, physics, materials), I2O (information innovation, AI, cyber), MTO (microsystems, electronics, photonics), STO (strategic, systems), and TTO (tactical). Each office has a distinct thesis and a distinct cadence of solicitations. DARPA SBIR topics are narrower than AFWERX Open Topic and tied to active programs.
Here is the structure.
| Office | Focus | Good fit for |
|---|---|---|
| BTO (Biological Technologies Office) | Biology, medicine, bio-manufacturing, neurotechnology | Biotech, neurotech, biosecurity, cell and gene engineering |
| DSO (Defense Sciences Office) | Fundamental physics, materials, mathematics, sensors at the edge of physics | Quantum, novel materials, unconventional computing |
| I2O (Information Innovation Office) | AI, software, cyber, information systems | AI/ML at scale, autonomous reasoning, cybersecurity |
| MTO (Microsystems Technology Office) | Electronics, photonics, microsystems | Semiconductors, photonic integrated circuits, novel electronics |
| STO (Strategic Technology Office) | Systems-level defense capabilities | Autonomy at scale, electronic warfare, command and control |
| TTO (Tactical Technology Office) | Tactical platforms and systems | Air, ground, maritime, space platforms |
For most first-time defense SBIR applicants, DARPA is a poor first grant. Three reasons:
- DARPA expects TRL 1-3 for basic research programs and TRL 4-6 for applied programs. Your technology needs to sit in a specific TRL band that matches the program manager's thesis.
- DARPA evaluates against a single program manager, not a panel. That one person's judgment is decisive. You cannot hedge by being generally strong.
- DARPA SBIR awards are tied to active programs with specific topics. The topic author already has a thesis. Your proposal either fits that thesis or it does not.
If you are a first-time applicant and your technology looks like DARPA work, start with AFWERX or an agency SBIR where your Phase I experience builds the narrative. DARPA is more approachable as a second or third grant, once you have a Phase I report and a more mature technology.
Reading USSOCOM's SOF Vision and priority areas
Special Operations Command is the smallest major DOD component for SBIR purposes, but it is often the most approachable for niche technologies. USSOCOM publishes the SOF Vision 2035 and annual SOF AT&L priorities.
Priority areas include:
- Next-generation mobility (ground, air, maritime, subterranean)
- Precision strike and ISR for small units
- Biotech and human performance optimization for operators
- Signature management (cyber, electromagnetic, acoustic, visual)
- Data, AI, and decision support at the tactical edge
USSOCOM SBIR award sizes are typically smaller than Air Force or Navy, but the proposal volume is lower and the technical match is more decisive. If your technology is narrow and clearly fits one of the SOF priority areas, USSOCOM is often a cleaner path than AFWERX Open Topic.
The translation step: map your tech to a priority signal
Here is the methodology we use with every defense-curious founder in the Cada pipeline. Three questions.
- Which DOD component's published priorities does your technology most directly serve? Not "defense generally." Name a specific OI or directorate or DARPA office or USSOCOM priority area.
- What is the specific capability gap you close, in that component's language? "We use AI to detect anomalies" is not a gap. "AFRL/RY's passive acoustic detection roadmap calls out the need for low-SWAP edge inference for small UAS threats" is a gap.
- Who on the government side would adopt this if it worked? Named unit, named program office, or named program manager. If you cannot answer this, the proposal will score low on Defense Need regardless of how strong the technology is.
Fictional worked example. A synthetic data company building training datasets for radar classification models maps across DOD components like this:
- AFWERX: OI-2 (Air Superiority) and OI-3 (Connected Battle Networks). AFRL/RY sensor fusion and AFRL/RI autonomy roadmaps both reference the scarcity of labeled radar training data. Strong fit.
- DARPA: I2O has several AI trustworthiness programs. Possible fit, but depends on an active program. Requires a program manager conversation before writing.
- USSOCOM: Data + AI priority area. Possible fit, but USSOCOM tends to want platform-integrated solutions more than horizontal training data. Marginal fit.
- Army: PEO Intelligence Electronic Warfare and Sensors, plus C5ISR Center. Strong fit for Army SBIR topics on radar ML.
A startup with this profile should pursue AFWERX first (clearest OI match, lowest Phase I cost) and Army SBIR topics in parallel. DARPA and USSOCOM are options but not first moves.
This kind of multi-component mapping is the portfolio approach. It is faster to build once you have the DOD priority structure in your head. It is also the approach we use in the Grant Roadmap Builder, which scores a technology across components instead of treating DOD as one bucket.
The AFWERX reframe: Phase I is customer discovery, not R&D
The most important thing to understand about AFWERX Open Topic Phase I is that it is primarily a customer discovery engagement, not a feasibility study.
The AFWERX playbook we use at Cada spells this out. The Defense Need criterion is weighted heavily and scored 1-9 on how credibly you can demonstrate an Air Force end-user engagement plan. The Work Plan is 90 days and $75K. That is not enough to do meaningful R&D. It is enough to run 10 conversations with an AFRL directorate, three AF units, and a PEO program office.
What this means for proposal framing:
- The Technical Approach section should describe technology that already works (TRL 3-6). Do not propose to build something novel in Phase I.
- The Work Plan should center on customer discovery activities: meetings with named AF units, capability gap validation, and a Customer Memorandum roadmap.
- The Commercialization Strategy must address both commercial and defense markets (dual-use is a requirement, not optional).
- The Path to Customer Memorandum is the Phase II gate. If you cannot identify a named AF unit who would sign a Customer Memorandum after Phase I, you will not win Phase II.
First-time AFWERX applicants often write civilian SBIR-style proposals, where Phase I is a feasibility study. That framing scores 2-4 on Defense Need. The reframe (Phase I as customer discovery) is worth the read.
Common mistakes when reading DOD priority documents
We see the same mistakes across first-time defense SBIR applicants. The pattern is consistent enough that it is worth naming explicitly.
- Citing the National Defense Strategy. It is too high-level. Reviewers read it as a signal you did not read the component documents.
- Citing an outdated version of the DAF Operational Imperatives. The list evolves. Check the publication date.
- Assuming DOD component alignment equals grant fit. Your technology might map to OI-2, but if TRL is too high or too low, the grant is still wrong.
- Using civilian SBIR language. "Broader impacts," "hypothesis-driven," "study section," "unmet medical need" are NIH and NSF terms. In an AFWERX or DARPA proposal, they are signals you are writing the wrong kind of proposal.
- Naming "the warfighter" without naming a unit. Reviewers hear "warfighter" from every applicant. Named units (ACC, AFSOC, AFRL/RX) are worth ten times more than "the warfighter."
- Claiming DARPA-worthy novelty in an AFWERX proposal. DARPA wants moonshot novelty. AFWERX wants dual-use technology with a credible AF customer. Pitching the wrong novelty signals a misread of the component.
- Using banned buzzwords. "Revolutionary," "game-changing," "paradigm shift," "cutting-edge" applied to your own technology are AI-telltale words in Government Technical Advisor (GTA) review. They score down, not up.
Frequently asked questions
Is defense SBIR worth the time for a dual-use startup?
If your technology maps cleanly to a DAF Operational Imperative, an AFRL directorate, or a USSOCOM priority area, yes. AFWERX Open Topic Phase I is $75K for 90 days. If you cannot map your technology to a specific component priority, the application will score low on Defense Need and cost you 40-80 hours. That is the filter to run first.
How do I pick between AFWERX, DARPA, and USSOCOM?
AFWERX for dual-use technology with a credible AF customer and TRL 3-6. DARPA only if your technology matches an active program manager's thesis and you have the TRL band right. USSOCOM for narrow technical fit to SOF priority areas. For first-time applicants, AFWERX is usually the clearest path.
What is the TRL range for DOD SBIR Phase I?
TRL 3-6 is the ideal band for most DOD SBIR Phase I programs. Below TRL 3 is too early (better fit for AFOSR or basic research). TRL 7+ is too mature. AFWERX specifically flags TRL 7+ as potentially over-mature for SBIR funding.
Can one proposal cover multiple DOD components?
Generally, no. Each component has its own solicitation, template, and scoring rubric. A single application targets one component. The portfolio approach is to run multiple applications in parallel, each customized to the target component.
What is a Customer Memorandum and why does it matter?
A Customer Memorandum is a signed document from a named AF unit stating intent to engage with your technology post-Phase I. It is the Phase II gate for AFWERX Open Topic. Without a credible path to a Customer Memorandum, Phase II is unlikely regardless of Phase I technical results.
How do I find named AF contacts for customer discovery?
Start with AFRL directorate publications and AFWERX challenge areas. Search SBIR.gov for prior awards in your technology area and look at the contracting office. Attend AFWERX Engage events. Ask program offices (PEOs) for technology intake conversations. For a first-time applicant, 10-15 conversations during Phase I is a reasonable target.
Does the DAF Operational Imperatives list apply to AFRL and AFWERX equally?
Yes. The DAF 7 OIs are department-wide. AFWERX Open Topic proposals, AFRL SBIR topics, and AFRL research budgets all reference the same OIs. They are the common top-level framing for the Department of the Air Force.
A straight answer on defense SBIR fit
If you are a founder with dual-use technology and you are not sure which DOD component to target, the translation step above is most of the work. Read the DAF 7 Operational Imperatives, scan the AFRL directorate pages for your technology domain, and check DARPA office pages and USSOCOM priorities for secondary fits.
If you want a second opinion on whether your technology is a credible defense SBIR candidate, we run a free 15-minute defense SBIR fit assessment. We will tell you which component(s) your technology maps to, which ones it does not, and what your first proposal should look like. No pitch, no obligation. Just a straight answer on whether AFWERX, DARPA, USSOCOM, or Army is the right first move.
If you are looking at multiple defense components simultaneously (common for founders with horizontal technology like AI, sensors, or materials), we build a grant roadmap that maps your technology across AFWERX, DARPA, USSOCOM, and Army at the component-priority level, not the generic "defense" level. That is the portfolio approach, and it tends to outperform the one-proposal-at-a-time approach for founders with dual-use tech.
Questions? The fastest way to get a specific answer is the 15-minute call.