The Complete SR&ED Filing Playbook: Old Way vs. sredy.io

Why every Canadian founder needs to see this comparison

In 2024, a Waterloo-based founder named Jordan filed his first SR&ED claim the old way. He hired a consultant recommended by his accountant. The consultant charged a 25% contingency fee. The process took 11 weeks from first contact to submission. Jordan's engineers spent 14 hours in interviews. The final claim was $127,000 in qualifying expenditures. The refund, when it arrived 8 months later, was $44,450. The consultant's fee: $11,112. Jordan's net: $33,338. His time investment: 23 hours across interviews, document collection, and review meetings. His stress level: 'I genuinely considered not filing again next year.'

In 2025, Jordan filed his second claim using sredy.io. The process took 6 days from signup to submission. Jordan spent 4 hours total — mostly reviewing auto-generated narratives and confirming numbers. The claim was $156,000 (his R&D team had grown). The refund was $54,600. The platform fee: $699. Jordan's net: $53,901. His time investment: 4 hours. His stress level: 'It was almost anticlimactic. I kept waiting for something to go wrong, and nothing did.'

Stage 1: Finding out SR&ED exists

The old way: Most founders discover SR&ED through one of three paths — their accountant mentions it at year-end (too late to document properly), a consultant sends a cold email promising 'free assessment' (which is actually a sales pitch), or another founder mentions it over coffee (usually with a horror story about the paperwork). The discovery is accidental, late, and often accompanied by the sinking realization that they should have been documenting for the past 11 months.

The sredy.io way: Founders discover the platform through search (how to file SR&ED without a consultant), referrals from founders who had a good experience, or organic content like this playbook. The eligibility check is genuinely free — no email required, no sales call scheduled, no consultant sizing up your company for fee potential. You answer 8 questions about your R&D work and get an instant assessment with a projected refund range. The whole thing takes 90 seconds.

Stage 2: The eligibility assessment

The old way: The consultant schedules a 90-minute 'discovery call' — which is really a qualifying call to determine if your claim is worth their time. They ask about your R&D spend, your team size, your industry, and your fiscal year. If your projected claim is below $50,000, many consultants will politely decline or refer you to a junior associate. If it's above $200,000, their eyes light up because the contingency fee math gets interesting. The assessment is free, but the consultant is already calculating their percentage.

The sredy.io way: The eligibility assessment is a structured questionnaire based on CRA's two-part test for SR&ED eligibility. It asks about technical uncertainty, systematic investigation, and technological advancement — not about your budget or team size. The assessment tells you whether your work shows indicators of qualifying R&D, gives you a confidence level (High, Moderate, or Low), and shows a projected refund range based on your expenditure estimates. There's no human gatekeeper deciding whether your claim is 'worth it.' The software evaluates the work, not the wallet.

