From Stealth to Seed Fund: Detecting Pre-Public Biotech Startups and Choosing Between NIH and NSF SBIR/STTR

TL;DR

• Stealth detection is a mosaic exercise, not a single signal. The strongest inferential indicators that a biotech/deep-tech company is still pre-public are: a filed-but-not-yet-published patent (a provisional, or a non-provisional inside the 18-month publication window), an SEC Form D or PitchBook/Crunchbase funding entry with no press release, incorporation records with no live website, "Stealth" LinkedIn titles, and simultaneous absence from NIH RePORTER and ClinicalTrials.gov. Cross-reference at least three signals before concluding a company is genuinely stealth.

• NIH vs. NSF comes down to whether your value proposition is a specific disease/health outcome or a broadly enabling platform. Choose NIH if your project is tied to a named disease, requires preclinical/human-subjects or FDA-regulated translation, and you can name the institute whose mission you serve. Choose NSF if your innovation is a high-risk, broadly applicable platform with strong intellectual and commercial merit and no clinical-study component (NSF explicitly returns clinical-study proposals without review).

• The dollars and mechanics differ materially in 2026. NIH's standard guideline caps (as of April 2026, per NIH SEED) are $323,090 (Phase I) and $2,153,927 (Phase II), with institute waiver ceilings up to $700,000 / $3,000,000; NSF Phase I is capped at $305,000 and Phase II at $1,250,000. NIH accepts unsolicited applications three times a year and lets you self-define the project; NSF requires an invited Project Pitch first and takes no clinical work. Both programs were reauthorized through September 30, 2031 by the Small Business Innovation and Economic Security Act (S. 3971 / P.L. 119-83), signed by President Trump on April 13, 2026.

PART 1 — HOW TO TELL IF A BIOTECH COMPANY IS STILL IN STEALTH

What "stealth" means and how long it lasts

Stealth mode is a deliberate strategy of minimal public exposure — no website, no press, minimal LinkedIn presence — while a company builds foundational science, IP, or go-to-market strategy. Analysts distinguish "total stealth" (no public-facing information at all; "Stealth Biotech" listed on LinkedIn) from "partial stealth" (a basic website or vague messaging exists but the core IP or business model is hidden). Deep-tech, AI, and biotech companies commonly run long-term stealth of one to five years because of extended R&D and regulatory timelines. The primary rationale is IP protection during the window before patents are secured, plus quiet talent recruitment and undistracted product development.

Signal 1 — Patent filing patterns (the most reliable inferable signal)

A provisional application is never published by the USPTO and automatically lapses at 12 months if not converted, so a company relying only on provisionals leaves no searchable patent footprint. A non-provisional (utility) application publishes 18 months after the earliest priority date under federal law — critically, that clock runs from the provisional filing date, so a converted application can publish sooner than founders expect. A company can therefore be operating with filed IP that is not yet public. Non-publication requests can also keep an application secret until it grants, but this binds the applicant to a US-only filing strategy.

Practical method: search USPTO Patent Public Search and Google Patents by inventor or founder name, not company name, since stealth entities often file under founders or assign the patent later. A named founder-inventor with no assignee, or an assignee shell with no web presence, is a strong stealth indicator.

Signal 2 — Funding records without public announcement

An SEC Form D must be filed within 15 days of the first sale of securities in a private raise, and it appears on EDGAR before any press coverage typically follows. However, research from Lehigh University finance professors documents that the majority of venture-capital-backed financing rounds are not accompanied by a Form D filing at all, and that rounds by firms with more proprietary information — especially early-stage, biotech, pharmaceutical, and high-tech companies — are less likely to file one. So a Form D is a positive signal when present, but its absence is not disconfirming for exactly the biotech companies you most want to find.

PitchBook and Crunchbase entries labeled "Stealth," "Stealth Mode," or "Stealth Biotech," or a round marked "Series Unknown" or undisclosed with no press release, are direct tells. Monitoring keyword filters on "stealth mode" in company descriptions can surface self-labeled companies even with free-tier database access.

Signal 3 — Incorporation vs. public disclosure gap

A live entity in a state's corporate registry (such as Delaware) with a reserved domain but no live website is a leading indicator. In the UK, a "dormant" status on Companies House can similarly signal a company quietly in development.

Signal 4 — Registry absences (the biotech-specific mosaic)

A genuinely stealth therapeutics or diagnostics company will typically be absent from all of the following: NIH RePORTER (no federal grants), ClinicalTrials.gov (no registered trials), SEC EDGAR (no public filings or Form D), FDA databases, and press or PR wires — while present in incorporation records and possibly a venture capital firm's portfolio. The combination of absences is the signal; any one absence alone is weak evidence.

Signal 5 — Team and LinkedIn hints

Founders listing "Stealth," "Stealth Startup," or "Building something new" alongside a real employment start date; senior scientific hires (VP of Research, Chief Scientific Officer) with no named employer; and job postings referencing NDAs all indicate an active but undisclosed company.

De-anonymizing tool — NIH RePORTER

The moment a stealth company accepts an NIH SBIR or STTR award, RePORTER exposes its legal name, principal investigator, project abstract, funding institute, and dollar amount. RePORTER's "similar projects" feature and activity-code filters (R41/R42 for STTR, R43/R44 for SBIR) let researchers map a company's technology, competitors, and assigned program officers. Several commercial lead-intelligence services now productize exactly this approach — mining SBIR.gov, NIH RePORTER, NSF Award Search, and SEC Form D data into daily "just-emerged" lead boards.

Checklist — is this company still in stealth? Score the mosaic across these indicators:

- No public website, or only a one-page holding page

- "Stealth" LinkedIn titles, or an unnamed employer for senior hires

- An active incorporation record with no product information

- Funding visible in PitchBook or Crunchbase but no press release, or a Form D on EDGAR with no announcement

- Provisional or unpublished (under 18 months old) patents filed under founder names, with no published applications

- Absent from NIH RePORTER

- Absent from ClinicalTrials.gov

- Present in a sector-focused VC's portfolio

Three or more of these present at once is high confidence the company is genuinely pre-public.

PART 2 — NIH SBIR/STTR: STRUCTURE, MONEY, CRITERIA, TRL

Structure

NIH is the dominant health-focused SBIR funder, awarding over $1.2 billion per year across its 27 institutes and centers. SBIR awards are coded R43 (Phase I) and R44 (Phase II or Fast-Track); STTR awards are coded R41 and R42. Applicants respond either to the Omnibus/parent solicitation or to targeted institute funding opportunity announcements, and can pursue Phase I, Fast-Track, or Direct-to-Phase-II pathways. The award always goes to the small business; STTR requires a subaward to a nonprofit research institution and permits a principal investigator who is not primarily employed by the company.

