Leveraging the Indigenous Business Set-Aside to Win $25M+ Professional Services Contracts via TBIPS and SBIPS
At a Glance
- The federal government mandates a minimum 5% target for Indigenous procurement, unlocking over $1.24 billion annually.
- Major IT and professional services vehicles like TBIPS and SBIPS frequently use voluntary and conditional set-asides.
- Winning requires a genuine joint venture with 51% Indigenous ownership and 33% Indigenous work content.
- Proper registration in the Indigenous Business Directory (IBD) is a non-negotiable first step.
This article explains how professional services firms can structurally align with the Procurement Strategy for Indigenous Business (PSIB) to secure massive, multi-year federal contracts through major supply arrangements.
If you want to know How to Win Government Contracts Canada, you need to understand the rapidly shifting dynamics of federal Government Procurement. Chasing open Government RFPs for IT and professional services is notoriously competitive, often pitting you against dozens of massive global integrators. Navigating these Government Contracts without a specific differentiator is a fast track to burned bid budgets. That is exactly where the Indigenous business set-aside comes in. By forming a compliant, highly capable joint venture under PSIB rules, you can compete in a much smaller pool for multi-million dollar TBIPS and SBIPS call-ups. Our AI platform, Publicus, helps teams Save Time on Government Proposals by aggregating these exact types of set-aside opportunities and qualifying them instantly.
The 5% Mandate: A Fundamental Shift in Federal Spending
Here's the thing: the federal government is legally bound to change how it buys. Indigenous Services Canada (ISC) clearly states that the Government of Canada uses the Procurement Strategy for Indigenous Business (PSIB) to limit competition for certain contracts exclusively to businesses listed in the Indigenous Business Directory (IBD) [2]. More importantly, the government must meet a minimum requirement that at least 5% of the total value of all federal contracts be awarded to Indigenous businesses [2].
This is not a token effort. According to ISC data from 2023-24, the federal government awarded over $1.24 billion to Indigenous businesses, effectively exceeding the 5% target and hitting 6.1% of eligible contracts [1]. About 40% of that massive spend was awarded directly through set-aside opportunities under PSIB [1]. For companies operating in the Task-Based Informatics Professional Services (TBIPS) or Solutions-Based Informatics Professional Services (SBIPS) spaces, this represents an enormous market pivot. A mid-sized government department might spend its entire annual external IT budget through these vehicles. If they need to hit their 5% target, dropping a $25 million SBIPS requirement into a PSIB set-aside is the most efficient way to do it.
The Three Types of PSIB Set-Asides
Understanding how procurement officers apply these rules is the first step to winning the work. The Office of the Procurement Ombud states there are three distinct types of set-asides under PSIB: mandatory, voluntary, and conditional [3].
A mandatory set-aside applies when a procurement is destined for an area, community, or group where Indigenous people make up at least 51% of the population, and the Indigenous population will be the recipient of the good or service [3]. While this is common for construction or regional services, large-scale IT professional services under TBIPS usually fall under the other two categories.
Voluntary set-asides happen when federal departments decide to limit the competition entirely to Indigenous businesses. Procurement officers do this if they are confident that Indigenous business capacity exists, relying on the Indigenous Business Directory to assess the market [3]. If they can ensure operational requirements and best value are met, they lock the RFP down to IBD-registered firms.
The catch? Sometimes departments are unsure if the Indigenous capacity is actually there for a massive, complex IT modernization project. When capacity is uncertain, they use a conditional set-aside [3]. In this scenario, the bid goes out to the open market, but if two or more Indigenous bids come in and meet all the technical requirements, the procurement automatically converts to an Indigenous-only competition. Non-Indigenous bids are completely discarded. If you have a highly qualified Indigenous-led joint venture, conditional set-asides are your prime target.
Structuring Your Joint Venture for TBIPS and SBIPS Success
You cannot simply slap a logo on a proposal and call it an Indigenous bid. The rules are strict, and the Office of the Procurement Ombud has increasingly emphasized compliance, oversight, and recourse mechanisms to prevent "fronting" [5].
To qualify for PSIB opportunities, the base business eligibility requires the bidding entity to be at least 51% owned and controlled by Indigenous peoples [3]. This means whether it is a standalone firm or a joint venture, the Indigenous partners must hold actual voting and operational control. (As a quick aside: we see so many firms try to paper over this requirement with vague agreements, only to be disqualified during the technical evaluation. Do not risk it.)
The 33% Content Requirement
Beyond ownership, there is a strict delivery requirement. At least 33% of the total value of the work must be performed by the Indigenous business or Indigenous subcontractors [3]. For a $25 million TBIPS contract spanning five years, that means over $8.2 million of the actual billable work must flow through Indigenous resources or firms.
How do successful industry players manage this on complex SBIPS deals? They design the resourcing model from day one to hit this target comfortably. Instead of scattering token roles, they allocate entire work packages to the Indigenous partner. Think cybersecurity auditing, data migration, user acceptance testing, or organizational change management. By carving out specific, high-value technical scopes, you ensure the 33% threshold is met even as the project flexes and changes over time [4].
Furthermore, this needs to be a long-term framework. Winning these deals requires a Master Teaming Agreement that explicitly covers PSIB compliance clauses, profit-sharing, intellectual property rights, and dispute resolution. Ad-hoc teaming days before a major TBIPS call-up simply does not work.
Proving Capacity and Influencing Procurement Strategies
Procurement officers are inherently risk-averse. When staring down a high-stakes, multi-million dollar IT project, their biggest fear is project failure. If you want them to use a voluntary PSIB set-aside, you have to prove that your Indigenous-led consortium has the technical depth to deliver without missing a beat.
This requires proactive, pre-RFP engagement. You need to meet with CIOs, program owners, and procurement authorities well before the RFP drops. Educate them on how structuring their upcoming TBIPS requirement as a PSIB set-aside will instantly solve their 5% mandate gap [1]. Show them concrete delivery models. Demonstrate exactly how your joint venture maintains 51% control and 33% content while bringing the technical firepower of a major systems integrator [4].
You also need to tailor your capabilities to the specific TBIPS/SBIPS categories. Map your Indigenous talent to high-demand roles like Application Architects, Business Analysts, and IM/IT Technical Authorities. Show an end-to-end capability where governance ensures Indigenous oversight across the entire solution lifecycle.
Registration and Audit Readiness
All of your relationship-building is useless if your paperwork is not perfect. ISC emphasizes that there are no restrictions on the location, size, or type of business that can register for the IBD, but it is the definitive tool procurement officers use [1]. Make sure the Indigenous entity is registered and constantly updated.
Moreover, expect tighter scrutiny. ISC is actively collaborating with Indigenous partners to transfer the administration of the IBD so Indigenous peoples can set their own criteria for qualifying businesses [1]. Vendors relying on a set-aside should expect much stricter attention to how status is verified. Keep pristine records of ownership documents, timesheets distinguishing Indigenous versus non-Indigenous contributions, and subcontract agreements.
How Publicus Accelerates Your Strategy
Finding these specific set-aside opportunities across massive supply arrangements is incredibly tedious. Publicus is an AI platform built specifically for Canadian government contracting. Our system aggregates RFPs from various federal, provincial, and municipal sources, allowing you to instantly filter for PSIB, TBIPS, and SBIPS tags. We use AI to qualify these opportunities against your joint venture's specific capabilities, helping you determine whether you can actually hit that 33% content requirement before you invest thousands of dollars into a bid. By automating the discovery and qualification phases, Publicus helps your team save time on proposals, letting you focus on writing winning technical responses.
The Road Ahead for Professional Services Procurement
The convergence of the 5% mandate and massive IT vehicles like TBIPS and SBIPS is creating a generational opportunity for Indigenous businesses and their non-Indigenous technical partners. As federal departments scramble to hit their targets, the volume of voluntary and conditional set-asides will only increase.
However, the days of hollow joint ventures are over. Recent reviews by the Office of the Procurement Ombud highlight the critical need for verifiable capacity and strict compliance [5]. Firms that invest in genuine partnerships, build real technical capacity within Indigenous communities, and maintain audit-ready records will dominate this space for the next decade.
Frequently Asked Questions
What is the difference between a voluntary and conditional PSIB set-aside?
A voluntary set-aside restricts bidding exclusively to Indigenous businesses from the start, because the department knows capacity exists. A conditional set-aside opens the bid to everyone, but converts into an Indigenous-only competition if two or more compliant Indigenous bids are received.
Does an Indigenous Joint Venture need to be 100% Indigenous-owned?
No. Under the federal guidelines, a joint venture must be at least 51% owned and controlled by the Indigenous partner to qualify for PSIB opportunities. The non-Indigenous partner can hold up to 49%.
How is the 33% Indigenous content rule calculated in professional services?
It is calculated based on the total value of the work performed. At least 33% of the contract's dollar value must be delivered by the Indigenous prime contractor or valid Indigenous subcontractors. This is heavily scrutinized via timesheets and billing records.
Is registration in the Indigenous Business Directory (IBD) mandatory?
Yes. Procurement officers use the IBD to verify eligibility and assess market capacity. If your business or joint venture is not registered in the IBD, you cannot bid on a PSIB set-aside contract.