IRAP proposal support

The hard part isn't the money. It's proving the uncertainty.

NRC IRAP funds the resolution of genuine technical risk — not the building of software. Most proposals describe a product roadmap and then wonder why the ITA goes quiet. We write the version that survives the technical read.

Start with an assessment See how it works
What actually gets funded

An ITA is looking for risk you might not retire

The gap between a proposal that gets funded and one that doesn't is rarely effort. It's whether a reader can find the technical uncertainty — and whether there's evidence you'd know if you had resolved it.

01

Business outcome first, uncertainty underneath

Every objective reads if we resolve this, then this business result follows, because this is the bottleneck today. Not a feature list with a budget attached.

02

Numbers, not adjectives

Baselines and targets for both the business KPI and the technical sub-targets — precision, recall, F1, cost per workflow. The sub-targets are the evidence the risk was retired.

03

Proof you can execute

A structured engineering process overview — lifecycle, review controls, testing, traceability — so the ITA isn't being asked to bet on hope.

04

Language that reads as R&D

Routine integration, CRUD and interface work isn't fundable. Dressing it up as research is how credibility gets spent, and it's a hard thing to earn back.

How it works

Two stages, and you can stop after the first

Stage one

Readiness assessment

One week. We look at what you're building and answer one question honestly: is there real technical uncertainty in here, and where? You get a written fit memo naming which parts of the work are fundable, which aren't, and what would need to be true to change that.

If the answer is no, you've spent a small fee instead of three months.

From $2K CAD credited in full against stage two
Stage two

Proposal build

  • Business objectives in if / then / because form, with full metric tables
  • Technical challenge write-ups against each objective
  • Engineering process overview — requirements, design and security review, development practice, testing, release
  • Support through your ITA conversations and revision rounds
Three to four weeks scoped after the assessment
What we don't do
  • We're not grant writers taking a percentage of your award.
  • We don't submit on your behalf or promise approval — that's the ITA's call, and nobody should tell you otherwise.
  • We won't help you frame routine development as research. It doesn't work, and it costs you the relationship.
Who this is for

Canadian CCPCs with a real R&D program and an engineering team already in place. Best if you've started an ITA conversation — or you're ready to.

Worth knowing: IRAP funding reduces your SR&ED base — the same salary dollar can't be claimed twice. We'll flag the interaction while scoping so the two aren't working against each other.

Not sure whether you're fundable?

That's the assessment. One week, a written answer, and no obligation to go further.

Start a conversation