Module 13: SBIR/STTR for Small Tech Companies

SBIR (Small Business Innovation Research) and STTR (Small Business Technology Transfer) are federal programs that fund research and development by small businesses. If you build software, AI, or technology products, these programs are designed for you.

How the programs work:

Eleven federal agencies are required to set aside a percentage of their extramural R&D budgets for SBIR/STTR awards. The largest funders are DoD, NIH, NSF, DOE, and NASA. In total, over $4 billion per year flows through these programs.

SBIR vs STTR:

SBIR: your company performs the R&D. You must be a small business (under 500 employees). You do not need a research institution partner, though you can have subcontractors.

STTR: your company partners with a nonprofit research institution (university, federal lab). The small business must perform at least 40% of the work, and the research institution must perform at least 30%. STTR exists specifically to bridge the gap between academic research and commercial products.

Why SBIR/STTR fits technology companies:

Non-dilutive funding. SBIR/STTR awards are contracts or grants, not equity investments. You do not give up ownership of your company.

You retain intellectual property rights. Under SBIR/STTR data rights (codified at 15 U.S.C. 638), the government gets a limited license to use your technology for government purposes, but you own the IP. You can commercialize it freely.

Phased structure reduces risk. You prove feasibility in Phase I (small award) before committing to full development in Phase II (larger award). If your idea does not work in Phase I, you stop without having invested years of effort.

Past performance builder. An SBIR award is a federal contract. It counts as past performance for future bids. This is one of the fastest ways for a new contractor to build a federal track record.

No cost sharing required (SBIR). Unlike many grants, SBIR does not require you to match funds. The government pays for the R&D. STTR may require minimal cost sharing depending on the agency.

Eligibility:

Small business: under 500 employees, for-profit, U.S.-owned and operated, principal investigator primarily employed by the company. STTR additional requirement: formal partnership with a nonprofit research institution.

Common misconceptions:

"SBIR is only for PhD scientists." False. If you build software or AI systems that solve a government problem, you qualify. Many SBIR winners are small software companies, not research labs.

"You need a relationship with the agency." False. SBIR proposals are evaluated on technical merit, not relationships. A strong proposal from an unknown company can win over a weak proposal from an established one.

"SBIR money comes with too many strings." False. The reporting requirements are modest compared to traditional government contracts. Quarterly progress reports and a final report are standard.

SBIR and STTR topics are published on SBIR.gov. Each topic describes a specific problem the government wants solved. Your proposal must address a published topic. You cannot propose random research; it must fit within a topic scope.

How to find topics:

Step 1: Go to sbir.gov and click "Funding Opportunities."

Step 2: Filter by agency. Start with the agencies most relevant to your technology: DoD: the largest SBIR funder. Topics cover cybersecurity, AI/ML, cloud computing, data analytics, communications, EW, and hundreds of other areas. DoD SBIR topics are published through the DoD SBIR/STTR Innovation Portal (DSIP) at dodsbirsttr.mil. NSF: funds fundamental technology research. Topics are broader and more open-ended than DoD. DHS: homeland security topics including cybersecurity, border security, disaster response. DOE: energy technology, grid security, nuclear, renewables. NASA: space technology, Earth observation, aeronautics.

Step 3: Search by keyword within the topic descriptions. Search for terms related to your technology: "machine learning," "natural language processing," "cybersecurity assessment," "compliance automation," "regulatory technology."

Step 4: Read the topic description carefully. Each topic includes: Title: short description of the problem. Technology area: the broader category. Objective: what the government wants to achieve. Description: detailed problem statement and desired capabilities. Phase I expectations: what you must demonstrate in Phase I (usually a feasibility study or prototype). Phase II expectations: what a successful Phase I would develop further. References: technical papers and resources to understand the problem context.

Evaluating whether a topic fits your company:

Does your existing technology address the stated problem? If yes, strong fit. You are not starting from scratch.

Can you credibly demonstrate Phase I feasibility? Phase I is about proving the idea can work, not building a finished product. If you already have a prototype, you have an advantage.

Is the topic aligned with your commercial strategy? The best SBIR proposals come from companies that want to build a product regardless. The government funding accelerates what you would build anyway.

Is the topic too crowded? Some topics receive 50+ proposals. Others receive 5. There is no way to know in advance, but niche topics with specific technical requirements tend to have fewer competitors.

Topic release schedule:

DoD: three open topic cycles per year (Open Topics run continuously, plus periodic targeted topic releases). NSF: accepts proposals year-round through the America's Seed Fund program. Other agencies: typically one or two solicitation cycles per year. Check each agency's schedule on SBIR.gov.

SBIR/STTR awards come in three phases. Each phase has a different purpose, funding level, and timeline.

