What to Do If You Don’t Win an Award

Not getting selected for a DHS SBIR award can feel like hitting a wall. After weeks—sometimes months—of preparing your proposal, receiving a “not selected” notice can be deeply frustrating. But if you’re building a technology that addresses homeland security needs, this moment is far from the end of the road.

Many DHS SBIR awardees didn’t win on their first try. What often separates eventual winners from those who move on is how they respond to that first rejection. This article is designed to help you make the most of your next steps: how to decode the feedback you receive, how to revise your proposal for a stronger resubmission, and what to do if resubmitting isn’t the right option.

If your project aligns with DHS priorities, there are still several powerful avenues—inside and outside the SBIR program—to explore. Let’s walk through how to turn a missed award into your next strategic advantage.

Make the Most of DHS Reviewer Comments

If you’ve applied to the DHS SBIR program and weren’t selected, one of the most valuable resources you’ll receive is reviewer feedback. While DHS does not provide detailed score breakdowns like some grant-based agencies, it typically shares summary comments from technical and business reviewers. These can offer critical insights—if you know how to read them.

DHS SBIR feedback is typically brief and not scored—but still valuable.
These comments reflect how well reviewers think your project fits DHS goals and criteria.

Understand the Format and Timing of DHS Feedback

DHS usually delivers reviewer comments alongside or shortly after the official notification of proposal outcomes. These comments often come as a concise summary rather than a point-by-point evaluation. Unlike agencies such as NIH, DHS does not provide a numerical scoring sheet or “impact score.” However, what they do provide still reflects the consensus of DHS reviewers on where your proposal succeeded—and where it fell short.

Categorize Feedback: Technical, Commercial, Clarity

As you read through your feedback, sort the comments into categories:

• Technical Concerns: Were there doubts about feasibility, methodology, or data? For instance, reviewers may state, “Feasibility was not clearly demonstrated.”
• Commercialization Gaps: Did reviewers question your market plan or DHS relevance? A comment like, “Unclear how this transitions into DHS use” signals this.
• Clarity Issues: Were parts of your proposal confusing or underdeveloped?

Breaking feedback into these buckets helps prioritize improvements for resubmission.

Map Comments to DHS Evaluation Criteria

DHS reviewers assess proposals based on technical merit, innovation, team qualifications, and mission alignment. Try mapping each reviewer comment to one of these areas. For example:

• “The proposer did not provide enough detail on the data analysis methods” = technical merit
• “The path to DHS commercialization is unclear” = mission alignment and commercialization

This mapping allows you to see not just what reviewers disliked, but why those elements mattered.

Treat Criticism as Strategic Input, Not a Verdict

It’s normal to feel defensive about criticism—especially when it’s about a project you’ve poured effort into. But DHS reviewers are often subject-matter experts or end-user representatives. Their insights are your best chance to understand what DHS needs and how to better align your technology with those needs. Even highly rated proposals often contain suggestions. Think of each comment as a data point on how to refine your approach for next time.

How to Improve and Resubmit a DHS Proposal

Rejection doesn’t mean the door is closed. DHS welcomes resubmissions, and many companies have successfully won funding on a second try—after taking the time to strengthen their proposal. Here’s how to do it effectively.

Identify and Prioritize Fixes

Start by reviewing your original proposal alongside the reviewer comments. Note every point of critique, then group them by issue type—technical depth, clarity, commercial strategy, or proposal structure. Create a checklist of concrete fixes. Prioritize the most substantive issues first: if your feasibility or technical approach was a concern, that takes precedence over formatting or grammar.

Strengthen Technical Sections with Evidence

One common weakness in initial DHS proposals is a lack of proof-of-concept data. Reviewers are more likely to support a proposal that shows early evidence, even if preliminary. You might need to run bench-top tests, provide simulation results, or include visuals like system diagrams or workflow charts. Make it easy for reviewers to see that your solution is more than a concept—it’s a plausible, executable plan.

If your methodology was vague, now’s the time to clarify it. Spell out your objectives, milestones, and how each step of your work plan contributes to feasibility. Avoid technical jargon unless it’s defined, and anticipate areas where reviewers may have lacked context.

