Connectivity / Buyer guide

How to Choose an SD-WAN Provider: A Guide for IT Leaders

A practical SD-WAN provider evaluation guide for businesses in the USA and Canada, from the first requirements conversation to the pilot that proves the design.

A branch loses its primary internet connection during a customer call. The network dashboard shows the backup link is available. The call still drops.

Use that scenario in your next SD-WAN provider discussion. Ask the provider to explain what happens to the call, which traffic gets priority, what the support team sees, and who owns the incident. The answer tells you more about the proposed service than a list of features.

For IT leaders comparing managed SD-WAN services, the buying decision reaches beyond equipment. It includes the connections beneath the network, the security controls around it, and the people responsible when something goes wrong. This guide helps you turn those responsibilities into requirements providers can answer.

What SD-WAN does, and what your provider must explain

Software-defined wide area networking, or SD-WAN, applies software-based policies to traffic across wide area network connections. The underlying connectivity can include internet and private network services. Cisco’s SD-WAN overview explains this separation between network management and the transport carrying the traffic.

That distinction matters when buying. An SD-WAN proposal still depends on the access services available at each location. Ask providers to separate the SD-WAN platform, connectivity, security services and operational support in their scope.

For a business with sites in the USA and Canada, require an address-level service check. A national coverage claim should lead to a confirmed installation plan for each office, warehouse or branch. Our business internet evaluation guide covers that part of the decision.

Start the comparison with applications and business impact

Write down the work the network must support: customer calls, payment transactions, inventory updates, video meetings or access to cloud applications. Then identify where that work is being interrupted and what acceptable performance would look like.

For example, a contact center may need voice traffic protected when other users are transferring large files. A warehouse may prioritize access to its order system.

Ask each provider how it identifies those applications, applies priority policies and measures the result. Agree which measures matter, such as delay, variation in delay or packet loss, and where they will be measured. Avoid accepting a performance target without a measurement method.

If your project includes a phone or contact center migration, bring the UCaaS and CCaaS requirements into the network brief before either provider finalizes its design.

Define what “managed SD-WAN” includes

A managed service needs a written division of responsibility. Ask who configures application policies, approves changes, applies updates, replaces failed equipment and coordinates with the internet carrier. If your team retains some of that work, document the shared responsibilities.

Give each shortlisted provider the same incident: a business application is slow, both connections are up, and the application vendor says its service is healthy. Ask who investigates first, what evidence is collected and who keeps your team informed.

The MEF 70.2 SD-WAN service framework describes service attributes agreed between a buyer and provider. You can apply that principle to your evaluation: turn a broad promise into a defined service characteristic and an agreed responsibility.

Test failover and specify the security scope

A second connection deserves its own scrutiny. Ask whether the proposed access paths share physical infrastructure, what capacity the backup provides, and which applications remain usable during an outage. If cellular backup is proposed, confirm coverage at the installation point and review its usage limits.

Make failover part of the pilot. Observe an active call, a new call and a business transaction when the primary connection fails. Test the return to normal service as well. Record interruption, recovery and any action required from employees.

For security, require an itemized scope. Identify which firewall, traffic inspection, segmentation, identity and logging functions are included, separately licensed or delivered by another service. Have the security team review how branch traffic reaches cloud applications and where policies are enforced.

When a proposal combines SD-WAN with secure access service edge (SASE), ask for a diagram showing the network and security components. Mplify’s SASE framework treats connectivity and security functions as parts of the service agreement. Use your cybersecurity requirements to check the proposed coverage.

Use one SD-WAN provider comparison checklist

Give every provider the same checklist. Record the evidence beside each answer and mark assumptions as unresolved. An attractive demonstration should not erase a missing installation detail or an unclear escalation route.

Evidence to collect before choosing a provider
CompareAsk for
Application performanceA demonstration using your critical workflows, with agreed measurements.
Site connectivityConfirmed availability, installation dependencies and access services for each address.
FailoverObserved behavior during connection failure and recovery, including backup capacity.
SecurityIncluded controls, extra licenses, log access and policy ownership.
Support and SLACoverage hours, escalation ownership, measurement boundaries and exclusions.
Total costComparable setup, recurring, usage, support and exit assumptions.
MigrationA pilot, acceptance criteria, rollback plan and named change owners.

Agree your priorities before scoring proposals. A site with limited local IT support may put more weight on replacement hardware and incident coordination. Another may prioritize application visibility or control of policy changes. Record why a criterion matters to your business.

Compare total cost and the SLA against the same scope

Build an SD-WAN cost comparison over the same evaluation period and site count. Include equipment, licenses, access circuits, installation, security subscriptions, managed support, backup usage and any temporary overlap with existing contracts. Ask what changes the price when a location opens, moves or closes.

Read the service-level agreement (SLA) alongside the support scope. Identify what is measured, where measurement begins and ends, the exclusions, and how an incident is reported. Distinguish a commitment to respond from a commitment to restore service.

A lower monthly figure is useful only when the proposals cover comparable work. Keep unpriced dependencies and optional services visible so the buying team can see what remains outside the quote.

Prove the migration plan before rolling out every site

Choose pilot locations that reflect the conditions you need to test. Include a site with demanding applications or limited connectivity if that represents a meaningful part of your operation. Agree success criteria before installation.

The acceptance plan should name who checks application behavior, security policies, monitoring access and support handoffs. Specify the change window and the conditions for rolling back. Keep current carrier renewal dates and new circuit installation dependencies in the same plan.

Before approving the wider rollout, review the pilot evidence with the people who will operate the service. Give unresolved issues an owner and a decision date. DuPont Tech Advisor’s SD-WAN and connectivity advisory focuses on preparing these requirements and comparing provider scope around your business need.

Common SD-WAN buying questions

Does SD-WAN replace business internet?

No. SD-WAN manages traffic over underlying connections. Your buying decision still needs to cover internet or private access services, installation, resilience and support.

What should a managed SD-WAN provider include in its proposal?

Ask for site-level connectivity, equipment and licensing, application policies, security scope, monitoring, change responsibilities, support, pricing assumptions and a migration plan. Confirm what is included rather than assuming a standard package.

How should we compare SD-WAN providers across the USA and Canada?

Use the same business requirements for each provider, then verify service availability and delivery assumptions at every address. Record support hours, carrier coordination, commercial currency and implementation ownership in each proposal.

Do we need a finalized budget before building a brief?

No. Start with the services involved, the business problem, the outcome you want and decision timing. DuPont Tech Advisor’s free brief tool has no minimum budget requirement.

Your next step

Give providers a brief they can answer.

Before you request another proposal, put your business need into a working brief. Select SD-WAN, business internet, multi-site connectivity or any other relevant service, describe the change you need, and record your desired outcome and timing.

Build and download your brief free. No email required. Your answers stay in your browser; creating a brief does not submit an enquiry.