Example requirements
45 UK locations on an existing MPLS and Ethernet WAN, with Azure, Microsoft 365 and several private applications. The buyer wants phased migration, resilient broadband underlay, co-managed SD-WAN, clear change control, measurable failover and no interruption to critical applications.
BT suitability
Plausible candidate with material validation gaps
BT could fit the stated estate, but important architecture or operating-model inputs are missing. Resolve them before treating BT as the preferred route.
The verdict uses 5 detected requirement signals and 6 linked evidence records; it never infers pricing or an undisclosed BT design.
Capabilities matched
- Application-aware managed WAN across a multi-site estate
- Cloud and SaaS connectivity is relevant to BT’s documented network and multi-cloud proposition
What remains unresolved
- The required self-managed, co-managed or fully managed boundary is not stated
- Security/SASE scope is not stated
Architecture considerations
- Model a phased MPLS coexistence and migration rather than assuming a single cutover.
- Map direct cloud/SaaS paths, private connectivity and internet egress per application.
- Translate resilience language into circuit diversity, failover times and application-level acceptance tests.
Security and SASE
- Decide whether the project is WAN-only or requires SASE/SSE security.
- Confirm whether regulated data, audit or residency obligations apply.
Questions BT must answer
- Which BT platform and managed-service components are proposed, and why?
- Which underlay, diversity and failover design applies to each site class?
- Which SASE controls, logs, evidence and data-residency commitments are contractual?
- What is customer-managed, co-managed, BT-managed or excluded?
- What are the implementation sequence, acceptance tests, SLA measures and service credits?
Evidence used
- 1.1: BT's SD-WAN proposition - naming/branding (e.g. BT SD-WAN, Dynamic Network Services, Cloud of Clouds positioning)
Buyer action: Use this confirmed finding as a baseline, then require BT to state how it applies to the proposed design for your estate.
- 1.2: BT's SASE proposition - naming/branding, how BT positions SASE vs SD-WAN vs 'Secure Connect' type offerings
Buyer action: Ask BT to itemise the included licences, security functions and managed-service components.
- 1.9: Full current list of underlying technology partners named on BT's live SD-WAN/SASE page
Buyer action: Require BT to name the proposed technology platform and explain why it fits the estate.
- 2.13: Confirmed unified service desk / support model (updates 2.5)
Buyer action: Confirm the service desk, escalation route and ownership boundary across underlay, overlay and security.
- 3.2: Application performance/QoS management as BT presents it
Buyer action: Document the access type, bandwidth, backup circuit and physical diversity required for each site class.
- 2.3: Network integration - how BT SD-WAN/SASE connects into BT's own MPLS, internet, mobile (EE), and cloud connect services
Buyer action: Document the access type, bandwidth, backup circuit and physical diversity required for each site class.
This is an anonymised example, not a customer case study or quotation. It uses Netify's deterministic assessment rules and the evidence dataset verified 2026-08-30.