Phase I: Feasibility Study Purpose: prove that your idea can work. This is concept validation, not product development. Typical award: $50,000-$275,000 (varies by agency). DoD Phase I awards are typically $50,000-$250,000. NSF Phase I awards are up to $275,000. Timeline: 6-12 months. Deliverables: a final report documenting your feasibility results, and a Phase II proposal if successful. What evaluators want to see: a clear technical approach, evidence that the principal investigator has relevant expertise, and a realistic assessment of what Phase I will prove.

Phase II: Full Research and Development Purpose: build and demonstrate a working prototype or system based on Phase I results. Typical award: $500,000-$1,750,000 (varies by agency). DoD Phase II awards are typically $750,000-$1,750,000. Timeline: 24 months. Deliverables: a working prototype, test results, and a commercialization plan. Eligibility: you must have successfully completed Phase I for the same topic. What evaluators want to see: Phase I results that demonstrate feasibility, a credible development plan, and a realistic path to commercialization (Phase III).

Phase III: Commercialization Purpose: transition the technology to production and/or commercial markets. Funding: Phase III is NOT funded by SBIR/STTR money. It is funded by the government agency using non-SBIR procurement funds, by private investment, or by commercial revenue. No competition required: Phase III awards can be sole-source. If a DoD program office wants your SBIR technology in production, they can award you a Phase III contract without competition. This is the goal: Phase III is where SBIR becomes real revenue. A Phase I award of $150K and Phase II award of $1M can lead to a Phase III production contract worth $5M-50M+.

The SBIR funding timeline:

Proposal submission to Phase I award: 3-6 months (varies by agency). Phase I performance: 6-12 months. Phase I completion to Phase II proposal: 1-3 months. Phase II proposal to award: 3-6 months. Phase II performance: 24 months. Total timeline from first proposal to Phase III opportunity: 3-4 years.

This is a long game. SBIR is not quick revenue. It is a strategy for building funded R&D capability and transitioning to production contracts. Companies that succeed in SBIR treat it as a product development pipeline, not a one-time grant.

Success rates:

Phase I: approximately 15-25% of proposals are selected (varies by agency and topic). Phase II: approximately 50-70% of Phase I awardees receive Phase II. Phase III: no published success rate, but companies with strong Phase II results and active engagement with the program office have the highest transition rates.

SBIR proposals that demonstrate regulatory awareness score higher. If your technology has regulatory implications (cybersecurity, data privacy, export control, safety), showing that you understand the regulatory requirements gives evaluators confidence in your commercialization plan.

How to use ClariFAR for SBIR proposal research:

Scenario 1: cybersecurity technology. If your SBIR topic involves cybersecurity tools or services, ClariFAR can help you: Identify which DFARS and FAR clauses your technology helps contractors comply with (ask: "What are the cybersecurity requirements under DFARS 252.204-7012?"). Quantify the compliance gap your technology addresses (ask: "How many NIST SP 800-171 controls relate to access control?"). Cite specific regulatory requirements in your proposal to demonstrate domain knowledge.

Scenario 2: compliance automation. If your technology automates regulatory compliance processes, use ClariFAR to: Map the regulatory requirements your tool addresses (ask: "What are the reporting requirements under FAR 52.204-8?"). Identify the pain points your technology solves (ask: "What happens if a contractor's accounting system is not DCAA-adequate?"). Build a regulatory requirement matrix that shows evaluators the scope of the compliance problem.

Scenario 3: supply chain security. If your technology addresses supply chain risks, use ClariFAR to: Understand counterfeit parts requirements (ask: "What does DFARS 252.246-7007 require for counterfeit electronic parts?"). Map telecommunications equipment restrictions (ask: "What are the prohibitions under Section 889 and DFARS 252.204-7018?"). Cite specific regulatory drivers that create demand for your technology.

Writing the regulatory context section of your proposal:

Most SBIR proposals have a section on the market opportunity or regulatory context. Use ClariFAR to populate this section with accurate, cited regulatory requirements. Example paragraph:

"The Department of Defense requires all contractors handling CUI to implement the 110 security controls specified in NIST SP 800-171, as mandated by DFARS 252.204-7012. Under the CMMC framework (DFARS 252.204-7021), contractors must achieve Level 2 certification, which requires a third-party assessment by an accredited C3PAO. Our technology reduces the assessment preparation time from an average of 6 months to 3 weeks by automating evidence collection and gap analysis across all 14 NIST 800-171 control families."

Every regulatory citation in that paragraph can be verified through ClariFAR's Q&A. This level of regulatory specificity distinguishes your proposal from competitors who write vaguely about "cybersecurity compliance requirements."

The key advantage: evaluators are technical experts, not regulatory specialists. When your proposal demonstrates precise regulatory knowledge alongside strong technical approach, it signals that you understand the full problem, not just the engineering challenge.