NRC IRAP 2026: Complete Guide to Canada's Premier R&D Funding Program

NRC IRAP — the National Research Council's Industrial Research Assistance Program — is the closest thing Canada has to a no-debt, no-dilution growth lever for technology SMEs. It pays a meaningful share of the cost of taking a technical idea from "we think this could work" to commercial reality, and it does so as a non-repayable contribution rather than a loan. For founders who have already heard about SR&ED, IRAP is the program that frequently sits one layer up: where SR&ED reimburses qualifying R&D after the year ends, IRAP funds the work as it happens, against a project plan, with an Industrial Technology Advisor at your side. This guide covers what IRAP actually funds in 2026, how the money is sized, who qualifies, how the ITA relationship really works, where applications fail, how to stack IRAP with SR&ED cleanly, and what the upcoming transition to the Canada Innovation Corporation means for current and prospective applicants.

What IRAP funds (and what it doesn't)

IRAP is fundamentally a technical project funder. The program is designed to help Canadian SMEs accelerate the development and adoption of innovative technologies that lead to a commercial outcome — new product, new process, materially improved capability, or new market entry on the back of a defensible technical advance. It is not designed to fund operating costs, sales pipelines, marketing campaigns, or businesses that don't have a meaningful technical component to begin with.

Across the SME files we see, the breakdown of what IRAP will and won't pay for is fairly consistent:

The "costs incurred before agreement signing" rule is the one founders most often discover the hard way. IRAP does not retroactively fund work you already did. If you started building the prototype six months ago and apply now, that six months is sunk — only forward-looking project costs from the agreement date onward are eligible.

How funding amounts are determined

There is no posted maximum on the IRAP website that founders can point to and say "I want that." The amount you can credibly request is a function of four things: the technical merit and ambition of the project, the strength of the team executing it, the cost structure of the work being proposed, and the budget envelope available within your ITA's region in that fiscal year. In practice, the contribution scales roughly with the size of the project — smaller, well-scoped projects might attract $50K–$150K, mid-sized projects $250K–$750K, and larger strategic projects can run into the millions, with the program's largest single-company contributions historically in the $5M–$10M+ range.

The cost-share percentage matters more than the headline number. IRAP does not fund 100% of any eligible cost — the business has to bring real cash to the project, paid from its own resources or other non-government funding. On a project with $1,000,000 of eligible labour and subcontractor cost and a 70% IRAP contribution, the contribution would be $700,000 and the business would be on the hook for the remaining $300,000 in genuine, traceable spend.

Two practical implications follow from this. First, IRAP works best for companies that can actually finance their share — either from operating cash flow, an equity round, or a credit facility. Pre-revenue startups with no runway often pass IRAP's eligibility screen but stall at financial assessment because the ITA cannot get comfortable that the business can carry the project to completion. Second, the program is a reimbursement model: you pay first, claim, and get reimbursed against approved milestones. There is real working-capital exposure in the gap between paying salaries and receiving the contribution payment.

Eligibility — who actually qualifies

The published bar to apply is straightforward. The bar to get funded is considerably higher and is decided by your ITA, not by a checklist. Start with the binary eligibility criteria:

• Incorporated, for-profit business based in Canada
• Small or medium-sized: 1 to 499 full-time equivalent employees
• Capacity to execute a technology-driven innovation project with a clear commercial outcome
• Financial capacity to carry your share of the project (the matching cash contribution)
• Willingness to enter a contribution agreement and report against milestones

Beyond that, the ITA assesses fit on softer dimensions that are real even though they don't appear on any application form. The most consistent of these:

• Technical ambition. The project must genuinely advance the state of your technology or process. "Building a better website" or "automating an existing manual process with off-the-shelf tools" generally does not clear the bar. The closer the work is to actual R&D — resolving a technical uncertainty that a competent professional could not resolve from existing knowledge — the stronger the fit.
• Commercial pathway. The ITA wants to see a credible route from the technical work to revenue: identified customers, channel strategy, IP position, market sizing. IRAP is not a research grant; it is a commercialization accelerant.
• Team capacity. A founder-and-an-intern team rarely gets approved for a $500K project. The ITA looks at the technical depth of the people who will actually do the work — engineering background, prior shipping experience, advanced degrees where the science demands it.
• Canadian benefit. Where does the IP sit? Where do the high-value jobs sit? Where does revenue flow back to? Projects where the technical work happens in Canada but the company is a foreign-controlled shell selling exclusively offshore are harder to fund.
• Financial health. The ITA will ask for financials. A business burning cash with no clear path to closing its share of the project budget is a financial-risk decline waiting to happen.

The ITA relationship — and why it matters more than the form

IRAP is unusual among federal funding programs because there is no general open-application portal where you upload a deck and wait. The program runs through a network of Industrial Technology Advisors — experienced industry professionals, frequently engineers or scientists with significant private-sector backgrounds, assigned regionally. The ITA is the person who decides whether your project is worth bringing forward, what size of contribution is appropriate, and how the file is positioned to the regional committee that issues the final approval.

For a first-time applicant, the practical sequence is:

1. Contact NRC IRAP through the regional intake (the program lists contact options on its site, including a 1-877 number and a self-serve initial questionnaire).
2. An ITA is assigned based on your region and the technical domain of your business.
3. You meet with the ITA — usually a video or in-person introduction — to discuss the business, the technology, and the project you want funded.
4. The ITA decides whether to formally engage. If yes, they will guide you through the project description and budget shaping that becomes the application.
5. If no, you receive a soft decline at this stage — no formal application gets submitted. This is the most common decline point and it does not appear in any approval statistic.

The implication is significant: the ITA is effectively a co-author of your application. They shape what gets submitted because they know what the regional committee will fund. A strong ITA relationship can take a borderline project across the line; a weak fit between your business and the assigned ITA's technical comfort zone can stall a strong project. Founders who go in cold, send a one-shot email describing their business, and wait for a reply often hear nothing — not because IRAP has rejected them but because the engagement never converted to an active file.

Application flow and timelines

Once the ITA has decided your project is worth bringing forward, the formal flow looks roughly like this. Timelines vary considerably by region, project size, and time of year (year-end and early Q1 are slower), but the structure is consistent.

Founders should plan around three to six months from first contact to a signed contribution agreement, with the spread driven primarily by how complete the technical and financial narrative is at the start and how much back-and-forth the ITA needs to get comfortable. Time-sensitive projects with a hard external deadline (a customer-funded pilot, a tender response) often don't fit IRAP's cadence and end up using SR&ED or a faster grant instead.

Common reasons projects get declined

Beyond the obvious eligibility issues, IRAP declines tend to cluster around a small number of recurring problems. The four most common we see in practice:

• Insufficient technical novelty. The work described is integration of off-the-shelf components, configuration of existing platforms, or routine engineering. There is no real uncertainty that requires experimentation. This is the same bar as SR&ED's "scientific or technological uncertainty" requirement — if a competent professional in your field could resolve the problem from existing public knowledge, the project doesn't qualify.
• Weak commercial narrative. The technical work is interesting, but the path from prototype to revenue is hand-waved. Without identified customers, a credible market, or a defensible IP position, the ITA cannot tell the regional committee why the contribution will return Canadian economic benefit.
• Team capacity gap. The project requires deep expertise that the company doesn't have on staff and isn't credibly bringing in through hires or subcontractors. ITAs will not fund projects whose execution risk is dominated by team gaps.
• Cash-flow risk. The business cannot demonstrate it can carry its 20–40% share of the project budget through to reimbursement. Even strong technical projects get held until the company can show evidence of matching capital, whether through revenue, a closed equity round, or a committed credit facility.

Less frequently but still meaningfully, projects get declined or right-sized because the proposed scope is too broad ("we'll build the entire product over 18 months"), too narrow ("we'll do this two-week experiment"), or insufficiently linked to a single coherent technical objective. A clean IRAP project description tells one story: here is the technical thing that is uncertain, here is how we will resolve it, here is what we will have built when we are done, here is how it leads to revenue.

There is also a quieter category of declines that founders rarely see acknowledged in writing: strategic fit with the ITA's portfolio. ITAs manage a book of business across many companies, and they balance their portfolio across stages, sectors, and risk profiles. A technically strong project from a sector the ITA is already heavily exposed to, or from a stage they are deliberately under-weight in, can lose to a comparable file that fills a gap in the ITA's book. This is not a written rule and is not a reason a founder will ever be given for a decline — but it is real, and it is one of the reasons treating the ITA as a partner rather than a transactional reviewer materially changes outcomes.

Stacking IRAP with SR&ED

This is the question we get most often from founders who already know both programs by name: can I claim SR&ED on the work IRAP is funding? The short answer is yes, with rules. The long answer is that IRAP and SR&ED are designed to work together and stacking them properly is one of the highest-leverage things a Canadian R&D business can do.

The interaction rule that matters: any costs reimbursed by IRAP must be subtracted from your SR&ED expenditure pool before computing the SR&ED tax credit. You cannot get federal funding twice on the same dollar. On a $1,000,000 labour project with $700,000 of IRAP contribution and $300,000 of company-funded labour, only the $300,000 company-funded portion forms the basis for the SR&ED claim. That $300,000, at a CCPC's 35% refundable federal rate plus the applicable provincial rate, still produces a meaningful credit on top of the IRAP contribution.

The net effect, well-structured, is that a Canadian SME can have a substantial majority of its eligible R&D labour cost covered by the federal government through the combination — IRAP on the company's share of qualifying work, SR&ED on the remainder. Whether that is 80%, 85%, or higher depends on province, project mix, and how cleanly the cost separation is tracked. Two practical points:

• Track IRAP-funded hours and SR&ED-claimed hours separately from day one. Doing this retroactively at tax-filing time is where errors creep in and where CRA reviewers focus during SR&ED audits.
• The S/THERI structure of your SR&ED technical narrative (Scientific/Technological uncertainties, Hypotheses, Experimentation, Results, Iteration) should align with the milestone structure you negotiated with your ITA. The same project, told two ways, for two purposes — but the underlying technical story has to be coherent.

One more wrinkle worth flagging: the timing mismatch between the two programs. IRAP reimburses against monthly or quarterly claims during the project; SR&ED is filed once a year with the corporate tax return and refunded several months after that. From a cash-flow perspective, IRAP is the program that gets you money during the build, and SR&ED is the program that closes the gap on the company's matching share after the year ends. Modelling both into your cash forecast at the start of the project — not at the end — is the difference between using the programs as designed and discovering you over-extended your working capital halfway through.

What the Canada Innovation Corporation transition means

The federal government has announced that NRC IRAP will be folded into the new Canada Innovation Corporation (CIC) as the centrepiece of Canada's industrial R&D support architecture. The intent, as set out in the supporting policy documents, is to consolidate fragmented federal innovation funding into a single, mission-driven Crown corporation with greater scale, greater speed, and stronger commercialization focus. The transition is in progress through 2026–27, and it will materially affect how IRAP is delivered going forward.

What this means for applicants in the near term:

• Existing contribution agreements continue as written. Projects already approved and under agreement are honoured through to completion under their existing terms. There is no clawback or re-papering of active files.
• The ITA network is being preserved. The expertise and regional presence of Industrial Technology Advisors is one of IRAP's most-cited strengths, and the policy intent is to carry this model into the CIC rather than dismantle it.
• Program parameters may shift. Cost-share rates, eligibility thresholds, and project sizing are subject to change as the CIC publishes its own program rules. Where IRAP today is somewhat conservative on what it funds, the CIC is signalled to be more ambitious on scaling Canadian-owned IP and supporting larger commercialization plays.
• New applications in 2026 are still being processed under the IRAP framework until the CIC's program rules formally take effect. If you have a project that is ready, there is no benefit to waiting for the transition — the safest path is to get into a contribution agreement now under known terms.

For founders evaluating the program for the first time in 2026, the practical advice is the same as it was a year ago: engage an ITA, shape a project, and get to a signed agreement. The contribution model, the ITA-led process, and the cost-share economics are the parts of IRAP that have proven most durable, and they are the parts the CIC explicitly intends to preserve. The risk of waiting for "more clarity" is that you spend a year not getting funded.

Final thoughts

NRC IRAP rewards companies that understand what the program is actually for. It is not a startup grant program, it is not a way to fund operations through a slow quarter, and it is not a substitute for raising capital. It is a contribution toward the cost of a real, well-scoped technical project, delivered through a relationship with an experienced advisor who functions as both a partner and a gatekeeper. Founders who treat it that way — who invest in the ITA relationship, who shape the project description carefully, who track costs cleanly, and who pair it with a properly structured SR&ED claim — routinely capture a level of non-dilutive support that materially changes their company's R&D economics.

Founders who treat IRAP as a one-shot application to be fired off in a weekend and forgotten about generally hear nothing back, conclude the program "isn't for them," and move on. It would be more accurate to say they never actually engaged with the program in the way it was designed to be engaged with.

The CIC transition will refine the delivery model but is not changing the fundamental contract: Canadian SMEs that build credible technical projects, in partnership with their ITA, with the financial capacity to carry their share, get funded. That is true today and is intended to remain true under the CIC.

IRAP is one of several Canadian innovation funding programs — SR&ED, Scale AI, FedDev, the provincial streams, and regional development agencies all play roles depending on stage and sector. Use our Grant Finder to compare IRAP against SR&ED, Scale AI, and the federal grants we cover before committing a quarter to applications.