Selling technology to government is a different discipline from selling to the private sector. The buyers are the same kinds of organizations in many ways — they need software that works, delivered on time, at a defensible price — but the path to a contract runs through formalized processes with strict rules, public accountability requirements, and vehicles that reward vendors who prepare well before an opportunity appears. This guide explains how Canadian public-sector procurement works in practice, with particular attention to what changes when the technology being bought involves artificial intelligence.

The federal landscape

The federal government is Canada’s largest single buyer of goods and services. For information technology, most large purchases flow through Public Services and Procurement Canada (PSPC), which acts as the central purchasing agency for federal departments. Individual departments and agencies define their own requirements and manage their own projects, but the actual competition and contracting is frequently run centrally by PSPC. Some organizations with delegated or separate authorities — the Department of National Defence, the Canada Revenue Agency, and Shared Services Canada for much of the government’s own IT infrastructure, among others — run their own procurements under their own rules.

CanadaBuys is the federal government’s tendering and procurement platform, and it is the first place any vendor considering federal work should become familiar with. Tenders are published there, and suppliers register their accounts and profiles on the same platform. Earlier legacy systems for publishing government tenders have been consolidated into it, so CanadaBuys is effectively the front door for federal opportunities. If you are not watching it, you are not in the game.

One structural point matters for anyone planning a go-to-market strategy: the federal government is not one buyer. It is more than a hundred departments and agencies, each with its own budget, priorities, and contracting authority for smaller purchases. This fragmentation means relationships, reputation, and past performance travel across departmental lines even when the contracts do not — a team that delivered well for one department is better positioned for the next opportunity with another.

Common vehicles

Government contracts are not always awarded through open competitions in the way a private RFP works. Much federal buying flows through pre-established procurement vehicles, and understanding them is essential.

Standing offers

A standing offer is an arrangement under which the government can call off goods or services as needed, over a set period, without running a fresh competition each time. Standing offers are established through an initial competitive process, after which pre-qualified vendors hold a place on the list. When a department needs something covered by a standing offer, it issues a call-up — effectively a mini-order against the existing arrangement.

For vendors, the implication is straightforward: the real competition happens when the standing offer itself is established or renewed, which can be years apart. If you are not on the standing offer when a department needs the work, you generally cannot compete for the call-up. Vendor strategy, therefore, starts with tracking which standing offers cover the services you sell and positioning to compete when they are re-competed.

Supply arrangements

A supply arrangement is similar in spirit but typically covers a broader or more varied set of goods and services, and it can remain open to new suppliers on an ongoing basis. Under a supply arrangement, the government runs the initial competition, admits qualified vendors, and then runs smaller competitions — sometimes called requests for proposals against the arrangement — among only the admitted suppliers.

The practical difference for a vendor: supply arrangements with continuous admission offer a realistic path to get pre-positioned, while closed arrangements require waiting for the re-competition. Either way, being inside the arrangement is the prerequisite for seeing most of the work that flows through it.

Competitive RFPs and trade-agreement obligations

Above certain dollar thresholds, federal procurements must be competed openly and in accordance with Canada’s international trade obligations — agreements that require fair, non-discriminatory treatment of suppliers from signatory countries. In general terms, higher-value procurements carry more formal requirements: longer posting periods, stricter evaluation criteria, and more documentation. Below the thresholds, departments have more discretion, and there are mechanisms for lower-value direct awards, though departments are still expected to obtain value for money and document their decisions.

The threshold structure is one reason the public-sector market has a distinctive shape. Many contracts sit just below thresholds, some far above them, and the compliance burden scales with value. A vendor’s bid-no-bid process needs to account for this: high-value open competitions are expensive to pursue and worth pursuing selectively, while smaller direct or limited competitions can be efficient entry points.

AI-specific considerations

Technology procurement in government now has a layer that did not exist a few years ago: formal expectations around how automated and AI-driven systems are governed.

The Directive on Automated Decision-Making

The federal Treasury Board Directive on Automated Decision-Making is a real and binding policy that applies to federal departments using automated decision systems. In general terms, it requires departments to assess the impact of such systems before deployment — the Algorithmic Impact Assessment (AIA) is the central instrument — and to scale governance measures to the assessed level of impact. Higher-impact systems face more stringent requirements around transparency, human oversight, data quality, testing, and ongoing monitoring.

For a vendor selling AI capability to the federal government, this directive matters in two ways. First, it shapes what departments can buy: a department evaluating an AI system must be able to satisfy the directive’s requirements, so vendors should expect questions about model behavior, data provenance, testing, and monitoring — and should be prepared to help the department complete its assessment. Second, it creates a market signal: departments that are further along in their AI adoption are actively looking for vendors who understand this governance framework rather than treating it as an afterthought.

