NRC IRAP for Manufacturers: What Qualifies and What Doesn't (2026)

If you run a Canadian manufacturer and you have heard of NRC IRAP, you have probably heard it described as a grant for tech companies. That description costs manufacturers money every year, because IRAP's actual clientele includes machine builders, processors, and fabricators doing technical development they never thought to call R&D. This post is the plain-language version: what IRAP is, what qualifies at a manufacturer, what does not, and one cross-border catch we disclose up front because it affects working with a firm like ours.

A dating note, because funding content rots fast: checked September 2026, and the current state of every open Canadian program lives in our companion guide, updated monthly.

What NRC IRAP is and how it works

IRAP is a non-repayable contribution program run by the National Research Council for incorporated, for-profit Canadian companies with 500 or fewer employees. It is not a portal where you file a form and wait. Your first step is a phone call (1-877-994-4727), after which you are assigned an Industrial Technology Advisor, an ITA, part of a network application guides count at roughly 275 advisors across the country, who works with you to shape the project before any application exists. Contributions are commonly reported at up to 80% of eligible technical salaries and up to 50% of eligible subcontractor costs, with first-time projects typically landing between $75,000 and $200,000. Treat those percentages as reported practice rather than published policy: NRC itself does not publish cost-share rates, and your ITA sets the terms for your project. Two rules are firm everywhere: costs incurred before the contribution agreement is signed are not eligible, and IRAP stacks with SR&ED tax credits, which is where the arithmetic gets genuinely attractive.

IRAP eligibility for manufacturers: the bar everyone misreads

IRAP eligibility turns on one test above all: genuine technological uncertainty, meaning the outcome cannot be achieved with standard engineering or existing knowledge. This is where most advice goes vague, so here is the concrete version for the projects we see on manufacturing front offices.

Plausibly qualifies: building a system that learns from your own quoting and job history to draft estimates, because retrieval and drafting tuned on your specific engineering data is development work with real uncertainty about achievable accuracy. The same logic covers proposal-drafting systems built on a machine builder's project history, like a machine builder's proposal workflow, fully costed, and process-data work where models must learn your presses' behavior before anyone knows what they will find.

Does not qualify: routine automation. Connecting your inbox to your ERP, standard chatbot deployment, off-the-shelf software configuration. That work can still pay for itself many times over, and builds we deliver at fixed price are usually exactly this shape, but it is ordinary engineering, and calling it R&D to an ITA wastes everyone's time. Fund it from the savings it produces, not from IRAP.

The dividing line is honest self-assessment of where the uncertainty lives, and the strongest thing you can bring to a first ITA conversation is documentation of the technical problem in measurable terms. That documentation is, not coincidentally, what the audit that produces that documentation exists to create: the measured baseline, the technical gap, the uncertainty stated plainly.

The cross-border catch, disclosed because it applies to us

Reported IRAP practice leans toward Canadian subcontractors for the subcontractor share, and published application guidance states it more bluntly: work outsourced to foreign contractors is not eligible. We are an American firm. So here is the straight version of what that means if you work with us: do not build a plan that assumes IRAP reimburses our invoices. The robust structure is the one IRAP prefers anyway: your own technical staff do the funded development work, IRAP cost-shares their salaries, and external help sits where it belongs, in scoping, architecture, and the measured business case, funded by the project's own returns. Raise the specifics with your ITA before signing anything; program practice is theirs to state, not ours. We would rather tell you this in a blog post than have you discover it in a contribution agreement.

How to apply for IRAP: the process, compressed

Call. Talk to the ITA about the technical problem, not the shopping list. If the fit is real, the ITA helps shape a proposal, NRC issues a contribution agreement, and you claim eligible costs against milestones as the work runs. Nothing spent before signature counts, so the sequence matters: measurement and scoping first, agreement second, build third.

Frequently asked questions

Does an AI project at a manufacturer qualify for IRAP?

Sometimes. The test is technological uncertainty, not the word AI. A system that must learn from your specific data to reach an unproven accuracy target can qualify; installing configured software cannot. Your ITA makes the call, and measurable documentation of the technical gap is what makes that conversation short.

Can IRAP pay for an American consultant?

Plan as if no. Reported practice leans toward Canadian subcontractors, and the cleanest structure funds your internal technical staff while external firms handle scoping and architecture outside the contribution. Confirm specifics with your ITA.

Is IRAP a grant or a loan?

Neither word is exact: IRAP provides non-repayable contributions. You do not pay the money back, but unlike a lump-sum grant it reimburses eligible costs against milestones after a contribution agreement is signed, and it never covers 100% of a project.

How long does IRAP take?

The advisor conversation can start this week; a contribution agreement typically takes weeks to a few months depending on project shape and timing in the fiscal year. The practical implication: start the ITA relationship before you need the money, and never start spending before the agreement is signed.