Carney's planned Privy Council Office budget tops that of Trudeau

The Privy Council Office plans $252,265,293 in spending for 2026-27 with 1,246 FTEs, about $521,104 (≈0.2%) more than the $251,744,189 spent in Trudeau’s final full year. The plan targets headcount reduction to 1,145 by 2028 (≈8.1% decline from 1,246) and budgets falling to $247,187,902 in 2027 (-$5.08M, -2.0%) and $239,747,370 in 2028 (-$12.52M, -5.0% vs 2026). Measures to cut costs include flattening the executive structure, automating Prime Minister correspondence, digitizing Cabinet and messenger services, reducing HR/Finance/IT roles, discontinuing select functions, and increased use of AI and procurement streamlining.

Analysis

This is a classic operational pivot: a short-to-medium term capex spike for software, cloud and integration services followed by a sustained decline in recurring headcount-driven spend. Expect an early procurement wave focused on content management, records/dockets, identity and secure cloud hosting — winners capture 12–24 months of implementation budgets, then face a smaller ongoing SaaS/maintenance revenue stream.

Middle managers, temporary contract pools and business-process headcount are the structural losers: automation reduces repeat hiring for HR, finance and messenger functions while creating a one-time demand surge for change-management, migration and security audits. That dynamic favors large systems integrators and enterprise software vendors with existing government credentials; small local integrators without scale face margin pressure and consolidation risk over 2–3 years.

Key tail risks: a high-profile data breach or AI-driven error would pause procurement and trigger audits, reversing momentum within weeks to months; political pushback or labour disputes can slow rollouts, turning projected savings into multi-year programs. Near-term catalysts to watch are formal RFPs/award notices (within 3–9 months) and supplier quarterly commentary that shifts revenue from professional services to subscription line items (visible within 4–8 quarters).

Consensus complacency will be on two fronts: investors may underprice the implementation risk and overprice the long-term revenue base for small integrators. The more durable and underappreciated opportunity is incumbent enterprise content and records-management vendors plus cybersecurity suppliers, which convert one-time program spending into sticky, higher-margin recurring contracts if they win initial rollouts.

Key Decisions for Investors

• Long OTEX (OpenText) — 12–24 month horizon. Rationale: enterprise content/records management is the logical anchor for digitizing cabinet docs; expect outsized contract flow and sticky maintenance revenue. Position sizing: 2–4% portfolio, consider a 6–12 month call spread to cap downside and amplify upside (target 20–35% nominal upside vs 10–15% downside if procurement stalls).
• Long PLTR (Palantir) — 9–18 month horizon via limited-risk options. Rationale: analytics/secure gov cloud capabilities are in scope for AI-driven coordination; winning initial pilots can lead to multi-year deployments. Trade: buy 12–18 month call spreads to target ~2:1 upside/downside given political/implementation risk.
• Pair trade — Long OTEX / Short RHI (Robert Half) — 12–24 months. Rationale: front-loaded tech spending benefits content/cyber vendors while digital automation suppresses demand for staffing/temporary placements in affected public-sector functions. Target asymmetric payoff: net long exposure to software with a modest short in staffing to hedge macro risk (rebalance on each procurement announcement).
• Event trigger rules: take partial profits on software winners after first major procurement award (likely within 3–9 months); cut positions by 50% if a data-security incident or formal parliamentary audit delays contracts beyond 12 months.