The standard SBIR ladder has three rungs: Phase I proves feasibility (a small, short award), Phase II funds development (six figures and up), and Phase III commercializes with non-SBIR dollars. Direct-to-Phase-II (DP2) lets you skip the first rung entirely — jumping straight to the development money — if you can prove you have already done Phase I-level work.
Congress created DP2 authority because many capable companies have already validated their technology on commercial or internal funding. Forcing them through a tiny Phase I feasibility study wastes time on both sides. DP2 pulls mature, dual-use technology into the Army faster.
For Army DP2, your feasibility documentation must not be derived from prior SBIR/STTR work. That work is already under development with the government, so it cannot justify a “skip Phase I” claim. DP2 is explicitly for technology maturing in the commercial market. This is the single most common eligibility mistake — teams cite a previous Navy or Air Force SBIR as their proof, and the proposal is thrown out.
The eligibility catch: DP2 rewards commercial-market maturity, not a head start on a government contract. If your feasibility data came from a prior SBIR/STTR award, you are not eligible to use it as DP2 justification.
See if you qualify for an Ansys eval The MVP playbook →Strong DP2 packages substantiate that the scientific and technical merit and feasibility of the concept has been met. That means concrete artifacts: technical reports, test data, a working prototype, pilot results, third-party validation. Vague claims of “years of R&D” do not clear the bar. You are effectively writing the Phase I final report you never got funded to write — so show the receipts.
Choose DP2 when: you already have a working prototype or fielded commercial product, your feasibility data is clean of prior government SBIR funding, and the Army topic maps closely to what you have built. Choose the normal Phase I route when your technology is earlier-stage, or when a small feasibility award and the relationship it builds are more valuable than speed.
DP2 opportunities appear as specific topics in Army solicitations on the Army SBIR|STTR site and the DoD SBIR/STTR Innovation Portal (DSIP). Read the topic's DP2 instructions carefully — page limits, feasibility documentation format, and commercialization sections are strictly enforced. The Army SBIR FAQ is the authoritative reference for current DP2 rules.
The appeal of DP2 is concentration of time and capital. Instead of spending months on a small Phase I feasibility study and then re-competing for Phase II, you go straight to the larger development award — often shaving the better part of a year off the path to a fielded prototype. For a hardware team burning runway, that compression is frequently worth more than the incremental Phase I check itself. It also signals maturity to the evaluating organization: a company that arrives with a working prototype and clean commercial validation reads as lower-risk than one still proving the basic concept.
Because DP2 leans entirely on evidence you already have, the work is front-loaded. Assemble your feasibility package — test reports, prototype documentation, pilot data, and a defensible provenance trail proving the work was commercially or internally funded — before a matching topic ever appears. When the right DP2 topic opens, you want to be assembling a proposal, not scrambling to generate data.
Official sources: Army SBIR|STTR FAQ & Resources · Army SBIR|STTR Program. Figures change; confirm on the official page before relying on them.
