Al Vigier is the founder and CEO of Vancouver-based AI company Caseway.
Something changed in our sales calls over the past year. Buyers who used to open with questions about features and pricing now open with questions about jurisdiction.
“Where is the company incorporated? Who owns it? Where does the data live? Which foreign government could order you to do something, and what happens to us if one does?”
Three years ago, nobody asked those questions. Now, it comes up even before the demo.
“This is a product opportunity, yet most Canadian startups are treating it as a paint job.”
The trade war did that. When the United States enacted 50-percent tariffs on $28 billion of Canadian goods over a single weekend, every buyer who wants to mitigate risk naturally started asking what can be switched off from Washington. Software dependency is high on that list. Vendor nationality has become a procurement variable in software, just as exposure to China became a variable for hardware over the past five years, first through the Huawei security bans and then the pandemic supply shocks.
The demand side has moved fast. The federal Buy Canadian Policy, in force since December 2025, directs departments and agencies to prioritize Canadian suppliers and Canadian content for major purchases, and it extends to grant programs and, where possible, Crown corporations. Provinces and cities are writing their own versions. Enterprise boards are running the same logic privately: the questionnaire that once asked about SOC 2 compliance now asks about ownership, control, and governing law.
This is a product opportunity, yet most Canadian startups are treating it as a paint job.
Sovereignty, specified properly, is a feature set. It should include data residency in Canadian regions with contractual guarantees, rather than best efforts; Canadian ownership and control, documented, so a procurement officer does not have to guess; a clear map of subprocessors and which foreign statutes reach them; governing law and dispute resolution in Canada; continuity commitments that describe exactly what happens to a customer’s deployment if a foreign platform provider cuts access or a border closes.
RELATED: Canada’s early-stage investment gap “now a sovereignty issue,” BDC says
Each of those involves engineering and legal work. Each of those is something a buyer under pressure will pay for.
Sovereignty can’t be just maple-washing. Do the work. A flag on the pricing page and a .ca domain is marketing, and it won’t stand up to procurement due diligence. If the stack underneath a product is entirely built on American cloud infrastructure, a competent procurement team will find that out in one architecture review—the credibility loss is worse than never having made the claim. Sovereignty claims are now verified the way security claims are.
There are three moves for founders who want to sell sovereignty the right way.
“Sovereignty claims are now verified the way security claims are.”
First, write a sovereignty spec sheet and make it a standard sales document. One page: incorporation, ownership, data residency, subprocessors, applicable foreign statutes, governing law, continuity plan. Hand it over before being asked. The vendor who answers the jurisdiction questions unprompted sets the bar the rest of the shortlist gets measured against.
