OTAs, SBIRs, and BAAs: How to Read the Defense Contracting Alphabet Without Losing Your Mind

Most defense tech founders encounter the acronym soup early—OTA, SBIR, BAA, IDIQ, CRADA—and make the same mistake: treating these as interchangeable funding mechanisms rather than distinct signals about what the government actually wants from you.

Photo by RDNE Stock project on Pexels.

They are not interchangeable. Choosing the wrong vehicle at the wrong stage can cost a startup twelve months and a runway crisis.

What Each Vehicle Is Actually Telling You

Start with the BAA—the Broad Agency Announcement. When a program office releases a BAA, they're broadcasting a research interest, not a procurement need. They want ideas. They may not have a clear operational requirement yet, or they're hedging across several technical approaches. Winning a BAA gives you credibility and some non-dilutive capital, but it often means you're early—earlier than you want to be if you're trying to build a company. BAAs are great for university labs and early-stage research spinouts. They're a slower path to revenue than most Series A investors will tolerate.

SBIRs (Small Business Innovation Research grants) occupy a different role. Phase I is $50K–$300K to prove feasibility; Phase II is up to $2M to build a prototype. On paper, this sounds like a clean on-ramp. In practice, the SBIR program has a well-documented "Phase II cliff"—companies that win Phase II but fail to transition to Phase III (actual government contracts) at alarming rates. The technology works; the acquisition system doesn't pick it up. We've written before about why that pipeline is broken. The short version: SBIR was designed for research, not commercialization, and the agencies administering it are evaluated on awards given, not on companies that survive.

That leaves OTAs—Other Transaction Agreements. These are the vehicle that actually gets founders excited once they understand them, and for good reason. OTAs exist specifically to bypass the Federal Acquisition Regulation (FAR) when speed and flexibility matter more than compliance theater. They don't require certified cost or pricing data. They can close in weeks rather than years. And critically, they allow non-traditional defense contractors—meaning companies that haven't done a lot of government work before—to compete without being buried by compliance overhead.

Here's what most people miss about OTAs: they're not a shortcut to unlimited government money. They require a "significant non-traditional contractor" on the agreement, meaning the government is specifically trying to pull commercial technology into the defense ecosystem. If you're a pure-play defense startup with no commercial revenue, you may need to structure your OTA team carefully to qualify.

How to Actually Sequence These

graph TD
    A[Early Research / TRL 1-3] --> B{BAA or SBIR Phase I}
    B --> C[SBIR Phase II / Prototype]
    B --> D[OTA Prototype Agreement]
    C --> E{Transition Risk}
    D --> F[OTA Production Agreement]
    E -->|Success| F
    E -->|Failure| G[Cliff — No Follow-On Contract]
    F --> H[Program of Record or IDIQ]

The sequencing matters more than the vehicles themselves. Founders who enter at the BAA stage and expect to reach a program of record in three years are setting themselves up for disappointment. Founders who chase OTAs before their technology is mature enough to demo convincingly are burning goodwill with program offices that have limited bandwidth and long memories.

The sweet spot for most venture-backed defense startups is entering via OTA at TRL 4–6: enough maturity to demonstrate something real, but early enough that the program office feels like a partner rather than a customer waiting on delivery.

What Investors Should Be Asking

When evaluating a defense tech startup, the contracting strategy deserves the same scrutiny as the cap table. A few questions worth pressing on:

• Does the team understand which office will own the eventual program of record—not just who's writing the current check?
• Is the OTA prototype agreement structured with a clear pathway to a follow-on production agreement, or is it a one-time study with no continuity clause?
• Has the company done the relationship work with a "middle tier" integrator who can prime a larger contract if needed?

That last point is underrated. Many startups treat the contracting vehicle as a paperwork problem and the relationship as a soft, secondary concern. It's the inverse. The paper follows the relationship. Program managers have discretion, and they exercise it in favor of teams they trust.

None of this is classified knowledge. But most of Silicon Valley treats defense acquisition like a black box—something opaque and irrational that they'll figure out after the product is built. The founders who treat acquisition strategy as a product decision from day one are the ones who actually get to revenue.