• Old way time: 90-minute discovery call + follow-up emails = 2–3 hours
• sredy.io way time: 90-second quiz + 5-minute review of results = 2 minutes
• Old way cost: Free (but you're now in a sales funnel)
• sredy.io way cost: Free (no follow-up sales calls, no email harvesting)

Stage 3: Documentation — the make-or-break stage

The old way: This is where the pain really starts. The consultant sends you a document request list that typically includes: project timelines, technical specifications, design documents, test logs, failure records, employee time allocations, payroll records, contractor invoices, and 'any other evidence of systematic investigation.' The request arrives 2–4 weeks before your filing deadline. You forward it to your engineering team. They groan. They have actual work to do.

The documentation scramble looks like this: You pull Git commit histories and try to remember which commits were R&D vs. routine development. You search Slack for technical discussions and find 4,000 irrelevant messages for every relevant thread. You ask engineers to write 'brief summaries' of their R&D work, and they produce either one-sentence descriptions or 3-page essays with no structure. You compile timesheets from multiple systems (Harvest, Toggl, spreadsheets, memory) and try to calculate who spent what percentage of their time on qualifying work.

The consultant reviews your documents and asks follow-up questions: 'Can you be more specific about the technical obstacle in Project B?' 'Do you have evidence of the failed iteration on March 15?' 'Can you get a signed statement from the contractor about their R&D allocation?' Each follow-up adds 2–3 days to the timeline. By week 6, you're resenting the entire process and wondering if the refund is worth the disruption.

The sredy.io way: Documentation is captured as you work, not reconstructed after the fact. The platform provides a structured evidence index where you upload or link documents as they're created — design specs, test results, meeting notes, technical decisions. Each document is tagged to a specific project and automatically connected to the relevant technical narrative section.

But the real magic is the retrospective capture. If you're starting sredy.io mid-year or even at year-end, the platform guides you through a structured reconstruction: it prompts you with specific questions about each project, suggests what evidence types would be most useful, and helps you organize scattered documentation into a coherent evidence package. Instead of 'send us everything,' it's 'let's build this together, step by step, with context.'

• Old way time: 20–40 hours of document collection, follow-up, and organization across 4–8 weeks
• sredy.io way time: 2–6 hours of guided capture, spread across 2–3 sessions at your own pace
• Old way stress: High — engineering team resents the interruption, quality is uneven, gaps are discovered late
• sredy.io way stress: Low — guided prompts mean you know exactly what's needed, quality is consistent, gaps are flagged early

Stage 4: Writing the technical narratives

The old way: This is the consultant's core value proposition, and it's where the fee percentage starts to feel questionable. The consultant schedules 1–2 hour interviews with each engineer who worked on R&D. They ask open-ended questions: 'Tell me about the technical challenges you faced.' 'What did you try that didn't work?' 'How is this different from standard development?' The engineer answers honestly but without structure — because they weren't trained in CRA's specific narrative requirements.

The consultant then goes away and 'writes the narratives.' What actually happens varies dramatically by consultant quality. A good consultant synthesizes the interview into structured narratives that align with CRA's expectations. A mediocre consultant transcribes the interview with minimal editing. A bad consultant writes generic narratives that could apply to any software project and hopes CRA doesn't read them carefully.

Jordan's first-year consultant fell in the 'mediocre' category. The narratives were grammatically correct but lacked specificity. Project A's narrative said: 'The team encountered performance issues with the data pipeline and experimented with several solutions before achieving acceptable throughput.' That's not false — but it's also not the level of detail CRA reviewers expect. A good narrative would say: 'The team encountered a specific technical obstacle: the existing streaming architecture (Apache Kafka with default partitioning) could not handle the bursty data patterns of industrial IoT sensors without either dropping events (unacceptable for manufacturing analytics) or buffering beyond 500ms latency thresholds. The team systematically investigated four approaches: (1) increasing partition count, which improved throughput but increased coordination overhead beyond acceptable CPU limits; (2) implementing custom backpressure logic, which reduced drops but increased latency to 1.2s; (3) switching to a pull-based consumer model, which solved latency but created ordering guarantees that violated downstream requirements; (4) implementing a hybrid push-pull approach with adaptive batch sizing, which achieved <300ms latency at 99.9th percentile with zero event drops.'

The sredy.io way: The platform uses AI-assisted narrative drafting, but the key difference is the structured input. Instead of open-ended interviews, the guided workflow asks specific, CRA-aligned questions for each project: What was the specific technical obstacle? What existing knowledge or methods were insufficient? What did you try, and what were the specific outcomes of each attempt? What new knowledge or capability did you develop? The engineer answers in their own words — but within a structure that automatically maps to CRA's evaluation criteria.

The AI then drafts the narrative using the engineer's own terminology, technical details, and project context. It's not generic template text — it's a structured, specific narrative built from the actual work. The founder reviews, edits, and approves. The result: narratives that are more specific, more defensible, and more authentic than most consultant-written equivalents. Because the engineer's actual reasoning is captured, not a consultant's interpretation of it.

• Old way time: 6–12 hours of interviews + 1–2 weeks of consultant drafting and review cycles
• sredy.io way time: 2–4 hours of structured input + 30 minutes of AI generation + 30 minutes of review and editing
• Old way quality: Highly variable — depends entirely on consultant skill and engineer articulation under interview pressure
• sredy.io way quality: Consistently high — structured input ensures completeness, AI preserves engineer's voice, founder review catches inaccuracies

Stage 5: Financial calculations and schedules

The old way: The consultant works with your accountant or bookkeeper to calculate qualifying expenditures. This typically involves: exporting payroll data, categorizing employee time by project and R&D percentage, calculating overhead allocations using either the traditional or proxy method, identifying eligible contractor costs, and producing the formal expenditure schedule that accompanies the T661 form. The consultant and accountant often have different understandings of what qualifies, leading to back-and-forth revisions.

Jordan's first-year experience: His consultant asked for payroll data in a specific format. Jordan's bookkeeper exported it in a different format. The consultant sent it back. The bookkeeper re-exported it. Three rounds later, they had the data. Then the consultant calculated R&D allocations using percentage estimates that Jordan's lead engineer disputed ('I didn't spend 60% of my time on R&D — it was more like 40%'). The consultant adjusted the numbers downward, reducing the claim by $18,000. The whole financial stage took 3 weeks and involved 8 email threads.

