Whether to prepare an SR&ED claim in house or hire a consultant is a question of net return, not of pride. Here is what each route really involves, where do-it-yourself claims fall short, and how to decide.
Preparing your SR&ED claim internally means your team handles everything. You identify eligible projects, gather documentation, write technical narratives, allocate costs, and submit the claim yourself. Concretely, that is Form T661, Schedule T2SCH31 for the credit, the technical narratives and the cost allocation.
For some companies, this works. If your claim is small, your R&D work is straightforward, and you have someone who genuinely understands CRA requirements, you might capture most of what you’re owed.
But here’s what I’ve seen over and over: most businesses only include the obvious R&D. They miss partial eligibility on development time. They exclude supporting roles. And in my experience they end up with a claim that is materially smaller than it should be.
The single biggest do-it-yourself error is conflating novelty with uncertainty. Founders argue that they built something new, when the programme asks whether they faced a technological uncertainty and investigated it systematically. Those are different claims, and CRA reviewers are trained to catch the difference. A product can be brand new and still be routine engineering, and an unremarkable product can rest on work that resolved a genuine technological uncertainty.
So the CRA isn’t looking for a description of what you built. They want to know what was uncertain. What did you not know at the start? What experiments or analysis did you run to find out? Most internal teams describe their work like a product update log: "Improved system performance." That’s not going to fly. A claim-ready narrative sounds more like: "Several architectures were tested because standard methods failed under the specific load constraints." That gap between description and demonstration is where refunds disappear. The CRA’s project description guidance asks three questions per project, on lines 242, 244 and 246 of Form T661: what uncertainty you faced, what work you did to resolve it, and what advancement you achieved.
Another common problem: reconstructed documentation. The CRA wants contemporaneous evidence. Project logs, testing results, meeting minutes, commit histories, failed prototypes. Anything that shows your systematic investigation as it happened, and who did the work, and when. If you’re piecing together your evidence after the fact rather than capturing it throughout the year, the CRA will notice. According to their review process guidelines, documents created when the work was being carried out are the most valuable supporting evidence. If your records only exist in the heads of your developers, you have a problem. If your documentation was rebuilt months after the work ended, you have a bigger problem.
In-house preparation does have real benefits. You keep 100% of your refund. No consultant takes a cut. For a company operating on tight margins, that matters.
You also build internal knowledge. When your team understands SR&ED eligibility requirements, they’re more likely to identify qualifying projects throughout the year. They document better. They think about innovation differently.
And there’s integration. An internal team knows your systems, your people, your R&D cadence. They don’t need a kickoff meeting to understand your business. They’re already inside it.
If your claim exceeds $50,000, you’re filing for the first time, your technical work is complex, or your documentation is scattered, a consultant isn’t a luxury. It’s risk management.
A good SR&ED consultant does more than fill out forms. They find projects your team missed. They translate your engineering work into CRA-compliant narratives. They structure your cost allocation so every eligible dollar gets claimed. And when the CRA comes knocking for a review, they’re standing beside you with documentation that holds up under scrutiny.
The check before filing is often where the value sits. One cleantech robotics startup drafted its first claim as a pitch for a new product; reframed around the specific uncertainties the team had worked through, the $70,000 first claim was accepted without a review. It is one of eleven engagements in these SR&ED case studies.
Most consultants charge on contingency. They take a percentage of your refund, typically between 10% and 25%. The larger your claim, the more you pay. A smaller group charges a flat fee, fixed in advance, so a larger refund does not mean a larger bill. Over several years the two models can cost very different amounts for the same filing work, so compare the lifetime cost of each before you commit.
But the real question isn’t what you pay. It’s what you keep.
Consider this scenario: a company files DIY and claims $180,000. After the CRA review, they’re approved for $130,000. The next year, they work with a consultant who identifies $260,000 in eligible work and gets $240,000 approved. Even after a 15% fee, they net $204,000. That’s $74,000 more than they kept doing it themselves.
DIY claims get reviewed more often. Not because the CRA targets self-filers, but because the claims tend to have gaps. Weak technical narratives. Missing cost documentation. Unclear project boundaries. A first-time filer also has no track record with the CRA, so the technical report carries all the weight, and a product-shaped narrative draws exactly the questions a reviewer then has to ask.
When a review happens, DIY claimants often lose ground. The refund they expected shrinks during the back-and-forth. They didn’t build their claim to withstand scrutiny, so it doesn’t.
Consultant-prepared claims are structured for this reality from day one. The documentation is organized. The narratives are tight. The cost allocation is defensible. When the CRA asks questions, there are clear answers.
Before you decide, start with the math: your expected claim size, what a contingency consultant would take, and what a flat fee would cost instead. Then look at capacity: does your team have time to learn SR&ED requirements, can they take weeks away from core R&D to prepare the claim, and will they still be around next year to handle the audit that might come 18 months later? Finally, assess your risk tolerance: a CRA review isn’t the end of the world, but if your claim gets reduced by 30%, can your business absorb that? If you still choose to file in house, check the draft against this list before you submit.
The in-house versus consultant question doesn’t have one right answer. It depends on your claim size, your team’s capacity, your risk tolerance, and your documentation practices.
Small, straightforward claims from teams with SR&ED experience? In-house might work. Complex technical projects, first-time filers, or anyone who wants to maximize their refund and sleep well during audit season? That’s where a consultant earns their fee.
The program is there. The credits are there. The question is whether you’re capturing everything you’re owed. If you want a second opinion on a draft before you file, book a free consultation; our pricing is on the site if you want to compare. The CRA’s SR&ED program page is the official source for the rules.
Related reading: the common SR&ED claim mistakes that cost refunds, how software development qualifies for SR&ED in Canada, and 8 SR&ED consultant facts first-time claimants should know.
Approval turns on the claim, not on who prepared it. A claim that shows a real uncertainty, a systematic investigation and records kept as the work happened is approved whoever wrote it. Where the two routes differ is in the size of the claim and in how well it stands up when a reviewer asks questions.
The deadline is the same whoever prepares the claim. A corporation has 18 months after its fiscal year-end to file, and it is a firm deadline: miss it and the claim is gone. A December 31, 2025 year-end therefore files by June 30, 2027. Calendar the date the day the year ends.
You can, but it’s risky. A review asks you to explain your technological uncertainty, systematic investigation and cost allocation in detail, and the CRA’s service standard for a claim selected for review is 180 days from a complete claim. If the people who did the work and kept the records are available to answer, you can defend it yourself.
Yes. Eligibility rests on whether you set out to resolve a technological uncertainty through systematic investigation, not on whether you succeeded. A failed approach is often the strongest evidence that the uncertainty was real, so keep the notes on what you tried, what happened, and why you moved on.
The CRA’s service standard for a refundable claim accepted as filed is 60 calendar days from a complete claim. A claim selected for review takes longer, which is one reason a narrative that answers the reviewer’s questions up front matters as much for cash flow as for the credit itself.
The clearest signal is a claim the CRA reduced during a review, because the shortfall usually came from framing or records, and the same pattern repeats the next year. Growth past roughly $50,000 in expected refund, a first filing, or R&D that now spans several teams are the other common triggers.
This article is general information, not tax advice. Tax figures depend on your corporation type, province, and taxation year.
Do you have a SRED question? Planning for the future or perhaps you want to know how much your claim might be? Don’t worry, our CPA is always ready to answer any question. Get a SRED expert in your corner.
Have a question? We’d love to help. If you don’t have a SR&ED expert in your corner, doesn’t it make sense to have one?
