My Kitchen Table Awakening in Leslieville
It was a freezing February night in my Leslieville kitchen, and I was nursing a cold pint from one of the local breweries-I think it was a Radical Road pale ale-when I realized something that would change how I thought about my side project. Outside my window, the streetcar rumbled past, and I could hear the muffled honking of cars crawling along the Gardiner Expressway in the distance, that familiar Toronto winter soundtrack of impatience and cold.
I was staring at my laptop, trying to make two incompatible APIs talk to each other for a custom inventory system I’d been building. For three weeks, I’d been hitting my head against this problem: System A wanted JSON, System B only spoke XML, and neither one of them came with any documentation about bridging the gap. I’d written and rewritten the integration code maybe fifteen times, tested it on fake data, scratched my head, walked away, came back with a fresh cup of coffee, and started over again.
Then something clicked. All this failing, all this systematic trial-and-error, all this real scientific uncertainty-it wasn’t just frustration. It sounded almost exactly like what I’d skimmed in a tax document someone had forwarded me months ago about something called SR&ED.
My Research Method: Sifting Through the CRA Jargon
The next Saturday morning, I sat at my kitchen table with a stack of printed pages from Canada.ca, a yellow highlighter, and my second coffee of the day. The CRA’s guidelines are dense, full of accountant-speak and circular definitions that seem designed to confuse regular people like me. I highlighted sections about “scientific uncertainty” and “systematic investigation,” but I’ll be honest-I didn’t fully understand half of it.
So I did what any sensible person would do: I called my buddy Dave, who runs a metal fabrication shop in Etobicoke near the industrial corridor. Dave’s been running his business for eight years, and I figured if anyone understood how a real, non-accountant business owner actually survives a CRA interaction, it was him. Over a couple of coffees at a Tim Hortons in his neighborhood, Dave walked me through his own experience: he’d claimed capital equipment purchases for his precision machinery, he’d documented his work carefully, and he’d decided pretty quickly that hiring a professional was worth the cost.
That conversation was more valuable to me than any of the dry PDFs. Dave made it clear that the CRA takes this stuff seriously, which meant I needed to take it seriously too-not in a scary way, but in a “get your documentation right” kind of way.
What I Learned: My Core Takeaways on SR&ED
After my kitchen table research and my chat with Dave, a few key truths about SR&ED became crystal clear to me:
- Failure is Rewarded, Not Penalized: The entire system is built on the idea that if you tried something hard and failed systematically, that’s still R&D. The government isn’t asking “Did you succeed?” They’re asking “Did you struggle with real uncertainty and document your process?” My three weeks of API failures absolutely qualified.
- Provincial Stacking is Real Money: Canada didn’t stop at federal credits. Ontario layered on the Ontario Innovation Tax Credit (OITC), which stacks right on top of the federal program. Most people I talked to had no idea this existed, which meant they were leaving cash on the table.
- Documentation is Non-Negotiable: The CRA doesn’t care if your story is convincing. They care about contemporaneous notes-stuff you wrote down at the time, not stuff you reconstruct in November when you’re filing your taxes. This is where most people trip up.
- Massive Changes are Landing in 2026: And this was the thing that really grabbed my attention. The rules are shifting significantly at the end of 2024 and into 2025, and if I was going to take this seriously, 2026 was going to be the year to really pay close attention.
The Big 2026 Changes That Caught My Eye
When I first started reading about the changes coming in 2026, it felt like the government was suddenly making this whole SR&ED thing more accessible. I remember thinking, “Wait, why are they loosening these rules? Are they trying to help us?” The answer, I learned, is that Canada’s trying to keep tech talent and R&D talent from fleeing to the US, so they’re sweetening the pot for companies that invest in innovation.
The timing is wild when you think about it. Toronto’s tech community has been growing like crazy-Liberty Village is packed with startups, Scarborough has small manufacturing shops that have been struggling, and the GTA overall is becoming more competitive for talent. If the government wanted to help that ecosystem thrive, adjusting the SR&ED rules was a smart move.
I found myself staring at Canada.ca more carefully, printing out more sections of the technical guidelines, and trying to understand what these 2026 changes would actually mean for someone like me.
Doubling Down: The New $6 Million Limit
Here’s the headline change that got my attention: the expenditure limit for the enhanced 35% refundable tax credit rate is effectively doubling from $3 million to $6 million of taxable capital, starting in tax years ending after December 2024. If you’re a growing software team crammed into a brick-and-beam office in Liberty Village, this is huge.
What this means in practical terms: if your company’s eligible R&D spending is under $3 million annually, you’ve been getting that sweet 35% refundable rate all along. But many companies hit that ceiling and then the rate drops. Starting in 2026, that ceiling doubles. So a team of eight or ten developers spending $5 million on salaries and related R&D costs now gets the full 35% treatment across the board.
I did the math in my head: if a software company in Toronto has ten developers at an average loaded cost of $120,000 each (salary plus benefits plus equipment), that’s $1.2 million right there, plus project management overhead, infrastructure, tools subscriptions-suddenly you’re looking at $2 million or more of eligible spending. Under the old rules, half of that might have hit a lower rate. Under the 2026 rules, it all stays at 35%.
For growing tech shops in Toronto, this is basically a raise from the government.
Hardware is Back: What It Means for Local Shops
The other change that made me sit up and take notice: capital expenditures are coming back. For the last few years, the CRA had been excluding machinery, hardware, and equipment from SR&ED claims. I’m talking about the physical tools you buy-servers, testing rigs, specialized hardware, 3D printers, precision equipment for manufacturing.
Then someone in Ottawa apparently realized, “Hey, these are actually crucial inputs to R&D,” and the rules shifted. Starting in the 2025 and 2026 tax years, capital expenditures used specifically for R&D are eligible again.
I thought immediately of the small fabrication shops scattered around Scarborough-you know, the ones you drive past near Warden Avenue or Kennedy Road, the metal shops and precision tooling places that have been around for decades. Those businesses often need to invest in new CNC machines or testing equipment to stay competitive and to develop new capabilities. Suddenly, those capital costs are eligible again. A $150,000 precision lathe that lets a shop develop a new manufacturing process? That’s now part of the claim.
Dave actually texted me about this when I sent him the news. He said his shop had been sitting on a equipment upgrade for exactly this reason-waiting to see if the rules would change. Now he’s seriously looking at it again, knowing the investment can be leveraged through SR&ED.
The Ontario Stacking Advantage: My Napkin Math
Quick disclaimer before I go further: I’m just a regular guy writing this from my porch in Leslieville, nursing a local craft beer. I’m not a CPA, I’m not a tax lawyer, and I’m definitely not giving you professional tax advice. Everything I’m about to share is based on my own research and conversations, and anyone actually filing a claim should talk to a certified professional before submitting anything to the CRA. Got it? Good. Now, back to the napkin math.
One of the coolest discoveries I made during my research was that Ontario doesn’t just have the federal SR&ED credit. They also have the Ontario Innovation Tax Credit (OITC), which is an additional 8% refundable credit that stacks right on top of the federal program. This is money on money.
Let me walk through a simple example that really made the lightbulb go off for me. Say you’re a software developer in Toronto, and your salary and benefits total $100,000 for the year. That entire amount is eligible for SR&ED if the work you did qualifies (which I’ll explain below). Here’s how the math works:
- Federal credit at 35%: $100,000 × 0.35 = $35,000
- Ontario Innovation Tax Credit at 8%: $100,000 × 0.08 = $8,000
- Combined gross credit: $43,000
But here’s where it gets tricky-and this is where the real-world recovery rate drops. The Ontario credits actually reduce your federal credit pool in a way that’s mathematically complex. After you account for provincial tax rates and federal reductions, the net cash you actually recover is typically between 60% and 70% of your eligible salary. So instead of the full $43,000, you might end up with $60,000 to $65,000 in actual cash back.
That’s still a 60% to 65% recovery on $100,000 in spending. If you’re a team of five developers at $100,000 each, that’s $500,000 in eligible spending and potentially $300,000 to $325,000 in net cash back. That’s real money that goes back into the business or into your pocket.
When I first did this calculation on a napkin at my kitchen table, I actually said out loud, “Wait, is this legal?” It felt too good to be true. Then I realized: yes, it’s not just legal, it’s intentionally designed this way. The government wants you to know about this and use it.
Do I Actually Qualify? The Five Questions I Had to Answer
All of this was exciting, but I kept coming back to the same question: did my three-week struggle with incompatible APIs actually count as R&D? To answer that, I had to work through the five questions that Canadian courts and the CRA use to define SR&ED. These questions come from actual legal precedents, not just bureaucratic whim, which made me take them seriously.
Question 1: Was there scientific or technological uncertainty? I asked myself: could a standard expert developer solve this problem instantly? The answer was no. There was no Stack Overflow post that said, “Here’s how to bridge System A and System B.” That was my uncertainty-real, documented, and specific.
Question 2: Did I formulate hypotheses specifically aimed at reducing that uncertainty? Yes, absolutely. I hypothesized that if I built a middleware layer that could translate JSON to XML on the fly, maybe the two systems could communicate. I hypothesized that maybe I could use a third-party library to handle the conversion. I hypothesized that maybe I was overthinking it. Each hypothesis was an attempt to solve the problem.
Question 3: Was my approach consistent with systematic investigation? This is where the documentation matters. I didn’t just randomly hack at the code. I tested each hypothesis, kept notes about what worked and what didn’t, and moved methodically through the process. That’s systematic investigation.
Question 4: Was I doing this to achieve technological advancement? Here’s the beautiful part: it doesn’t matter if I succeeded or failed. It doesn’t even matter if I was trying to make something revolutionary. I was trying to gain new knowledge about how to solve a specific technical problem, which counts as advancement. And honestly, even though my side project might never become a billion-dollar business, figuring out how to bridge those APIs was new knowledge for me and for my code base.
Question 5: Did I actually keep records? This is where I had to be honest with myself. I had git commit messages, I had a folder of notes, and I had screenshots of errors and test outputs. Not perfect documentation, but contemporaneous-created at the time, not reconstructed later. The CRA would accept this.
Walking through these five questions, I realized I actually qualified. It felt almost anticlimactic, but also empowering. I wasn’t claiming something dodgy; I was claiming something that legitimately fit the definition.
The Boring Battle with Documentation
If there’s one thing that almost stopped me from pursuing this whole SR&ED thing, it was the word “documentation.” I hate administrative work. I really do. Give me a coding problem to solve, and I’m happy for eight hours straight. Ask me to organize receipts and timesheets, and I want to cry.
But here’s the thing I learned: “contemporaneous documentation” is just a fancy tax word for “don’t wait until November to remember what you did.” It means writing things down at the time you’re doing the work, not months later when you’re scrambling to justify your claim.
The CRA doesn’t need a leather-bound journal with perfectly written summaries. They need evidence that you were thinking through the problem as you worked. That could be git commit messages, timestamped screenshots, email threads where you describe a problem you’re stuck on, notes in a shared document, or even scribbles on a notepad with a date on them. The key word is contemporaneous-created at the moment, not reconstructed afterward.
I remember reading one CRA guideline that actually said something like, “A disorganized pile of notes is better than an organized pile of notes written after the fact.” That made me feel a lot better about my chaotic approach to documentation.
My Simple DIY Tip for Stress-Free Tracking
Here’s the practical hack I came up with to solve the documentation problem without going insane: set a recurring Friday afternoon calendar alert. Every Friday at 3 PM, I get a notification. I spend five minutes dumping everything related to my project work into a dedicated folder. Screenshots of error messages, a link to a git commit log, a sentence or two about what I was trying to solve that week, anything relevant.
I use a simple Google Drive folder, but it could be Dropbox, OneDrive, or just a folder on your desktop. The point is that it takes five minutes, it’s done when the work is fresh in your mind, and by the end of the year, you’ve got a solid trail of evidence that you were actually doing R&D work.
This also solved a second problem for me: when I eventually do file a claim, I won’t be scrambling through a year’s worth of chaotic notes trying to reconstruct timelines. Everything is already organized by week. It’s boring, but it’s the kind of boring that makes the CRA happy-and more importantly, makes the process way less stressful for me when the deadline approaches.
My Search for Help: Sidestepping the High-Pressure Sales Mills
After I understood the basics of SR&ED and realized I probably qualified, I started thinking about whether I should actually file a claim. That’s when I started Googling “sr&ed toronto” and “r&d tax credits near me,” and oh man, did the sales calls start coming in fast.
I got contacted by firms that promised to “unlock thousands in tax savings” (their words, not mine). They wanted to charge me 25%, 30%, even 35% commissions on whatever refund I claimed. These are the places I started to think of as the “high-pressure sales mills”-slick office spaces downtown, aggressive cold-calling, big promises, zero technical understanding of what they were actually filing on my behalf.
One firm even tried to convince me that I could claim retrospectively for the past five years of work I’d done, which immediately raised a red flag. The CRA has rules about filing deadlines, and if something sounds too good to be true, it probably is.
What I really wanted was someone who actually understood the technology. Someone who could sit down and talk about APIs and integration challenges without making my eyes glaze over. Someone who understood not just the tax code, but the actual engineering work.
Dave actually had a recommendation from his own experience. He said if I ever decided to hire help, I should look for firms that have engineers or software architects on staff, not just accountants and sales reps. Those firms tend to be smaller, they charge more reasonable fees (usually 15% to 20% instead of 30%+), and they actually understand what you’re talking about.
For now, though, I’m going the DIY route. I figure I have enough documentation and I’ve done enough research that I can at least file a first claim myself. If it gets complicated or if the CRA comes back with questions, that’s when I’ll bring in the professionals.
Beyond the Credit: How I Look at the Bigger Picture
As I got deeper into understanding SR&ED, I started thinking about the bigger picture of how this all fits into my financial life. The tax credit itself is great, but it’s not the whole story.
I started exploring something called the Proxy Method for calculating overhead. Basically, if you’re a software developer doing SR&ED work, you can claim a percentage of your overhead costs-rent, utilities, administrative salary, tools subscriptions-using a formula instead of trying to allocate every single expense. For software companies, the Proxy Method often results in a higher claim than the traditional method, and it’s way less administratively painful.
I also started thinking about what I’d do with the refund once I received it. That’s where my personal interest in TFSA strategies came in. If I get a $20,000 refund from an SR&ED claim, my immediate thought is: “Can I funnel this into my TFSA?” Any money I put into my TFSA grows tax-free forever. It’s like a second layer of tax shelter on top of the tax credit itself. Over time, that compounds into real wealth protection.
This is where SR&ED started to feel like more than just a one-time refund. It became part of a larger financial strategy: earn income from my side business, claim R&D credits on the work, take the refund, shelter it in my TFSA, and let it grow tax-free. It’s a personal financial journey, not just a tax form.
Max’s DIY Checklist Before Submitting Anything
Before I even think about submitting a claim to the CRA, I made a checklist for myself. I figure if anyone reading this is thinking about the DIY approach, this might help you avoid the mistakes I almost made:
- Verify Contractor Residency: Canadian-based contractors or subcontractors can be claimed at 80% of their cost. Foreign contractors (like developers in India or outsourced work from overseas) are 0% eligible. I had to verify that all the hours I was claiming were my own work done in Canada. No outsourcing sneaking in there.
- Check the 18-Month Filing Deadline: This is strict and non-negotiable. You have 18 months from the end of your fiscal year to file a claim. For me, with a calendar year fiscal year, that means I have until June 30 of the following year to get it done. Miss that, and you’ve forfeited the claim forever.
- Review the T661 Form: This is the official form the CRA uses. I printed one out and just stared at it for a while. It’s dense, but understanding what it’s asking for now (rather than in a panic on June 29) makes the whole process less terrifying.
- Document Your Qualifying Work: Make sure you actually have contemporaneous notes for the work you’re claiming. Not perfect notes, just real notes that show you were thinking through problems as you worked.
- Understand Your Eligible Costs: Know exactly what you can claim: salaries, subcontractor costs (up to 80% for Canadian-based), capital equipment (in 2025 and beyond), and overhead (either by allocation or using the Proxy Method). Know what you can’t claim: marketing, general administration unrelated to R&D, and most overhead for foreign subcontractors.
Wrapping It Up Over a Leslieville Craft Beer
Final disclaimer: Everything I’ve shared here is based on my own research, my own experience, and conversations with people I trust. This is a blog post from a Toronto guy thinking out loud, not professional advice. Before you file anything with the CRA, talk to a certified accountant or tax lawyer who can review your specific situation. Trust me on this-it’s worth the consultation fee.
But here’s what I want you to take away from my kitchen table research and my conversations with Dave and my dive into Canada.ca documents: SR&ED is real, it’s designed for people like us, and the 2026 changes are making it even more accessible. If you’re doing R&D work in Toronto-whether it’s coding, manufacturing, engineering, or any other technical field-there’s likely money sitting on the table that the government is literally offering to give you.
The barrier isn’t that SR&ED is complicated or exclusive. The barrier is that most people don’t know it exists, and the ones who do market it aggressively with sketchy sales tactics. I’m hoping this post helps cut through that noise and just give you the facts from a neighbor’s perspective.
I’m planning to file my first SR&ED claim this coming spring, probably with a professional’s help to make sure I get it right. When I do, I’ll update this post with what I learn from the actual filing process. In the meantime, if you’re in Toronto and you’ve gone through this process yourself, I’d love to hear about your experience in the comments. What worked for you? What surprised you? What wish you’d known before you started?
For now, I’m going back to my Leslieville kitchen table to finalize my documentation and make sure my Friday afternoon tracking system is actually catching everything. And I’m planning to celebrate the first SR&ED refund-when it comes-with something nicer than a local pale ale. Maybe a trip to a local restaurant I’ve been wanting to try. The government’s basically giving me a bonus for doing the work I wanted to do anyway. That feels worth celebrating.