Kamin Applied Research Program

Kamin Applied Research Program

Kamin is best understood as a bridge program. Its core purpose is to help research groups in Israel move technology from the academic lab to an industrial context where a company can adopt it and build a commercial product.

This is a long-term program for teams that can prove they have both technical substance and a believable commercialization path. It is not a seed grant for exploratory curiosity. It is for projects that already have a defined technical direction and can show how the work connects to an industrial need.

The official program is listed by the Israel Innovation Authority, and the currently reachable official page is the English “Applied Research in Academia – Applied Research Fund” page at:

• https://innovationisrael.org.il/en/programs/applied-research-in-academia/

A previous URL used by this opportunity record (/en/program/kamin-applied-research) returned HTTP 404 when checked, so links should now point to the current official page above.

Before reading the mechanics, decide if the core promise matches your project: can your research produce a result that industry can test, evaluate, and move toward commercialization in a realistic time window? If yes, this program can be worth your time.

At-a-Glance Snapshot

What the program is (and what it is not)

This program is for applied research at the interface of science and industry, not basic research disconnected from use cases.

It is intended to fund:

• teams that can identify a practical technical problem and show industry relevance
• research that can be validated to TRL3-TRl5 (with specific windows depending on call details)
• work that can deliver meaningful milestones and reduce uncertainty for commercialization

It is not designed for:

• pure scientific publications without industry-facing scope
• projects without clear implementation ownership in an industry setting
• teams that submit only one-sided technical narratives without evidence of use context
• vague consortia with no defined partner roles

A simple way to test alignment: if your project can be explained in one sentence as “an applied technology from academia that a defined industry actor can adopt,” it may fit. If your sentence starts with “we need to explore whether this is useful,” fit is lower.

What this opportunity offers in practical terms

The most useful way to understand value is not just “money.” It is: does the program reduce execution risk?

Core value

• It can fund applied R&D work in a way that reduces early-stage cash pressure.
• It improves project credibility by requiring a formalized process, reporting, and explicit milestones.
• It creates a recognized pathway to move toward commercialization agreements.
• It can provide additional commercialization support (such as business-oriented technical guidance) when approved by the program committee.

Financial support

The official material includes two key financing scenarios:

1. Without a supporting corporation: support at lower rates.
2. With a supporting corporation: higher support rates (notably 90% in current Hebrew-language program notes).

Historical English snapshot and current Hebrew page differ in the exact budget caps shown, which indicates some program rules are time-sensitive. That is why you should use current official pages for exact calculations before submission.

What is clear from official text:

• support can be large enough to make serious feasibility work possible
• support share and maximum amounts vary with consortium structure
• when a corporation is involved, contribution and rights structure are defined up front

Royalty treatment and ownership

The program is presented as a grant-style instrument in which support is shown as exempt from repayment of royalties. The Israeli-side official content also notes that knowledge generated remains with the research institution, while commercialization rights and processes are handled through commercial agreements.

This distinction matters: ownership remains with the research institution, while the corporate partner often gets first negotiation rights for commercialization.

Who should apply: a practical self-screen

Use this checklist before investing time in writing the application.

1. Is your project already rooted in prior research from an Israeli research institution?
2. Can you point to an industrial application with measurable potential value?
3. Do you have at least one possible industrial path (customer, sector, partner, or pilot)
4. Can your project reach meaningful TRL milestones with finite tests?
5. Can your application company deliver complete, submission-ready documentation by the deadline?

If you can answer “yes” to most of these, you are likely a candidate.

Eligibility summary

The official pages consistently define eligibility around research institutions and application groups representing them:

• Universities, colleges, research centers, and medical centers
• Research groups that can justify prior base research and current applied scope
• Teams that are part of one to three collaborating institutions (in some tracks, explicitly up to three)
• Projects with clear industrial translation path and high added value potential for Israel

Practical applicant fit examples

• Strong fit: a materials science lab with an existing industrial molder partner and defined prototype milestone sequence.
• Moderate fit: an academic team with a promising concept and letters of interest from industry but no technical integration plan.
• Weak fit: a group with only an idea and no industry-facing validation plan.

A strong application should present both scientific credibility and commercialization fluency.

Why this program can be worth your time

Many teams overestimate the difficulty of this program and underestimate what it filters out. The real value comes from whether the opportunity can de-risk the gap between research and commercialization.

Apply if:

• your team already has technical depth and needs support to bridge to TRL5
• you have or can recruit an industry partner willing to participate
• you can produce clear deliverables (experiments, pilot plans, commercialization path) in a funded cadence
• you are willing to follow a formal reporting model every six months by work package

