Thought Leadership · 23 April 2026
Procurement Patterns for Emerging Connectivity — Why Traditional RFT Fails for LEO Transitions
The procurement models that work for established telecommunications services fail when applied to LEO-based connectivity transitions, because the commercial structures, risk profiles, and integration requirements are fundamentally different from the commodity telecommunications purchasing that most government procurement frameworks assume.
Traditional telecommunications procurement operates on the assumption that connectivity is a utility service with established suppliers, known service levels, and standardised commercial terms. The procurement process asks suppliers to bid on a defined scope, with evaluation focused on price comparison for equivalent services. This model works when the market offers mature products with predictable performance characteristics and when the buyer's requirement is for connectivity as a standalone utility.
LEO transition procurement operates in a different context. The suppliers are establishing new service offerings with evolving capability profiles. The technology integration requirements vary significantly between constellation providers and between direct-to-device and traditional satellite architectures. The commercial models range from traditional service contracts to outcome-based structures that tie payment to operational performance. Most critically, the value to the infrastructure operator depends on how well the connectivity integrates with existing operational technology and asset management systems — an integration challenge that no telecommunications supplier can address without deep understanding of the client's operational context.
The procurement alternative that addresses these characteristics structures the engagement in phases. The first phase is a strategic assessment — a fixed-fee advisory engagement that produces a client-specific transition strategy covering what to change, why, when, and what it costs to get wrong. The second phase is the procurement architecture — a fixed-fee engagement that converts the strategy into procurable commercial structures, including market approach, evaluation framework, commercial model, and contractual architecture. The third phase is the market engagement. The fourth phase is the systems integration and programme management — a retainer engagement covering delivery and operational transition.
This phased approach recognises that LEO transition procurement is not a supplier selection exercise but an asset management and commercial architecture challenge that requires independent, outcome-oriented advice before the market engagement begins. Organisations that attempt to procure LEO connectivity through traditional RFT processes will receive supplier proposals optimised for the supplier's commercial interests rather than the client's operational outcomes.
The infrastructure operators that recognise procurement as a strategic capability — not just a compliance process — will shape the commercial architecture and supplier relationships that convert connectivity from a cost centre into a measurable operational capability.
More insights
The Australian LEO Constellation Landscape for Infrastructure Operators
Security of Critical Infrastructure Act — Connectivity Operator Obligations
The Security of Critical Infrastructure Act (SOCI) applies to connectivity providers serving critical infrastructure sectors. Obligations include mandatory cybersecurity risk management, cyber incident reporting, and enhanced protections for systems of national significance. Infrastructure operators who depend on satellite connectivity for operational technology systems are within scope as connectivity becomes a critical dependency.
Universal Outdoor Mobile Obligation — Commencement 1 December 2027
The Universal Outdoor Mobile Obligation takes effect 1 December 2027. Telstra, Optus, and TPG must deliver outdoor voice and SMS across approximately five million square kilometres of new coverage through direct-to-device satellite partnerships. The operational layer above each satellite partnership — coverage verification, device compatibility, customer support, emergency services integration, regulatory reporting — is the carrier's responsibility, not the satellite operator's.