Lessons From SBIR Transitions: What We've Learned Helping Companies Get to Phase III
Across the Phase III transitions we've supported, a small number of patterns repeat. The companies that get to a signed contract do specific things early. The ones that don't, miss the same things.
The Phase II awards that transition cleanly to Phase III follow a small number of repeating patterns. Most of them are about procedure and customer development, not technology. Most of them are doable. Most of them are not done.
The pattern I saw repeated in every successful Phase III: the contractor was already speaking the contracting officer's language before they asked for the award. They knew the statute, they had a draft DEC, they could tell you which appropriation would fund the work. The unsuccessful Phase IIIs almost always started the conversation cold and tried to learn the language during the negotiation.
Across the Phase II to Phase III transitions we've supported, the differences between the awards that close and the ones that don't are remarkably consistent. The technology rarely decides it. The team rarely decides it. The thing that decides it is whether a small set of procedural and relationship moves got made early enough. These are the lessons that repeat.
Lesson 1: Phase III is a customer-development problem, not a proposal problem.
Most SBIR awardees have a good capture muscle for proposals. They know how to read solicitations, write to evaluation factors, and shepherd a submission through review. None of that helps with Phase III. There is no solicitation. There is no evaluator. There is a customer with a real mission need and a contracting officer who needs documentation.
The companies that close Phase III contracts have usually re-shaped their go-to-market work around customer relationships. They spend the second half of Phase II not refining the prototype but introducing it to operators, identifying the agency program offices that have the mission match, and learning the budget cycle that will eventually fund the work.
Lesson 2: The funding agency is rarely the using agency.
The program office that funded your Phase II is often a research-funding office. They do not operate the resulting capability. They do not have an O&M budget for it. Their job ends when the Phase II period of performance ends. The transition has to flow to a different organization — sometimes inside the same agency, often inside a different agency entirely.
Awardees who treat their Phase II program manager as the path to Phase III are usually surprised when that path doesn't exist. The PMs are friendly and want the technology to succeed, but they don't have the authority or the budget to close the loop.
Lesson 3: The contracting officer's confidence is the second gate.
Once the customer is identified and the budget is on the table, the contracting officer becomes the next gating factor. Many contracting officers have never awarded a Phase III contract. The unfamiliarity translates to caution. Caution translates to schedule slip.
The fix is not to push harder. It is to make the contracting officer's job easier — bring them the statute, bring them a draft DEC statement, bring them an example D&F from another agency, bring them the agency's own Phase III guidebook. Most of the friction disappears once the contracting officer can see the path clearly.
Lesson 4: Documentation drafted in advance is worth ten times what it costs.
The single highest-leverage piece of work an awardee can do during Phase II is to draft, in advance, the documents the eventual Phase III contracting officer will need: a DEC statement, a suggested SOW, a market research summary, a draft D&F. These can all be drafted six to twelve months before they're needed. When the customer is ready and the budget is identified, having a package ready to hand to the contracting officer can compress the award timeline by months.
Lesson 5: Fiscal-year timing is real and it is unforgiving.
Federal budget authority is fiscal-year-specific. Missing a year-end deadline can cost twelve months. The awardees who succeed know which appropriation will fund their Phase III, when that funding expires, and when the next budget cycle starts. The ones who don't usually find out about fiscal-year mechanics by missing a deadline and watching the award slip a full year.
Lesson 6: A Phase III is a beginning, not an end.
The teams that get to a first Phase III sometimes treat it as the finish line. The teams that build durable federal businesses treat it as a baseline. A single Phase III contract creates the legal foundation for follow-on Phase III work with the same customer, with adjacent customers, and with other agencies. The customer relationships, data rights, and contract-file precedent established by the first award are leverage for the next ten.
What's the single biggest factor in whether a Phase II transitions to Phase III?
Whether the awardee started the transition work — customer development, budget identification, and contract-file documentation — before Phase II ended. Companies that wait until Phase II closes are usually too late.
Does great technology guarantee a Phase III?
No. We've seen excellent technology fail to transition because nobody built the customer relationship or the contract documentation, and we've seen modest technology transition cleanly because the awardee did the procedural work early.
Is there a typical Phase II to Phase III timeline?
For awardees who start transition work during Phase II, a Phase III award can sometimes be in place within a few months of Phase II closeout. For awardees who start after Phase II ends, the typical gap is 12–24 months — and many companies never close it.
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