The sredy.io way: The platform has an integrated expenditure calculator. You connect your QuickBooks, Xero, or FreshBooks account (or manually enter payroll data), and the platform automatically categorizes employees and calculates time allocations based on the project assignments you've already entered in the technical section. The overhead calculation uses the method you select (traditional or proxy) and applies the correct formulas automatically.

The key difference: the financial and technical sections are connected. When you assign an engineer to Project A at 40% time allocation in the technical section, that allocation flows automatically into the financial calculation. No manual re-entry. No format conflicts. No consultant-accountant email tennis. The founder reviews the numbers, adjusts if needed, and approves. Total time: 30–60 minutes.

Stage 6: Form preparation and package assembly

The old way: The consultant assembles the filing package — T661 form, technical narratives, expenditure schedule, evidence index, and supporting documents. They typically use a combination of Word templates, Excel spreadsheets, and PDF compilation tools. The package is sent to the founder for review as a large PDF or a shared folder. The founder scrolls through 40–80 pages of technical and financial documentation, trying to spot errors while not fully understanding the tax mechanics.

Jordan's review experience: 'I got a 67-page PDF and an email that said 'Please review and confirm.' I opened it. I saw the T661 form with numbers I didn't recognize. I saw technical narratives that sounded like my projects but used words I wouldn't have chosen. I saw an evidence index with 34 documents, some of which I didn't remember uploading. I replied: 'Looks good, I think?' I had no idea if it was actually good. I just wanted it submitted so I could stop thinking about it.' This is common. Founders in the old system review out of obligation, not understanding.

The sredy.io way: The platform generates the complete filing package automatically — T661 form populated with your data, technical narratives formatted to CRA specifications, expenditure schedule with all calculations shown, evidence index with hyperlinked documents, and a cover letter. The founder reviews it in the platform interface, which highlights each section with explanatory tooltips: 'This number comes from your Project A time allocation of 40% x $130,000 salary.' 'This narrative references the evidence document you uploaded on March 15.'

The review is structured, not overwhelming. You review each section independently, with the ability to edit any field directly. The platform flags potential issues: 'This time allocation seems low compared to the narrative description — did you intend 40% or should it be higher?' 'This evidence document is referenced in the narrative but hasn't been uploaded yet.' When you're satisfied, you export the package as a single PDF or as separate documents for your accountant. Total review time: 45–90 minutes with full understanding of every number.

Stage 7: Submission and CRA processing

The old way: The consultant typically submits the claim on the company's behalf, using their own CRA representative account. This is convenient but creates a dependency: if you have questions about the claim later, you need to go through the consultant. If you want to file next year's claim with a different approach, you need the consultant's cooperation to transfer access. Some consultants resist this because it reduces their lock-in.

After submission, the consultant's involvement drops sharply. They may send a quarterly 'status check' email. They may not. If CRA requests additional information (an RFI — Request for Information), the consultant handles the response — often billing additional hourly fees for the work. The founder is largely in the dark about where their claim is in the queue, what the review timeline looks like, or whether additional documentation might be needed.

