In defense SBIR, the prize is not the Phase II award. It is becoming part of a program of record — a funded acquisition program with a line in the budget, a program manager, and a schedule for buying your technology year after year. Most successful Phase II projects never get there, and the reasons have less to do with technology than with budget cycles and relationships.

What a program of record is

A program of record is an acquisition program formally approved and funded in the department's budget. It has an office, a program manager, requirements documents, and money appropriated against a plan. Once a technology is written into such a program, purchases become routine rather than exceptional. Everything outside a program of record — prototypes, experiments, demonstrations, pilot funding — is discretionary and can disappear when priorities shift. That distinction is why two companies with equally good technology can end up in completely different places: one is a line item that gets bought every year, the other is a demonstration that impressed people and then stopped.

The valley of death

The gap between a successful Phase II and a funded program has a name in defense circles: the valley of death. It exists because the two sides are funded from different pots on different clocks. Science and technology money paid for your Phase II. Procurement money buys your product. The office that liked your demonstration frequently has no authority to buy it, and the office that can buy it plans its budget years ahead and has already allocated the years in question.

So a technology can be technically ready and still have no funded home for a long stretch. Bridging it is what pilot and demonstration funding and follow-on award mechanisms are for, but they buy time; they do not create the program.

What actually decides the outcome

  • A named sponsor with a requirement. Not an enthusiast — someone whose program has a gap your technology closes and who will say so in writing.
  • Budget-cycle timing. Federal budgets are built well in advance. To be bought in a given year, a technology usually has to be advocated for during the planning cycle that precedes it by a year or more. Miss that window and you wait a full cycle regardless of how good the demonstration was.
  • Integration reality. Program offices buy things that fit their existing platform, sustainment plan and cybersecurity requirements. A technology that forces the program to change is one the program will decline.

The behavior that follows is unglamorous relationship work: talking to program offices early and often, understanding the requirements chain described in our overview of defense product development, and keeping a working relationship with your program manager alive after the award ends. Many transitions also run through a prime contractor already on the program rather than directly, and the mechanics of federal buying in selling to the government apply either way.

Projects House helps small firms mature hardware to the point where a program office can integrate it. Start with the contact form.