Founders pursuing federal funding face a choice between SBIR and STTR programs. Both fund technology development without requiring equity. Both operate in three phases. Both connect startups to federal agency missions. But they fund different company structures, require different partnerships, and suit different commercialization paths. Choosing the wrong program costs time, proposal effort, and opportunity.

Here is how SBIR and STTR differ, which one fits your startup, and what gets most applications rejected. This guide draws on work with founders navigating non-dilutive funding, federal agency innovation programs, and I-Corps customer discovery.

The fundamental difference: research partnership requirements

SBIR allows small businesses to perform all research and development work internally. The company controls the technology, hires the team, and manages the project without requiring external research partnerships.

STTR requires a formal research partnership between the small business and a qualified research institution, typically a university or nonprofit research lab. At least 30 percent of the work must be performed by the research partner. At least 40 percent must be performed by the small business. The remaining 30 percent can be allocated to either party or subcontractors.

This structural difference determines which program fits your company. If your startup has the technical capability in-house and does not need university research infrastructure, SBIR offers more control and fewer partnership complications. If your technology depends on university labs, specialized equipment, or faculty expertise, STTR provides the funding and structure to formalize that collaboration.

Eligibility: Who qualifies for each program

Both programs require the company to be a for-profit small business, U.S.-owned and operated, with fewer than 500 employees including affiliates. The principal investigator must be primarily employed by the small business at the time of award and for the duration of the project.

SBIR has no partnership requirements beyond standard subcontracting rules. The company can work alone or bring in subcontractors as needed.

STTR requires a formal cooperative research and development agreement with a nonprofit research institution before application. That partner must be a university, federally funded research and development center, or nonprofit research organization. The partnership must demonstrate genuine collaboration, not just a university lending its name for proposal credibility.

Phase structure and typical award amounts

Both programs operate in three phases. Phase I funds feasibility studies and proof of concept. Phase II funds full research and development toward a working prototype or product. Phase III is commercialization, pursued through non-SBIR funding sources including contracts, venture capital, or revenue.

Phase I awards typically range from $50,000 to $275,000 over six to twelve months, depending on the agency. Phase II awards range from $750,000 to $2 million over two years. Some agencies offer Direct to Phase II pathways for companies with strong preliminary data, allowing them to skip Phase I and compete directly for Phase II funding.

Award amounts vary by agency mission and topic. Defense and intelligence agencies tend to fund at the higher end. Health and energy programs vary. The Small Business Administration SBIR/STTR resources provide agency-specific details and historical award data.

What agencies actually buy: Matching technology to mission need

SBIR and STTR applications fail most often because founders pitch technology without demonstrating mission fit. Agencies do not fund interesting science. They fund solutions to specific mission problems they cannot solve with existing capabilities or commercial products.

Before writing a proposal, founders must answer four questions. What mission problem does the agency face? Which program office owns that problem and controls the budget? What is the current solution and why does it fail? How does your technology address a capability gap the agency cannot close internally?

Customer discovery with agency stakeholders is not optional. Founders should conduct interviews with program managers, end users, and technical leads to validate the problem, understand procurement constraints, and learn what evidence would convince the agency to transition from Phase II to operational procurement.

Proposals that demonstrate mission alignment, cite conversations with agency stakeholders, and articulate a commercialization path beyond the initial award win at higher rates than those pitching generic technology capabilities.

Common rejection reasons and how to avoid them

Most SBIR and STTR applications get rejected for predictable reasons. The technology does not align to the agency topic or mission priorities. The team lacks relevant experience or has no track record delivering similar work. The proposal offers a solution to a problem the agency does not prioritize. There is no evidence of customer discovery with agency stakeholders. The commercialization plan is vague or ignores pathways beyond federal contracts.

Technical reviewers also reject proposals with weak Phase II transition plans, unrealistic budgets that underestimate development complexity, and teams missing critical skills required to execute the work.

Founders improve their odds by aligning proposals to published agency topics, demonstrating prior customer discovery with the target agency, building teams with relevant domain expertise and past performance, articulating realistic commercialization pathways including dual-use commercial applications, and budgeting honestly for the work required rather than stretching thin to hit funding caps.

STTR-specific challenges: Making partnerships work

STTR introduces partnership complexity that SBIR avoids. The research institution and small business must negotiate intellectual property rights before submitting the proposal. Work allocation between the two parties must be realistic and defensible. Communication and project management across institutional boundaries require structure.

Successful STTR partnerships clarify who owns background IP, who controls foreground IP developed during the project, and how commercialization rights will be managed. They establish regular coordination rhythms, clear decision authority, and conflict resolution processes before problems emerge.

Founders should also verify that the university research partner has experience with SBIR/STTR projects and can move at the pace federal contracts require. Academic timelines do not always align with startup urgency or federal reporting requirements.

Which program fits your startup

Choose SBIR if your startup has technical capability in-house, wants full control over IP and execution, does not require university research infrastructure, and can staff the project with internal hires or independent contractors.

Choose STTR if your technology depends on university labs or specialized equipment, faculty or research staff bring essential expertise you cannot hire, your commercialization path benefits from university partnership credibility, or you need the formal structure to convert an informal university collaboration into funded work.

Some startups pursue both. They apply for SBIR when the work can be done internally and STTR when specific projects require university research partnerships. The programs are not mutually exclusive, but each application must meet its program's structural requirements.

For founders ready to pursue non-dilutive federal funding, the work begins with customer discovery focused on a specific agency mission problem. Identify the program office, budget line, and decision-maker who owns that problem. Validate that switching to your solution is worth the organizational friction. Then choose the SBIR or STTR path that matches your team structure and development needs.