The sredy.io way: The founder submits the claim directly through their own CRA business account — maintaining full ownership and visibility. The platform provides a submission checklist to ensure nothing is missed. After submission, the platform tracks claim status and sends updates: 'Your claim was received by CRA on [date]. Expected processing time for claims of this size: 90–120 days.'

If CRA sends an RFI, the platform provides guided response templates based on the most common RFI types: 'Request for additional technical detail,' 'Request for time allocation documentation,' 'Request for contractor payment evidence.' Each template references the specific documents already in your evidence index, making response preparation fast and complete. The founder can handle the response themselves or engage the optional CPA review service for complex RFIs.

The complete comparison table

Here's the full before-and-after at a glance, based on a typical $100,000 qualifying expenditure claim by a 5-person Canadian tech startup:

Total time investment: Old way = 35–55 hours over 8–14 weeks. sredy.io way = 6–12 hours over 3–10 days.

Total cost on a $100,000 claim (35% federal + 8% Ontario = $43,000 refund): Old way = $10,750 (25% contingency). sredy.io way = $699 (flat fee). Net difference to founder: $10,051 more in their bank account.

Quality comparison: which approach produces better claims?

This is the question that matters most, because a cheap claim that gets rejected is worse than an expensive claim that gets approved. Here's the honest breakdown:

Narrative quality

Good consultants produce excellent narratives — better than sredy.io's AI drafts in some cases, because an experienced consultant understands CRA reviewer psychology and knows how to frame technical work for maximum clarity. But good consultants are expensive and rare. Most consultants produce adequate narratives that are fine for straightforward claims but weak for complex technical work. sredy.io's AI drafts are consistently above-average — not because the AI is brilliant, but because the structured input forces completeness and specificity. The founder's review step then adds the human judgment that AI lacks.

Evidence completeness

sredy.io wins here decisively. The guided evidence capture ensures nothing is missed, and the platform's gap analysis flags missing documentation before submission. Consultants rely on the founder's document collection, which is often incomplete because founders don't know what's needed.

Financial accuracy

Tie. Both approaches can produce accurate financial schedules when the underlying data is correct. sredy.io's advantage is the integration between technical and financial sections — when time allocations change in the narrative, the financial schedule updates automatically. Consultants do this manually, which introduces error risk.

Defensibility under review

sredy.io has a slight edge for the same reason it wins on evidence: completeness and specificity are the best defenses against CRA scrutiny. A consultant-written claim with vague narratives is more vulnerable than a software-generated claim with detailed, evidence-backed narratives. But a truly excellent consultant who deeply understands your technical work can produce a more defensible claim than either approach. The problem: finding that consultant costs more than the platform's entire fee.

The hybrid approach: expert advice only when you ask for it

sredy.io's operating model is not software-only, and it's not consultant-driven. It's a hybrid: the software handles 90% of the work, and human experts show up only when you explicitly need them. This is fundamentally different from both traditional consulting (where a person does everything and charges a percentage) and pure software tools (where you're entirely on your own if something goes wrong).

Here's how the hybrid model works in practice:

• Self-service foundation: Every claim starts with the guided software workflow. Eligibility check, documentation capture, narrative drafting, financial calculation, and form generation are all handled by the platform. No expert required. No hourly billing. No percentage fee.
• Expert review checkpoint: At the review stage, you can request a CPA or SR&ED specialist to review your claim before submission. This is entirely optional. If your claim is straightforward and you're confident, you submit directly. If you want a second pair of eyes, you book a review at a fixed fee — typically $300–$800 depending on complexity, not a percentage of your refund.
• RFI response support: If CRA sends a Request for Information after submission, the platform provides guided response templates. For standard RFIs, most founders handle the response themselves in under an hour. For complex RFIs, you can escalate to the expert team for hands-on support at a fixed hourly rate.
• Complex claim advisory: For claims with unusual complexity (multi-year programs, international cost-sharing, disputed eligibility), the expert team is available for structured advisory sessions booked by the hour. You get specialist expertise when you need it, not a generalist consultant assigned to your account full-time.

