SBIR/STTR Phase II and III: Scaling Your Innovation

Advanced

sbir sttr scaling commercialization phase-ii

Listen up. You’ve won a Phase I SBIR. Maybe you’re celebrating. Good. Enjoy it for exactly twenty-four hours, because statistically, you’re about to fail.

Here’s the reality that keeps me up at night after twenty-five years in Air Force acquisition: seventy percent of Phase I winners never make it to Phase II, and of those who do, sixty percent never see a dollar of Phase III funding. They’re not failing because their technology doesn’t work. They’re failing because they think they’re still selling a product. They’re not. They’re building a partnership, and most don’t realize the rules changed the moment they signed that Phase II contract.

This isn’t R&D anymore. This is operational capability development disguised as small business innovation. Treat it like a science project, and you’ll end up as another cautionary tale in a Program Manager’s briefing slides.

Strategic Foundations: From Prototype to Partnership

Stop thinking like an inventor. Start thinking like a program ally.

Phase I proved your technology could work in a lab. Phase II proves it can work in the hands of a warfighter under brutal operational constraints. But here’s what separates the survivors from the casualties: Phase II isn’t about perfecting your widget. It’s about proving you understand the acquisition ecosystem well enough to become indispensable.

Strategic patience meets operational reality.

You need strategic patience because acquisition timelines are glacial. Budget cycles, POM (Program Objective Memorandum) development, requirements reviews—these move in eighteen-month increments minimum. But you need operational urgency because your Phase II performance period is likely only twenty-four months. That gap between strategic timeline and tactical deadline kills companies.

The shift happens in your head first. In Phase I, you answered to a Technical Point of Contact (TPOC) who cared about technical merit. In Phase II, you’re answering to a Program Manager (PM) who cares about risk reduction, AoA (Analysis of Alternatives) schedules, and whether your solution solves a problem they actually have budget to fix. Different animal entirely.

Innovation within constraints isn’t just a principle—it’s your market entry strategy.

The Department doesn’t need bleeding edge. It needs “edge enough” that fits existing infrastructure, training pipelines, and maintenance concepts. Your Phase II engineering must deliberately constrain innovation to operational realities. If your solution requires new power standards, new security architecture, or new training regimes that aren’t already funded in the POM, you’re not innovating—you’re creating a procurement nightmare.

Operational Leadership: Bridging the Valley of Death

The valley of death isn’t a funding gap. It’s a leadership failure.

I watched hundreds of brilliant technologies die in the gap between Phase II completion and Phase III adoption. Not because the tech failed, but because the company failed to lead the transition. They treated Phase III like a commercialization bonus round when it’s actually the main event.

Build the bridge before you need it.

Operational leadership in Phase II means building relationships with three specific stakeholders simultaneously:

  1. The Requirements Community (The warfighter/user): If they don’t write a requirement document (ICD, CDD, CPD) that describes your capability, you don’t exist in the acquisition system. Period.

  2. The Sustainment Community (Logistics, maintenance, contracting): If they can’t maintain it, field it, and buy spare parts for it through existing supply chains, your technology is a prototype forever.

  3. The Budget Community (FM, PEO resources): If there isn’t a line of accounting that can absorb your solution without a reprogramming action or new-start violation, you’re unfundable regardless of your technical merit.

You must lead cross-functionally across these tribes while managing your Phase II technical deliverables. Miss any one, and you’re building a bridge to nowhere.

Partners, not products.

This is where most small businesses stumble. They walk into Phase II deliverable reviews thinking they’re demonstrating a product. The PM is evaluating whether you’re going to be a reliable partner when the program hits turbulence—and it will. Technical problems are expected. Contractual surprises, schedule slips without early warning, and CYA behavior when things go sideways—these are fatal.

Your Phase II monthly reports aren’t technical documents. They’re relationship management tools. Yes, document the technical progress. But also document the operational risk you’re mitigating, the stakeholders you’re engaging, and the transition path you’re clearing. Show the PM you’re thinking like a program partner, not a grant recipient.

Tactical Execution: The Mechanics of Scaling

Phase II Contract Management: Data Rights are Destiny

Listen carefully because this will save or cost you millions. When you negotiate that Phase II contract, you’re not just negotiating scope and price. You’re negotiating your future commercialization pathway through data rights and deliverables.

CDRLs (Contract Data Requirements Lists) are weapons.

Government Program Offices use CDRLs to capture technical data they need for competition in Phase III and beyond. But if you give away unlimited rights to your core intellectual property in Phase II, you’ve just donated your company to the government. The incumbent advantage in Phase III evaporates when the government owns your designs and can hand them to a defense prime for production.

Tactical moves:

  • Mark every deliverable with specific rights assertions (FAR 52.227-14)
  • Negotiate “developed exclusively at private expense” language explicitly
  • Never deliver source code under unlimited rights unless you’re prepared to become a services company instead of a product company
  • Use the technical data package strategically—give them enough to evaluate, not enough to replicate without you

The Phase III Transition isn’t Automatic