Note that the directive is federal policy. Provincial and municipal governments have their own approaches — some have issued their own AI guidelines, others are still developing them — so vendors working across jurisdictions should not assume one framework applies everywhere.

Data residency and security expectations

Public-sector buyers in Canada generally expect data to be handled in accordance with Canadian privacy law and, in practice, frequently expect or require Canadian data residency — data stored and processed within Canada. Security expectations are formalized rather than informal: departments assess systems against established government security guidance, and cloud services are subject to published assessment processes.

For AI systems, these expectations extend to training data, model artifacts, and inference logs. A vendor proposing an AI solution should be ready to answer, in concrete terms: where does the data live, who can access it, what crosses the border, and how is each of those answers documented. Vagueness on these questions is a reliable way to lose a government evaluation.

Provincial and municipal procurement

Each province runs its own procurement system, separate from the federal government’s. Ontario, Quebec, British Columbia, Alberta, and the others each have their own central procurement organizations, tendering portals, and vendor-registration processes — and their own standing arrangements. A vendor qualified to sell to the federal government has no automatic standing with any province.

Municipalities are a further layer down, and they are more varied still. Larger cities run formal procurement operations with published tenders and vendor registries; smaller municipalities may handle purchasing through general administrative staff. The scale of individual municipal contracts is often smaller than federal ones, but the number of buyers is far larger.

MERX is a widely used tendering platform in Canada where many public-sector buyers — including federal organizations in some cases, provinces, municipalities, and broader public-sector entities such as hospitals and universities — publish opportunities. Alongside CanadaBuys, it is one of the two platforms a vendor watching the Canadian public sector will encounter most often. Registration and monitoring across the relevant portals is unglamorous work, but it is the practical foundation of a public-sector pipeline.

What vendors should prepare

Winning public-sector work rewards preparation done before any specific opportunity appears. The vendors that do well treat this as a capability to build, not a scramble to run when a tender drops.

Corporate readiness. Government evaluations score the vendor, not just the proposal. Basic corporate hygiene matters: current business registration, financial statements that can be produced on request, insurance at the levels government contracts typically require, and references from comparable work. If the company cannot demonstrate it is a going concern with the capacity to deliver, the proposal rarely gets a full read.

Past performance and the reference problem. Public-sector buyers place heavy weight on demonstrated delivery, and they prefer references from comparable organizations — ideally other public-sector clients. This creates the classic cold-start problem for firms new to government: you need government references to win government work. The standard ways through are subcontracting on someone else’s contract, pursuing smaller direct-award or limited-competition opportunities where evaluation is less reference-heavy, and packaging private-sector work that is genuinely analogous.

Teaming and subcontracting. A large share of public-sector technology work is delivered by teams, not single vendors. Prime contractors hold the contract and assemble subcontractors for specialized capability. For a smaller firm, subcontracting is often the most realistic first route into government: it builds the past-performance record, teaches the firm how government delivery actually works, and creates relationships with primes who bring the next opportunity. Teaming arrangements should be formalized — roles, rates, and intellectual property terms agreed in writing — because government delivery has a long memory and informal understandings do not survive a dispute.

Proposal discipline. Government evaluations are scored against published criteria by evaluators who are required to justify their scores. This has a direct implication: answer the criteria as written, in the order written, with explicit cross-references. Evaluators cannot award points for capability they cannot find in the proposal, however well known it is in the industry. Compliance matrices, clear writing, and evidence attached to claims are the difference between a good firm that loses and a good firm that wins.

For readers mapping out where their own organization fits in this landscape, our government and enterprise practice describes how we think about public-sector delivery, and the engagements page outlines the ways we typically work with partners and clients.

An honest note on where Arihant fits

This guide is written by a small consultancy, and it would be dishonest to present ourselves otherwise. Arihant Global Ventures Inc. currently holds no standing offers, no supply arrangements, no government security clearances, and no pre-qualification status with any federal, provincial, or municipal buyer. None of these are held, applied for, or pending. We state this plainly because the public-sector market punishes misrepresentation — claiming credentials you do not hold is a fast way to end a government relationship permanently.

What we do offer is specialized delivery capability: enterprise architecture, applied AI and agentic systems, and the governance and audit-trail thinking that AI procurement now demands. For public-sector work, that positions us as a subcontractor, specialized resource, or teaming partner — the firm a prime brings in when the requirement calls for AI depth the prime’s bench does not have. Our capabilities describe the technical ground we stand on, and if you are a prime contractor, systems integrator, or departmental team evaluating whether a specialized AI partner fits an upcoming requirement, contact us and we will give you a straight answer — including telling you when we are not the right fit.

AI Procurement in Canada's Public Sector: How It Works