The key distinction: with sredy.io, you are always in control of when and how expert advice enters the process. The expert is an on-demand resource, not a gatekeeper. You don't need permission to file. You don't need an evaluation call to get started. You build your claim, and you decide whether you want expert review at any of the decision points.

The hybrid model respects something most consultants ignore: founders are capable of handling their own claims for the majority of the work. The bottleneck isn't the founder's competence — it's the complexity of the process. Remove the complexity with good software, and the founder can handle 90% of the work. Reserve expert time for the 10% where judgment, experience, and CRA-specific knowledge genuinely add value.

When to use each approach: a decision framework

sredy.io is the right choice for most Canadian founders filing SR&ED claims. But there are legitimate cases where the traditional consultant approach makes sense:

• Use a consultant if your claim exceeds $500,000 and involves complex multi-year R&D programs with overlapping projects, subcontractor chains, or international cost-sharing arrangements. The structural complexity may benefit from hands-on professional judgment.
• Use a consultant if you're in the middle of a CRA audit or review and need someone with established CRA relationships and review experience to navigate the process.
• Use a consultant if you have zero technical documentation and zero engineering team availability — though in this case, you should also consider whether you actually have a defensible claim.
• Use sredy.io for everything else: first-time claims, claims under $500K, straightforward software or AI R&D, companies with decent Git history and some project documentation, founders who want to understand their own claim, and anyone who resents giving away 15–30% of their refund.

Two paths, two outcomes: the founder stories

Path A — The old way: Sarah, a Toronto healthtech founder, raised a $1M seed round in 2024. Her 4-person team spent 70% of their time on R&D — building an AI diagnostic tool. Her accountant introduced her to a consultant in February 2025. The consultant charged 20% contingency. The process consumed 6 weeks of her attention, 12 hours of her CTO's time, and created tension with the engineering team ('Why are we spending a whole day talking about what we did last year?'). The claim was $180,000. The refund was $63,000. The consultant's fee: $12,600. Sarah's net: $50,400. Her assessment: 'The money was real, but the process was so disruptive that I delayed hiring a developer I needed. I probably lost more in delayed product development than I gained from the claim.'

Path B — The sredy.io way: David, a Montreal fintech founder, raised a $750K seed round in 2024. His 3-person team also spent ~70% of their time on R&D — building a real-time fraud detection pipeline. He found sredy.io in April 2025 through a Google search. He did the eligibility check on a Tuesday evening (2 minutes). He started the claim workflow on Wednesday morning. He worked through it in 3 sessions over 5 days — about 5 hours total. His CTO reviewed the technical narratives and made edits directly in the platform (45 minutes). The claim was $145,000. The refund was $50,750. The platform fee: $699. David's net: $50,051. His assessment: 'I spent less time on the entire claim than Sarah spent on her first consultant meeting. And I understood every number in my claim — which meant I could answer CRA questions confidently when they called. That confidence alone was worth more than the fee savings.'

The subtle difference: Sarah felt like a client being processed. David felt like a founder in control. Both got similar net refunds. But David's path took 1/10th the time, 1/20th the cost, and left him with a system he could repeat next year without relearning anything. Sarah will face the same 6-week disruption every year. David will face a 5-hour routine.

The compounding advantage

The biggest difference between the old way and the sredy.io way isn't visible in the first-year comparison. It's the second year, the third year, and the fifth year.

With the old way, every year is a fresh scramble. New consultant (or same one, starting from scratch). New interviews. New document requests. New timeline pressure. The documentation habits don't improve because the process is externalized — the consultant handles it, so the team has no incentive to document better.

With sredy.io, every year is easier than the last. Your projects, narratives, and evidence index are saved in the platform. Next year's claim starts with a 'duplicate and update' of last year's projects — not from a blank page. Your documentation habits improve because the platform makes it easy to capture evidence as you work, not after. By year three, you're filing claims in 3 hours instead of 5, with better documentation than most consultant-prepared first-year claims.

Turn this guide into a claim package

SREDY.IO walks you through eligibility, project narratives, supporting costs, and evidence so your CPA has a cleaner file to review.

More guides

Ready to check if your work qualifies? Take the free eligibility assessment.