SR&ED evidence, captured the week the work happens.
One five-minute conversation per engineer, every Friday. By year-end the claim is already written, dated, and defensible - no March reconstruction, no timesheets, no forms.
The interview
A colleague, not a form
Every Friday each engineer gets a link - no login, no account. The agent reads their commits, asks what actually happened, and digs for the failures engineers bury. Their own words become the evidence record, timestamped that week, immutable after.
It never invents. A routine week is captured as a routine week - an honest empty record is worth more than a manufactured claim.
$0
estimated SR&ED credit, fiscal year ending Dec 31 2026
- federal
- $1,216
- ON
- $399
- qualified spend
- $3,876
capture, week by week
streak 2 · 25 weeks to fiscal year end
The number
Watch the claim build weekly
Every captured week moves the estimate: salaries, time splits, the 55% overhead proxy, federal and provincial rates - one math path, shown transparently. Built-in audit guardrails flag what a CRA reviewer would flag, before they do.
The Monday digest
What last week's five minutes were worth
Every Monday morning: the delta last week's capture added, what got captured, and who still owes a check-in - with the stake spelled out, because uncaptured weeks count as zero.
Monday digest
+$212
added to your estimated credit last week.
Arjun captured 2 experiments on SYNC-01: chunked merge held under budget
Maya's check-in is still open - nudge from the dashboard, one click. Uncaptured weeks count as $0.
$1,615 to date · federal $1,216 + ON $399 · 25 weeks to fiscal year end
your week
open threads
Monolithic merge with pre-sorted op log
SYNC-01 · didn't pan out - worth an update
teleop-rig
- Jul 9 · Fixed: tombstone traversal accounting in merge profiler
- Jul 7 · Performance: merge benchmark fixture, 50MB structured doc
Memory, not homework
Their artifacts jog. They testify.
Commits appear beside the conversation in plain English. Failed experiments from past weeks resurface as open threads. And your team's group chat? Paste the week's tech chat straight in - the agent reads it like commits, then asks your engineer about what matters.
The hard rule under all of it: artifacts scaffold the answer, never replace it. Only the engineer's own words enter the record.
The filing
The T661 writes itself
The three narratives CRA requires draft directly from the captured ledger - every sentence traceable to a dated entry, word limits enforced. Hand your preparer one zip: cover sheet with capture-date proof, narratives, experiment log, allocations, photos, commit corroboration.
Line 242 - Technological uncertainties
78 / 350 words
No published controller design maintained stable haptic force feedback at 1 kHz over network links with 5 to 40 ms of variable latency…
If a review ever comes
Your engineers, already prepared
The Review-Defense Pack preps each engineer for CRA's interview questions with their own verbatim captured answers - nothing generated, nothing paraphrased, every line dated.
Q3. What did you try that did not work?
Maya Chen · experiment · week of Jun 22 · captured Jun 24
"Pre-sorting the op log didn't pan out - sorting wasn't the bottleneck; tombstone traversal dominates and grows with document size regardless of op order."
Contemporaneous
Capture dates are server-set and immutable, at the database level. Evidence dated the week it happened is the evidence CRA weights most.
Honest by design
The agent never leads the witness and never harvests from commits or pasted chats - artifacts jog memory, testimony becomes the record.
Yours, exportable
Every entry, transcript, photo, and allocation exports in open formats, anytime. No lock-in - the evidence belongs to your company.
Retroactive scan
Connect GitHub and six months of commit history clusters into candidate projects - day-one value, a map for what to capture.
Photo evidence
Rigs, broken parts, scope traces - snapped in the conversation, captioned, dated, and included in the export package.
Corroboration
Two engineers on one experiment become one experiment with two accounts - the strongest shape evidence can take.
GitHub, read-only
Commit metadata only: author, message, date. No code is ever stored, and you pick the repos on GitHub's own screen.