2026 funding amounts (per NIH's SEED program office, effective April 2026)

Phase I standard guideline (soft cap): $323,090 total costs, over six months to two years.

Phase II standard guideline: $2,153,927 total costs, over one to three years.

Commercialization Readiness Pilot: up to $4,191,495, over up to three years.

Institute waiver ceilings: up to $700,000 for Phase I and up to $3,000,000 for Phase II at institutes such as NINDS, NIDA, and NIDCD for SBA-approved waiver topics, plus a newer Phase IIB Strategic Breakthrough funding lane.

Budget guidelines are identical for SBIR and STTR, but each institute sets its own limits, so checking the funding document for your target institute can meaningfully change your available budget. Note that older sources may still cite the previous, now-superseded caps of $314,363 and $2,095,748.

Review criteria (2025 Simplified Framework)

Five regulatory criteria — Significance, Investigators, Innovation, Approach, and Environment — are now organized into three review factors: Factor 1, Importance of the Research (combining Significance and Innovation, scored 1 to 9); Factor 2, Rigor and Feasibility (Approach, scored 1 to 9); and Factor 3, Expertise and Resources (combining Investigators and Environment, evaluated as sufficient or insufficient). Scoring runs from 1 (exceptional) to 9 (poor), and the overall impact score is not a simple arithmetic average — a fatal flaw in the Approach criterion can sink an otherwise strong application. Approach is empirically the strongest predictor of whether an application gets funded. Study sections typically include 15 to 20 domain scientists, with about three reviewers assigned per application.

TRL expectations

NIH Phase I typically supports technology readiness levels 2 through 4 — exploratory research and feasibility work for medical technologies — aligning closely with the FDA approval pathway. Phase II moves toward prototype and validation work, roughly TRL 4 to 6. NIH study sections generally expect preliminary data even at Phase I, such as in vitro results, animal model data, or a published proof of concept; unlike some other agencies, topic responsiveness alone cannot compensate for a thin data package. Common rejection causes for biotech applicants include proposing Phase II-level scope within a Phase I application, and failing to address the FDA regulatory pathway in the commercialization plan.

Success rates

NIH is widely regarded as the most competitive SBIR program in the federal government. Phase I success rates have historically run roughly 15 to 18 percent, with institutes like NCI and NIAID being especially competitive; some more recent analyses cite an overall rate closer to 12 percent (roughly 10 percent for Phase I and 18 percent for Phase II). Resubmission materially improves odds — one historical NCI dataset showed roughly 14 percent success for original submissions versus roughly 24 percent for resubmissions.

PART 3 — NSF SBIR/STTR: STRUCTURE, MONEY, CRITERIA, TRL

Structure

NSF's SBIR/STTR program, branded "America's Seed Fund," awards about $200 million annually and funds roughly 400 companies per year, administered by the Directorate for Technology, Innovation and Partnerships. Awardees from fiscal years 2014 through 2023 raised an estimated $28 billion in private investment combined, with roughly 450 exits. NSF takes no equity and awardees retain full ownership of their intellectual property. The defining structural feature is the mandatory Project Pitch: applicants must submit a short pitch and receive an invitation from a program director before submitting a full proposal; uninvited proposals are returned without review. NSF funds broadly across nearly every technology area rather than soliciting specific topics.

2026 funding amounts (per NSF's May 2026 solicitation)

Phase I: up to $305,000, over six to eighteen months, inclusive of all direct and indirect costs, fee, technical assistance funding, and optional entrepreneurial training.

Phase II: up to $1,250,000, typically over 24 months.

Fast-Track pilot: up to $400,000 for Phase I plus up to $1,155,000 for Phase II.

Technical assistance: up to $6,500 in Phase I for commercialization activities, plus roughly $25,000 budgetable for entrepreneurial training programs.

Relevant life-science topic areas include Biological Technologies (covering synthetic biology and metabolic engineering, bioinstruments and biosensors, cell and tissue engineering, life-science research tools, microbiome work, and plant or animal biotechnology) and Biomedical Technologies (covering diagnostics, drug delivery methods, materials for biomedical applications, medical imaging, and monitoring devices).

Review criteria

NSF reviews proposals on three criteria: Intellectual Merit (the potential to advance knowledge via fundamental science or engineering that overcomes real technical risk), Broader Impacts (societal or economic benefit), and Commercial Impact or Commercialization Potential. Reviewers classify novelty into tiers, with a genuinely new scientific principle scoring highest and pure engineering optimization rarely scoring competitively. Proposals to NSF are kept confidential and do not constitute public disclosure — only a funded company's abstract eventually becomes public. Letters of support from customers are not allowed at the Phase I stage, but are required at Phase II; as of June 2026, these letters have returned as a requirement for NSF Phase II proposals.

TRL expectations

NSF Phase I typically starts around TRL 1 to 3 and advances to roughly TRL 3 to 4. The program is explicitly intended for high-risk research and development, not straightforward engineering or incremental product development. Crucially, clinical studies are considered non-compliant with NSF's scope — limited human-subjects work is allowed only for feasibility or proof-of-concept purposes, not clinical trials.

Success rates

NSF funds roughly 12 to 20 percent of Phase I applications historically, with Phase II rates considerably higher in some years. In one recent five-year window, 85 percent of Phase I awards went to companies with five or fewer employees, and 72 percent went to companies founded within the prior three years.

PART 4 — WHICH AGENCY FITS WHICH BIOTECH PROJECT

The core distinction is orientation: NIH is organized around a specific disease or health outcome and institute mission, while NSF is organized around broadly enabling platforms judged on intellectual and commercial merit.

On funding size, NIH's 2026 caps are higher — $323,090 for Phase I (up to $700,000 for waiver topics) and $2,153,927 for Phase II (up to $3,000,000 for waiver topics) — compared with NSF's $305,000 Phase I and $1,250,000 Phase II caps.

On timing, NIH Phase I projects run six months to two years, while NSF Phase I runs six to eighteen months.

On entry process, NIH accepts direct applications with no pre-invitation required, while NSF requires a mandatory invited Project Pitch before a full proposal can be submitted.

On deadlines, NIH has three standard cycles per year (roughly September, January, and April), while NSF ties deadlines to when a Project Pitch invitation is issued, with several windows across the year.

On review criteria, NIH scores Significance, Investigators, Innovation, Approach, and Environment on a 1-to-9 scale, while NSF scores Intellectual Merit, Broader Impacts, and Commercial Impact.

On clinical and human-subjects work, NIH actively supports it through Clinical Trial Optional funding announcements, while NSF does not allow it and returns such proposals without review.

On preliminary data, NIH generally expects it even at Phase I, while NSF is more tolerant of early-stage, high-risk concepts with less preliminary data.

On majority venture-capital ownership, both agencies allow it under specific conditions, with NIH having formally opted into this eligibility authority.

On typical technology readiness level at Phase I, NIH sits around TRL 2 to 4, while NSF sits around TRL 1 to 3.

Neither program takes equity; both are structured as grants.

Project-fit heuristics

Choose NIH if your product is a therapeutic, diagnostic, or device tied to a named disease or condition; if you need preclinical, animal-model, or human-subjects work; if your commercialization path runs through an FDA regulatory pathway such as an IND, 505(b)(2), 510(k), or PMA; if you can name the specific institute whose mission your work serves (searching RePORTER for similar prior awards can identify the right institute and program officer); if you want access to a larger Phase I or Phase II budget; or if your company is majority-owned by venture capital.

Choose NSF if your innovation is a broadly applicable platform or enabling tool — a research instrument, biosensor, synthetic-biology chassis, computational biology tool, or manufacturing and biomanufacturing process — whose value isn't tied to one specific disease; if you are pre-preliminary-data and carrying high technical risk; if there is no clinical-study component to your work; and if you can clearly articulate both fundamental technical risk (intellectual merit) and a genuine commercial market.

A note on pursuing both agencies: it is illegal to accept duplicate funding for the same work, and both agencies require disclosure of overlapping or equivalent proposals on Current and Pending Support forms. Program officers at NIH and NSF do coordinate on overlap. You may pursue genuinely distinct projects at each agency — for example, an NSF-funded enabling platform alongside an NIH-funded disease-specific application — but the scope of each must be clearly delineated. NIH will not review duplicate or highly overlapping applications simultaneously, even across different activity codes, allows one resubmission within a 37-month window, and HHS now caps submissions at nine per small business per fiscal year. NSF allows only one proposal per principal investigator under review at a time, and permits resubmission of a returned-without-review proposal under the same Project Pitch within two subsequent deadlines.

CASE EXAMPLES

NSF — platform and enabling technology fit: Shasqi, a company developing targeted "click chemistry" drug activation led by a physician-chemist founder, began with an NSF SBIR grant when it was too early-stage for venture capital. Yesse Technologies, developer of a "nose on a chip" odor-sensing platform, progressed from a $225,000 Phase I award to a $750,000 Phase II award. Azitra, which engineers the skin microbiome to treat skin disease, and Caption Health, which built an AI-guided ultrasound platform, are both NSF-funded life-science companies. These companies share the broad-platform, high-merit profile that NSF tends to reward.

NIH — disease-specific translation fit: An economic-impact study of NCI's SBIR program found that 444 companies received NCI Phase II funding across 690 projects between fiscal years 1998 and 2010, against an NCI investment of $787 million; 53 percent of those projects resulted in product or service sales, generating an estimated $9.1 billion in total sales and roughly 108,000 jobs. As a representative example, one company received a $1.5 million Phase II award from NINDS in 2018 to develop a bioabsorbable surgical clip, using the funding to accelerate development and cover commercialization costs. Therapeutics and diagnostics tied to a specific condition — cancer, neurological disease, infectious disease — represent the NIH sweet spot.

RECENT POLICY CHANGES EVERY BIOTECH APPLICANT SHOULD KNOW (2025-2026)

Reauthorization through 2031: After the prior authorization lapsed on September 30, 2025 — halting new awards during roughly a six-month freeze — the Small Business Innovation and Economic Security Act passed the Senate by voice vote on March 3, 2026, passed the House 345 to 41 on March 17, 2026, and was signed into law by President Trump on April 13, 2026, extending SBIR/STTR through September 30, 2031. The roughly $6 billion measure also created a new "strategic breakthrough award" of up to $30 million, requiring a 100 percent private-capital match.

New national-security and foreign-influence rules: National-security reviews are now mandatory, and awards are prohibited to companies with specified foreign ties. HHS due diligence now covers cybersecurity, patent analysis, employee analysis, foreign ownership and affiliations, investment relationships, licensing, joint ventures, and business relationships with countries of concern. Applicants must be prepared to document ownership structure, capital origin, IP control, and any foreign affiliations of key talent.

NIH-specific changes: HHS now limits SBIR/STTR submissions to nine per small business per fiscal year, and small-business applications are no longer eligible for NIH's late-submission policy. NIH reissued its parent funding announcements in late May 2026, with the submission window reopening August 5, 2026, and the first standard deadline around September 5 or 8, 2026, followed by January 5, 2027, and April 5, 2027. NIH maintained its study-section infrastructure through the funding freeze, allowing a fast restart.

NSF-specific changes: NSF released a new solicitation in May 2026, reframed around developing deep technologies that advance U.S. competitiveness and security, replacing the prior solicitation series. New Project Pitch submissions opened June 2, 2026, with full-proposal deadlines including late July 2026 and early November 2026, then settling into a recurring pattern of the first Wednesday in November, first Thursday in March, and first Wednesday in July annually. Letters of support also returned as a requirement for NSF Phase II proposals as of June 2026.

Budget-environment caveat: The administration's FY2026 discretionary budget request proposed a roughly 37 percent cut to NIH and more than a 50 percent cut to NSF. Because each agency's SBIR/STTR set-aside is a fixed percentage of extramural R&D spending under the 2026 reauthorization, enacted cuts of that scale would proportionally shrink these programs. As of this writing, these are proposals, not enacted appropriations, and should be treated as a risk factor rather than a certainty.

RECOMMENDATIONS

For founders deciding between NIH and NSF, a staged approach works well:

First, classify your value proposition. Write one sentence: "Our technology enables or treats ___." If the blank is a named disease or an FDA-regulated product, start with NIH. If it's a broadly applicable capability, start with NSF. If any Phase I aim involves a clinical study, NSF is disqualified outright — go to NIH.

Second, for NIH candidates, run the RePORTER test. Search NIH RePORTER for prior R43/R44 awards matching your keywords. If several overlapping projects were funded by one institute, that institute is your target, and it's worth contacting its SBIR program officer at least a month before the deadline.

Third, for NSF candidates, run the Project Pitch test early. Draft and submit the pitch as soon as possible; the invitation — or its absence — is a fast, free signal of fit. Without an invitation, a full proposal isn't worth the effort.

Fourth, match your technology readiness level and data package to the agency. If you have preliminary in vitro or animal data and a clear regulatory story, NIH rewards it. If you're pre-data with high technical risk and a genuinely fundamental science question, NSF is the better home.

Fifth, optimize the budget ask. NIH candidates should check whether their target institute has waiver topics allowing requests up to $700,000 for Phase I or $3,000,000 for Phase II without a separate individual waiver. NSF candidates should budget the $6,500 in technical assistance funding and roughly $25,000 in entrepreneurial training within the $305,000 cap.

Sixth, consider a deliberate dual-agency strategy for more advanced situations — funding an enabling platform at NSF and a specific disease application at NIH — but delineate the scope of each precisely and disclose both on Current and Pending Support forms to avoid overlap issues.

For consultants qualifying stealth-company prospects, build a mosaic score using the eight-point checklist above, treating any single signal as weak evidence and requiring at least three simultaneous signals for a "genuinely stealth" classification. Automate a primary-source sweep across SEC EDGAR Form D filings, USPTO and Google Patents searches by founder name, state incorporation records, NIH RePORTER, NSF Award Search, and ClinicalTrials.gov. The transition from stealth to public visibility is often first detectable through a RePORTER award or a Form D filing — sometimes days or weeks before any press coverage follows. Time outreach to that emergence moment: a newly posted SBIR award, a first published patent, or a first Form D filing marks the window when a stealth biotech becomes a warm prospect for funding-strategy help.

Two benchmarks worth watching: if enacted FY2026 or FY2027 appropriations cut NIH or NSF R&D funding substantially, expect paylines to tighten and success rates to fall below the historical 15-to-18-percent (NIH) and 12-to-20-percent (NSF) ranges, which would argue for prioritizing resubmission quality and earlier-cycle submissions. And if a company becomes majority-owned by a single VC or private equity firm at more than 50 percent, it loses SBIR eligibility at most agencies — restructuring the cap table so no single investor exceeds 50 percent ownership should happen before applying.

CAVEATS

Cap figures move over time. The most current NIH guideline caps as described here — $323,090 for Phase I and $2,153,927 for Phase II — reflect NIH's SEED program office guidance as of April 2026; older sources still cite the previous $314,363 and $2,095,748 figures, or direct-cost-only figures that understate the true total. Always confirm against the live solicitation before finalizing a budget.

Success-rate figures vary by source and year, and are sometimes conflated across grants versus contracts, or Phase I versus Phase II. Treat the ranges given here as directional rather than precise.

Stealth detection is inferential by nature. Absence from a registry can reflect genuine stealth, or simply reflect a company that hasn't yet needed federal funding or registered a trial. False positives are common, and no single signal should be treated as proof — notably, the biotech firms most worth finding are also the least likely to file a Form D.

Policy is in flux following the recent reauthorization. New foreign-influence and national-security due-diligence rules, the nine-submission HHS cap, and reissued funding-announcement numbers are all recent developments — verify current deadlines and requirements directly against the agencies before relying on them.

Finally, the FY2026 budget cuts described above are proposals, not enacted law. Any statement about future NIH or NSF SBIR funding shrinkage is contingent on appropriations that had not been enacted as of this writing.

One of the Best AI Prompts for Finding Non-Dilutive Funding for Your Startup

There is a lot of grant money out there for innovative tech. You do not have to give up any equity to get it.

The problem? It is scattered across dozens of websites. No single place pulls it all together.

Founders miss out all the time

I recently spoke with a founder building a niche technology. He just missed the perfect grant. It would have funded his work. He simply never knew it existed.

AI tools help, but they miss things

Plenty of AI tools try to solve this. We have never found one that catches everything.

So we use a prompt as a backup. It is one of the same prompts we use to find opportunities for our clients.

How the prompt works

It is simple:

1. It asks about your technology and your company.

2. It searches the funding sites we recommend.

3. It gives you a list of the 10 best grant and contract opportunities for your tech.

It works with all the major models. Claude Opus 4.8, ChatGPT, Gemini, take your pick.

Want it?

Does NSF SBIR/STTR Fund Research, Not Development? Here's the 2026 Answer

Short answer: No — not in the absolute sense the claim implies. NSF SBIR/STTR funds commercialization-oriented R&D. A Phase I proposal wins when it centers on resolving high-risk technical uncertainty, not when it simply avoids the word "development." The real dividing line isn't research vs. development — it's high-risk R&D vs. straightforward engineering or incremental product build-out.

This is a common question for founders scoping their first NSF Phase I proposal, usually triggered by a widely shared Reddit thread claiming NSF proposals get rejected for being "too developmental." Below is what NSF's own 2026 guidance says, where that popular claim holds up, and where it oversimplifies.

Where the "research, not development" claim comes from

The claim traces back to a real document: George A. Hazelrigg's Research 101 for Engineers, hosted on NSF's America's Seed Fund site. After reviewing "many hundreds" of panels and thousands of proposals over 30 years at NSF, Hazelrigg concluded that proposals framed around new knowledge outperformed those framed around building an artifact. He defines research as the process of finding out something not already known, and argues that artifact-centered proposals tend to read as development and score lower.

That's a real and useful data point. But the same document includes a caveat easy to lose in a social-media summary: it explicitly states the views are the author's own and don't necessarily reflect NSF or federal policy. It's applicant guidance from deep institutional experience — not a binding statement of current program rules.

What does NSF actually fund in 2026?

NSF funds high-risk technical R&D with a credible path to commercialization — not research in a purely academic sense, and not routine engineering. The 2026 SBIR/STTR solicitation frames the program as relaunching to help startups and small businesses turn high-risk technologies into products and services with commercial impact, offering up to $2 million total across Phase I (up to $305,000, 6–18 months) and Phase II (up to $1.25 million).

NSF's own "What is R&D?" guidance sharpens the target further: the project should determine the scientific and technical feasibility of a new concept that could become a product, process, or service. That definition is broad enough to include design, development, and improvement of prototypes — so "development" itself isn't disqualifying. What NSF screens out is work that's really just execution: building something whose feasibility is already known.

Where exactly is the line between R&D and disqualifying "development"?

The line is between resolving genuine technical risk and doing predetermined engineering work. NSF's Project Pitch — required before any Phase I full proposal — asks applicants to show the work will prove technical feasibility or significantly reduce technical risk, and states plainly that proposed work must be R&D "rather than straightforward engineering or incremental product development tasks." Describing product features or customer benefits isn't sufficient; applicants have to name the specific high-risk technical innovation and the R&D needed to prove it out.

This shows up again in the full proposal instructions: the project summary must identify the technical hurdles the R&D addresses and why they're crucial to commercialization, and the project description needs a detailed R&D plan with milestones, risk mitigation, and quantitative success criteria — a generic task list can get a proposal returned without review.

So is "avoid development framing" the main reason proposals get rejected?

No — and treating it as the single dominant failure mode is the biggest way this popular claim oversimplifies things. NSF's merit review runs on three explicit criteria: Intellectual Merit, Broader Impacts, and Commercial Impact. Reviewers also weigh market opportunity, durable technical advantage, business model strength, and team readiness. NSF doesn't publish a ranked list of decline reasons — only the criteria proposals are judged against — so any claim about "the number one reason" should be treated with caution.

Consulting sources reinforce that rejections are usually multifactorial, not single-cause:

• The NC Small Business and Technology Development Center flags poor agency fit, overpromising against the available budget/timeline, unclear measurable milestones, and insufficient innovation (a tweak rather than a genuine advance) as recurring pitfalls.

• A University of Wisconsin Center for Technology Commercialization recap of a BBCetc workshop quotes consultant Megan Varnum on NSF wanting "revolutionary, not evolutionary" technology, paired with aggressive commercialization plans and real market understanding — plus credible letters of support tied to actual partners or customers.

• E.B. Howard Consulting points to a more mundane but increasingly costly failure mode: teams working from stale templates instead of treating the solicitation, the America's Seed Fund instructions, Research.gov materials, and NSF's Critical Information page as one connected system.

What changed in the 2026 NSF SBIR/STTR cycle?

NSF consolidated its solicitation structure and tightened the pipeline rules teams need to plan around. NSF 26-510 (posted May 2026) merged the old separate Phase I, Phase II, and Fast-Track solicitations into one. Full proposal deadlines are now July 27, 2026; November 4, 2026; and March 4, 2027, with annual cycles after that. Phase I proposers still need an invited Project Pitch before a full proposal is reviewed.

Three practical changes matter most for founders scoping applications:

1. One active project, two pitches, two proposals. A company can have only one Phase I or Fast-Track project under review at a time, may submit at most two Project Pitches in any 12-month window, and at most two full proposals per fiscal year — making early screening and timing strategy more important than in looser prior cycles.

2. Letters of support are mandatory again. Standard Phase I and Phase II proposals need at least one Letter of Support (Fast-Track needs three), and letters must come from real stakeholders — potential customers, strategic partners, investors — not consultants or subcontractors. NSF wants these letters to validate market demand and reduce non-technical risk.

3. Post-award scrutiny is real. Successful proposals now face a due diligence process that can include clarification requests, research-security checks, and legal certifications, plus a separate financial capability review for Phase II that can take months and affect final budget.

The bottom line for founders writing a Phase I proposal

A winning NSF SBIR/STTR narrative has to hold up on three fronts simultaneously, not just one:

• A technically substantive R&D plan with measurable milestones and quantitative success criteria that clearly targets unresolved technical risk, not assumed-solved engineering.

• A broader impacts case showing tangible societal benefit.

• A commercialization case with real market opportunity, technical defensibility, and a credible business model — backed by letters of support from actual market stakeholders.

The fastest way to sink an NSF SBIR/STTR application is to pitch routine product development when NSF is looking for high-risk, commercialization-relevant R&D that proves technical feasibility — but that's only one failure mode inside a broader scoring framework that also weighs market, impact, team, and execution. Get the research-vs-development framing right, and you've cleared the entry bar. The proposal still has to win on the other three criteria.

FAQ

Does NSF SBIR/STTR fund development work at all? Yes. NSF's own R&D definition explicitly includes design, development, and improvement of prototypes and new processes. Development isn't disqualifying — development without an unresolved technical-risk question behind it is.

Is the Hazelrigg "Research 101" paper official NSF policy? No. It's NSF-hosted applicant guidance from a former NSF program veteran, but the document itself states the views are the author's and don't necessarily reflect NSF or federal policy.

What are NSF's three merit review criteria? Intellectual Merit, Broader Impacts, and Commercial Impact.

Do NSF SBIR/STTR proposals need letters of support in 2026? Yes. At least one is required for standard Phase I and Phase II proposals, and at least three for Fast-Track. Letters must come from stakeholders like customers, partners, or investors — not consultants or subcontractors.

How many NSF Project Pitches or proposals can one company submit per year? Up to two Project Pitches in any 12-month window and up to two full proposals per fiscal year, with only one Phase I or Fast-Track project under consideration at a time.

What are the 2026 NSF SBIR/STTR full proposal deadlines? July 27, 2026; November 4, 2026; and March 4, 2027, under the consolidated NSF 26-510 solicitation, with annual cycles thereafter.

Free Patents. Free Money to Develop Them. Yes, Really.

The T3CP Patent Holiday SBIR is one of the most unusual opportunities in defense R&D, and it likely won’t be around again.

If your company has two things, strong R&D capability and the ability to commercialize new technology, this program hands you a business strategy that's hard to beat:

The government gives you a patent. Then the government pays you to develop it.

Here's how it works, in four steps.

The Play in 4 Steps

Step 1: Find a government patent you could develop

The Department of War holds thousands of patents from government-funded research. The Patent Holiday Initiative curates the priority ones — in microelectronics, advanced materials, energetics, munitions, critical minerals, biomanufacturing, and other priority tech areas — and puts them on the table for industry.

You don't start from a blank page. You start from an invention the government already paid to create and patent.

Step 2: Get a license — totally free

Through the Patent Holiday, you can get a Commercial Evaluation License (CEL) at no cost. The CEL lets you evaluate the patent before committing to anything long-term:

• Can this become a commercial product?

• Can we adapt it into a defense-relevant prototype?

• What modifications, customers, and regulatory issues are involved?

No licensing fees. No expensive diligence before you know if it's worth it.

Step 3: Apply for SBIR funding to develop it

T3CP is soliciting proposals to turn Patent Holiday IP into prototypes:

• Phase I: up to $250,000 to do the feasibility work — connect the patent to a product concept, define the prototype, and map the transition path.

• Phase II: up to $2,153,927 over up to 24 months to build a functional prototype, validate performance, and drive toward commercialization.

Already done the feasibility work? Direct to Phase II (D2P2) lets you skip Phase I entirely and go straight for the larger award.

Step 4: You now have a patent AND the money to develop it — all funded

Put it together and the math is remarkable:

Government patent → free evaluation license → up to $250K in Phase I funding → up to $2.15M in Phase II funding → a new product line.

Is This Right for Your Company?

This opportunity fits companies that can answer yes to two questions:

1. Do you have strong R&D capability to adapt and mature an existing invention?

2. Can you commercialize — take a technology to real customers, commercial or defense?

If so, the next moves are simple: identify which Department of War patents match your capabilities, pursue a free CEL, and build the strongest single patent-to-product case for Phase I (or D2P2).

Want help figuring out where you fit? Contact our team for a Patent Holiday SBIR fit assessment. We'll help you identify relevant patents, evaluate the business case, and map the path from free license to funded prototype.

When Should a University Spinout Choose an NSF STTR Instead of an NSF SBIR? Understanding the Principal Investigator Employment Rules

Last updated: July 2026 · BW&CO Consulting — non-dilutive federal funding for deep-tech founders

Launching a company around university-developed technology is exciting, but it also creates one of the most common eligibility questions we hear from founders pursuing NSF funding:

"Our Principal Investigator still works at the university. Can we apply for an NSF SBIR?"

The answer is: sometimes—but often an NSF STTR is the better fit.

Many faculty founders, postdoctoral researchers, and university scientists assume they must immediately leave their university position to pursue NSF funding. Others incorrectly assume that simply being a founder qualifies them to serve as the Principal Investigator (PI) on an SBIR proposal.

Neither assumption is necessarily correct.

Understanding the differences between NSF SBIR and NSF STTR—particularly the PI employment requirements—can save months of planning, prevent eligibility issues, and allow a startup to pursue funding without forcing major employment decisions too early.

Why PI Employment Matters

Although NSF SBIR and NSF STTR are closely related programs, they were created to solve slightly different commercialization challenges.

SBIR is designed for research primarily conducted within the small business.

STTR was specifically created to encourage commercialization of technologies emerging from research institutions.

That distinction shows up most clearly in the rules governing the Principal Investigator.

NSF SBIR: The PI Must Primarily Work for the Company

For NSF SBIR awards, the Principal Investigator must be primarily employed by the small business.

In practical terms, that means the PI's principal professional commitment must be to the startup during the award period—not to a university, national laboratory, or another employer.

This requirement often surprises faculty founders.

Owning equity in a startup is not enough.

Serving as CEO is not enough.

Even being the inventor of the technology is not enough.

If the PI's primary employment remains with the university, the company generally cannot use that individual as the PI for an NSF SBIR award.

The Challenge for University Spinouts

This becomes particularly difficult during the earliest stages of commercialization.

Many founders are still:

• Tenure-track faculty

• Research professors

• Postdoctoral researchers

• Staff scientists

• Research engineers

• Clinical investigators

They may be spending nearly all of their working hours at the university while simultaneously building a startup around licensed intellectual property.

From a commercialization perspective, this is perfectly normal.

From an SBIR eligibility standpoint, however, it can create complications.

NSF STTR Was Built for Exactly This Situation

The NSF STTR program recognizes that commercialization often begins before the inventor is ready to leave academia.

Unlike SBIR, the STTR program allows the Principal Investigator to be primarily employed by either:

• the small business or

• the partnering nonprofit research institution.

This flexibility removes one of the biggest barriers facing university spinouts.

A faculty member can continue fulfilling university responsibilities while leading the technical direction of the startup's STTR project.

For many early-stage companies, this provides a much smoother transition from laboratory research to commercial development.

Why This Matters for Faculty Founders

Imagine a professor who has developed a breakthrough medical device.

The university licenses the technology into a newly formed startup.

The professor wants to remain on faculty while the company validates the technology.

Under an NSF SBIR, that employment arrangement may prevent the professor from serving as PI.

Under an NSF STTR, however, the professor may be able to remain at the university while leading the project, provided all NSF eligibility requirements are satisfied.

That difference alone makes STTR the better option for many university spinouts.

STTR Requires a University Partnership

Of course, this flexibility comes with tradeoffs.

Unlike SBIR, STTR requires a formal collaboration with a nonprofit research institution.

That institution may be:

• a university

• a nonprofit research institute

• a federally funded research and development center (where eligible)

The relationship is not informal.

It requires documented cooperation between the startup and the research institution, including agreements governing intellectual property and the conduct of the research.

Research Responsibilities Are Shared

Another major distinction is how the work must be divided.

Under NSF STTR:

• the small business must perform at least 40% of the research effort

• the partnering research institution must perform at least 30%

This structure reflects the collaborative nature of the STTR program.

Rather than outsourcing university work under a standard subcontract, STTR treats both organizations as active research partners.

Common Misconceptions

"I'm the founder, so I can automatically be the PI."

Not necessarily.

Founder status and PI eligibility are two separate issues.

Employment requirements still apply.

"I'll just keep my university job while running an SBIR."

That may create eligibility problems if your primary employment remains with the university during the award.

"We should always choose SBIR."

Not always.

Many university spinouts are actually stronger STTR candidates during their earliest stages.

"Once we're a company, we no longer need the university."

In many cases, the university remains critical because it provides:

• laboratory facilities

• specialized equipment

• graduate student support

• ongoing technical expertise

• access to the original inventors

STTR is specifically designed to leverage those strengths.

Practical Paths Companies Can Consider

Every spinout is different, but several common approaches emerge.

Option 1: Apply Through NSF STTR

This is often the cleanest solution when:

• the inventor remains employed by the university

• significant research will continue on campus

• the company is just beginning commercialization

Advantages

• PI can remain at the university.

• Strong alignment with university-developed IP.

• Preserves research continuity.

Considerations

• Requires a formal university partnership.

• Must meet STTR work allocation requirements.

• Additional coordination with the university's technology transfer office is often necessary.

Option 2: Transition the PI to the Startup

Some founders decide to leave the university—or significantly change their employment status—before the award begins.

This can position the company for an NSF SBIR application.

Advantages

• Greater flexibility in project management.

• No mandatory university research allocation.

Considerations

• Major career decision.

• May affect university responsibilities, benefits, or tenure progression.

• Timing must align with NSF requirements.

Option 3: Appoint a Different PI

Some companies designate another qualified individual whose primary employment is already with the startup.

The faculty founder continues contributing as a senior technical advisor or key personnel.

Advantages

• Preserves SBIR eligibility.

• Founder remains scientifically involved.

Considerations

• The designated PI must genuinely lead the technical project.

• Titles alone are insufficient if they do not reflect actual project leadership.

Option 4: Start with STTR, Then Pursue SBIR Later

Some companies begin with an STTR while the technology is still closely tied to the university.

As the company matures, hires staff, and builds its own research capabilities, future projects may fit more naturally under SBIR.

For many university spinouts, this progression mirrors the company's evolution from academic research to independent commercialization.

Questions Every University Spinout Should Ask

Before deciding between NSF SBIR and NSF STTR, founders should consider:

• Where is the PI's primary employment today?

• Will that employment change before the award begins?

• How much research still depends on university facilities?

• Is the university expected to remain a major research partner?

• Would changing the PI strengthen the application?

• Does STTR better reflect how the project will actually be performed?

These questions are often more important than the technology itself when determining program eligibility.

The Bottom Line

For university spinouts, the decision between NSF SBIR and NSF STTR is rarely just about funding—it is about organizational readiness.

If the Principal Investigator is still primarily employed by the university, the startup should carefully evaluate whether an NSF STTR is the more appropriate path. The program was created specifically to bridge the gap between academic discovery and commercial innovation, allowing university researchers and startups to collaborate while new companies establish themselves.

Choosing the right mechanism early can reduce eligibility risks, simplify project planning, and position the company for long-term success as it transitions from the laboratory to the marketplace.

Need Help Determining Whether SBIR or STTR Is the Better Fit?

At BW&CO, we regularly work with faculty founders, university spinouts, and first-time entrepreneurs navigating the complexities of NSF funding. From evaluating PI eligibility and selecting the right funding mechanism to coordinating with technology transfer offices and developing competitive proposals, our team helps companies build a commercialization strategy that aligns with NSF requirements from day one.

Schedule a free consultation to discuss your technology and determine whether NSF SBIR or NSF STTR is the strongest path for your company.

How to Write the NSF Project Pitch "Technical Objectives and Challenges" Field (2026 Guide)

Last updated: June 2026 · BW&CO Consulting — non-dilutive federal funding for deep-tech founders

Quick answer: The Technical Objectives and Challenges field (up to 3,500 characters) is where you lay out the specific R&D tasks that will prove your innovation works in Phase I — and the technical risks that could stop it. To write it well, define a small set of specific, measurable objectives tied to demonstrating feasibility, then name the real technical challenges honestly and give a high-level plan for managing each. NSF reviewers use this field to judge whether you actually understand the core research required. Listing business milestones or hiding the risks gets pitches declined.

If the Technology Innovation field is where you say what your innovation is, this is where you prove you know how to test it. It's the same 3,500 characters, and it's where reviewers find out whether there's a real research plan behind the big idea — or just optimism.

Here's how to get it right.

What is the Technical Objectives and Challenges field in an NSF Project Pitch?

The Technical Objectives and Challenges field is the section of the NSF Project Pitch where you describe the specific research and development required to prove your foundational technology works, and explain the technical challenges you'll face along the way. It's capped at 3,500 characters. NSF's instruction is explicit: spell out the R&D needed to prove the technology, address each challenge directly, and give a high-level description of how each will be managed.

In plain terms, this field has two jobs: show you know exactly what must be proven in Phase I, and show you understand what could go wrong — and have a plan for it.

How is this different from the Technology Innovation field?

The Technology Innovation field describes what your innovation is and the scientific insight behind it. The Technical Objectives and Challenges field describes what you'll do to prove it works and what stands in the way. One is the idea; the other is the research plan that tests the idea.

A reviewer reads them as a pair. If the first field promised a high-risk innovation but this field lists no real technical risk, the two contradict each other — and that contradiction sinks pitches. This field is where the "research risk" you claimed earlier has to show up as concrete, testable work.

What makes a strong technical objective?

A strong technical objective is specific, measurable, and tied directly to proving feasibility — not to building a business. It states what you will demonstrate and how you'll know you succeeded.

• Specific: "Demonstrate the sensor resolves glucose to ±15 mg/dL," not "improve accuracy."

• Measurable: attach a number, a threshold, or a success criterion a reviewer can picture.

• Feasibility-focused: each objective should answer part of the question "Does the core innovation actually work?"

• Bounded: aim for a handful of objectives (often three to five). A long list of vague goals reads as less rigorous than a few sharp ones.

The test: could a reviewer tell, at the end of Phase I, whether you hit the objective or not? If the answer is fuzzy, the objective isn't done yet.

Why you should name your technical challenges instead of hiding them

You should state your technical challenges openly because naming them is what proves you understand the research. Founders instinctively want to look confident and minimize risk. In an NSF pitch, that instinct backfires.

Remember the logic from the innovation field: NSF funds research risk. So a pitch with no acknowledged challenges tells a reviewer one of two things — either there's no real research here (so why fund it?), or you don't yet understand your own problem (so you're not ready). Honestly identifying the hard parts signals technical maturity. It's a credibility move, not a confession.

How do you address a challenge without overpromising?

You address each challenge with a high-level approach to managing it — not a guarantee that it'll be solved. NSF asks for a brief description of how each challenge will be handled, not a promise that nothing will go wrong.

The strong pattern is: name the challenge → state the technical approach you'll use → define what success looks like (a go/no-go threshold). That last part matters. Framing an objective as "if we hit X, we proceed; if not, we've learned something specific" shows you think like a researcher, where a negative result is still a result. Avoid hand-waving ("we'll iterate until it works") and avoid pretending the risk is trivial.

Common mistakes in the Technical Objectives and Challenges field

The most common mistake is listing business milestones instead of technical objectives. A few others show up again and again:

• Commercial milestones disguised as objectives: "file a patent," "hire engineers," "sign three pilot customers," "raise a seed round." None of these prove the technology works.

• Vague verbs with no metric: "optimize," "enhance," "improve" — with nothing measurable attached.

• No challenges listed: a pitch that claims everything will work undercuts the high-risk innovation you described one field earlier.

• Challenges with no plan: naming a risk and then saying nothing about how you'll manage it.

• Confusing objectives with methods: the objective is what you'll prove; the method is how. Lead with what.

Technical Objectives and Challenges example: weak vs. strong

Weak (business milestones + vague verbs):

In Phase I we will optimize our algorithm, build a working prototype, file a patent, and begin conversations with device manufacturers. We'll improve accuracy and reduce the device's size. Our main challenge is raising enough capital to scale manufacturing.

This is a business plan, not a research plan. The "objectives" aren't measurable, and the only named challenge is commercial. A reviewer can't tell what would count as success. Declined.

Strong (measurable objectives + real challenges + management):

Objective 1: Demonstrate that the mid-infrared signature isolates glucose to within ±15 mg/dL of reference blood draws across at least three Fitzpatrick skin types (n≥20). Challenge: skin scattering varies with melanin and hydration. Approach: dual-wavelength reference-channel subtraction plus a brief per-subject calibration; go/no-go is 80% of readings in Clarke Error Grid Zone A.

Objective 2: Establish signal stability under motion and across a 4-hour wear period. Challenge: motion artifacts may swamp the signal. Approach: adaptive filtering benchmarked against a clinical CGM as ground truth; success is <10% drift over the window.

Each objective is measurable, each names a genuine technical risk, and each says how it'll be managed and judged. This reads like research.

Checklist: review your Technical Objectives and Challenges field before submitting

• Is every objective something you could clearly pass or fail by the end of Phase I?

• Did you attach a number, threshold, or success criterion to each one?

• Did any "objective" actually describe a business milestone (patent, hire, customer, funding)? Cut it.

• Have you named the real technical challenges — including the ones you'd rather not admit?

• Does each challenge have a high-level management approach, not just a mention?

• Do these objectives clearly test the innovation you described in the previous field?

• Are you under 3,500 characters?

Frequently asked questions

What is the Technical Objectives and Challenges field in an NSF Project Pitch? It's the section where you describe the specific R&D needed to prove your foundational technology works, and the technical challenges you'll face, with a high-level plan for managing each. It is capped at 3,500 characters.

How many technical objectives should I include? There's no fixed number, but a focused set of roughly three to five specific, measurable objectives is stronger than a long list of vague ones. Quality and clarity beat quantity.

Should I list business milestones as technical objectives? No. Patents, hires, customer pilots, and fundraising are not technical objectives. NSF wants the R&D tasks that prove feasibility — the science and engineering, not the business.

Should I mention technical risks or challenges in my NSF pitch? Yes. Naming your challenges honestly demonstrates that you understand the research. A pitch with no acknowledged technical risk contradicts the high-risk innovation NSF is being asked to fund.

What's the difference between a technical objective and a technical challenge? An objective is what you intend to demonstrate or achieve in Phase I. A challenge is the technical risk or unknown that could prevent you from achieving it. Strong pitches pair each objective with its challenge and a way to manage it.

How to Write the NSF Project Pitch "Technology Innovation" Field (2026 Guide)

Last updated: June 2026 · BW&CO Consulting — non-dilutive federal funding for deep-tech founders

Quick answer: The Technology Innovation field is the most important section of an NSF Project Pitch, capped at 3,500 characters (~500–600 words). To write it well, describe the new scientific or engineering insight behind your innovation — not your product, features, or market. NSF funds research and development of unproven, high-impact innovations, so your answer must name a specific, unanswered technical question and explain why solving it gives a durable advantage over the state of the art. Pitches that read as product descriptions are routinely declined.

If your NSF Project Pitch gets declined, there's a good chance it died in the first field. It's only 3,500 characters, but it carries more weight than anything else you'll write, and most first-time applicants walk straight into the same trap.

Here's how to avoid it.

What is the Technology Innovation field in an NSF Project Pitch?

The Technology Innovation field is the opening section of the NSF Project Pitch, where you describe the core high-risk technical innovation your Phase I project would research and develop. It has a hard limit of 3,500 characters — roughly 500 to 600 words. Reviewers read it first, and it is the single biggest factor in whether you're invited to submit a full proposal.

NSF's instructions are explicit: describe the technical innovation, its origins, and why it meets the program's mandate to support R&D of unproven, high-impact innovations. Notice what's missing from that list — your product, your customers, and your market.

Why do most first-time NSF Project Pitches get declined?

Most NSF Project Pitches get declined because the founder describes a product instead of a technical innovation. You've spent months explaining your company to investors and customers, and that exact muscle works against you here. NSF does not fund products. It funds the research that proves whether an innovation is even possible.

So when you write "Our platform uses a proprietary AI engine to give clinicians real-time decision support, addressing a $12B market…" a reviewer sees a product description and a market pitch — both disqualifying. NSF's own guidance states plainly that describing a product or its features is not sufficient and will likely result in a declined pitch. The fix isn't better wording. It's a different subject entirely.

What does NSF actually mean by "innovation"?

To NSF, the innovation is the new scientific or engineering insight that sits underneath your product — not the product itself. It helps to separate three layers:

• The product is what a customer buys.

• The innovation is the new capability that makes the product possible.

• The insight is the scientific or engineering principle that makes that innovation possible — the thing that wasn't known, or wasn't thought feasible, until you came along.

Your pitch needs to live in the bottom two layers. A reviewer reading this field is silently asking one question: Is there a genuinely hard technical question here that requires research to answer? If the honest answer is "no, we just need to build it," you don't have an NSF project — you have an engineering roadmap.

Research risk vs. engineering risk: what's the difference?

Research risk means you don't yet know whether something will work because it depends on an unanswered scientific or technical question. Engineering risk means the outcome is known to be achievable but hard to execute. NSF funds research risk, not engineering risk. This single distinction explains most declined pitches.

• Engineering risk:"This is hard to build, but we know it can be done." Scaling a known process, integrating mature components, optimizing cost. Real work — but not research.

• Research risk:"We don't yet know if this will work, because it depends on a question nobody has answered." That uncertainty is the point.

A blunt gut check: if you're certain it'll work, it's not research. Lean into the uncertainty instead of hiding it. The high-risk element isn't a weakness to paper over — it's the reason the program exists.

What must the Technology Innovation field include?

A strong Technology Innovation field includes three things, in this order: the innovation in plain terms, the scientific insight that enables it, and the durable advantage it creates over existing solutions.

1. The innovation, in plain terms. State what you'll build or discover and what technical principle you're leveraging. Be concrete. Define any jargon the moment you use it — assume a smart reviewer who is not an expert in your exact niche.

2. The insight that makes it possible. This is the layer founders skip, and skipping it is fatal. What new scientific or engineering understanding unlocks this, and where did it come from — a lab result, an observation, a first-principles rethink? This is the heart of the field.

3. The durable advantage over the state of the art. Don't just say "better" or "faster." Explain how you are fundamentally different from existing solutions and why that difference creates a substantial, lasting advantage competitors can't easily copy. If you're creating a new market, explain why anyone will adopt it at all.

NSF Technology Innovation example: weak vs. strong

Weak (product + market):

Our wearable continuously monitors blood glucose without finger-pricks, using a proprietary AI algorithm to give diabetics real-time alerts. The continuous glucose monitoring market exceeds $13B and is growing fast. Our device is smaller and cheaper than existing monitors.

Everything here is product, market, and incremental comparison. A reviewer learns nothing about what new science is involved. Declined.

Strong (innovation + insight + research risk):

We are developing a non-invasive glucose sensor based on a previously uncharacterized mid-infrared absorption signature in interstitial fluid. Existing optical approaches fail because skin scattering swamps the glucose signal; our insight is that a specific spectral band, combined with a reference-channel subtraction method, isolates that signal at the dermal depth where glucose concentration tracks blood levels. The core research question — and the high-risk element — is whether this signature remains stable across skin tones, hydration states, and motion, which prior work has not established. If it does, the result is a fundamentally different sensing principle than the enzymatic, consumable-based electrodes that define today's monitors, eliminating both the implanted sensor and the recurring consumable.

Same product. Completely different field. The second version names the insight, the specific unknown, and why the advantage is structural rather than incremental.

Checklist: review your Technology Innovation field before submitting

• Could a competitor read this and say "we already do that"? If so, your innovation isn't differentiated — or you haven't explained the insight.

• Have you named the specific technical question your research will answer?

• Did you describe a product feature where you should have described a principle? Cut it.

• Is there jargon a non-specialist reviewer wouldn't follow? Define it or lose it.

• Does the field make clear why this is hard and unproven — not in spite of the risk, but because of it?

• Are you under 3,500 characters?

Frequently asked questions

How long should the NSF Technology Innovation field be? The field is capped at 3,500 characters, which is roughly 500 to 600 words. Use the space to explain the science, not to describe product features.

Can I describe my product in the NSF Technology Innovation field? Briefly, for context, but the field must focus on the underlying technical innovation and the science or engineering that enables it. NSF states that describing a product or its features alone will likely result in a declined pitch.

Does NSF fund product development? No. NSF's SBIR/STTR program funds research and development of unproven, high-impact innovations. If the feasibility of your idea is already established and you only need to build it, it is generally not a fit for the program.

What is the difference between an innovation and a product for NSF? A product is what a customer buys. An innovation is the new technical capability that makes the product possible, and it rests on a scientific or engineering insight that wasn't previously known or proven. NSF funds the innovation and the insight, not the product.

What is research risk in an NSF Project Pitch? Research risk is technical uncertainty about whether something will work, because it depends on a scientific or engineering question nobody has answered yet. NSF funds projects with genuine research risk, as opposed to engineering risk, where the outcome is known to be achievable.

NIH SBIR September vs. January: Should Startups Submit Now or Wait?

For founders preparing an NIH SBIR application, one question is surfacing repeatedly in 2026:

Should we submit in September, or wait until January?

At first glance, January may seem like the safer choice. September is the first major NIH SBIR submission cycle following the program's reauthorization, and many companies assume it will attract a flood of applications from teams that were unable to apply during the lapse in authorization.

But while there are legitimate reasons to consider January, the evidence suggests that most well-prepared companies should seriously consider submitting in September rather than waiting.

The decision ultimately comes down to a simple question:

Will four additional months materially improve your proposal, or are you delaying primarily because you assume January will be less competitive?

If it's the latter, waiting may be a mistake.

Why September Feels Different

The concern about September isn't irrational.

After NIH SBIR/STTR authority expired in October 2025, NIH suspended its small business funding opportunities until Congress reauthorized the program in April 2026. As a result, what would normally have been active submission cycles effectively disappeared.

September 2026 became the first standard receipt date after the program reopened.

That creates a reasonable expectation that many companies who intended to submit earlier will now target September, creating a backlog of applications and potentially increasing competition.

NIH itself has acknowledged rising application volume in recent years and recently implemented a cap on the number of annual SBIR/STTR submissions a company can make.

Taken together, it's fair to assume September will be a busy cycle.

But that's only half the story.

The Case for Waiting Until January

There are certainly situations where January is the better strategic decision.

The strongest argument for waiting is simple:

A significantly stronger application beats a rushed application every time.

Four additional months can make a meaningful difference if your team needs to:

• Generate additional feasibility data

• Strengthen preliminary results

• Clarify regulatory strategy

• Refine commercialization plans

• Improve intellectual property positioning

• Finalize partnerships or letters of support

• Address cybersecurity or foreign-affiliation disclosure requirements

• Complete registrations and administrative requirements

If those improvements could meaningfully increase your score, January may offer a higher probability of success.

Importantly, NIH reviewers fund strong science and strong commercialization plans—not speed.

If waiting transforms a good proposal into a great proposal, waiting is justified.

The Problem With the "January Will Be Easier" Argument

Where the logic starts to break down is when companies choose January solely because they believe competition will be lower.

The reality is that NIH does not publish SBIR success rates by receipt date.

There is no public data showing that January applications are funded at higher rates than September applications.

In fact, if September absorbs only part of the backlog created during the reauthorization pause, some of that demand could easily spill into January.

In other words:

January is not guaranteed to be less competitive.

The assumption sounds reasonable, but there is no public evidence proving it.

What we do know is that NIH SBIR funding has become more competitive overall.

Application volume has increased substantially in recent years while success rates have declined.

That trend existed before the program pause and continues after reauthorization.

The competition problem isn't confined to September. It's a broader reality across the entire program.

The Hidden Cost of Waiting

Many founders focus on competition and overlook timing.

Waiting until January doesn't just delay submission.

It delays everything.

Under the standard NIH review calendar, a September submission can lead to an earliest project start date around April.

A January submission pushes that timeline to roughly July.

That's approximately three months of lost time.

For startups, three months matters.

Those months can affect:

• Product development timelines

• Investor conversations

• Runway planning

• Regulatory milestones

• Pilot studies

• Customer engagement

• Hiring plans

Even if funding odds were identical—and they may be—the January strategy comes with a real opportunity cost.

Founders should treat that delay as part of the decision.

Competition Isn't One Giant Pool

Another common misconception is that all NIH SBIR applications compete against one another.

They don't.

Applications are assigned to specific review groups and NIH institutes based on scientific focus.

As a result, your actual competition is determined less by the total number of NIH applications and more by factors such as:

• Scientific topic

• Study section assignment

• Institute priorities

• Program fit

• Reviewer perception of significance and innovation

A company applying to NIAID, for example, isn't competing directly against every NIH applicant.

They're competing within a much narrower scientific and programmatic lane.

That's why institute fit and application quality often matter far more than speculation about which receipt date will be busiest.

So Which Deadline Should You Choose?

For most companies, the answer is surprisingly straightforward.

Submit in September if:

• Your science is mature

• Your commercialization plan is solid

• Your registrations are complete

• Your team can submit a proposal you would be proud to have reviewed today

Wait until January if:

• Additional data could materially strengthen your application

• Regulatory strategy is still evolving

• Key partnerships are not finalized

• Administrative or compliance requirements remain unresolved

• The proposal is simply not ready

The key distinction is motivation.

Wait because you can improve the application—not because you're trying to avoid competition.

Our Recommendation

While September 2026 is likely to be one of the more crowded NIH SBIR cycles in recent memory, we still believe most qualified applicants should submit in September rather than wait until January.

The reason is simple:

The downside of increased competition is largely theoretical.

The downside of delaying a strong application is very real.

A September submission gets your proposal in front of reviewers sooner, accelerates potential funding by approximately one quarter, and provides earlier feedback if a resubmission becomes necessary.

Most importantly, there is no public evidence that January offers meaningfully better funding odds.

If your application is truly ready, don't let fear of a crowded cycle become an excuse for unnecessary delay.

Submit the strongest application you can—and submit it as soon as it's ready.

Because in NIH SBIR, quality matters far more than trying to outsmart the calendar.

Cornerstone, DIBC, and IBAS: Which Defense Innovation Pathway Is Right for Your Technology

For small businesses and emerging technology companies looking to break into the defense market, the number of acronyms, programs, and contracting vehicles can feel overwhelming. Among the most frequently discussed pathways are Cornerstone, the Defense Industrial Base Consortium (DIBC), and Industrial Base Analysis and Sustainment (IBAS)—now known as Innovation Capability and Modernization (ICAM) within the Department of Defense.

While these names are often mentioned together, they serve very different purposes. Understanding those differences can help companies focus their time, resources, and business development efforts where they will have the greatest impact.

Understanding the Relationship Between Cornerstone, DIBC, and IBAS

A common misconception is that Cornerstone, DIBC, and IBAS are competing organizations or equivalent membership programs. They are not.

Instead, they operate at different layers of the defense industrial base ecosystem:

• Cornerstone is a government-managed OTA (Other Transaction Authority) consortium that provides industry access to industrial-base modernization and capability-gap initiatives.

• DIBC is an ATI-managed consortium that supports industrial-base projects through structured solicitations, teaming opportunities, and member resources.

• IBAS (now ICAM) serves as the policy and mission framework that drives many of the industrial-base priorities addressed through vehicles like Cornerstone and DIBC.

The simplest way to think about it is:

IBAS/ICAM defines the mission. Cornerstone and DIBC provide the pathways for industry participation.

Why This Matters for Small Businesses

For many small businesses, the biggest challenge is not finding opportunities—it's understanding how to position their technology within the Department of Defense's industrial base priorities.

The DoD is actively investing in technologies that:

• Strengthen domestic manufacturing capacity

• Reduce supply chain vulnerabilities

• Expand critical production capabilities

• Improve workforce readiness

• Accelerate commercialization of emerging technologies

• Support strategic industrial resilience

Companies that can clearly connect their technology to one or more of these outcomes are often far better positioned for success than companies that simply describe themselves as "innovative."

Cornerstone: A Direct Path to Industrial Base Challenges

Cornerstone was established to help the Department identify and address critical industrial-base capability gaps across a wide range of sectors, including:

• Advanced manufacturing

• Electronics

• Cybersecurity

• Space systems

• Critical materials

• Munitions

• Ground vehicles

• C4ISR

• Industrial workforce development

• Supply chain resilience

One of the most attractive aspects of Cornerstone is that membership is free and the application process is relatively streamlined. Once approved, members gain access to opportunities distributed directly through the consortium.

However, Cornerstone operates differently than many networking-focused organizations. It is designed around fairness and competition. Companies should expect formal solicitation processes rather than direct introductions, matchmaking, or one-on-one meetings with government stakeholders.

For technology companies that can solve a clearly defined industrial-base problem, Cornerstone offers a highly valuable pathway into the defense market.

DIBC: The Most Structured On-Ramp

For organizations that prefer a more structured ecosystem, DIBC provides one of the clearest entry points into defense industrial-base opportunities.

Members gain access to:

• Active solicitations

• Teaming opportunities

• Training resources

• Proposal templates

• Industry events

• Member databases

• Funding opportunities

• Government engagement pathways

DIBC also provides one of the fastest onboarding experiences once required documentation is complete, often processing applications within a matter of days.

The consortium's public award history demonstrates that significant industrial-base investments are being executed through this vehicle, making it particularly attractive for companies focused on scaling production, domestic sourcing, or advanced manufacturing capabilities.

The Real Barrier Isn't Membership—It's Readiness

Many companies focus on consortium membership and overlook the readiness requirements that determine whether they can actually pursue opportunities.

Before pursuing DIBC or Cornerstone opportunities, organizations should ensure they have:

• Active SAM registration

• UEI and CAGE/NCAGE information

• A clearly defined capability statement

• Cybersecurity readiness aligned with CMMC requirements

• DD2345/JCP planning when controlled technical data may be involved

• A dedicated business development point of contact

Companies that prepare these foundational elements early are often able to move much faster when opportunities emerge.

How to Position Your Technology for Success

The strongest companies entering the defense industrial base don't lead with technology features.

They lead with outcomes.

Instead of saying:

"We have an AI-powered analytics platform."

Say:

"Our platform reduces manufacturing bottlenecks and increases production visibility across critical defense supply chains."

Instead of saying:

"We developed a novel material."

Say:

"Our material reduces dependence on foreign sources and strengthens domestic production capacity for critical defense applications."

The closer your messaging aligns to industrial-base challenges, the more relevant your solution becomes to organizations operating within the Cornerstone and DIBC ecosystems.

Which Path Should You Choose?

For most companies, the answer isn't one or the other.

A practical strategy is to:

1. Join DIBC to gain access to structured opportunities, resources, and teaming networks.

2. Join Cornerstone to access industrial-base focused OTA opportunities.

3. Use IBAS/ICAM priorities as the framework for positioning your technology and identifying where it creates strategic value.

Companies that pursue all three perspectives—opportunity access, consortium engagement, and mission alignment—are typically best positioned to succeed.

Is Your Technology a Fit for Cornerstone?

Many innovative companies struggle to determine whether their solution aligns with the industrial-base priorities that drive Cornerstone opportunities.

The good news is that the answer often goes beyond traditional defense technologies. Solutions that improve manufacturing efficiency, strengthen supply chains, support workforce development, enhance resilience, or accelerate production can all have strong alignment within the Cornerstone ecosystem.

If you're evaluating whether your technology could be a fit for Cornerstone opportunities, our team can help.

We work with companies to assess industrial-base alignment, identify relevant opportunity pathways, and determine whether Cornerstone is the right vehicle for your solution.

Schedule a conversation with our team to explore whether your technology aligns with Cornerstone priorities and how to position your company for success in the defense industrial base.

SBIR Foreign Disclosure Requirements: What NIH, NSF, and Department of Defense Applicants Need to Know

Learn how SBIR/STTR foreign disclosure and foreign risk review requirements affect NIH, NSF, and Department of Defense applicants, including what to disclose and when to prepare.

SBIR and STTR applicants used to treat “foreign disclosure” as a back-office compliance item. That is no longer safe.

Across federal SBIR/STTR programs, agencies are now expected to assess foreign ownership, foreign affiliations, certain investment relationships, IP transfers, cybersecurity practices, and other risk factors before making awards. For startups, this means foreign disclosure is not just a form. It can affect whether an otherwise strong proposal is considered fundable.

This is especially important for companies applying to NIH, NSF, or the Department of Defense, where the rules may appear similar at a high level but play out differently in the application process.

Why Foreign Disclosure Matters in SBIR/STTR

The SBIR and STTR Extension Act of 2022 required small businesses applying for SBIR/STTR awards to disclose information about foreign ties and investment relationships. SBA then updated SBIR/STTR policy guidance and created a common disclosure framework for participating agencies.

SBIR.gov explains that the disclosure requirement is intended to capture information about an applicant’s “investment and foreign ties.” It also identifies the current SBIR/STTR “foreign countries of concern” as:

• People’s Republic of China

• Democratic People’s Republic of Korea

• Russian Federation

• Islamic Republic of Iran

As of the SBIR.gov foreign disclosures page, no additional countries have been designated for SBIR/STTR purposes.

The practical lesson: applicants should review foreign relationships early, not after a notice of award appears likely.

What Types of Relationships Can Trigger Review?

Foreign disclosure does not only mean foreign ownership. Agencies may look at a broader set of relationships, including:

• Owners or covered individuals involved in malign foreign talent recruitment programs

• Parent companies, subsidiaries, or joint ventures tied to a foreign country of concern

• Foreign business arrangements, contractual obligations, or joint venture-like relationships

• Venture capital or institutional investment with leadership ties to a foreign country of concern

• Technology licensing, IP sales, or IP transfers to a foreign country of concern

• Foreign business entities or offshore entities related to the applicant

• Foreign research institution affiliations involving owners, officers, or key personnel

NIH’s 2026 guidance also states that HHS due diligence may assess cybersecurity practices, patent history, employee analysis, foreign ownership, investment relationships, technology licensing agreements, joint ventures, and business relationships involving foreign countries of concern.

NIH SBIR/STTR: Disclosure Often Happens During Just-in-Time

For NIH, foreign disclosure has become a major pre-award and post-award issue.

NIH SEED says SBIR/STTR applicants are required to disclose funded and unfunded relationships with foreign countries using the SBIR/STTR Foreign Disclosure Form for all owners and covered individuals. NIH defines a covered individual as someone who contributes in a substantive, meaningful way to the scientific development or execution of the project, or someone identified as senior/key personnel.

A key NIH-specific point: applicants submit the form when requested through the Just-in-Time process. NIH also says applicants who do not submit the completed form during JIT will not be considered for funding.

That means companies should not wait until JIT to start gathering information. By then, timing can be tight, and incomplete disclosure can slow or jeopardize an award.

NIH’s April 20, 2026 notice also clarifies that HHS cannot make an SBIR/STTR award if certain security-risk criteria are met. NIH states that if an award cannot be made because of a security risk, HHS will identify the denial category, but it will not provide applicants an opportunity to address the risk before award.

NIH Post-Award Monitoring: The Obligation Does Not End at Award

NIH’s rules also extend beyond the application.

Recipients must monitor covered foreign relationships after award. NIH says updated disclosure forms are required for changes to disclosures, material misstatements that pose national security risk, changes in ownership, changes in entity structure, covered individual changes, or other substantial changes in circumstances.

For changes between regular reports, NIH states that updated disclosures are required within 30 days. Regular updates are also required with annual, interim, and final RPPRs.

For founders, the message is straightforward: treat foreign disclosure as an ongoing compliance system, not a one-time submission.

NSF SBIR/STTR: Due Diligence Is Part of the Review Environment

NSF’s current SBIR/STTR solicitation says NSF follows federal guidance on assessing and mitigating foreign risk related to countries of concern during the required due diligence process. Importantly, NSF also notes that receiving due diligence-related questions is not, by itself, a negative indicator of award probability.

NSF’s Seed Fund eligibility guidance also includes several related requirements:

• The company must have fewer than 500 employees, including affiliates.

• The company must meet U.S. ownership and control requirements.

• All R&D must be performed in the United States.

• No senior/key personnel on an SBIR/STTR proposal may be party to a malign foreign talent recruitment program.

This makes NSF somewhat different from NIH in workflow. NSF applicants should be prepared for foreign risk questions as part of due diligence, while also ensuring that basic eligibility, ownership, personnel, and work-location requirements are clean before submission.

Department of Defense SBIR/STTR: Missing Forms Can Make a Proposal Noncompliant

For Department of Defense SBIR/STTR applicants, foreign disclosure can be especially consequential at submission.

Department of Defense SBIR/STTR guidance has incorporated mandatory foreign disclosure requirements into solicitations. A Department of Defense SBIR BAA preface stated that proposals missing the required completed and signed foreign disclosure attachment would be deemed noncompliant and would not receive an evaluation.

A Department of Defense release also stated that all proposals submitted through the Defense SBIR/STTR Innovation Portal must include forms that assess security risks, and proposals without those forms are noncompliant.

That makes the Department of Defense process less forgiving from a submission-readiness standpoint. Applicants should verify the exact required volume, attachment, signature, and component-specific instructions before submission.

Practical Checklist Before You Apply

Before submitting an SBIR/STTR proposal, companies should review:

1. Ownership and control
   Confirm whether any ownership, parent/subsidiary structure, or investor relationship creates a disclosure issue.

2. Key personnel affiliations
   Ask founders, technical leads, consultants, and senior/key personnel about foreign appointments, research affiliations, talent programs, and institutional relationships.

3. Investors and financing
   Review venture capital, institutional investment, debt, and other financing relationships for foreign ties, especially involving countries of concern.

4. IP and licensing history
   Identify any technology licensing, IP transfer, patent activity, or sales involving foreign entities or countries of concern.

5. Contractors and research partners
   For STTR and university-linked work, clarify who is performing the work, where the work is performed, and whether any foreign affiliations need to be disclosed.

6. Post-award change monitoring
   Create an internal process to review ownership changes, personnel changes, investor changes, and new foreign relationships during the award.

What Applicants Should Not Assume

Do not assume that a foreign relationship is automatically disqualifying. Many disclosures may simply require explanation and review.

Do not assume that only countries of concern matter. Some forms and agency questions may ask about broader foreign relationships, even when risk criteria focus heavily on countries of concern.

Do not assume that a “no” answer is safer if the facts are unclear. NIH specifically encourages applicants to disclose affiliations if they are uncertain whether disclosure is required.

And do not assume the same workflow applies across agencies. NIH, NSF, and Department of Defense all operate under the broader SBIR/STTR framework, but submission timing and consequences can differ.

Conclusion

Foreign disclosure is now a core SBIR/STTR readiness issue. For NIH applicants, it can affect Just-in-Time and post-award reporting. For NSF applicants, it is part of the due diligence environment and intersects with eligibility, ownership, personnel, and U.S.-based work requirements. For Department of Defense applicants, missing or incomplete disclosure materials can make a proposal noncompliant before it is ever evaluated.

The best strategy is to review foreign ties before choosing an agency, before assembling the proposal team, and well before the submission deadline. A strong technical proposal still matters, but today, fundability also depends on whether the company can clearly explain who owns it, who supports the work, where the relationships are, and whether any of those relationships create a security risk.

Sources Used

• SBIR.gov: Required Disclosures of Foreign Affiliations or Relationships

• NIH SEED: Foreign Disclosure and Risk Management

• NIH Grants: NOT-OD-26-074

• NIH Grants: Required Disclosures Form Guidance

• NSF: NSF 26-510 SBIR/STTR Solicitation

• NSF Seed Fund: SBIR/STTR Eligibility and Requirements

• Department of Defense: SBIR/STTR Due Diligence Policy Release

NIH SBIR Just-in-Time (JIT) Requirements: What Applicants Need to Know Before Award

For many small businesses pursuing NIH SBIR funding, receiving a Just-in-Time (JIT) request is one of the most encouraging milestones in the application process. It often signals that an application has performed well in peer review and is being considered for funding. However, it is also one of the most misunderstood stages of the NIH award process.

Many applicants mistakenly assume that a JIT request means funding is guaranteed, while others rush to submit materials as soon as the JIT link appears in eRA Commons. Both assumptions can create unnecessary risk and delays.

This guide explains how the NIH JIT process works for SBIR applicants, what documents are typically required, common compliance pitfalls, and how companies can prepare for a smooth transition from application review to award.

What Is NIH Just-in-Time (JIT)?

Just-in-Time (JIT) is NIH's process for collecting administrative, compliance, and eligibility documentation after peer review but before an award is issued.

Rather than requiring every applicant to submit extensive compliance documentation with the original application, NIH requests these materials only from applications that are under active consideration for funding.

For SBIR applicants, JIT serves as the final stage of due diligence before NIH can issue a Notice of Award (NoA).

While some organizations informally refer to the process as "JIT-C" or a "JIT certification package," NIH officially refers to the process simply as Just-in-Time (JIT).

Does a JIT Request Mean Funding Is Guaranteed?

No.

A JIT request is a positive development because it generally indicates that an application is being considered for funding. However, it is not a funding commitment.

Applications may still undergo:

• Administrative review

• Budget negotiations

• Foreign risk assessment

• Compliance verification

• Programmatic review

Funding decisions are not final until NIH issues an official Notice of Award.

Companies should view JIT as an important milestone, but not as a guarantee of funding.

A Common Mistake: Submitting Too Early

One of the most frequent errors made by applicants is submitting JIT materials simply because the JIT link appears in eRA Commons.

The JIT link often becomes visible after an application receives a score, but NIH guidance is clear: applicants should wait until they receive a formal request from the awarding Institute or Center before submitting materials.

The appearance of the link alone is not authorization to submit.

Submitting materials prematurely can create confusion and may result in unnecessary administrative work if requirements change.

What Documents Are Typically Requested During JIT?

The exact requirements vary depending on the funding opportunity, Institute, and project characteristics. However, NIH commonly requests several categories of information.

Current and Pending Support

NIH frequently requests updated Current and Pending Support information for senior and key personnel.

These disclosures allow NIH to evaluate:

• Scientific overlap

• Commitment levels

• Foreign affiliations

• Potential conflicts of interest

Because disclosure requirements have become increasingly stringent, applicants should carefully review all external research support and affiliations before submission.

Updated Biosketches

Applicants may be asked to provide updated biosketch information for key personnel.

Current NIH requirements generally require the use of SciENcv-generated forms, and applicants should avoid modifying generated documents after creation.

Human Subjects Documentation

Projects involving human subjects research may require:

• Current IRB approval

• Federalwide Assurance (FWA) information

• Human subjects training documentation

• Single IRB information when applicable

A common issue is that approvals are still pending when NIH requests JIT materials. Because obtaining approvals can take weeks or months, organizations should begin planning early whenever funding appears likely.

Vertebrate Animal Documentation

Projects involving live vertebrate animals may require:

• Current IACUC approval

• Animal Welfare Assurance documentation

• Verification of compliance with NIH animal welfare policies

As with IRB approvals, timing delays frequently occur at the institutional review level.

SBIR Foreign Disclosure Requirements

Foreign disclosure requirements have become an increasingly important component of NIH SBIR oversight.

NIH may request information regarding:

• Foreign ownership interests

• Foreign affiliations

• Foreign relationships involving covered individuals

• Certain contracts and agreements

The purpose of these disclosures is to support NIH's assessment of potential foreign risks and ensure compliance with federal research security requirements.

Organizations with international collaborations should expect additional review and should begin gathering documentation as early as possible.

SBIR Funding Agreement Certification

SBIR awardees are typically required to complete a Funding Agreement Certification before award.

This certification confirms eligibility requirements related to:

• Small business status

• Ownership structure

• Principal investigator eligibility

• Workshare requirements

• Program compliance

Although often straightforward, companies should review the certification carefully to ensure all eligibility criteria remain satisfied.

Where Is JIT Submitted?

Another common source of confusion involves the submission system.

The original SBIR application may be submitted through:

• ASSIST

• Grants.gov Workspace

• Institutional system-to-system solutions

However, JIT materials are submitted through eRA Commons.

Applicants should be aware that:

• Principal Investigators can upload and save information.

• Only the Signing Official (SO) can formally submit JIT materials to NIH.

This distinction frequently causes last-minute delays when organizations discover that the appropriate institutional official has not reviewed the submission.

Common Compliance Challenges

After supporting hundreds of grant applications, several patterns consistently emerge during the JIT phase.

Delayed IRB or IACUC Approvals

Institutional review timelines often move slower than anticipated.

Organizations should begin approval processes as early as possible rather than waiting until NIH requests documentation.

Incomplete Disclosure Information

Foreign collaborations, consulting agreements, sponsored research agreements, and external funding sources can all trigger additional scrutiny.

Incomplete disclosures are among the most common reasons NIH requests clarification.

Incorrect Forms

NIH periodically updates forms and submission requirements.

Using outdated templates or failing to generate required forms through approved systems can delay review.

Missing Internal Coordination

Successful JIT submissions often require coordination among:

• Principal Investigators

• Research administrators

• Regulatory personnel

• Business offices

• Executive leadership

• Signing Officials

Organizations that treat JIT as a company-wide compliance effort generally experience fewer delays.

Best Practices for NIH SBIR Applicants

Companies can significantly reduce administrative burden by preparing before a JIT request arrives.

Recommended practices include:

Maintain Current Compliance Records

Keep approvals, certifications, and training records current throughout the project lifecycle.

Review Foreign Relationships Early

Document international collaborations, consulting relationships, ownership interests, and agreements before NIH requests them.

Establish Internal Roles

Define responsibilities for:

• Document collection

• Regulatory approvals

• Executive certifications

• Final submission

Monitor eRA Commons Regularly

Ensure that all personnel have active accounts and that organizational roles are current.

Prepare for Rapid Response

NIH often expects timely responses to JIT requests. Organizations that maintain a readiness file can respond much faster than those starting from scratch.

Final Thoughts

For NIH SBIR applicants, the Just-in-Time process is more than a paperwork exercise. It is NIH's final opportunity to verify compliance, eligibility, and programmatic readiness before issuing an award.

Organizations that understand the purpose of JIT, prepare documentation early, and coordinate effectively across scientific, regulatory, and administrative teams are far more likely to navigate the process efficiently.

Receiving a JIT request is encouraging, but the work is not finished. A well-prepared JIT package can help ensure that promising applications move smoothly from review to award and ultimately to successful project execution.

The Grant Wasn't Lost on the Idea. It Was Lost on Page 11.

Most companies prepare for government grants the wrong way. They spend weeks polishing their pitch and five minutes checking the rules. That imbalance kills otherwise strong proposals — and it's more common than you think.

The myth that costs people awards

"If the idea is strong enough, the reviewer will look past the small stuff."

We hear this constantly. And we understand why founders believe it — you've spent months on the technology, the market analysis, the proof points. Surely that work carries the day.

It doesn't. Federal reviewers are not evaluators looking for reasons to say yes. In many cases, they are checkers looking for reasons to stop reading. A mismatched budget line, an over-limit page count, a URL buried under hyperlinked text — any one of those can end your review before it begins.

Your idea never got a fair hearing. Not because it wasn't good. Because it wasn't clean.

What actually gets proposals rejected

These are not rare edge cases. We see them in nearly every submission cycle:

• Outdated forms. Agencies update forms between solicitation cycles. Submitting last year's version — even with the right content — is a compliance failure.

• Page limit violations. Going one page over often means reviewers are required to stop reading at the cutoff. If your strongest data is on page 16 of a 15-page limit, it doesn't exist.

• Budget inconsistencies. Labor hours in the narrative that don't match the spreadsheet. A subcontractor cost that appears once but not twice. These aren't math errors to reviewers. They're red flags about your ability to manage money.

• Ineligible cost requests. Requesting items the grant explicitly excludes is an easy disqualifier — and easy to avoid if you read the solicitation before you write the budget.

• Hidden hyperlinks. Many solicitations prohibit URLs. A clickable word buried in your text counts.

None of these are quality problems. They are process problems. The good news: process is fixable.

Case study — anonymized at client request

A seed-stage deep tech startup came to us after a federal SBIR rejection. Strong technology. Positive reviewer feedback from a prior round. They assumed they were close.

The rejection had nothing to do with their science. Their budget narrative and detailed budget spreadsheet didn't match. Labor hours differed by line item. A subcontractor cost appeared in one place, not the other.

From the agency's view, that raised one question: Can this team actually manage federal funds? That question alone was enough to stop the proposal.

The situation - Solid technology, rejected before full scoring

The problem - Budget narrative didn't match the spreadsheet

What changed - Built a compliance workstream, not just a checklist

Next cycle: awarded. The idea didn't change. The team didn't change. The outcome changed because the small mistakes were gone — and reviewers had nothing to question.

What we actually changed for them

We didn't rewrite their proposal. We fixed their process. Specifically:

• Built a line-by-line crosswalk connecting the budget, narrative, and work plan so every number appeared consistently across all three documents.

• Created a compliance checklist tied directly to the current solicitation — not a generic template, but a document that mapped every requirement from that specific FOA.

• Assigned a single person as the compliance owner for final validation. Shared ownership almost always means no one owns it.

• Ran a mock review pass focused only on consistency and completeness — not on whether the idea was compelling.

We treated compliance as a core workstream, not an afterthought. That's the shift most teams need to make.

Why this matters beyond winning one grant

Government reviewers are evaluating two things at once: your idea, and your ability to deliver on it. Small inconsistencies send a loud signal about the second one.

If your numbers don't align, what else won't? If you didn't follow the instructions here, how will reporting go? If the details are sloppy in the proposal, what happens when you're managing taxpayer funds?

It's not about being perfect. It's about giving reviewers no reason to doubt you.

How to approach your next submission differently

• Start compliance day one. Not the week before submission. Build around the solicitation requirements from the beginning, not after the content is written.

• Treat the budget as a document. Every number in your narrative must trace back to the same number in your spreadsheet. Read them together, not separately.

• Make one person accountable. Not the team. One person. They own the final compliance review, and they're not also writing the technical narrative.

• Check for consistency, not just completion. Having all the required pieces isn't enough if they contradict each other. Run a dedicated consistency pass.

• Read the solicitation like a contract. Every word in a federal FOA is deliberate. "Shall" means required. Page limits are hard stops. Eligible costs are defined, not suggested.

The bottom line

You don't lose government grants only because your idea isn't strong enough. You lose because something small gave the reviewer a reason to stop trusting the application — and in federal procurement, that's all it takes.

If you're preparing a submission and want a second set of eyes on compliance before you submit, we're easy to reach. We've seen what kills proposals. More often than not, it's fixable.

The Best SBIR/STTR Consulting Firms (2026 Guide)

Choosing the right SBIR/STTR consulting firm can significantly impact your chances of securing non-dilutive funding.

With over $4B in annual federal funding available through SBIR/STTR programs, competition is intense and the difference between winning and not often comes down to strategy, positioning, and execution.

Quick Summary: Top SBIR Consulting Firms (2026)

Here’s a high-level overview of the most recognized SBIR/STTR consulting firms and what they are best known for:

• BBCetc
  Best for first-time applicants
  Core strength: Training and SBIR education

• Dawnbreaker
  Best for commercialization
  Core strength: Market strategy and transition support

• Eva Garland Consulting
  Best for traditional grant writing support
  Core strength: Grant frameworks and guidance

• REOFTech
  Best for full-service consulting
  Core strength: End-to-end support

• BW&CO Consulting
  Best for highest probability of funding
  Core strength: AI + human + validated positioning

Each firm takes a different approach, ranging from training and execution to strategy and positioning. The right choice depends on your stage, needs, and how competitive your target program is.

Top SBIR/STTR Consulting Firms

1. BBCetc (BBC Entrepreneurial Training & Consulting)

Best for: First-time applicants and SBIR training

BBCetc is one of the most established organizations in the SBIR ecosystem, with over 30 years of experience supporting companies through training, proposal development, and program navigation.

Strengths:

• Strong training programs and workshops

• Deep experience across agencies

• Structured SBIR education

Considerations:

• More education-focused than strategy-driven

• May be less tailored for advanced applicants or those who are familiar with grant applications

2. Dawnbreaker

Best for: Commercialization and market strategy

Dawnbreaker is widely known for its commercialization support and has worked with thousands of SBIR/STTR awardees.

Strengths:

• Strong focus on commercialization pathways

• Market research and partner development

• Long-standing agency experience

Considerations:

• More focused on post-award support

• Less emphasis on early-stage positioning

3. Eva Garland Consulting

Best for: Structured SBIR strategy and guidance

Eva Garland Consulting supports startups and researchers with grant strategy, education, and proposal development.

Strengths:

• Strong strategic frameworks

• Educational resources and tools

• Experience across agencies

Considerations:

• Based more on historical experience

• Less emphasis on real-time positioning

4. REOFTech SBIR Consultants

Best for: End-to-end consulting

REOFTech provides full-service SBIR consulting across multiple agencies.

Strengths:

• End-to-end support

• Experience across NIH, DoD, DOE

• Commercialization alignment

Considerations:

• Broader scope may reduce specialization

• Varies by engagement

5. BW&CO Consulting

Best for: Companies seeking the highest probability of funding

BW&CO represents a newer model of SBIR consulting providing end-to-end support based on how funding decisions are made today.

Strengths:

• AI-driven analysis of agency behavior

• Human expertise aligned with reviewer mindset

• Direct validation with Program Officers before submission

What makes it different:
BW&CO emphasizes:

• identifying precise programmatic fit

• validating alignment directly with agencies

• positioning proposals based on real-time signals

The Bottom Line

Most SBIR consulting approaches fall into three categories:

• training-focused

• execution-focused

• experience-driven strategy

A newer category is emerging:

validation-driven, data-informed SBIR strategy

The firms that perform best in 2026 are those that:

• combine data with human insight

• validate alignment with agencies

• focus on positioning, not just writing

Has Your SBIR Consultant Adapted to What NIH SBIR Funding Has Become in 2026?

by Josiah Wegner - CEO

If you’re evaluating NIH SBIR consulting firms and newer AI proposal tools, you’re asking the right question:

Which approach gives me the highest probability of winning an NIH SBIR today, not three years ago?

Grant writing has changed in two major ways in 2026 and most firms haven’t fully adapted.

The Two Shifts Reshaping Grant Funding

1. AI has fundamentally changed what’s possible

AI is no longer optional.

Firms that ignore AI are denying their clients access to capabilities that didn’t exist even a few years ago, including:

• the ability to analyze large volumes of agency data and past awards quickly

• identifying patterns in what actually gets funded

• surfacing strategic positioning opportunities that are easy to miss manually

Without these tools, decisions are based on limited visibility and narrower experience.

At the same time, relying only on AI creates a different problem.

AI-generated proposals often:

• flatten technical depth

• miss nuance in how ideas should be framed

• fail to capture unstated priorities or context

They also lack the human judgment needed to interpret gray areas, ask the right questions, and adjust strategy based on subtle signals.

In some cases, over-reliance on AI can even introduce risk.

As of September 2025, the NIH explicitly states: “Applications that are either substantially developed by AI… will not be considered by NIH.” 

The advantage today isn’t avoiding AI or replacing people with it.

It comes from combining AI-driven insight with human judgment — using each where it adds the most value.

2. NIH Priorities Are Shifting Faster Than Most Applicants Realize

What worked even a few years ago is not a reliable guide today.

This is being driven in large part by recent policy changes under the current Trump administration, which are actively reshaping how agencies define priorities, evaluate proposals, and allocate funding.

We’re seeing real-time shifts such as:

• stronger emphasis on different aspects of health than in the past

• giving more power to NIH Program officers by eliminating paylines

• tighter alignment between funding decisions and national priorities

These are not gradual changes; they have alredy happened.

That creates a growing disconnect:

• many applicants are still positioning proposals based on how NIH operated in the past: Reviewers held most of the power.

• while NIH is funding  proposals based on how well they align with their internal priorities: POs hold most of the power.

In some cases, proposals that would have been competitive last year are no longer aligned with what NIH is looking for today.

Success now depends on understanding:

What NIH’s priorities are today and how to position your work accordingly.

Where Traditional Options Fall Short

Strategy-led firms

Strategy-led firms bring strong experience and structured processes. They’ve supported many successful applications and understand the grant landscape well.

But their model is still largely built on human-driven experience and historical pattern recognition.

That creates a limitation:

• Insights are often based on what has worked before

• There is less ability to systematically analyze large volumes of current data

• Quality can vary depending on the individual consultant and time constraints

In a slower-moving environment, this worked well.

In today’s environment, it can lag behind shifting priorities.

Execution-focused firms

Execution-focused firms have strong teams and real experience supporting proposal development. They are known for quality talent and can provide meaningful support in organizing and executing submissions.

Their model emphasizes:

• writing and submission support

• structured execution processes

However, it places less emphasis on:

• identifying precise programmatic fit

• validating alignment with NIH before submission

• shaping proposals around NIH priorities

You get capable execution—but not always strategic clarity upfront.

And in today’s environment, execution alone is not enough.

AI Proposal Tools

There is a growing category of tools that promise to generate proposals using AI.

They can be helpful for speed.

But they come with clear tradeoffs:

• No validation of positioning (the most important thing)

• Technical depth often gets flattened

• No understanding of reviewer psychology

And critically:

NIH policy now makes clear that proposals substantially generated by AI may not be considered original and may not be reviewed competitively.

These tools accelerate writing but do not solve the hardest problem: knowing what to write and how to position it.

The BW&CO “MAP” Approach

We built our “MAP” approach specifically for the new 2026 SBIR environment.

M - Market Gap

We identify the specific gap your company fills within an Institute or Center (IC)

We use AI-powered analysis to study:

• IC priorities

• past awards

• Other relevant IC signals

This allows us to pinpoint where your work fits in a way most applicants miss.

But we don’t stop at analysis.

We help you validate that positioning through direct outreach and conversation with NIH.

Because not everything that drives funding decisions is written down.

NIH often operates with:

• informal preferences

• emerging priorities not yet fully published

• interpretations of program language that only become clear through discussion

By engaging directly through calls, emails, or conversations, you gain insight into how that particular IC is actually thinking, not just what is written.

Most applicants are guessing where they fit.

We help you confirm it with NIH directly.

A - Aligned Writer

Your proposal is shaped by someone who understands your field and thinks like a reviewer.

While aligning with programmatic priorities is key in 2026, a well written and scored proposal is still essential to get funded.

Working with a writer that understands your field avoids three common failure modes:

• founders writing proposals that are too dense or unclear

• generalist writers missing important technical details

• AI-generated drafts that lack depth

Our approach combines the best elements of each — without their downsides.

You bring the deep expertise.

We bring someone who understands your field well enough to ask the right questions, surface what matters, and shape it clearly.

We also reduce the burden on your team.

Instead of starting from scratch, we work from:

• materials you’ve already developed

• prior proposals

• technical documents and internal content

We use those inputs to build structured drafts quickly, so you’re not spending hours writing from a blank page.

That means:

• you don’t lose technical depth

• your time isn’t consumed writing

• and the proposal is structured in a way reviewers can immediately understand

Because the person shaping the proposal is close to your domain, they can:

• ask better questions and identify key gaps

• highlight what matters most

• structure the narrative in a way reviewers recognize

And since reviewers often come from similar technical backgrounds, the proposal is aligned with how it will actually be evaluated.

P - Proven Intelligence

We apply lessons that our team has amassed by assisting companies with hundreds of proposals to every submission.

In many firms, outcomes vary based on who you work with and how much time they have.

In practical terms, that often means this:

You might be working with someone who has submitted 5–15 proposals. They’ve had a few wins, learned some lessons, and developed their own approach.

And that’s valuable — but it’s also limited to their individual experience.

So when they review your proposal, the feedback you receive is shaped by:

• what they’ve personally seen

• what they remember

• and what they have time to apply

That becomes the ceiling of insight going into your submission.

Our approach works differently.

With every proposal — no matter who you’re working with on our team — you benefit from the accumulated lessons of hundreds of submissions, across various ICs, outcomes, and scenarios.

We’ve taken those lessons:

• what led to wins

• what caused proposals to fall short

• how reviewers responded in different contexts

And we’ve embedded them into our process using AI and structured review systems.

What that looks like in practice:

Instead of one person saying,

“In my experience, this section could be stronger…”

Your proposal is evaluated against patterns like:

• how successful proposals frame innovation vs. risk

• where reviewers tend to get confused or lose confidence

• which sections consistently correlate with higher scores

• how positioning shifts based on agency priorities

And those insights are applied consistently, not just when someone happens to think of them.

This is how AI has changed the game.

It allows us to move beyond individual experience and apply collective experience at scale.

So instead of getting the benefit of one person’s 10 proposals,

you’re getting the benefit of experience across hundreds of proposals applied systematically to yours.

And that’s a level of consistency and depth that traditional models simply can’t match.

The Bottom Line

Most options fall into one of three categories:

• experience-driven firms → strong, but limited by human bandwidth

• execution-focused firms → organized, but not deeply strategic

• AI tools → fast, but lacking depth and positioning

BW&CO is built differently.

We combine:

• validated positioning based on real agency signals and direct conversations with those agencies

• human insight aligned with how reviewers think

• AI that scales experience across hundreds of proposals

Because in today’s environment, winning isn’t about writing more proposals.

It’s about submitting the right proposal, positioned the right way, with a full understanding of both the written and unwritten rules behind funding decisions.

Contact us to learn more.

We’re Guessing What the Government Actually Wants

by Kristian Mueller - Chief Grants Officer

If you’ve ever read a federal solicitation-especially a DoD SBIR/STTR topic-and thought “I can follow every instruction here and still miss the mark,” you’re not wrong.

One of the least talked-about realities of federal proposal writing is this: the solicitation is necessary, but rarely sufficient. The strongest proposals don’t just comply-they anticipate what the government actually wants, even when they can’t say it outright.

After years of writing and reviewing proposals for technology startups, and working directly with engineering teams and government stakeholders, we’ve learned that winning proposals live in the space between strict compliance and educated interpretation.

Let’s talk about what that really means.

Yes, You Must Follow the Solicitation-But That’s the Floor, Not the Ceiling

Let’s get this out of the way first:
You must follow the solicitation requirements exactly.

Page limits, formatting rules, evaluation criteria, topic scope, cost caps-these are non-negotiable. Noncompliance can get you rejected before anyone reads your brilliant technical approach.

But here’s the uncomfortable truth:
Hundreds of proposals follow the rules. Very few get funded.

Reviewers aren’t scoring you on whether you can read instructions. They’re scoring you on whether your solution aligns with a mission need that often isn’t fully spelled out.

That’s where reading between the lines comes in.

Especially for DoD: Some of the Real Requirements Aren’t Written Down

DoD solicitations are a special case. Many topics are intentionally vague, constrained, or abstracted-sometimes because of classification, sometimes because the program office itself is still refining the requirement.

When a topic says something like:

“Innovative approaches for resilient, next-generation sensing in contested environments”

What it might mean is:

• They’ve had a system fail in the field

• A prime contractor solution is too expensive or fragile

• They need something deployable in 18–36 months

• They want optionality, not a single locked-in architecture

None of that will appear explicitly in the solicitation.

Your job-and ours-is to infer those drivers without inventing things that aren’t defensible.

How Do You Figure Out What’s Not in the Solicitation?

This is where many small companies struggle, especially first-time proposers. The good news: there are ways to reduce uncertainty and make informed guesses instead of blind ones.

1. Talk to the Humans Behind the Topic (Yes, You’re Allowed To)

For most SBIR/STTR and BAA opportunities, you can-and should-reach out to:

• Topic Authors

• Technical Points of Contact (TPOCs)

• Program Managers or Directors
  

These conversations won’t give you proprietary information, but they can clarify:

• What success looks like at the end of Phase I or II

• Whether the topic is exploratory or transition-driven

• What applications they care about most

• What approaches they’ve already seen (and aren’t excited about)

A short, well-prepared email or call can save months of misaligned proposal work.

2. Read the Agency’s Funding History Like a Signal, Not a Spreadsheet

Past awards are one of the most underused sources of insight.

Looking at what an agency or program office has funded before can tell you:

• Technology maturity they’re comfortable with

• Typical Phase II award sizes

• Whether projects routinely transition-or stall

• Which primes or end users show up repeatedly

For recurring BAAs or long-running programs, funding patterns often reveal strategy. Are they doubling down on a capability area? Spreading bets? Letting one domain quietly sunset?

Those patterns should influence how you position your technology.

3. Understand the Money Reality (Not Just the Maximum Award)

Solicitations often list a maximum award amount. That does not mean:

• That amount is fully available

• Every topic will be funded equally

• The program isn’t already partially allocated

Experienced proposal teams pay attention to:

• Number of awards anticipated

• Typical funding per award in prior years

• Whether this is a new call or a continuation

• Signals of constrained or expanding budgets

This matters not just for pricing, but for scope credibility. Over-promising in a constrained funding environment is a fast way to lose reviewer confidence.

What Reviewers Are Actually Asking When They Read Your Proposal

Even when they’re scoring against formal criteria, reviewers are often implicitly asking:

• Does this team understand our problem, not just the topic text?

• Is this a real solution, or a research project looking for a use case?

• Can this company execute, or will we be managing them?

• Does this scale beyond Phase I/II?

• Would I want to champion this internally?

Great proposals answer these questions without ever stating them explicitly.

So… Are We Guessing?

Yes-but not randomly.

Winning federal proposals are built on informed inference:

• Grounded in the solicitation

• Reinforced by agency behavior

• Clarified through direct engagement

• Shaped by real engineering constraints

At BW&CO, this is where our background in both technology development and proposal review matters. We don’t just translate your technology into government language-we help position it in the context of what the government is quietly trying to accomplish.

Because the truth is, the government often can’t say exactly what it wants.

But with the right approach, you can still give it to them.

Contact us to learn more.

Our Technology Is Strong but Reviewers Don’t Get It

by Sameera Panchangam - Senior Grant Consultant

It is one of the most common and frustrating statements we hear from founders pursuing non-dilutive funding:

“Our technology is strong. The reviewers just didn’t get it.”

And often, the first part is true. The technology is strong.

But here is the uncomfortable reality:

If reviewers do not get it, the problem is rarely the reviewer.

It is almost always the proposal. Strong technology alone does not secure funding. Perspective does.

When You Are Too Close to the Product

Founders are deeply committed to what they build. You have spent years refining the science and engineering around constraints, protecting IP, and proving feasibility. That depth of knowledge is a strength.

But it can also create blind spots. You may be attached not only to the product, but also to the story you tell about it.

When we suggest reframing objectives, narrowing aims, repositioning impact, or even changing agencies, it can feel like we are undermining the core innovation.

We are not.

We are translating it for a reviewer who is seeing it for the first time.

Reviewers do not live inside your roadmap. They do not know your technical shorthand. They only see what is written on the page.

Clarity is not simplification. It is a strategy.

You May Be Married to the Wrong Agency

Another common challenge is agency misalignment.

For example, a founder building advanced sensing technology for crop optimization may target NSF because the platform is novel and technically sophisticated.

But the proposal emphasizes farm productivity, food security, and field validation across specific commodities. That may align more tightly with USDA priorities.

Similarly, a dual-use autonomy platform may feel like an NSF engineering proposal, yet its strongest case may lie in resilience, mission readiness, or logistics optimization in a defense context.

Each agency has a mission. Each division within that agency has specific priorities. Some are focused on basic science. Others are mission execution. Others are deployment and transition.

Defense agencies in particular evaluate not just technical novelty, but operational relevance, integration pathways, and end-user value.

Strong innovation in the wrong mission context is still misaligned.

Understanding the intent behind the funding opportunity is as important as understanding the science.

Who Is Actually Reviewing Your Proposal?

Review panels are diverse.

They may include:

• Academic researchers

• Industry technologists

• Former founders

• Program awardees

• Domain specialists/Scientists 

• Mission operators in defense contexts

They are trained to apply scoring criteria objectively. They are instructed to dissect feasibility, impact, risk, and alignment.

But they are also human.

They may review dozens or even hundreds of applications in a cycle. They are balancing this responsibility with full professional workloads.

If your proposal buries the value proposition, overloads the reader with technical detail before establishing the problem, or assumes prior knowledge, cognitive fatigue sets in quickly.

An exercise we recommend to founders:

Review your application once as a professor, evaluating rigor.
Then review it as an operator evaluating utility.
Then review it as a commercialization expert evaluating transition potential.

Would each of them clearly understand why this matters within the first few pages?

If not, revise.

The Broken Leg Test

Across sectors, one principle holds: Reviewers are looking for a clear and compelling problem.

In health, it may be a clinical gap.
In agtech, it may be yield loss or resource inefficiency.
In defense, it may be operational vulnerability or capability gaps.
In energy, it may be grid instability or storage constraints.

Whatever the domain, the problem must feel urgent and real.

If the pain point is vague or abstract, interest fades.

Reviewers are not there to infer the need. They are there to evaluate whether you have clearly articulated it.

If they cannot see the broken leg, they will not fund the cast.

One Major Weakness Can Influence Everything

Even when the technology is strong, a single glaring issue can affect overall perception.

It could be:

• An unrealistic transition timeline

• Weak validation data

• A mismatch between objectives and methods

• No clear path to end users

• Lack of regulatory or compliance awareness

• Insufficient understanding of field deployment constraints

Reviewers strive for objectivity. Still, an early red flag can create doubt that influences scoring across sections.

That is human nature.

Coherence matters. Internal logic matters. Alignment between problem, solution, validation, and impact matters.

Non-Dilutive Funding Is Mission-Driven

Unlike venture capital, government agencies are not investing in valuation growth.

They are investing in mission outcomes.

That mission may be:

• National security

• Agricultural resilience

• Energy independence

• Scientific advancement

• Economic competitiveness

• Public health

Your proposal must clearly connect your innovation to that mission.

The strongest applications consistently do three things:

1. Demonstrate credible technical innovation

2. Define a clear and urgent problem

3. Align tightly with agency mission and program priorities

If one of these elements is weak, reviewers will notice.

What We See at BW&CO

At BW&CO, we spend significant time analyzing prior reviewer comments across agencies and sectors. Patterns emerge regardless of the domain.

Common critiques include:

• Impact not clearly articulated

• Transition pathway insufficient

• Overly ambitious scope

• Limited understanding of the end-user environment

• Weak commercialization or deployment strategy

Studying prior reviews helps us understand how panels think. It reveals trends in what agencies emphasize year over year. It also helps founders step outside their attachment to the technology and into the mindset of the evaluator.

When you understand the reviewer’s incentives, you stop writing to explain your technology and start writing to justify investment in your mission alignment.

Final Thought

When proposals are not funded, it is easy to conclude that reviewers did not understand the innovation.

More often, they understood exactly what was presented.

They just did not see enough clarity, alignment, urgency, or feasibility to justify funding within their mission constraints.

Strong technology is the foundation.

But perspective wins awards.

If you are exploring non-dilutive funding across health, defense, energy, climate, or agriculture and wondering why strong science is not translating into awards, the issue may not be your core innovation.

It may be how it is framed, aligned, and communicated.

At BW&CO, we help founders see their proposals through the reviewer’s lens and build applications that speak not just to innovation, but to mission.

Contact us to learn more about how we can help your next proposal suceed.

The Forgotten Customer: Why Health Tech Startups Overlook the VA

By Robert Wegner - Chief Revenue Officer

When doing business with the government, most biotech, medtech, and health tech companies focus on one place: the Department of Defense.

If they don’t have something that directly supports the active warfighter, they usually move on. They assume government work is not for them.

That’s a mistake.

What most founders forget is that the Department of Veterans Affairs operates 170 medical centers and more than 1,000 outpatient sites. It serves over 9 million enrolled veterans each year. It is one of the largest integrated healthcare systems in the country.

If you are building technology for chronic disease, aging, mental health, oncology, or rehabilitation, the VA is not a side option. It is a major healthcare customer.

Ignoring it leaves opportunity on the table.

The VA Is a Real Healthcare System — Not a Side Program

The VA is not just a benefits administrator.

It delivers care every day. It runs specialty clinics. It manages long-term chronic conditions. It treats middle-aged and geriatric populations at scale. It funds research. It buys equipment. It runs clinical studies.

If your product is built for hospitals, health systems, or aging populations, there is a strong chance it applies to the VA.

The key is alignment.

Not “we improve healthcare.”

But “we solve this specific problem the VA has publicly said it cares about.”

Health Priority Areas: Where Alignment Often Exists

The VA maintains a wide range of research and clinical priority areas. These are tied directly to patient needs across its system.

Several common areas of interest include:

Alzheimer’s disease and related dementias.
Arthritis and musculoskeletal disorders.
Brain health, including mental health and PTSD.
Cancer, including prostate and ovarian cancer.
Cardiovascular disease.
Diabetes, obesity, and kidney disease.

These are not niche categories. They reflect the real disease burden inside the veteran population.

If you are building diagnostics for early dementia detection, remote cardiac monitoring, oncology tools, metabolic disease platforms, AI-enabled mental health support, or rehabilitation technologies, there may be direct overlap.

The question is not whether the VA “funds innovation.”

The question is whether your product addresses a defined health priority within its system.

If you can clearly connect your solution to one of these areas, you are in a stronger position than most startups who approach government work.

Securing Internal Advocates

Alignment on paper is not enough.

You need a human inside the system who believes in what you are building.

Once you identify a relevant health topic, your next step is to find an internal advocate. This is someone working within or closely affiliated with the VA who understands the disease state and sees how your solution could help veterans.

This could be at the local level, such as a clinician at the VA Palo Alto Health Care System. It could also be at the national level, such as someone connected to the VA Office of Research & Development (ORD).

These advocates matter for three reasons.

First, they help you refine your value proposition so it actually fits VA workflows and patient populations.

Second, they guide you toward the right funding mechanisms or pilot pathways.

Third, they provide credibility when you pursue formal studies, grants, or procurement vehicles.

Without internal support, most companies stall. They submit cold applications. They wait for responses. They burn time.

With internal support, conversations move faster and become more focused.

Funding and Procurement Pathways

Once you have meaningful engagement from an internal advocate, you can begin evaluating funding and procurement options.

There are multiple pathways depending on your stage.

If you are still in pre-clinical or early clinical development, research-focused mechanisms may be appropriate. In some cases, programs like CDMRP can provide significant funding for assets that align with veteran health priorities.

If your product is further along and ready for deployment, there may be procurement pathways within the VA itself. This can include structured pilot programs, clinical studies, or direct purchasing mechanisms for solutions that address defined needs.

The mistake many startups make is chasing mechanisms first.

They search for open calls. They draft proposals. They try to “fit” themselves into whatever funding vehicle is available.

That rarely works.

The more effective approach is this:

1. Confirm alignment with a VA health priority.

2. Secure internal support.

3. Then identify the right mechanism.

When done in that order, funding becomes a tool — not a gamble.

The Practical Takeaway

If you are a biotech, medtech, or health tech founder, do not assume government work equals defense contracts.

The VA is a massive healthcare provider. It treats millions of patients across many of the exact disease areas commercial startups target.

Before you dismiss government engagement, ask:

Does our product clearly align with a VA health priority?
Can we identify a specific patient population within the system?
Do we have a plan to secure an internal advocate?

If the answer is no, you need refinement.

If the answer is yes, you may have a serious opportunity.

If you are considering the VA as a co-development partner or procurement customer, book a call with our team. We’ll help you assess alignment, identify realistic entry points, and determine whether pursuing the VA makes strategic sense for your stage.

The VA is often the forgotten customer.

For the right company, it shouldn’t be.

Stop Wasting Time on Low-Probability Grant Opportunities

by Narges Tafreshi - Grant Consultant

For many founders, researchers, and small business teams, grant funding is supposed to be a catalyst, not a distraction. Yet too often, teams find themselves pouring months of effort into applications that were never realistically competitive in the first place.

The result? Burned time, exhausted teams, and stalled momentum.

The Hidden Cost of “Shot-in-the-Dark” Applications

Grant writing isn’t just about filling out forms. It requires:

• Strategic planning

• Scientific and technical alignment

• Budget modeling

• Internal coordination and reviews

When an opportunity has a very low probability of success, the real cost isn’t just the submission fee or consultant time; it’s the opportunity cost. Those months could have gone toward product development, customer discovery, partnerships, or higher-probability funding paths.

Why So Many Grant Opportunities Are Low Probability

Many grant solicitations look promising on the surface, but hide structural challenges that drastically reduce competitiveness:

• Overly broad solicitations that attract hundreds of applications

• Unpublished or shifting paylines, especially in SBIR/STTR programs

• Institute-specific preferences that aren’t obvious from the FOA

• Portfolio-balancing decisions that have little to do with scientific quality

Without insight into how funding decisions are actually made, teams often assume that a “decent” application is good enough. In reality, competitiveness is relative, and often far more selective than it appears.

Scoring Alone Doesn’t Tell the Whole Story

NIH and other agencies rely on impact scores and review outcomes, but funding decisions are rarely mechanical.

A technically strong application can still fall short if:

• It doesn’t align tightly with current program priorities

• The institute’s budget is constrained in that cycle

• Similar projects were recently funded

• The application lands just outside a practical zone of consideration

This is why many applicants receive solid reviews, and still no award.

A Smarter Question to Ask Before Applying

Instead of asking, “Can we apply?”, more teams are now asking:

“Is this opportunity actually worth our time?”

High-probability opportunities tend to share a few characteristics:

• Clear alignment with institute or program priorities

• Realistic competitiveness based on recent funding patterns

• A defined scoring or selection pathway

• A credible strategy to address reviewer risk

If those elements aren’t present, even a well-written application may be a long shot.

Fewer Applications, Better Outcomes

The most successful grant-funded teams are not applying to everything. They are:

• Selective about where they invest effort

• Strategic in how they use prior scores and reviewer feedback

• Focused on opportunities where marginal improvements can meaningfully change outcomes

This approach doesn’t reduce ambition, it increases efficiency.

Moving From Hope-Based to Strategy-Based

Grant funding will always involve uncertainty. That’s inherent to competitive, peer-reviewed systems. But uncertainty does not have to mean guesswork, and it doesn’t have to mean going it alone.

A strategy-based approach replaces blind optimism with informed confidence. It allows teams to make deliberate decisions about where to invest their time, energy, and scientific effort before months are spent writing.

By prioritizing fit, probability, and timing, organizations can move away from low-yield opportunities and toward a funding roadmap that is both realistic and forward-looking. This includes understanding which programs are actively funding work like yours, how competitiveness is assessed, and when small adjustments can meaningfully improve outcomes.

Importantly, this approach doesn’t limit opportunity, it focuses it. Many strong ideas fail to secure funding not because they lack merit, but because they were submitted to the wrong mechanism, the wrong institute, or at the wrong moment. Strategy turns those uncertainties into informed choices.

When teams apply selectively and intentionally:

• Applications become clearer and more compelling

• Reviewer feedback becomes more actionable

• Resubmissions are more efficient and targeted

• Funding outcomes feel repeatable, not random

The goal isn’t to submit more applications. It’s to win the right ones, at the right time, with the right positioning. With a strategy-driven approach, grant funding becomes not just possible, but increasingly predictable.

Need help with crafting your grant strategy? Contact our team today.

Understanding NIH Impact Scores

By Narges Tafreshi - Grant Consultant

As NIH review results are released, many applicants are asking the same question: how should I interpret my outcome, and what does it mean for funding? Recent NIH review cycles have introduced clearer distinctions in how applications are categorized, making it especially important to understand what your result actually signals.

How NIH Review Outcomes Are Assigned

NIH study sections now generally place applications into one of three categories during peer review:

1. Not Discussed

Applications in this category were not selected for full discussion by the study section. This typically means reviewers felt the application was not competitive relative to others in the pool.

• No overall impact score is assigned

• Written critiques are still provided

• These applications are generally not considered for funding in the current cycle

While disappointing, this outcome can still provide useful feedback for a substantial revision or repositioning.

2. Not Discussed – Competitive

This is a newer and important distinction. These applications were not discussed, but reviewers considered them borderline or potentially competitive.

• No overall impact score is assigned

• Reviewer comments often indicate specific, fixable weaknesses

• These applications may be close to discussion thresholds in strong review rounds

A “Not Discussed – Competitive” outcome often signals that a targeted resubmission could meaningfully improve funding chances.

3. Scored

Applications that are discussed by the study section receive an overall impact score, typically ranging from 10 (best) to 90.

• Lower scores indicate stronger perceived impact

• Being scored means the application cleared the initial competitiveness bar

• A scored application can still fall inside or outside likely funding ranges, depending on institute priorities and budget

From Impact Score to Funding Decision

Impact scores are evaluated in the context of institute-specific paylines or zones of consideration. A payline represents the approximate score threshold below which applications are more likely to be funded, based on available funds and application volume.

• Applications scoring better than the payline are more likely to be funded

• Applications just outside the payline may still be considered, especially with strong programmatic relevance

• Applications well outside the payline typically require either exceptional justification or resubmission

It’s important to note that many NIH institutes do not publish formal paylines, particularly for SBIR and STTR programs.

What’s New in Current NIH Funding Cycles

Recent funding cycles have placed increased emphasis on:

• Programmatic fit, not just numerical rank

• Portfolio balance and strategic priorities

• Institute-level discretion, particularly for small business awards

As a result, applicants with competitive scores near traditional paylines are seeing more variability in outcomes. Early communication with Program Officers (POs) has become increasingly valuable, especially for applications that are scored or labeled “Not Discussed – Competitive.”

SBIR and STTR Applications: Additional Context

For SBIR (R43/R44) and STTR (R41/R42) applications, funding decisions depend on more than the impact score alone. Reviewers and institutes also weigh:

• Commercial and translational potential

• Technical feasibility and risk

• Alignment with institute-specific missions

Because SBIR/STTR paylines are often unpublished, understanding how your review outcome is categorized is a key signal for next steps.

What to Do After You Receive Your Outcome

Once your NIH review results are released:

1. Identify whether your application was Not Discussed, Not Discussed–Competitive, or Scored

2. Carefully review reviewer comments for common themes

3. Compare your outcome to recent institute funding patterns

4. Consider outreach to your Program Officer to assess competitiveness and strategy

5. Decide whether revisions could materially improve your positioning

While no single outcome guarantees funding, understanding how NIH now categorizes applications allows you to make more informed, strategic decisions about resubmission and next steps.

If you’d like our team’s free assessment, click here.