How to Expand Your SBIR Portfolio: Turning One Award Into a Pipeline

A single Phase III contract is a milestone. A portfolio of SBIR-backed federal work is a business. Most companies that successfully build a federal business around SBIR technology do not do it by winning more Phase I solicitations — they do it by extracting more Phase III contracts from the technology they already have.

The structural reason cross-agency expansion works.

The SBIR statute does not tie Phase III to the funding agency. Any federal agency can award Phase III based on your prior SBIR/STTR work, as long as the proposed work derives from, extends, or completes that earlier effort. That single rule unlocks the expansion strategy: one Phase II investment, many possible Phase III customers across many agencies.

Each cross-agency Phase III stands on its own — its own customer, its own scope, its own funding — but they all share the same underlying Phase I/II anchor. That anchor is the asset. Building the portfolio is mostly about finding the right operational customers for the asset you already have.

A three-axis expansion model.

Useful expansion typically runs along three axes simultaneously:

• Cross-customer (same agency). A first Phase III with one program office often opens doors to adjacent program offices in the same agency. The contracting precedent is established; the next deal is procedurally simpler.
• Cross-agency. The same underlying technology can usually support customers at DoD, DHS, DOE, and civilian agencies with adjusted scope. Each requires its own customer development cycle but the contract-file template is reusable.
• Cross-application. The Phase III work doesn't have to look identical to Phase II. Production at one agency, sustainment at another, integration into a different platform at a third — all can be Phase III as long as the DEC nexus holds.

What gets reused, and what doesn't.

The work that's reusable across Phase III awards:

• The underlying Phase I/II technical baseline.
• The core DEC statement structure (with customer-specific scope language swapped in).
• Market research and price analysis methodology.
• The contract-file template (D&F, suggested SOW, suggested clauses).
• SBIR data-rights position.

What does not transfer:

• The customer relationship — every new agency or program office is its own customer-development cycle.
• The funding identification — every Phase III is funded by its own customer's appropriation.
• The contracting officer's confidence — every new contracting officer needs the same education from scratch.

Sequencing matters.

The expansion typically works in this order: first Phase III closes, contract file precedent is established, the company uses that precedent to credibilize itself to a second customer. The second Phase III is usually faster than the first — less education required, an existing contract you can cite, a clean DEC template, and an awardee who now knows how to navigate the process. By the third Phase III, the company is usually building a small contracting infrastructure to support multiple parallel awards.

The companies that try to skip to the third Phase III directly, without ever closing a first one, usually struggle. The first one is the proof point. The portfolio is what becomes possible after.

What "portfolio" really means as a strategic outcome.

A mature SBIR portfolio gives a company three things that no single contract does: revenue concentration risk that drops across multiple customers, reusable contracting infrastructure that lowers the cost of each new award, and a defensible 20-year SBIR data-rights position across multiple deployments. That combination is what makes SBIR-anchored companies attractive long-term federal vendors — and attractive acquisition targets for larger primes.