What to Avoid in SBIR Pursuit: The Mistakes That Kill Phase III Transitions
Some Phase III pursuits die for technical reasons. Most die for procedural ones. These are the avoidable mistakes we see most often, and the cheap moves that prevent them.
Most Phase III pursuits fail for procedural reasons, not technical ones. The avoidable mistakes are predictable. So are the cheap, early moves that prevent them.
Most of the avoidable mistakes I saw on Phase III pursuits weren't dramatic. They were small — a missing marking, a generic DEC paragraph, an unclear funding source — that compounded over months until the award couldn't be saved. The same mistakes also have the smallest fixes. The expensive mistake is letting them sit.
There is a small catalog of mistakes that come up over and over in SBIR pursuit, particularly at the Phase II-to-Phase III transition. None of them are catastrophic on their own. Most of them compound. By the time three or four of them are in play, the award is in trouble for reasons that have nothing to do with the technology. These are the patterns to avoid, and the early moves that prevent them.
Mistake 1: Waiting until Phase II ends to start transition work.
This is the single most common pattern, and the one that does the most damage. Transition work — identifying the customer, securing the budget, drafting the DEC — is not something you can do in the last few weeks of Phase II. By then the team is focused on closeout, the team's bandwidth is committed to deliverables, and the customer-development cycle has not even started.
The early move: start transition work no later than the midpoint of Phase II. Even short conversations with potential using customers, started early, are worth more than months of capture activity started after the fact.
Mistake 2: Treating the SBIR program office as the Phase III customer.
The agency office that funded your Phase II is almost never the office that will operate the resulting capability or pay for it under Phase III. They are a research-funding office. They cannot give you a contract for production or sustainment work. Many awardees burn months treating the funding office as the path to Phase III when they should have been looking for the using customer.
The early move: map the operational customer separately from the funding customer. Identify which agency program office, fleet, or operational unit would actually use the capability if it existed.
Mistake 3: Ignoring the customer's fiscal calendar.
The customer's appetite is necessary but not sufficient. The customer also needs obligated funding in the correct fiscal year. Awardees who ignore the budget cycle find out the hard way: the customer wants the work, the contracting officer is ready, the documentation is clean — and there is no money to obligate because the right appropriation has already expired.
The early move: learn the customer's budget cycle. Know which appropriation will fund the work, when it becomes available, and when it expires.
Mistake 4: Letting a contracting officer write a J&A by default.
Phase III awards do not require a J&A. The Phase III statutory authority is its own justification. Letting a contracting officer default to FAR Part 6 (where the J&A lives) drags the award into a process it does not need to be in, with higher-level review requirements, threshold issues, and rework risk that the SBIR pathway avoids.
The early move: bring the statute, the SBIR/STTR Policy Directive, and the agency's Phase III guidebook to the contracting officer in the same first meeting. Make it easy for them to invoke the right authority.
Mistake 5: Losing data rights through poor marking.
SBIR data rights only protect what gets properly marked at delivery. Unmarked or improperly marked technical data can lose its SBIR protection and fall into a broader-rights category, which is very hard to undo. By the time anyone notices the marking is wrong, the data has often already been distributed inside the government.
The early move: implement a marking discipline during Phase II. Every delivery, every drawing, every line of code. Treat the marking legend like a checklist item, not an afterthought.
Mistake 6: Assuming an OTA or other vehicle is a shortcut around Phase III.
Other Transaction Authority (OTA) and similar non-FAR vehicles are useful for prototyping, but they are not Phase III. Their data-rights regimes are different. Their follow-on-production rules are different. Confusing one with the other — or substituting an OTA for a Phase III when a Phase III was the right tool — can leave the awardee in a worse position both contractually and commercially.
The early move: understand which vehicle solves which problem. If the goal is to commercialize SBIR-funded technology with the strongest possible data-rights position, Phase III is usually the right answer.
What's the most common avoidable mistake in Phase III pursuit?
Waiting until Phase II ends to start transition work. By the time the prototype is delivered, the awardee has no time, no funding, and no customer relationship to fall back on. Transition work belongs inside Phase II, not after.
Is technical capability ever the reason a Phase III fails?
Rarely. Technology that completed a Phase II is almost always technically sufficient for a Phase III. Failure is almost always procedural — wrong customer, wrong funding, wrong documentation, wrong timing.
Can a Phase III award fail in legal review?
Yes. The most common reason is a weak DEC statement that doesn't make the technical lineage between Phase I/II and Phase III clear enough for a reviewer who is not deep in the technology.
Have a Phase II that needs a Phase III path?
A 30-minute conversation. No pitch. We'll tell you what we'd do and whether we're the right fit.
Book a Call