NIH RFA-HL-26-018: CATALYZE Product Definition for Small-Molecule Biologic Combination Therapies

NIH RFA-HL-26-018: CATALYZE Product Definition for Small-Molecule Biologic Combination Therapies

The CATALYZE Product Definition RFA is a focused NIH program aimed at speeding early translational movement from promising science to a development-ready therapeutic concept. If your team has combination therapy assets that are scientifically attractive but currently sit in an “interesting preclinical discovery” phase, this solicitation is structured around exactly that gap: producing a credible and testable product definition that can sustain a more advanced development path.

This page is a practical guide for teams evaluating this opportunity in mid-2026. It summarizes official eligibility, deadlines, funding parameters, and review expectations, then translates them into an application strategy you can actually execute.

Key details at a glance

The single most important thing to understand is this is not a broad basic science grant. NIH is asking for development-ready planning quality: mechanistic rationale plus concrete design for safety, manufacturing, regulatory, and pathway decisions that would justify progression beyond early-stage work.

Why this is a good fit for translational teams

This funding mechanism is attractive if you are building a therapy strategy that integrates two classes of modalities and you already have enough early evidence to justify translational commitment. It is less suitable if your project is only a discovery idea with no clear development hypotheses or preclinical validation plan.

What this RFA is explicitly trying to reduce

The CATALYZE framing is about the “uncertainty gap” between discovery and development. NIH has historically had excellent support for early innovation, but many programs do not require teams to demonstrate product-level operational thinking before moving forward:

• how to define a development pathway,
• what milestones prove de-risking,
• how safety and feasibility questions are resolved in sequence,
• where manufacturing and regulatory considerations must shape design.

This solicitation explicitly asks teams to deliver a coherent package that can inform future program-level investments. If your deliverable is a well-justified plan, not merely a scientific report, you are aligned.

Who benefits most

1. Startups and small biotech teams with one or more late preclinical candidate combinations.
2. Academic groups that can move from mechanism to development-stage planning with CMC and pharmacology support.
3. Non-dilutive partnerships where small firms can pair with translational researchers and CRO support for execution.
4. Cross-disciplinary consortia where biomarker strategy, mechanism-of-action science, and early manufacturing are coordinated.

Because NIH emphasizes practicality, teams that can show they know who does what, what decision gates exist, and what evidence is missing are favored over teams with only broad vision and little operational grounding.

Eligibility and applicant profile (from official language)

The solicitation is an R33-structured translational program in a therapeutics niche, so the standard NIH framework applies with some important program-specific focus points.

Eligibility conditions to capture in your planning checklist:

• Organization must be eligible to receive NIH funding under standard NIH rules.
• Awardees must submit compliant institutional and administrative registrations (not optional).
• Projects should fit the specific small-molecule and biologic combination context.
• Budget justification and project design should match R33 expectations: no unrestricted exploratory study, but a targeted product-definition pathway.
• Non-US entities and partnerships need to ensure all compliance requirements are met before submission.

You should verify the detailed “Eligibility” language in the official RFA and any parent announcements because wording and definitions can evolve at the release level. In particular, if your organization is an investigator-led startup, pay special attention to institutional authority, legal assurances, and cost-share constraints.

Funding, timeline, and application logistics

Budget and award structure

The program indicates an average per-award cap of up to $400,000 direct costs per year and states a pool-level commitment where NIH has identified a total of $4,466,000 for FY26/27/28 with approximately eight awards per year in the described structure. This framing is important because it signals competitive selectivity and finite slots.

Treat budget expectations as constrained: your proposal should be lean, with clearly budgeted workstreams mapped to milestones. Reviewers expect that you can defend every cost center against an explicit output:

• mechanistic experiments,
• translational qualification,
• tox/PK/PD planning,
• manufacturing or formulation readiness,
• decision logic for continuation.

What deadlines matter

The solicitation includes a 2026 cycle date set that includes a submission window. The deadline field for this opportunity page is set to 2026-06-18 based on the official listing in the posting.

Interpretation for planning:

• Register your institution early if not already fully enabled in the required systems.
• Submit internal drafts at least two weeks before due date to catch registration or routing issues.
• Confirm any required just-in-time info and compliance docs before final upload.

Application route and submission points

NIH opportunities generally route through the NIH/Grants.gov ecosystem with standard required forms and institutional signatures. Do not assume one “email submission” path exists. Use the official RFA announcement as the authoritative submission reference and follow that exact pathway.

Operationally, your internal action list should include:

• verified Institutional Profile and DUNS/UEI identity handling,
• Grants.gov/ASSIST path readiness,
• institutional official approval chain,
• attachments in the requested format,
• final compliance statement review before submission.

Application packet: what to submit and what reviewers look for

This is where many teams lose time: they submit technically strong science but underdeveloped development logic.

Core sections you should center

1. Problem definition and mechanism relevance

   • Why this combo is worth a translation investment.
   • Clear rationale for pairing a small-molecule and biologic modality.

2. Product definition plan

   • Your measurable outputs by quarter.
   • The decision points and pivot criteria.
   • What constitutes “definition done” versus mere discovery.

3. Execution pathway

   • Experimental design connected to development goals.
   • Who does each package of work.
   • External partnerships and technical risk-sharing.

4. Implementation realism

   • staffing and subcontracting assumptions,
   • regulatory and safety planning,
   • manufacturing or formulation constraints,
   • go/no-go milestones.

