DoD SBIR and the DSIP Portal: A Capture Strategist's Guide

The Department of Defense is the largest single source of SBIR and STTR funding in the federal government — a multi-billion-dollar annual pipeline that spans the Air Force, Army, Navy, DARPA, MDA, DTRA, SOCOM, and the Office of the Secretary of Defense. Every dollar of it flows through one electronic portal: DSIP, the Defense SBIR/STTR Innovation Portal.

Treating DSIP as a submission utility is the first mistake. Treating DoD topics as wish lists is the second. The DoD SBIR system is a structured demand signal — and reading it correctly is the difference between a Phase I award and a wasted quarter.

What DSIP Is, and What Replaced

DSIP — the Defense SBIR/STTR Innovation Portal — is the unified electronic submission system for all DoD SBIR and STTR solicitations. It replaced the legacy DoD SBIR/STTR Submission Site, consolidating proposal submission, topic browsing, evaluation, contract award, and post-award reporting into a single environment. Every DoD component runs through DSIP. There is no alternative submission path.

DSIP hosts three distinct artifacts that respondents must understand: the topic, the solicitation, and the proposal package. Each has its own format, its own deadlines, and its own evaluation language.

The DoD Solicitation Cycle

DoD runs three SBIR solicitations per fiscal year, supplemented by component-specific Broad Agency Announcements and special programs. The standard cycle has three predictable phases that respondents can plan against:

• Pre-release. Topics are published; respondents may contact the topic author with technical questions. This window typically runs three to four weeks. Use it.

• Open. The solicitation opens for submission. Topic-author contact closes — with rare exceptions — and respondents are limited to formal Q&A through DSIP.

• Close. Submission deadline. Late submissions are not accepted under any circumstances; system load on the final day routinely causes uploads to fail.

How to Read a DoD SBIR Topic

DoD topics are not abstract requests for innovation. They are written by program offices with specific Programs of Record in mind. The topic author is a real person with a budget, a transition target, and a defined operational gap. Reading a topic well is reading the topic author.

Three signals matter most:

1. The references. Cited reports, standards, and prior contracts indicate which programs the topic is feeding and which technical lineage the author is extending. Read them.

2. The TRL targets. The Phase I, Phase II, and Phase III TRL expectations are explicitly stated in well-written topics. They reveal the program office's expected transition path.

3. The dual-use language. Component-driven topics use precise operational vocabulary. Generic topics that read like consultant summaries are usually low-priority. Component-specific language signals an engaged program office.

AFWERX, Open Topics, and the Component Variants

AFWERX, the Air Force innovation arm, runs the most aggressive SBIR program in the DoD enterprise. Its Open Topic mechanism allows respondents to propose against an Air Force capability gap rather than a narrowly scoped requirement — expanding the addressable proposal universe substantially. The Army Catalyst program functions similarly for Army-aligned dual-use technologies.

Open Topics are not easier. They are differently demanding: respondents must prove dual-use commercial viability and a concrete pathway to a DoD end user. The bar shifts from technical credibility to operational relevance.

The DoD Quad Chart: A Brief Note

Most DoD topics require a Quad Chart — a single-page graphical proposal summary divided into four quadrants: technology concept, operational benefit, schedule and milestones, and key personnel and partners. The Quad Chart is not a marketing artifact. It is the document a program manager forwards inside their organization — the only piece of your proposal that will be read by people who never open the full submission.

Treat your Quad Chart as the executive summary that has to survive being printed in black and white and pinned to a wall. Most do not.

Common DSIP and DoD SBIR Mistakes

• Submitting against the topic instead of the topic author. The topic is the artifact. The topic author is the customer.

• Treating the Quad Chart as an afterthought. It is often the first — and sometimes only — page evaluators read.

• Underestimating DSIP. The portal’s validation engine is unforgiving — page-count violations, missing data fields, and improper file types cause silent failures. Submit twenty-four hours before the deadline; the final day always breaks.

• Skipping the pre-release window. Three weeks of direct dialogue with a topic author is the most valuable resource in DoD SBIR — and the easiest one to forfeit by waiting.

Where Capture Strategy Begins

DoD SBIR is a capture discipline before it is a writing discipline. The proposal is the deliverable of a months-long effort that begins with topic intelligence — reading the solicitation forecast, identifying topics aligned to your technology, and engaging topic authors during the pre-release window. Firms that win consistently treat each award as a single point in a multi-year pipeline, not a one-shot lottery ticket.

If you are evaluating DoD SBIR for the first time, or if your last submissions came back without an award, the constraint is rarely the writing. It is the capture work that should have happened before the writing began.