Guides

How to Select SD-WAN for a Growing Business

Learn how to select SD-WAN for reliable multi-site performance, stronger security and continuity, with the right access, support and controls in place.

9 min readUpdated August 2026

A new branch opening, a cloud migration, or persistent application complaints often exposes the limits of a traditional WAN. Knowing how to select SD-WAN starts with defining the business problem it must solve, not simply comparing appliance features.

What SD-WAN is really for

Sending every site's traffic back through a head office firewall can add delay, create a single point of failure and make troubleshooting needlessly slow. For UK businesses, the right choice should improve application performance, maintain secure connectivity when a circuit fails, and give IT teams clear operational ownership.

SD-WAN is not a replacement for good connectivity. It is the intelligence layer that makes the best use of it.

Start with your sites, applications and risks

Before approaching providers, map what happens at each location. A 10-person sales office using cloud CRM, Teams and VoIP has different requirements from a warehouse running scanners, CCTV and a local line-of-business system. A site with guest Wi-Fi, payment terminals and remote support access needs appropriate separation and security controls.

Identify the applications that are genuinely business-critical, who uses them and where they are hosted. This might include Microsoft 365, cloud PBX, hosted desktops, SaaS platforms, private cloud workloads and on-premises systems. Then establish what poor performance looks like in practical terms: calls breaking up, delayed transactions, inaccessible files, or employees reverting to mobile hotspots.

This work gives you a basis for prioritising traffic. SD-WAN can recognise applications and apply policies so that real-time voice, video and critical systems take precedence over lower-priority activity. That only helps, however, when the policy reflects how the business actually operates.

Treat the underlying connections as part of the decision

One of the most common mistakes is selecting an SD-WAN platform without first assessing the access available at each site. The overlay can steer traffic around a poor connection or use multiple paths, but it cannot create capacity or resilience where neither exists.

A head office or main data site may need dedicated internet access or a leased line with a clear service level agreement, committed bandwidth and defined repair targets. Smaller sites might be well served by business FTTP paired with a different backup service. In some locations, a secondary circuit from a separate carrier or a 4G or 5G service provides a sensible continuity option.

Ask how the proposed design handles a full circuit failure, not merely a short period of packet loss. Automatic failover should be fast enough that staff can continue working without manual intervention. It is also worth checking whether primary and backup services share the same physical route, exchange or local infrastructure. Two connections do not automatically equal true resilience.

Bandwidth deserves the same scrutiny. Look beyond the advertised download speed. Consider upload demand, peak concurrent users, voice and video use, cloud backup windows, and traffic between sites. A circuit that feels adequate on a quiet Tuesday morning may struggle during a large Teams meeting or an overnight backup.

Choose SD-WAN capabilities that match the operating model

SD-WAN products vary considerably. Some are designed primarily for traffic steering and central management; others include a broader security stack. Neither approach is automatically better. The sensible choice depends on your existing firewall strategy, internal skills, compliance obligations and appetite for managing separate services.

At a minimum, assess how the solution monitors link quality. It should make routing decisions based on latency, jitter and packet loss, not just whether a connection is technically up. For voice and video, that distinction matters. A live circuit with severe packet loss can be as disruptive as an outage.

Application-aware routing is equally valuable. The platform should identify important applications reliably and apply policy by application, user group or traffic type where needed. Avoid a design that relies on broad rules which become difficult to maintain as services change.

For many organisations, secure local internet breakout is a major reason to adopt SD-WAN. Rather than sending all cloud traffic back to a central site, branches can access approved cloud services locally under consistent policy. The trade-off is that security must be applied consistently at every location. Consider whether the provider offers integrated next-generation firewall functions, secure web filtering, intrusion prevention and segmentation, or whether these will be delivered through existing security tools.

Make security and segmentation explicit

Connectivity and security decisions should not be made separately. When branches connect directly to the internet, the controls protecting users, devices and data need to be clear.

Ask where security policies are managed, how changes are approved and how quickly threats can be investigated. A central portal is useful, but it is not the same as a managed security service. Establish who is responsible for monitoring alerts, applying software updates, maintaining firewall policies and responding to incidents outside office hours.