5. Budget and justification

   • Why each dollar contributes to product-readiness,
   • contingency for failed experiments,
   • cost discipline matching NIH scale.

Review expectations you should mirror

The program is likely scored on clarity of translational logic and feasibility. Write to decision-makers who must judge readiness, not only novelty.

Your proposal should consistently answer:

• What question is this award actually de-risking?
• If this succeeds, what comes next and who funds it?
• Which evidence is decisive versus exploratory?
• Why is this combination likely to be deliverable with available resources?

Fit-checking framework: are you genuinely a CATALYZE candidate?

Before you begin writing, run this gate:

• Clinical anchor present? No, you do not need large trials, but you need a development-oriented anchor, not only hypothesis.
• Actionable milestones defined? Yes if each task leads to a binary outcome.
• Risk map explicit? Yes if safety, manufacturability, and regulatory questions are spelled out.
• Team map complete? Yes if every critical discipline is assigned and not hand-waved.
• Timeline plausible? Yes if your work fits the budget and timeline without heroic assumptions.

If more than one of these is weak, you should consider a smaller internal pilot first, or partnering with a translational CRO or clinical collaborator before submitting.

Common mistakes in NIH R33-style translational submissions

1. Submission that describes science but not a development problem. Reviewers will tolerate technical depth only when it connects to measurable progression.

2. Milestones with no fail-paths. The review team wants to see whether you can fail fast and still produce useful definition.

3. Overly broad scope. NIH often favors crisp, narrow objectives with high signal.

4. Weakly linked budget. Itemized costs must tie to each milestone and expected learning.

5. Late registration/compliance errors. This causes avoidable delays and in some cases automatic ineligibility.

6. Unclear commercial transition logic. Even though it is a research mechanism, this RFA expects product definition quality, so discuss follow-on pathways and partnership routes.

Preparation strategy: a practical six-week plan before the 2026-06-18 deadline

Weeks 1-2: strategic lock-in

• Build a one-page concept note with specific measurable outputs.
• Confirm eligibility, registration status, and whether your institution can legally accept this award.
• Identify any required partnering agreements and draft them early.

Weeks 3-4: content buildout

• Draft Specific Aims and rationale with direct references to translational risk.
• Prepare milestones by month and define pass/fail criteria.
• Gather supportive data and internal letters only where they strengthen feasibility.

Weeks 5-6: compliance and hardening

• Convert text into the required package formats.
• Run a full internal audit against NIH requirements in the RFA.
• Do a complete pre-submission dry-run in the submission platform.

Teams that finish this sequence early are not only more likely to submit on time, they usually submit cleaner packages with fewer reviewer-avoidance penalties.

Documents and evidence to include only where they add signal

A strong submission is not the one with the largest appendix; it is the one with evidence mapped to claims.

Include material that directly reduces reviewer uncertainty:

• validated preliminary data tied to combination rationale,
• protocol and assay plans,
• manufacturing or formulation feasibility indicators,
• regulatory logic when applicable,
• clear governance and project management structure.

Avoid including:

• generic institutional brochures,
• broad letters with no specificity,
• budget-heavy appendices unsupported by milestones.

Review calendar and decision preparation

Because this is an NIH competition with a stated pool target, the process can be competitive and schedule-sensitive. Keep your team aligned on review milestones:

• internal internal deadline before NIH due date,
• internal compliance and budget signoff,
• final proofread and formatting check,
• backup copy of required files and supporting documents.

After submission, prepare an operations postmortem plan independent of award outcome:

• If funded, you should have a rapid-start implementation plan for the first 30–60 days.
• If not funded, extract internal reviewer feedback as development intel and decide if this cycle’s findings support a reapplication.

FAQ

Is this strictly a funding opportunity for small startup businesses?

No. It is open to organizations that can demonstrate translational capacity and submit compliant NIH proposals, including academic consortia, translational groups, and entities with strong project-management structure.

Does this provide large-scale Phase II funding?

No. The intent is product definition and de-risking, not late-stage development. Budget level is capped and time-limited.

Is preclinical data required?

Strong preliminary rationale is essential. The stronger your preclinical and mechanism context, the more credible your product definition milestones will appear.

Can international teams apply?

Use the official eligibility language in the RFA. Teams should ensure institutional and funding structures are eligible and fully compliant with NIH administration requirements.

Are letters of support enough?

Letters help only if they confirm concrete execution capacity and contribution, not rhetorical endorsement.

Official links

• NIH RFA master page: https://grants.nih.gov/grants/guide/rfa-files/RFA-HL-26-018.html
• NIH grants office and help resources: https://www.nih.gov/grants-funding

2026/2027 cycle planning notes

If you are planning around the broader 2026/2027 funding environment, treat this opportunity as a bridge mechanism. It is valuable because it rewards teams that can define the translational product path with discipline. That means applicants should prioritize evidence architecture: define what “proof” looks like for your combination therapy at each stage, and ensure your proposal is built around that logic.

Even with strong science, NIH decisions for this mechanism can be sensitive to execution quality. Your strongest applications make reviewers confident that money is used to remove unknowns that block next-stage investment. The most common success pattern is precise ambition: enough risk-taking to innovate, enough discipline to justify each spend.

At 2026-05-18, this remains a relevant opportunity to monitor if your team is at the translational boundary where mechanism strength is ahead of development maturity and you now need a structured public-sourced bridge to make the next move possible.