SBIR and STTR for Software Companies: Funded R&D as a Federal Entry Point
#contract-vehicles#saas#federal-market
By Philip Luca — Founder of GovExpress; prior domain experience at Bloomberg Government and GovWin IQ.
Most federal market advice for a software company starts at the end of the story: a finished product, a GSA Schedule seat, and a sales team chasing task orders. The Small Business Innovation Research program starts earlier. It pays small companies to do research and development that an agency needs, and it gives the companies that succeed a protected path to selling the result.
For a small software company with a technical idea and no federal customers, SBIR is one of the few routes where the government funds the work before it buys the product. This guide covers who is eligible, what each phase is for, why Phase III is the part that matters, and what the program does not do for you.
What SBIR and STTR are
SBIR is a set-aside of federal research and development budgets. Every agency whose extramural R&D budget crosses the statutory threshold has to run a program and reserve a share of that budget for small businesses. The Small Business Administration sets the policy; each participating agency runs its own topics, schedules and evaluation.
The Small Business Technology Transfer program, STTR, follows the same structure with one addition: the small business must formally partner with a nonprofit research institution, such as a university or a federally funded research centre, and both parties carry a minimum share of the work.
| SBIR | STTR | |
|---|---|---|
| Who performs the work | The small business | The small business and a research institution, under a written agreement |
| Where the principal investigator works | Primarily employed by the small business | May be employed by either party |
| Best fit for a software company | Product teams with in-house engineering | Teams building on university research |
The Department of War runs the largest SBIR program by a wide margin, but civilian agencies with large research budgets run their own, with their own topics.
Who is eligible
The core tests are the same across agencies:
- Size. The company, together with its affiliates, has no more than 500 employees.
- Ownership. The company is majority owned and controlled by US citizens or permanent residents, or by other eligible small businesses. Some agencies also accept majority ownership by venture capital or private equity firms, under limits they choose to adopt.
- Location. The company is for-profit and has its place of business in the United States.
You also need an active SAM.gov registration and a registration with the SBA’s SBIR company registry before you submit. Neither is quick if you have never done it, so start both before a topic you want opens.
SBIR eligibility is not the same as a set-aside certification. You do not need 8(a), HUBZone, WOSB or SDVOSB status. Being small and independently owned is the qualification.
The three phases
Phase I: feasibility
Phase I funds a short, small project to show that your approach is technically feasible and worth developing. For a software company this usually means a working prototype of the core capability against the agency’s stated problem, not a finished product.
Phase II: development
Phase II funds the substantial development work, and it is generally open only to Phase I awardees, although some agencies allow a direct-to-Phase-II award when a company can show feasibility already exists. Phase II is where most of the program’s money sits, and where a software company builds the version an agency could actually run.
Phase III: commercialization
Phase III is work that derives from, extends or completes an earlier SBIR or STTR award, paid for with funds that are not from the SBIR budget. That last condition is what makes Phase III different. It can be a production contract, a follow-on license or an agency-wide deployment, and there is no ceiling on its value or its duration.
Phase III is the prize
The reason SBIR matters for a business, not just a research budget, is that an agency can award Phase III work to the company that did the earlier phases without a new competition. The competition already happened when the Phase I and Phase II topics were awarded.
That makes the earlier awards load-bearing in a way first-time participants often miss:
- Scope your topic response carefully. Phase III has to derive from the earlier work. A Phase II scoped too narrowly gives an agency less room to say a later contract qualifies.
- Find the user, not just the topic. A Phase II that ends without a program office that wants the result ends as a report. The companies that reach Phase III usually started talking to the eventual user during Phase I.
Data rights protect your product
Small software companies often worry that taking federal R&D money means handing the government their code. The program is designed to prevent that.
Technical data and software generated under an SBIR or STTR award carry SBIR data rights. For a protection period that begins at the award, the government may not disclose that data outside the government, and it gets only the limited use the rules allow. Mark your deliverables correctly, because unmarked data can lose the protection.
The protection is real but technical. Read the data rights clause in your award, keep your commercial code base separate from what you deliver where you can, and have someone who reads data rights terms review the markings before your first delivery.
What SBIR does not do
- It does not grant an authorization. Software that will touch government systems or CUI still needs the agency’s security approval. An SBIR award does not grant an ATO, and a Phase III deployment is where that requirement usually lands.
- It does not replace a vehicle. Phase III can be awarded directly, but a buyer who wants to reach you through an IDIQ or a GSA Schedule may still need you on one.
- It does not make you a defense contractor overnight. Topics move on agency schedules, reviews take months, and the gap between Phase I and Phase II funding is a cash-flow problem you need to plan for.
Is SBIR the right route for you?
SBIR is worth pursuing when three things are true: an agency has published a topic your product genuinely addresses, you can turn the topic into a scoped technical project rather than a sales pitch, and you can carry the company through the months between awards.
It also pairs well with the other non-traditional route. A company that has done SBIR work is often a natural participant in an Other Transaction prototype, and both routes reward the same habit: start from a user with a problem.
Score your company’s federal readiness to see where contract vehicle strategy stands next to the other categories buyers look at.
Related reading
The CMMC brief
What the Phase 2 suspension changed and what it did not — the obligations that still bind, the assessment path a contract puts you on, the scoping decision that drives the cost, and the sequence that fits inside a pipeline. Sourced from the primary record.