Canada’s defence procurement reforms share one design principle: they make it safer for the buyer to choose an unproven company. The Defence Investment Agency gives program managers sole-source and interoperability exceptions they can defend on the record. The modernized Industrial and Technological Benefits policy, with its enhanced multipliers and 90-day approval standard, makes it cheaper and faster for a prime to bet on a small Canadian supplier. This is the right target. Risk aversion in procurement was never a culture problem; it was a rational response to incentives that punished anyone who picked the unknown option.
But de-risking the buyer solves exactly one side of the transaction. The seller still carries four problems that no reform touches, and I say this as someone living inside them. My company, Caseway, is a Vancouver AI firm working through these pathways right now, so read what follows as field notes rather than theory.
Problem one: visibility
A de-risked buyer who has never heard of you still does not choose you. The concierge services and single-window proposals route companies to programs, but programs do not buy anything. Project offices, primes with ITB obligations, and now the DIA do. The fix is to stop waiting to be found. Get on every standing vehicle before you need it: source lists, supply arrangements, security clearances. Each one matters less as a revenue channel and more as a pre-answered objection sitting in an evaluator’s file. Respond to Requests for Information even when no contract is attached, because RFIs are where requirements get written, and if your capability language shows up in the eventual statement of work, the shortlist conversation answers itself. And treat ITB obligations as a search engine running in reverse. Primes with value propositions coming due are actively hunting for creditable Canadian content. Approach them as the answer to their compliance problem, not as a supplicant with a demo.
Problem two: selection
The buyer’s core need is an on-the-record justification for choosing you. You cannot rewrite their incentives, but you can hand them the paperwork. Certifications, independent penetration tests, and security attestations do not win contracts on their own. What they do is let an evaluator write “vendor holds these credentials” instead of “we took a chance.” The buyer is quietly assembling a defence file for a decision they have not yet made; your job is to pre-write it. The other selection tool is teaming. When a prime chooses you, the prime owns the risk, which is why a subcontract position is worth accepting on worse economics than a direct deal. First the reference, then the direct relationship. And if your capability is genuinely unique or interoperability-critical, say so in writing, in advance, in language a contracting officer can lift straight into a justification document. Sovereign, non-ITAR positioning exists for precisely this reason.
Problem three: runway
Government time runs slower than a startup’s burn rate. The BDC Defence Platform and the regional investment initiatives help, but capital programs favour firms that already look fundable. The companies that survive the gap tend to do three things. They keep a commercial revenue engine running while defence gestates; dual-use is the standard answer because a paying civilian customer means a departmental timeline cannot kill you. They stack non-dilutive money aggressively, from IDEaS to IRAP to allied programs, with the discipline of only chasing grants aligned to the roadmap they were building anyway. And they raise equity against qualified pipeline rather than booked revenue, timing the raise to land just after a visible catalyst instead of just before one.
Problem four: the missing lane
Canada still has no ring-fenced route from a validated pilot to a production contract. Our on-ramps drop companies at a successful trial and leave them there. Until that lane exists, three workarounds apply. Design every pilot as a wedge into an existing program of record, and negotiate the transition language before the pilot starts, even if it is non-binding. A pilot whose only exit is “interesting results, thanks” is a funeral with a report attached. Second, use allied systems that do have the lane. The American SBIR Phase III and Other Transaction authorities, and NATO DIANA’s route into alliance procurement, explicitly pre-authorize the transition Canada lacks. A firm that validates at home, converts abroad, and returns with a foreign contract in hand becomes the proven option domestically. That is perverse, and it is also the current reality. Third, target the sustainment and upgrade cycle rather than the new-platform cycle. Software insertions into in-service systems move on shorter clocks, with lower approval thresholds, and they build the incumbency the whole system rewards.
The honest ledger
None of this guarantees conversion, and the base rate for Canadian defence SMEs reaching sustained production revenue remains low. But the reforms have genuinely moved the government’s half of the bargain. The half that remains belongs to the founder. It reduces to a single discipline: keep converting the buyer’s residual risk into someone else’s problem. A prime’s. A certifier’s. An allied government’s. A paying commercial customer’s. Ottawa built better roads. Learning to drive them was never going to be in the policy document.