There’s no “Phase III” button in SAM.gov. Phase III funding comes from real programs with real money, usually through:

  • Sole source justification ( FAR 6.302-1 or 6.302-5)
  • Other Transaction Authority (OTA) follow-on
  • Direct insertion into a program of record

You must start planning your Phase III strategy by month six of Phase II, not month twenty-four. If you’re waiting until Phase II is complete to figure out how to get Phase III money, you’re already dead. You just don’t know it yet.

Commercialization Planning That Actually Works

Forget the business school template. Government commercialization planning answers three brutal questions:

  1. Who is the contracting officer who can actually obligate Phase III funds? (Hint: It’s probably not your TPOC)
  2. What specific requirement document validates your solution? (Not “future requirement”—documented, validated, approved)
  3. What color of money will fund transition? (RDT&E? Procurement? O&M? Different approvers, different timelines)

Your commercialization plan should read like an acquisition strategy, not a marketing plan. Include:

  • Specific program offices and PMs targeted for transition
  • POM/budget cycle alignment (when do they next refresh requirements?)
  • Risk mitigation for production scaling (supply chain, CMMC compliance, quality systems)
  • Exit strategy if transition fails (dual-use market pivot)

Buyer Perspective: What the PM Actually Sees

After twenty-five years sitting on the other side of the table, let me tell you what your Phase II effort looks like from the acquisition authority’s chair.

The Risk Calculus

When I reviewed SBIR Phase II deliverables as a PM, I wasn’t evaluating technology—I was calculating risk. Every new small business vendor represents:

  • Schedule risk: Will they deliver on time when the warfighter is screaming?
  • Performance risk: Will it work in the field, not just the lab?
  • Business risk: Will they exist in three years when I need tech support?
  • Political risk: Will Congress/support commands accept a non-traditional vendor for this mission?

Your Phase II execution must systematically mitigate all four. Technical reports mitigate performance risk. Financial transparency and bonding mitigate business risk. Stakeholder engagement and requirement alignment mitigate political risk. Ruthless schedule adherence mitigates the rest.

The “Transition” Reality Check

“Transition” is the dirtiest word in Air Force acquisition because it implies a handoff. There is no handoff. There’s integration into an existing ecosystem that’s already stressed, underfunded, and skeptical.

When you say “we’re ready to transition,” the PM hears “we want you to stop everything you’re doing, change your requirements, find new money, retrain your personnel, and bet your career on our unproven company.” That’s not a transition. That’s a procurement revolution.

Instead, position your Phase II exit as “infusion.” You’re not replacing their system. You’re reducing risk on their existing program. You’re filling a gap they already know they have. You’re the insurance policy, not the disruption.

The Phase III Authorization Game

Phase III doesn’t happen because your technology is awesome. It happens because a Contracting Officer can legally justify sole-source procurement or a PM can obligate OTA funds without competition.

This requires documentation trails you must start building in Phase II:

  • Technical evaluations showing your unique capabilities
  • Cost comparisons proving re-competition would waste resources
  • Letters of support from user communities validating operational need
  • Market research proving no commercial alternative exists

If you haven’t started this paper trail by month twelve of Phase II, you’re not preparing for Phase III. You’re preparing for a polite thank-you letter and a return to commercial sales.

Strategic Takeaways

1. Partners, Not Products—The Final Word

Your Phase II deliverable isn’t the hardware or software you ship. It’s the trust you build. The government doesn’t buy technology from small businesses; it enters into long-term dependencies. Act like a vendor, get treated like a vendor. Act like a mission partner, become irreplaceable.

2. Strategic Patience Requires Tactical Urgency

Yes, acquisition moves slowly. But your burn rate doesn’t. Phase II requires the discipline to invest in long-term relationships while executing short-term technical milestones without compromise. This is the schizophrenic reality of defense innovation. Master it or exit.

3. Innovation Within Constraints is the Only Innovation That Matters

Your Phase II engineering constraints shouldn’t frustrate you—they should guide you. If you can’t fit into existing training, maintenance, and security frameworks, you’ve built a science project, not a defense product. The constraints are the market.

4. Values-Based Decisions Win Phase III

Integrity in data rights assertions. Transparency when schedules slip. Courage to tell a PM their requirements are operationally unsound. These values build the trust necessary for Phase III sole-source justifications. Technical competence gets you to Phase II. Character gets you to Phase III.

The Bottom Line

Phase II and III aren’t funding mechanisms. They’re filters. They filter out inventors who can’t become industrial partners. They filter out technologies that can’t become capabilities. They filter out companies that can’t navigate the brutal complexity of defense acquisition.

You’re not scaling innovation. You’re scaling trust, operational relevance, and organizational maturity. Do it right, and you become part of the national defense industrial base. Do it wrong, and you become a line item in a report about “valley of death attrition.”

The warfighter needs what you’re building. But they need it delivered by a partner who understands that defense procurement isn’t a market—it’s a mission. Think like a strategist. Lead like a program ally. Execute like your company’s survival depends on it.

Because it does.

Dr. Jesse W. Johnson Strategic foundations. Operational leadership. Tactical execution.