Clarify Commercialization Path Specific to DHS

Generic market plans won’t win over DHS reviewers. You need to show a credible path for how your solution will transition into DHS use. That includes:

• Naming DHS components or programs that could adopt your technology
• Referencing conversations with end users or acquisition officers
• Including a letter of interest from a relevant DHS office, if available

Refining your Phase III strategy is especially important for resubmission. Emphasize your plan for pilot testing, procurement channels, or potential partners within DHS.

Use External Review and Mentoring

Before you resubmit, get a second set of eyes on your revised proposal. DHS’s “Phase 0” program includes webinars and proposal prep sessions—these are designed to help you write a more fundable application. Many states also offer no-cost SBIR advising through small business development centers or tech incubators. External reviewers can help you catch weaknesses that internal teams often miss.

Don’t resubmit a lightly edited proposal—address all past weaknesses in full.
Reviewers expect meaningful improvements if you want a different outcome.

What to Do if Your DHS SBIR Proposal Isn’t Funded

If resubmitting to the DHS SBIR program isn’t the right move—or if you’re between cycles—there are still valuable next steps you can take. DHS offers multiple alternative pathways for technology development and acquisition, and your solution may be a better fit for one of them. Here’s how to keep momentum going.

Request a Debrief (If Possible)

While not always guaranteed for Phase I rejections, DHS may honor requests for a debriefing. This is especially true for Phase II or higher-value proposals. If your feedback seemed vague or incomplete, consider emailing the DHS SBIR Program Office or contracting officer to politely ask if a debrief is available. Even a short conversation can help clarify why your proposal didn’t succeed and what DHS reviewers prioritized.

Explore Other DHS Pathways

DHS has two non-SBIR programs that support innovation, both of which are worth exploring:

DHS Long Range Broad Agency Announcement (LRBAA)

This is an open, topic-agnostic call for innovative solutions that support homeland security missions. If your technology doesn’t fit neatly into the SBIR topics—or if the topic is no longer open—the LRBAA lets you propose a white paper for DHS consideration. It’s a rolling process and can lead to funding or a contract if DHS expresses interest.

DHS Silicon Valley Innovation Program (SVIP)

If you’re a startup or early-stage company with a commercial-first product that could be adapted for DHS, SVIP may be a match. SVIP funds tech pilots in areas like cybersecurity, border tech, and first responder tools. Unlike SBIR, it emphasizes rapid iteration and end-user feedback.

Look Beyond DHS

Sometimes a project that wasn’t a fit for DHS can still thrive elsewhere. Other federal SBIR programs—like DoD, NSF, and DOE—may have similar mission needs with different emphasis or criteria. For example, a technology rejected by DHS due to limited transition planning might succeed at DoD with a strong military use case. Explore open topics across all 11 SBIR/STTR agencies via SBIR.gov.

Leverage State and Private Sector Resources

Many states offer SBIR matching grants, proposal prep support, and bridge funding for companies between application cycles. Some even provide small grants for companies that submitted but didn’t win—designed to help you revise and try again. Look into your state’s innovation or economic development agency.

Private investment is also worth considering. An unfunded SBIR proposal doesn’t mean your idea lacks potential—it may just need a different narrative or target customer. Accelerators, incubators, and corporate venture arms in your domain may be interested in early engagement.

Final Thoughts: Rejection Isn’t the End

Rejection from the DHS SBIR program can be discouraging, but it doesn’t mean your technology is unviable. In fact, many successful DHS awardees started out with a proposal that didn’t make the cut. What made the difference was their willingness to learn from the process and come back stronger.

DHS evaluates each submission on its own merits—without penalizing applicants for past rejections. This means you can resubmit a refined version of your idea in a future cycle and still be fully competitive. In some cases, reviewers may not even know it’s a resubmission unless you mention it.

Success in the SBIR world often comes down to persistence and continuous improvement. By treating feedback as actionable guidance and exploring all the funding avenues DHS offers, you’re giving your project the best possible chance to move forward.