SBIR is Reauthorized- Here’s How to Actually Leverage the Program (and Avoid the Traps)

With SBIR/STTR reauthorized, a lot of founders are asking the same question:

“How do we actually use this program the right way?”

That’s the right question—because while SBIR is a powerful tool, it’s also one of the most misunderstood programs in federal contracting. Every year, we see strong companies stall out, burn time, or get stuck in Phases I and II because SBIR doesn’t operate the way most people assume it does.

SBIR was designed for a purpose.
The reality of how it’s executed doesn’t always align with that original intent.

Let’s break down how the program really works, the two major SBIR topic types, the most common pitfalls, and—most importantly—how to use SBIR to cross the Valley of Death and scale into real Phase III contracts.

Two Types of SBIR Topics (And Why the Difference Matters)

At a high level, SBIR topics fall into two buckets:

1. Specific Topics
2. Open Topics

They behave very differently—and they attract very different types of winners.

1. Specific Topics: High Precision, Low Forgiveness

Specific topics have been around for decades and were originally intended to help spin up new businesses and new technologies. In theory, they fund innovation.

In practice?
Most specific topics are tied to very well-defined government problems.

Take the Navy as an example.

A program office may:

• Have a very narrow technical problem
• Not have immediate budget
• Decide SBIR is a convenient way to fund a few million dollars of R&D

The resulting topic is extremely specific. And unless you’ve:

• Worked with that community for years (often decades), or
• Already understand the operational and technical context

…you’re unlikely to be competitive.

Even If You Win, There’s a Catch

Let’s assume best case:

• You win a Phase I or Phase II award

The reality:

• Funding may arrive 6–8 months later
• For an early-stage company, that timeline can be existentially dangerous

For agencies like NSF, award timelines can stretch even longer—sometimes close to a year. At that point:

• Your company may already be out of runway
• Or you’ve solved the problem without funding because you couldn’t wait

That’s not a growth model.

Bottom Line on Specific Topics

Specific topics are a very particular flavor of SBIR. They can work—but generally:

• Not as a company-building strategy
• Not as a primary source of early capital
• Not without deep prior customer knowledge

Exception:
On the STTR side—especially when paired with open topic dynamics—there can be an entry point for earlier-stage teams. But that’s the exception, not the norm.

2. Open Topics: Flexibility, With Strings Attached

Open topics feel more open—and that’s where many teams misread the opportunity.

Common assumption:

“I have a good idea, so I can pitch it here.”

What we’ve actually seen succeed:

• Companies with existing revenue, or
• Companies with venture backing and technical credibility

Open topics are far more effective as a federal market expansion tool than a company formation tool.

Where Open Topics Are Working

Open topics have primarily come from:

• Air Force
• Space Force

With:

• Some experimentation by the Army
• Likely increased Navy participation going forward

If you already have commercial validation, open topics can be a strong way to:

• Get in the door
• Prove relevance
• Start building a defense customer base

If you don’t yet have traction?
Open topics are rarely the on-ramp people expect them to be.

Why SBIR Feels So Different (and Trips People Up)

SBIR does not operate like the rest of the Department of Defense acquisition ecosystem.

Here’s why:

SBIR Is Structured and Predictable

• Fixed submission deadlines
• Set funding amounts
• Defined evaluation cycles
• Published topic rounds

It’s one of the only places in DoD where:

“This is a $1.25M opportunity”
…actually means you’ll bid around $1.25M.

That’s not how most federal contracting works.

Everywhere Else Is the Opposite

Outside SBIR:

• Funding cycles are irregular
• Amounts are negotiable
• Timelines depend on appropriations, fallout funding, or leadership priorities
• Price competition and cost scrutiny are intense

SBIR is its own island.
Once you learn it, it feels safe and repeatable.

And that’s exactly the problem.

Why Companies Get Stuck in Phase I and II

Most companies don’t fail in SBIR.

They fail after SBIR.

The structure makes Phase I and II feel comfortable:

• You learn the process
• You know when topics drop
• You understand the awards

So teams keep doing more of the same.

But SBIR alone does not scale companies.

Which brings us to the real question.

Using SBIR the Right Way: Start With the End in Mind

SBIR should not be the strategy.
It should support the strategy.

Before you write a Phase I proposal, you should already be asking:

• Where does this technology ultimately live?
• Who owns this capability long term?
• Is there a program of record?
• Which program office has the actual budget?

Because that program office—not the SBIR office—is your real customer.

Those are the groups that control:

• $10M, $50M, $100M+ contracts
• Annual recurring funding
• Long-term scale

Phase I Matters More Than People Think

Here’s why scope matters:

We’ve seen Phase III contracts with hundreds of millions in ceiling value justified off:

• A $50K–$150K Phase I effort

One real example:

• Phase I SBIR: ~$150K
• Resulting Phase III IDIQ ceiling: $489M

That doesn’t happen by accident.

It happens because:

• The Phase I scope aligned to a real program need
• The use cases mapped to larger mission objectives
• The groundwork for scale was laid early

Phase I isn’t about proving your idea works.
It’s about proving your idea belongs.

Bring Transition Partners in Early—or Pay for It Later

One of the biggest SBIR mistakes we see:

“We’ll focus on delivery first and worry about transition later.”

That’s how companies end up with:

• A great Phase II
• A happy government user
• And nowhere to go when the contract ends

People PCS.
Leaders rotate.
Pet projects disappear.

What Works Better

Use Phase I and II to:

• Identify long-term transition partners
• Pull program offices into discussions early
• Get feedback beyond the immediate end user

Why? Because:

• End users think tactically
• Program offices think strategically
• Contracting thinks structurally

You need all three perspectives.

Crossing the Valley of Death (Where Most SBIR Companies Fail)

The most dangerous moment isn’t Phase I.
It’s the end of Phase II.

If you wait until the contract ends to ask about follow-on funding:

• You’re already 12–24 months too late

The solution:

• Start Phase III conversations during Phase II
• Ideally 9–12 months before the end date

Even then, gaps can happen—but they are survivable if planned.

We’ve seen cases where:

• Early conversations unlocked bridge funding
• Initial small obligations grew into multi‑year contracts
• What started as $500K became $12M+ over time

That only happens when transition planning starts early.

SBIR Should Fund the Prep—Not the Panic

Used correctly, SBIR can pay for:

• Authority to Operate (ATO)
• Security and compliance work
• Integration prep
• Early enterprise enablement

That’s how you exit SBIR ready to scale—rather than scrambling to catch up.

The Takeaway

SBIR is valuable.
But only if you treat it as a pathway, not the destination.

If you:

• Start with the end user who owns the budget
• Scope Phase I with Phase III in mind
• Build transition relationships early
• Use Phases I and II to prepare for scale

You won’t get stuck running the same hamster wheel.

You’ll cross the Valley of Death—and move into real programs, real funding, and real growth.

‍