Consider skipping if:

• your project needs only early discovery funding with no commercialization path yet
• you cannot define any industrial owner, even at a pilot level
• your team lacks decision authority and cannot provide complete documentation

Eligibility deep dive

The official pages present several layered checks:

• Origin and authority: The project must be tied to a legitimate research institution in Israel.
• Applied orientation: The project should be a continuation toward implementation, not purely exploratory.
• Industrial relevance: Outputs must be applicable in Israeli industry and deliver broad added value.
• Commercial readiness: The team must show a route toward commercialization, not only technical novelty.
• Consortium and governance clarity: If multiple institutions are involved, roles and responsibilities must be explicit.

For teams with a corporate partner, include evidence of that partner’s role and contribution, including guidance and technology validation support.

Corporate partner role in practice

When a partner is attached, program sources describe the partner as:

• a professional guide in research goal setting
• a financial contributor at a defined share (10% of project cost is explicitly referenced in official text)
• a party with first negotiation rights for commercialization after project completion

The partnership model is not optional theater. It should influence both R&D planning and commercialization design.

Funding details and planning expectations

Because published numbers vary slightly across languages and dates, use conservative planning:

• Confirm current exact percentages/caps on the official page right before application.
• Do not rely on outdated assumptions from snapshots.
• Keep your budget conservative enough to survive conservative committee interpretation.

How to write a realistic budget

Your budget should align with milestones and outputs, not with a wish list. Good applicants link each cost to a specific output:

• Personnel and time allocation tied to technical milestones
• Subcontracting and services with reasoned unit costs
• Prototyping, testing, and validation costs
• Management and reporting overheads
• Optional commercialization support elements that strengthen adoption

Make sure the budget can explain why and how the project reaches TRL milestones under each phase.

Application process (verified process steps)

The official Hebrew page states submission is handled by the application company in the research institution and is done through the Authority’s personal area.

A practical sequence:

1. Read the current eligibility/technical criteria on the official page.
2. Select your submission window carefully and confirm the exact cut-off time.
3. Register or sign in to personal area.
4. Open the online investment submission form.
5. Fill in the full proposal in the required online structure.
6. Upload all requested attachments through the “add attachments” section.
7. Verify that each file meets naming rules and is not password-protected.
8. Re-check that budget and summary details are internally consistent.
9. Confirm partner commitments and rights/roles in documents.
10. Submit before the published deadline (daily cut-off is strict at 12:00).
11. Track submission confirmation and expected decision timeline for your window.

Submission timing and windows

The currently visible official pages show that applications are not restricted to a single yearly call window in a simple manner. The Hebrew page includes:

• Annual continuous submission framing
• Published submission windows that can include multiple dates per year
• Submission cutoff by noon on published dates
• Technical support until that cutoff on submission day

This means you should treat deadlines as a date system, not a single date. Keep a weekly process where you watch date updates and prepare before the window begins.

A specific “next” date visible in the checked material is 10/03/2026. The same page family also showed several 2026 dates in public snippets. Because dates can shift, your default action is always “check the program page immediately before submission planning.”

Required documents and submission quality controls

The program requires attachments listed in the program page. Key document categories include:

• investment request form in the personal area structure
• budget file
• partner and research-team role statements (where relevant)
• signed signature pages and authorizing signatory details
• resource concentration forms and any additional forms required by published instructions
• consent/waiver statements when requesting specialist commercialization support
• in some consortia contexts, consortium agreements and any international grant-related documents

Do not submit partial sets. The official guidance is explicit that complete submissions are required.

Common technical submission mistakes to avoid

• Filename or attachment formatting issues (especially restricted characters)
• Missing full set of documents
• Password-protected files
• Inconsistent budget figures across attachments
• Submitting before partner agreement is signed or before commercial contribution is confirmed
• Unclear TRL plan (weak link between task and expected output)
• Vague roles between institutions and partner organization

When these mistakes happen, the program often returns or rejects late submissions quickly.

Decision criteria (how proposals are judged)

Expect review to look beyond the technical story. It is usually assessed on multiple axes:

• Technological feasibility: novelty, feasibility, and technical foundation
• Commercial potential: market relevance and competitiveness of the solution
• Institutional execution capability: team capability, management, and ability to deliver within stated milestones
• Alignment with issued challenge: relevance to published sector themes if any
• Milestone credibility: whether outputs are measurable and realistically scheduled

A strong proposal does not just say “this is important”; it demonstrates exactly what success looks like at each stage.

