How Architecture Firms Win $10M+ Federal Design Contracts Through TBIPS & Standing Offers
Here's what most architecture firms don't realize: you can't actually win a $10 million design contract through TBIPS. Not in one go, anyway. The Task-Based Informatics Professional Services framework has tier caps—$3.75 million for Tier 2 task authorizations—and it's technically meant for IT professional services, not architecture[6]. Yet mid-sized engineering and design firms are routinely generating $10 million or more in federal revenue through these vehicles. How? They're treating government procurement like a volume business, aggregating multiple task authorizations across departments and years rather than chasing single massive RFPs[1][2].
This approach fundamentally changes how you pursue government contracts in Canada. Instead of spending months crafting 200-page proposals for open competitions on CanadaBuys with 5-10% win rates, qualified suppliers compete against just 15-20 pre-approved peers on rapid-turnaround solicitations, achieving win rates of 30-40%[1][2]. The government RFP process guide traditionally emphasizes one-off bids. But the real money—the predictable, scalable revenue—comes from understanding how to find government contracts Canada actually procures through frameworks, then systematically working those channels to simplify government bidding process requirements and save time on government proposals[1].
The catch? Pre-qualification. And a willingness to rethink what "winning" looks like when government procurement thresholds and RFP automation Canada mechanisms favor aggregation over individual awards.
Understanding the Framework Landscape
Standing Offers and Supply Arrangements are non-binding pre-qualification mechanisms. The government solicits bids through a Request for Standing Offer (RFSO), evaluates suppliers against specific criteria, then establishes a roster of approved vendors[6][8]. No contract exists until a department issues a "call-up"—an actual purchase order or task authorization against the standing offer[3][6]. Think of it as getting on an approved supplier list. You still compete for individual pieces of work, but only against others on that list.
TBIPS technically sits outside architecture's traditional scope. Public Services and Procurement Canada designed it for informatics and IT professional services[6]. But here's where it gets interesting for design firms: several TBIPS streams overlap with architecture-adjacent work. Enterprise architecture. Cloud infrastructure design. Application services for building information modeling systems. Project management for major capital projects[1][2]. Firms with technical depth in these areas qualify under IT streams, then pivot that access into design-heavy engagements.
The framework includes three main types of standing offers: National Master Standing Offers (NMSO) used across all departments, Regional Master Standing Offers (RMSO) for specific geographic areas, and Departmental Individual Standing Offers (DISO) for single-department needs[1]. PSPC runs TBIPS qualification cycles three times annually—March, June, and September—where firms submit evidence of prior experience exceeding $1.5 million, certifications, and detailed capability statements[1][2].
What most don't realize: the 2018 shift from preset-pricing Standing Offers to merit-based Supply Arrangements changed the economics. The old model compressed margins through rate competition. The new approach emphasizes technical expertise and past performance over low bids, favoring specialized firms that can differentiate on capability rather than price[1].
The $10 Million Math
No single TBIPS task authorization will hit $10 million. Tier 1 caps at $3.75 million. Tier 2 starts above that threshold but still faces approval hurdles for truly large amounts[1][2]. So how do firms reach eight figures?
Volume and velocity. A mid-sized systems integrator—whose model applies directly to architecture firms pursuing design-build or infrastructure work—might bid 8-12 opportunities per quarter across multiple TBIPS streams and departments[2]. Converting at 30-40% win rates, that's 2-4 task authorizations per quarter. At $400,000 to $1.2 million each for discovery and initial design phases, you're looking at $800,000 to $4 million in annual revenue just from Tier 1 work[1][2].
Then you orchestrate the lifecycle. Use TBIPS for the pilot or design phase ($400,000-$1.2 million). Transition to SBIPS—the Solution-Based Informatics Professional Services framework—for implementation ($5-8 million). Secure a Standing Offer for ongoing operations and maintenance ($100,000-$150,000 monthly)[1][2]. One department, three vehicles, three to four years. That's $10 million from a single client relationship, all stemming from an initial TBIPS qualification.
Real examples from procurement data: one firm secured seven task authorizations totaling $9.3 million in 18 months. Another generated $12.8 million over four years by qualifying in aligned streams and systematically bidding opportunities as they appeared[1][2]. These aren't unicorns. They're firms that treat framework qualification as infrastructure, not individual opportunities.
Strategic Qualification and Positioning
Qualification isn't passive. PSPC evaluates applications against specific criteria: demonstrated experience above threshold amounts, professional certifications relevant to the stream, past performance evidence, and resource capability[1][2]. For architecture firms, this means carefully selecting which 2-3 TBIPS streams align with your actual depth.
Don't shotgun your application across every category. The Federal Contractors Program adds complexity for larger firms. If you employ 100 or more people, you must sign an Agreement to Implement Employment Equity (AIEE) when bidding. Once any contract or call-up hits $1 million (including taxes), ongoing obligations activate[3]. These aren't cumulative across contracts—each individual call-up of $1 million or more triggers compliance[3]. Failure to maintain compliance risks loss of future contract eligibility[3].
The practical implication: if your firm sits near the 100-employee threshold, anticipate the administrative overhead before qualification. If you're well above it, ensure your HR systems can demonstrate ongoing employment equity compliance, because multiple $1 million+ task authorizations will be the goal.
Stream selection matters enormously. Application Services sees heavy competition from established IT firms. Project Management attracts generalists. Enterprise architecture and specialized infrastructure streams have fewer qualified suppliers with genuine depth[1]. For architecture firms, focus on streams where your design expertise translates to genuine differentiation—infrastructure modernization, capital project planning, complex systems integration touching the built environment.
Your capability statement becomes your primary sales document. Departments search the Canadian Public Servants Procurement Service (CPSS) for qualified suppliers when issuing task authorization requests. They filter by stream, region, and capability keywords. If your profile emphasizes generic IT delivery, you blend into the pack. If it highlights specialized design expertise—say, heritage building modernization or mass timber federal facilities—you stand out when the right opportunity appears[1].
Competing Within the Framework
Once qualified, the competitive dynamic shifts dramatically. Departments must invite at least two suppliers from the standing offer or supply arrangement roster, though typical practice involves 10-20 invitations for significant work[1]. You receive a notification through CPSS or directly via email. The RFP is short—20 to 40 pages instead of 200-plus. Response time might be as brief as five days[1].
This compresses the sales cycle but demands readiness. You can't spin up a detailed technical proposal in five days without preparation. Successful firms maintain proposal libraries: pre-written technical approaches for common scenarios, CVs for senior resources formatted to government requirements, past performance narratives already drafted, pricing models ready to adapt[1][2].
Evaluation criteria skew heavily toward technical merit. Where open RFPs might weight price at 40-50%, framework competitions often emphasize technical approach and past performance at 60-70% or higher[1]. This rewards depth over cost-cutting. Your proposal should lead with senior resource commitment—actual principals or technical leads, not junior staff—and demonstrate domain expertise specific to the requirement.
Value-based pricing outperforms low-bidding in this environment. If the evaluation is 70% technical and 30% price, dropping your rate 10% to undercut competitors gains you minimal points while sacrificing margin. Proposing a senior architect with 20 years of federal facility experience gains you significant technical points and justifies premium pricing[1][2].
The initial win matters disproportionately. Deliver exceptionally on your first $400,000 task authorization. That performance becomes past performance for the next bid. It builds relationship capital with the project authority. And it positions you for follow-on work—expansions, related phases, referrals to other departments[1]. One firm turned a $450,000 pilot into a $1.9 million expansion with the same department, then secured a $2.2 million contract from a different department based on the reference, ultimately generating $4.57 million from an initial qualification and strong delivery[1].
Aggregation Strategies Across Departments
Federal procurement is fragmented by design. Each department has its own project authorities and budgets. A Standing Offer or Supply Arrangement qualification with PSPC grants you access to compete across all of them. This creates a portfolio opportunity that single-department strategies miss.
Monitor CanadaBuys systematically, but don't rely solely on public postings. Many task authorization requests go directly to qualified suppliers via CPSS without broad advertisement[1]. Maintain relationships with procurement officers and technical authorities across multiple departments. When your name comes up in their CPSS search, they're more likely to include you in the invitation if they've met you or seen your work.
Different departments have different fiscal year pressures and project timelines. National Defence might issue requests in Q2 for infrastructure planning. Environment and Climate Change Canada might procure facility design services in Q3. Indigenous Services Canada has distinct needs around remote community facilities. By diversifying across departments, you smooth revenue and increase total opportunity volume[1][2].
The Federal Contractors Program thresholds apply per contract or call-up, not cumulatively[3]. This means you can accumulate multiple $900,000 task authorizations across departments without triggering the $1 million compliance requirement—though obviously aiming below thresholds to avoid compliance isn't a sustainable growth strategy. Better to build the compliance infrastructure and pursue the larger opportunities aggressively.
Requalification is ongoing. Standing Offers have firm periods—the mandatory timeframe during which the supplier must honor the offer—and optional extension periods[5]. TBIPS operates on multi-year cycles, but you'll need to requalify periodically and certainly when new framework versions launch. Treat this as maintenance, not an obstacle. Your existing task authorization performance becomes your strongest requalification evidence.
Practical Implementation for Architecture Firms
Start by auditing your existing federal work against TBIPS and Standing Offer categories. Do you have $1.5 million or more in relevant experience? Can you document it with client references, project summaries, and outcomes? If your work has been primarily provincial or municipal, consider whether federal departments would accept it as equivalent experience or if you need to build federal credentials first through smaller open competitions.
Assemble your qualification package well before the cycle opens. Capability statements, corporate experience narratives, security clearances if required, financial statements, insurance certificates, professional designations and certifications. PSPC publishes solicitation closing dates; bids submitted after closing are rejected outright[5]. Missing a deadline means waiting months for the next cycle.
Budget for the business development pipeline. Framework access doesn't eliminate BD costs; it shifts them. Instead of expensive proposal development for low-probability open RFPs, you're investing in relationship development, capability marketing, and rapid response infrastructure. Platforms like Publicus aggregate government RFPs from various sources and use AI to qualify opportunities, helping you identify which framework solicitations match your capabilities without manual monitoring. This saves time on the front end—filtering 200 irrelevant postings to find the three where you're genuinely competitive.
Build your team's response capacity. Five-day RFP turnarounds require internal coordination most firms lack. Designate proposal leads. Maintain current CVs for all senior staff in government format. Create technical approach templates for your core service areas. Establish pricing authority and approval workflows so you're not waiting for executive sign-off while the clock runs out.
Track your metrics ruthlessly. Bids submitted, win rate, average task authorization value, time from qualification to first win, revenue per department. The firms generating $10 million through frameworks don't do it accidentally. They measure performance, identify which streams and departments convert best, and allocate BD resources accordingly[1][2].
Looking Forward
PSPC continues centralizing procurement through frameworks. The $8.6 billion federal informatics and IT market increasingly flows through TBIPS, SBIPS, and related Supply Arrangements rather than ad-hoc open competitions[2]. For architecture firms with technical capabilities in infrastructure, this trend creates sustained opportunity—provided you qualify and compete systematically.
Emerging areas offer particular potential. Cloud transformation and data center modernization touch facilities and infrastructure. Cybersecurity requirements for federal buildings drive physical design considerations. Climate adaptation and net-zero mandates affect all capital projects. These aren't purely IT streams; they're interdisciplinary engagements where architecture expertise adds genuine value[1][2].
The framework model rewards consistency and relationship capital over sporadic big wins. A $10 million contract from three departments over four years—built from ten task authorizations, strong delivery, and systematic BD—generates more sustainable revenue than a single $10 million open RFP win followed by years of drought. It's less exciting. It's vastly more profitable.
The question isn't whether architecture firms can win $10 million through TBIPS and Standing Offers. They can't, not in the traditional sense of a single large award. The question is whether your firm can shift from episodic large-bid thinking to systematic framework leverage—qualifying strategically, bidding with volume, delivering excellently, and aggregating results across departments and years. That's how the $10 million actually happens. It just doesn't look like what most expect when they read the headline.