Lessons from the Field: 6 Non-Science Reasons SBIRs Get Rejected
Updated: 6 days ago
And what changed at NIH this year that makes them easier to trip over.
It was a Friday afternoon, the application was finished, and the submit button would not work.
The science was done. The budget matched the plan. Every biosketch was in. The system kept saying no, and both help-line numbers went nowhere. Eventually someone reset a password, clicked again, and it went through.
(I aged about a year. The grant was fine.)
I tell that story because most of what sinks a good SBIR has nothing to do with science. Reviewers can only score what reaches them, in the shape it reaches them.
This summer I worked on over 10 applications across NIH, NSF and state programs. The same six problems kept showing up. None of them need better data. All of them can be fixed before you’re even near the deadline.
1. You don't exist yet
To submit an SBIR, your company has to exist in four separate systems. SAM.gov is the federal registry that gives you a UEI, your company's ID number. Grants.gov requires a login.gov sign-in. eRA Commons is NIH's portal. The SBA company registry issues your SBC Control ID. Everyone named on the grant also needs an eRA Commons account linked to ORCID.
Each one is simple. Together they are a relay race where every runner has a different password.
This summer, one client's login.gov account was tied to one email while their Grants.gov role sat under another. Another couldn't find their SBC Control ID and opened a help-desk ticket days before the deadline. A third hit ORCID errors for two team members in the middle of the upload.
All three submitted on time. None of the trouble was science.
The fix: treat registration as the first task on your timeline. NIH says the full chain can take six weeks or more, with three weeks or more for a new SAM registration. For Jan 5, that means the week of November 23 at the latest, and sooner if your company is new to SAM.
2. You're answering ghosts
I once worked with a PI who remembered every bad reviewer comment he had ever received. He answered all of them, in every new application, forever.
One reviewer, one cycle, wondered whether the assay could also work in zebrafish. Nobody on the team worked with zebrafish, and nobody planned to. Every grant after that got a paragraph explaining why zebrafish were a promising future direction. Another reviewer didn't love that the figures used a rainbow color scale, so every Approach section got a sentence defending the color scale, whether the grant had figures or not.
By the time I saw his draft, it was a museum of old objections. Each one had its own little plaque. The science was good, but you had to dig through the defenses to find it, and reviewers don't dig.
One comment from one reviewer is noise. A comment that repeats across reviewers, or across cycles, is a pattern. Only the pattern earns space on the page. How do we know if an objection is worth including pre-emptively? Here’s some guidelines:
Did more than one reviewer say it, in any words?
Did it come up in more than one cycle?
Would a reviewer who never saw the old statement still wonder about it?
Three no's means cut the paragraph. You're answering a question nobody on this panel asked.
The fix: before Jan 5, reread your draft and highlight every sentence that exists to answer a past reviewer. Run each one through the test. If you're resubmitting, answer this panel's summary statement in your Introduction to Resubmission and let the rest go.
3. You said "first ever"
"Never before." "First ever." "No one else has." They feel like strong innovation claims. To a reviewer they read as "I didn't check," and one counterexample from someone on the panel undoes the paragraph.
Specific claims read as expertise. Say what exists, what it can't do, and what yours changes.
Before: "Our platform is the first ever tool to enable real-time monitoring of X."
After: "Current tools measure X once per clinic visit. Our sensor measures it continuously, so clinicians see changes in hours instead of weeks."
The same goes for big outcome claims. One client's reviewers called a "restoring function" claim risky. The team kept the idea and moved it from a headline promise to supporting evidence inside an aim. Same science, far less exposure.
The fix: search your draft for first, never, only, novel, unprecedented and revolutionary. Replace each one with the comparison it's hiding.
4. Your milestones can't be graded
"We will have a working app" is a hope. A milestone is something a reviewer can check with a yes or no: "The assay detects the target in at least 85% of spiked samples by month 6." So yes, essentially, to have a strong milestone, you must set yourself up in a way that there is metric for success…and failure.
This matters even more in a Fast Track (Phase 1 and Phase 2 submitted together). Phase 2 money depends on hitting your Phase 1 milestones as written. Overpromise, and you can lock yourself out of your own Phase 2. The project has to look risky enough to deserve SBIR money and achievable enough to reach the next phase.
The fix: end every aim with a number, a threshold and a timeframe. Make the aims independent, so if Aim 1 fails, Aim 2 still delivers something useful.
5. Your plan and your budget tell different stories
Reviewers read your budget and timeline as evidence of feasibility. One client's PO flagged a six-month drug screening plan as too ambitious. The fix was an updated Gantt chart showing a staged start from day one, using infrastructure the team already had. The plan didn't shrink. It became believable.
The opposite problem is just as common: founders ask for less than they're allowed. Here's the Phase 1 math I walked through with one founding team this summer.
Total costs up to $700,000 for their topic. The NIH guideline is $323,090, and some institutes and topics allow more, up to $700,000. Many don't.
Inside that total, a fee of up to 7% of direct plus indirect costs. It's profit the company keeps and can reinvest. NIH's total includes direct costs, indirect costs and fee.
Indirect costs up to 40% of your direct costs if you don't have a negotiated rate, per NIH's application instructions.
Plus up to $6,500 for TABA (Technical and Business Assistance: help with patents, regulatory work, commercialization), per the 2026 policy.
The 67/33 rule: at least two-thirds of Phase 1 work has to happen inside your company. Consultants and contractors share the other third.
Take the full 40% and the full 7%, and $700,000 breaks down to about $467,290 in direct costs, $186,916 in indirect and $45,794 in fee. Add TABA and their real ceiling was $706,500. Their first draft asked for less.
The fix: build the budget from the plan, then check it against the ceiling. If the gap is big, ask whether the plan is as big as the problem.
6. Your work happens in the wrong place
This one isn't a judgment call. New NIH policy says SBIR and STTR research must be performed in its entirety in the United States. Separately, NIH stopped allowing foreign subawards in May 2025.
One client moved planned animal studies to their CRO's US site. It cost more, but it removed a problem that could have kept the application from being funded at all.
The fix: list every study in your plan, who runs it and where. Get quotes from US-based sites. If foreign work truly is unavoidable, talk to your program officer (the NIH staff member who manages your research area) before you submit.
What changed this year
First, the ground moved. Each change below links to the NIH notice behind it.
Paylines are gone. Since the January 2026 Council round, NIH institutes no longer use a score cutoff. They weigh peer review alongside institute priorities, career stage, geographic balance, and available funds. What to do: say plainly on your aims page why your project fits your institute's priorities.
Your SBIR is still scored on five criteria. Academic R01s moved to a three-factor framework. Small business applications didn't: the current parent SBIR announcement scores Significance, Investigator(s), Innovation, Approach and Environment separately. What to do: don't restructure your application around advice written for R01s.
Review runs in three tiers through January. Panels discuss roughly the top third. The middle third is labeled "competitive but not discussed" and gets written critiques but no score, and can still be funded. NIH extended this through the January 2027 Council round, which covers September applicants. What to do: if you submitted in September, plan for critiques without a number.
NIH may stop releasing scores altogether. An August request for information proposes three labels (most competitive, competitive, not discussed) instead of scores and percentiles. What to do: if you have a view, comment by October 13.
The biosketch moved. The new Common Form biosketch is built and certified in SciENcv, and every senior/key person needs an ORCID linked to eRA Commons. Since May, eRA blocks submissions that don't comply. What to do: get your whole team set up now. It takes longer than anyone expects.
Where the work happens is a rule. See reason 6.
You get nine shots a year, and no late ones. HHS now accepts at most nine new and resubmission Phase I, Fast-Track and Direct to Phase II applications per small business per fiscal year, and NIH no longer accepts late small business applications. What to do: plan your slate for the year, and set your own deadline early.
Money is slower. Several clients have seen the time from submission to first dollar stretch from about six months toward a year. Even a winning September application has an earliest start date of April 2027. What to do: don't build your runway around a spring award.
Comments