Readiness scorecard: are you truly ready?

Ask your team to score each area from 1 (weak) to 5 (strong):

• Problem definition and user value
• TRL evidence and experimental plan
• Business model and commercialization path
• Partner engagement and commercialization support
• Documentation quality and internal deadline discipline
• Reporting capacity (financial and technical)

A score below 3 in any area usually predicts rework or rejection risk.

If one or more areas are below 3, fix them before submission rather than relying on writing quality.

Preparation roadmap (12-week style)

The following timeline can be adapted to your team size:

1. Weeks 1-2: validate fit with official criteria, confirm partner interest, assign roles.
2. Weeks 3-5: finalize use case, TRL path, and milestone map.
3. Weeks 6-8: draft proposal and detailed budget, align with application form structure.
4. Weeks 9-10: prepare attachments, legal signatures, and partner documents.
5. Weeks 11-12: run pre-submission dry run against checklist and cut-off conditions.

This gives you time to revise before the next published date and avoids “last-hour submission” errors.

Practical tips for a stronger submission

• Put commercialization at the center of your narrative from page one.
• Keep partner scope explicit: who validates, who funds, who owns which risk.
• Translate science into industry outcome language for reviewers.
• Show measurable success criteria (e.g., prototype readiness, validation criteria, pilot metrics).
• Link each budget line to an output and a date.
• Include a simple risk register with mitigation actions.
• Keep reporting assumptions realistic: if required biannual reporting is impossible in your structure, fix governance first.

Common mistakes (read before writing)

1. Submitting a beautiful technical paper without commercial execution logic.
2. Assuming one institution can represent all roles without clarifying consortium governance.
3. Underestimating the impact of missing signature pages or partner documents.
4. Ignoring the submission cutoff and technical check window.
5. Treating TRL as jargon rather than a concrete test plan.
6. Overstating expected outcomes while underestimating resources.

Frequently Asked Questions

Who is the official applicant?

The research institution’s application company submits through the Authority’s personal portal. Industry partners may support, co-guide, and negotiate commercialization rights, but the submission is made by the institution channel.

Are there fixed dates only?

The program is described as a rolling annual intake with published submission windows and windows often updated throughout the year.

Do industry partners matter?

They matter substantially. They strengthen commercialization probability, can increase funding support rate, and define commercialization pathways. However, the project should still stand on technical merit and management clarity.

Is this an all-or-nothing grant?

It is presented as a grant-style support instrument for approved projects, and official descriptions emphasize repayment-free support in this context. Keep in mind this can be revised in detailed terms of the specific incentive track; read current track language before application.

Do I need to file annual reports?

Yes. Program notes include periodic reporting expectations (including semi-annual progress updates by work package in current official documentation).

Can one person apply?

Yes, with one research group, but partnership and funding limits are usually better managed when roles are defined and partner contribution is realistic for execution.

FAQ on readiness and post-award behavior

• What should we do if we miss the deadline? Prepare for the next published window; do not submit incomplete revisions the same day.
• Can we reapply with changes? Yes, but keep consistency in scientific scope and keep clear explanation of what changed.
• How do we protect ourselves legally? Keep rights assignment and commercialization rights statements clear; do not assume default arrangements.

Official links you should keep open

• Program page (English): https://innovationisrael.org.il/en/programs/applied-research-in-academia/
• Program page (Hebrew current): https://innovationisrael.org.il/programs/%D7%9E%D7%A1%D7%9C%D7%95%D7%9C-%D7%9E%D7%97%D7%A7%D7%A8-%D7%99%D7%99%D7%A9%D7%95%D7%9E%D7%99-%D7%91%D7%90%D7%A7%D7%93%D7%9E%D7%99%D7%94-%D7%A7%D7%A8%D7%9F-%D7%94%D7%9E%D7%97%D7%A7%D7%A8-%D7%94%D7%99/
• Personal area submission: https://my.innovationisrael.org.il/
• General contact for submission support (per official page): [email protected]
• Technical/coordination inquiries for this program: [email protected]
• Contact phone (official hours): +972-3-7157900, weekdays 8:30–16:30

Next step checklist

1. Open the official page and copy the latest submission schedule.
2. Confirm current funding rates and budget caps for your track.
3. Build your proposal around one measurable commercialization objective.
4. Finalize partner roles and contribution terms before writing the narrative.
5. Run a pre-submission document audit for completeness and naming rules.
6. Submit early in the chosen window, then track confirmation and decision communications.

If this matches your opportunity profile and you can defend the commercialization logic under scrutiny, this is likely worth pursuing.