Every estimator who has ever worked a public job with domestic content rules knows the specific dread of the melt certificate chase. The steel numbers on the takeoff were never the hard part. The hard part was proving, with paperwork from a mill three suppliers removed from the one you actually called, that the rebar was melted and poured in the right country, on the right date, by the right process, before a compliance officer with a clipboard would let the pour proceed. Get one certificate wrong and the whole shipment sits on a truck while the project burns a week of schedule float over a document nobody on site could read even if they wanted to.

That particular flavor of paperwork purgatory has always been reserved for physical materials, steel, concrete, fasteners, the stuff you can hold and trace to a mill. A Canadian contech company is now arguing it should apply to something nobody has ever asked for a melt certificate on: the software running the job.

SMARTBUILD Construction Solutions, a Brampton, Ontario based construction software company, announced on September 1 the launch of its BUY CANADIAN TECHNOLOGY Initiative, a campaign asking federal, provincial, and municipal governments to extend Buy Canadian and Buy Ontario procurement policy to software and digital platforms, not just building materials and physical goods. The campaign makes three specific asks of officials: name construction and infrastructure software as its own strategic procurement category, set procurement thresholds that reflect what software contracts actually cost rather than what the building itself costs, and apply a Canadian content test to the platform layer of every publicly funded project, the same way domestic content rules already apply to the steel and concrete. SMARTBUILD is also inviting other Canadian contech companies to sign on and put forward a common industry position rather than lobbying separately.

The timing is not incidental. Canada's federal Policy on Prioritizing Canadian Suppliers and Canadian Content in Strategic Federal Procurements had its application threshold lowered from 25 million dollars down to 5 million dollars as of June 15 this year, according to the government's own CanadaBuys procurement portal, pulling a far larger share of public contracts, software included, into scope for domestic preference scoring. A construction software vendor headquartered in Brampton, hosting its own data on Canadian servers, is exactly the kind of company that threshold change was built to help, provided procurement officers actually start applying the same content logic to a SaaS contract that they already apply to a rebar order. SMARTBUILD founder and CEO Zulq Malik and the company's Chief Customer Experience Officer Vinay Nair reportedly raised the issue directly with Evan Solomon, Canada's Minister of Artificial Intelligence and Digital Innovation, which is the kind of detail that separates a genuine policy push from a press release written to look like one.

SMARTBUILD's own product suite is a useful window into what is actually at stake here. Beyond its estimating and project tools for architects, general contractors, and trade subcontractors, the company built smrt-E, a voice activated AI assistant for field reporting that lets crews capture site documentation hands free in up to 200 languages, a real problem on jobsites where the person best positioned to log an issue is standing on a ladder holding a phone in one hand and a tape measure in the other. That is precisely the category of homegrown AI tool that has no chance of surviving a scale fight against Procore, Autodesk, or Trimble on procurement neutral terms, and exactly the category a domestic content carve out at the software layer is designed to protect.

Whether this campaign goes anywhere is genuinely uncertain. Extending Buy Canadian rules from physical materials to software is a much harder thing to define and audit than a melt certificate, since a platform's servers, code, and workforce can straddle borders in ways a ton of rebar cannot. But the underlying instinct, that AI sovereignty policy should not stop at chips and cloud infrastructure and skip the vertical software actually running public construction projects, is going to keep showing up as governments everywhere get more comfortable writing domestic AI preferences into procurement. For anyone building or buying bid and proposal software, that is worth watching closely: if a government client starts scoring the software stack the way it already scores the steel, that becomes one more line item a compliant RFP response has to prove, not just describe.

Sources