SBIR Resubmission Strategy: How to Turn a Rejection Into Funding

Rejection rates across the SBIR program run between 75 and 85 percent depending on the agency and the cycle. That means the default outcome for any SBIR proposal — no matter how good the science, how experienced the team, or how well-written the narrative — is a rejection letter. What separates companies that eventually win funding from those that give up is not the quality of their first submission. It is what they do with the feedback that comes back.

Resubmission is not a consolation prize. At NIH, resubmitted applications historically fund at higher rates than new submissions because the revisions are informed by specific, actionable reviewer critiques. At DOD and NSF, resubmission operates differently but carries the same fundamental advantage: you know exactly what the reviewers did not like, and you can fix it.

Getting and Reading Reviewer Feedback

The first step after a rejection is obtaining the most detailed feedback available, and the process varies by agency.

NIH provides summary statements — written critiques from each reviewer on the study section, covering significance, investigator, innovation, approach, and environment. These documents are detailed, sometimes brutally specific, and available through eRA Commons roughly six weeks after the review meeting. Read them in their entirety. Then read them again the next day with fresh eyes. The initial sting of criticism fades, and the actionable content becomes clearer on a second pass.

DOD offers debriefs upon request. After a DOD SBIR rejection, companies can request a debrief from the SBIR program office, which typically provides a summary of the evaluation panel's findings. The specificity of DOD debriefs varies — some are detailed assessments of technical approach and operational relevance, others are generic statements. Request the debrief regardless; even limited feedback is more than most applicants work with.

NSF uses the Project Pitch system, where initial concept pitches receive an invite or decline decision. Declined pitches include brief feedback explaining why the concept was not invited to submit a full proposal. For full proposals that are reviewed and declined, NSF provides panel summaries and individual reviewer comments through Research.gov.

DOE, NASA, and civilian agencies handle feedback inconsistently. Some provide written evaluations, others only notify applicants of non-selection. Check the specific solicitation's instructions for debriefing procedures and request whatever is available.

The NIH-specific nuances of the resubmission process are covered in depth in the NIH SBIR resubmission guide, including how to write an effective Introduction page for amended applications.

Categorizing Feedback Into Actionable Buckets

Raw reviewer feedback is a mix of technical objections, scope concerns, presentation complaints, and occasionally contradictory opinions. Before drafting a single revision, categorize every critique into one of four buckets.

Technical concerns. Reviewers questioned whether your approach will work, whether your preliminary data supports your claims, or whether your methodology is sound. These are the most important criticisms to address because they strike at the core of your proposal. Fixing technical concerns usually requires generating new data, refining your experimental design, or providing stronger evidence for your key assumptions.

Scope and feasibility. Reviewers felt your aims were too ambitious for the Phase I timeline and budget, or conversely, that your scope was too narrow to demonstrate meaningful feasibility. Scope criticism often manifests as comments like "overly ambitious" or "it is unclear how the applicant will accomplish all three aims in twelve months." The fix is recalibrating your aims to match what is realistically achievable, not arguing that reviewers underestimated your capability.

Presentation and clarity. Reviewers could not follow your logic, found the proposal disorganized, or felt that key information was missing or buried. These are the easiest criticisms to fix and the most frustrating to receive because they imply your science might be strong but your writing failed it. A comprehensive reorganization, better figures, and a clearer narrative structure can transform a presentation-penalized proposal.

Commercial viability. Reviewers questioned your market analysis, your commercialization plan, or your team's ability to translate research into a product. Commercial critiques are increasingly common as agencies weight commercialization more heavily in evaluations. Addressing them typically requires adding letters of support, refining market size estimates with real data, or strengthening the business development section of your team.

Building a Response Matrix

Create a document — a simple table works — that maps every distinct criticism to a specific change in the revised proposal. Three columns: the reviewer comment (quoted or paraphrased), the page and section where the revision appears, and a brief description of what you changed and why.

This response matrix serves two purposes. For NIH resubmissions, it becomes the backbone of your Introduction page, where you are required to describe how you addressed prior reviewer feedback. For DOD and NSF resubmissions, the matrix guides your revision strategy even though there is no formal response section in the proposal.

Be comprehensive. If a reviewer raised five concerns, address all five — not just the three you agree with. Ignoring a criticism signals to the next review panel that you either did not read the feedback carefully or disagree with the reviewer's expertise. Neither impression helps your score.

The SBIR complete application guide covers proposal structure and formatting rules that intersect with resubmission strategy, particularly around page limits and supplementary materials.

Agency-Specific Resubmission Rules

Each agency handles resubmissions differently, and getting the procedural details wrong can waste months.

NIH allows one resubmission (A1) per application. The resubmission must include a one-page Introduction section that explicitly addresses reviewer critiques from the prior review. Resubmissions are typically reviewed by the same study section, and the A1 application is evaluated alongside new submissions — it does not receive special treatment in the scoring process, but reviewers can see the prior summary statement and appreciate when concerns have been substantively addressed. If the A1 is not funded, you cannot submit an A2. Instead, you must submit a new (A0) application with a substantially revised specific aims page. In practice, many successful NIH SBIR applicants submit a "new" A0 that incorporates everything they learned from two rounds of review.

DOD does not have a formal resubmission mechanism tied to prior feedback. Each solicitation cycle presents new topics, and a proposal submitted to a new topic is evaluated as a new application. However, you can resubmit to the same technology area in a subsequent cycle, and program managers who remember strong-but-not-funded proposals from prior rounds may be receptive. Referencing that you received and addressed prior feedback — without a formal response section — can be done in the technical narrative.

NSF allows resubmission of Project Pitches at any time after a decline. The revised pitch should address the feedback from the initial review. Full proposals that are declined can be resubmitted in the next solicitation window. NSF does not limit the number of resubmissions, but the program director will notice if the same proposal returns without meaningful changes.

The Resubmission Mindset: Fix More Than What Broke

The most dangerous resubmission strategy is fixing only the issues reviewers flagged while leaving everything else untouched. Reviewer feedback identifies the most visible problems, but a proposal that scored below the funding line usually has weaknesses beyond what made it into the written critiques.

Use the rejection as an opportunity to strengthen the entire proposal. Tighten the specific aims so each aim has a clear milestone and a defined decision point. Sharpen the significance section with updated literature and stronger framing of the unmet need. Improve figures so they communicate results without requiring paragraph-long captions. Add preliminary data if you generated any in the months since the last submission.

Resubmission also means reassessing the competitive landscape. Other companies may have published results, filed patents, or won SBIR awards in your space since your last submission. Updating your innovation section to distinguish your approach from recent developments demonstrates that you are tracking the field, not working in isolation.

One technique that experienced SBIR applicants use: before revising, have someone who has never seen the proposal read it cold and mark every point where they had to re-read a sentence, lost the thread of the argument, or wanted more evidence. Fresh-eye feedback catches presentation problems that you — and possibly the original reviewers — were too close to articulate clearly.

Related SBIR reading:

• Your First SBIR Application in 2026
• Tips for Writing a Successful SBIR Proposal
• SBIR Eligibility Rules 2026

Turning a rejection into a funded proposal is one of the highest-return activities in the SBIR world, and tracking upcoming deadlines across agencies through Granted ensures you never miss the resubmission window that turns last cycle's feedback into this cycle's award.