Segmentation is especially important for multi-site organisations. Corporate devices, guest Wi-Fi, voice services, operational technology and third-party access should not all share the same level of network trust. A suitable design can isolate these traffic types while still allowing the connectivity each one needs.

SD-WAN should also fit alongside endpoint, identity and email security. It is one part of a wider defence model, not a standalone answer to cyber risk. This matters where staff access cloud services from offices, home networks and mobile connections.

Ask operational questions before comparing prices

A lower monthly price can conceal a design that transfers too much responsibility to your IT team. When comparing proposals, establish exactly what is included in deployment, monitoring, support and ongoing change.

A managed service should set out the practical details:

  • who designs the WAN and validates the chosen circuits;
  • whether configuration, installation and cutover are included;
  • what monitoring is provided for devices, tunnels and underlying access;
  • how faults are triaged when the issue could be the SD-WAN, ISP, local network or cloud service;
  • the helpdesk hours, escalation process and service level commitments; and
  • how moves, adds, changes and security policy updates are requested and charged.

Match ownership to your team's skills

For a business with limited in-house network expertise, one accountable UK team can remove a great deal of friction during an incident. Larger IT teams may prefer more direct control, but should still expect clear demarcation between their responsibilities and the provider's.

Reporting should be useful to both technical and business stakeholders. Look for visibility of application performance, circuit health, bandwidth use, outages and failover events. The aim is not a dashboard for its own sake. It is evidence that supports capacity planning, supplier conversations and decisions about future sites.

Test the proposed design against failure scenarios

A good selection process includes a design workshop or proof of concept for complex estates. Do not limit testing to whether a branch can browse the web through the new device. Test the failures that would affect the business.

What happens if the primary fibre circuit fails during a customer call? Can voice traffic move to the backup path without a noticeable drop? What happens if a cloud provider experiences a regional issue, or if latency rises on one broadband circuit? Can the platform steer selected traffic over an alternative path while keeping lower-priority traffic controlled?

Also test day-two tasks. A service can look impressive in a demonstration and become burdensome when a new site opens, a VLAN is added or a supplier requires restricted access. Check how policies are documented, whether changes can be audited and whether the configuration can be recovered quickly after a device replacement.

Build the commercial case around continuity, not boxes

The right SD-WAN proposal should make its commercial assumptions visible. Separate the cost of hardware, licences, circuit installation, ongoing connectivity, security services, management and support. Confirm contract terms, renewal pricing, bandwidth upgrade options and any charges for early termination or site moves.

Then measure cost against the avoided impact of outages and poor performance. If a branch loses access to cloud applications for half a day, what does that mean for sales, service delivery, payroll or customer confidence? If IT spends hours coordinating several suppliers during every fault, that also has a cost.

Avoid buying capacity and features that will never be used. Equally, do not save money by choosing a single-path design for a site that cannot afford to be offline. The appropriate level of resilience depends on the function of the location and the workable fallback process.

Select a partner that can support the next change

Your network is likely to change during the life of an SD-WAN agreement. Sites move, more staff work remotely, cloud applications change and security requirements tighten. Select a provider that will revisit the design as those conditions evolve, rather than treating installation as the end of the relationship.

The best choice is usually the one that combines appropriately resilient access, application-aware SD-WAN routing, clear security ownership and responsive support. Start with the disruption your business cannot tolerate, design for it deliberately, and make sure the people responsible for keeping the network running are known before the first site goes live.

Share

Connectivity enquiry · How to Select SD-WAN for a Growing Business

Talk to a connectivity specialist

Free, no-obligation advice and a same-day quote for your postcode.

› let's talk

Ready to hand off the IT headaches?

Leave your details and a London-based engineer will call you back — usually within one business hour. No sales scripts, no obligation.

020 3355 1151 [email protected]

Mon–Fri, 8am–6pm · 24/7 for managed clients

Or explore Managed IT →

› quick callback

No spam. We'll only use your details to respond to your enquiry.