BT SD-WAN Use Cases for UK Multi-Site Businesses

Use-case guidance

This page helps determine if your UK multi-site estate warrants BT managed SD-WAN or if a simpler WAN model is more appropriate. Match your estate to the patterns, triggers and scenarios below.

At a glance

On this page

Related pages

Topic	Page
Cost drivers and commercial scope	BT SD-WAN Cost Factors
Managed WAN vs SD-WAN architecture	BT Managed WAN vs BT SD-WAN
Vendor and platform selection	Fortinet vs Meraki
Security tiers and SASE explanation	Secure SD-WAN Explained

Strong-fit indicators

Where SD-WAN is a strong fit

Most businesses that proceed to scoping match two or more of these indicators.

Indicator	What it means	Why it points to SD-WAN
Multiple sites, different requirements	Offices, branches, retail, warehouses each with different bandwidth, resilience, security	Single overlay applies per-site policies without separate infrastructure
Growing cloud / SaaS dependency	Microsoft 365, cloud ERP, Salesforce, Azure, AWS, GCP	Direct internet breakout at each site instead of backhauling to a hub
MPLS / VPLS approaching renewal	Legacy WAN contracts nearing expiry	Natural decision point – phased migration with parallel running
Mixed underlay needed	Not every site justifies a leased line	BTnet + FTTP + EE cellular in one managed overlay
Variable resilience by site	Head offices need failover; smaller branches tolerate simpler models	Different resilience tiers per site, automatic path selection
Integrated branch security	Firewall, IPS or SASE at each branch without separate hardware	Security built into the SD-WAN appliance – NGFW to full SASE by licence tier
Centralised visibility / policy	No single view across estate; changes take days	Single-pane dashboards, centralised policy engine
Application-aware routing	VoIP, video, cloud ERP, POS need priority	Real-time path selection based on application identity

Less-suitable patterns

Where it may be unnecessary

If you match one or more of these, evaluate if SD-WAN overhead is justified.

Pattern	Why SD-WAN may be disproportionate	Consider instead
Single site or <5 sites, simple needs	Managed overlay delivers value at 5+ mixed sites	Standalone broadband or leased lines
All apps on-premises, no cloud planned	Weak case for local breakout and app-aware routing	Traditional hub-and-spoke WAN
Completely uniform estate	No variability to manage across sites	Simpler managed WAN (compare models)
No need for centralised policy	Infrequent changes, no real-time monitoring needed	Individual broadband + VPN
Budget excludes managed service	Per-site licensing + hardware + underlay exceeds appetite	Standalone circuits (cost factors)
Current WAN performing well	No app complaints, no visibility gaps, no change-speed issues	Re-evaluate when triggers emerge

Estate-type fit assessment

Use-case matrix

Find your estate type → check relevance → review evaluation priorities.

Estate type	Relevance	Key indicators	Evaluate first
Multi-branch retail	High	Cloud POS · variable bandwidth · rapid rollout · seasonal sites	Broadband vs leased line · cellular backup · standard vs SASE
Distributed office	High	Microsoft 365 · cloud ERP · VoIP · video conferencing	Bandwidth per site · resilience · security tier · management model
Warehouse / logistics	High	Cloud WMS · IoT · uptime critical · fluctuating bandwidth	Broadband suitability · cellular failover · IoT segmentation
Mixed estate	Very high	Diverse site types · variable requirements · centralised policy	Site-type segmentation · underlay per tier · security per type
MPLS replacement	Very high	Contracts expiring · cloud migration · slow change process	Migration phasing · parallel running · dual-running budget
Healthcare – clinics	High	Cloud patient management · compliance · data sensitivity	SASE for compliance · resilience at clinical sites · data segmentation
Professional services	High	Practice management · client data · video/VoIP · mobile workforce	Security tier · VoIP quality · ZTNA for remote access
Education – campuses	Moderate-High	Cloud learning platforms · student records · guest Wi-Fi · term peaks	Bandwidth by campus · guest isolation · seasonal variability
Hospitality – venues	Moderate-High	Cloud POS · booking systems · guest Wi-Fi · seasonal locations	Guest vs operational segmentation · cellular for seasonal sites
Single-site / two-site	Low	Simple connectivity · no overlay needed	Whether broadband or leased line is sufficient
Data centre-centric	Moderate	Most traffic to on-prem DC · limited cloud · hub-and-spoke	Whether cloud plans justify SD-WAN now

Illustrative profiles

Estate scenario cards

Composite profiles – not customer case studies. Find the pattern closest to your business.

Evaluation signals

Operational triggers

If you recognise 2+ triggers, scoping is likely worthwhile.

Trigger	Signal
MPLS/VPLS renewal	Natural decision point. Plan 6-12 months ahead.
Cloud migration accelerating	Backhauling degrades Microsoft 365, ERP, video. Direct breakout needed.
Estate expanding or changing	New sites, closures, type changes. Cellular enables rapid deployment.
Branch security fragmented	Separate firewalls per site = overhead + inconsistency. NGFW/SASE consolidates.
Change requests too slow	Multi-day lead times. SD-WAN policy engine enables faster deployment.
No visibility across sites	No centralised view of app performance or security events.
App performance complaints	Cloud lag, dropped video, VoIP issues. App-aware routing prioritises critical traffic.
Hybrid working increasing	Branches become key connection points. SASE/ZTNA extends remote access.
Compliance tightening	Consistent, auditable security policy required across all sites.

Triggers matched	Guidance
0-1	May not be a priority. Revisit when more triggers emerge.
2-3	Evaluation likely worthwhile. Use the calculator.
4+	Strong case. Estate has likely outgrown simpler models.

Next-step paths

Decision logic

Readiness

Quote readiness checklist

Having these defined produces a more useful initial scope. You do not need all inputs finalised.

 
• Multiple UK sites (typically 5+)
 
• Approximate site count known
 
• View on circuit type per site or open
 
• Backup circuit requirements identified
 
• Using or moving to cloud/SaaS applications
 
• Management model preference or open
 
• At least one operational trigger identified
 
• Contract term preference (12 / 24 / 36 / 60 months)
 
• Vendor preference (Fortinet / Meraki / open)
 
• Security tier view (standard NGFW vs SASE)
 
• Hub or data centre connections (if any)
 
• Greenfield or migration from existing WAN

Frequently asked questions

Common questions about BT SD-WAN use cases