top of page
brainwaves-logo-horizontal.png

Three things people get wrong about SBIR and STTR every single time.

Writer: Melanie Das
Melanie Das
Sep 29
2 min read

Even experienced researchers tend to get these same three aspects of SBIR and STTR wrong.


Person using a red pen to mark corrections on a document, representing common SBIR and STTR mistakes.

For a pair of programs that have been around since the 1980s, SBIR and STTR generate a surprising amount of persistent confusion.


Here are the three misconceptions I run into most often with early-stage founders encountering these mechanisms for the first time.


Myth 1: They're basically the same program with different names.

They're not. They share a structure and run through the same agencies, but the core operational requirement is genuinely different. SBIR keeps the research in your company. STTR requires a formal partnership with a research institution, with specific effort allocations that are written into the award. Treating them as interchangeable when you're setting up your project is how you end up with a structural mismatch between your application and your actual research plan.


Myth 2: You can add a university partner to an SBIR to strengthen the application.

You can absolutely collaborate with university researchers under an SBIR. What you can't do is use that collaboration to meet the effort requirements that STTR is specifically designed for. If a university PI is doing 30 percent or more of the proposed work, you're in STTR territory whether you call it that or not. Reviewers notice when the described collaboration doesn't match the mechanism, and it raises questions you don't want raised.


Myth 3: The STTR partnership agreement is just paperwork.

It is not just paperwork. It is a legal agreement between two institutions covering IP ownership, licensing rights, publication terms, and effort allocation. Universities have legal teams and tech transfer offices that review these agreements on their own timelines, which are almost never aligned with grant deadlines. Founders who treat this as an administrative formality to sort out at the end of the application process consistently run into problems. The agreement needs to be in motion before you've committed to a submission date.


The good news is that all three of these are easy to get right once you know about them. The hard part is that nobody tells you until after you've already made the mistake.




Comments


brainwaves-logo-horizontal.png

Helping science and health organizations secure funding to accelerate their impact.

2261 Market Street PMB 86866,

San Francisco, CA 94114

© 2026 Brainwaves Consulting, LLC

bottom of page