SD-WAN as a Service: A Buyer's Guide for Mid-Market and Multi-Site Businesses

If you run more than a couple of locations, your network and your network bill have probably drifted apart. Circuits cost more at each renewal, most of your applications now live in the cloud, and the IT team holding it together is two or three people. SD-WAN as a service is what carriers and providers will pitch to fix all three at once.
The pitch arrives as the old model fades. TeleGeography's WAN Manager Survey found that MPLS (multiprotocol label switching), the private circuits most multi-site networks were built on, fell from an average of 82% of sites in 2018 to 22% by late 2025. That survey skews toward large multinationals, so read it as direction rather than a mid-market benchmark.
This guide is for the people who approve the decision and live with it: finance, operations, security, and IT leaders. It does not rank vendors. By the end you should be able to decide four things:
Whether SD-WAN is worth pursuing for your number of sites
Which buying model fits: run it yourself, buy it as a service, or move to SASE
What the full cost looks like, including the parts left out of the quote
What to ask before you sign
What is SD-WAN, and how does it work?
SD-WAN stands for software-defined wide area network. A wide area network (WAN) is the set of connections linking your offices, data centers, and cloud services. Gartner describes SD-WAN as the products that connect branch locations to other company and cloud locations.
Here is how SD-WAN works in practice. A small device at each site connects to two or more circuits: business broadband, dedicated internet, cellular, or an existing private line. Software then does three jobs:
Steers traffic. It identifies each application and sends it over the best circuit available at that moment, so a video call is not stuck behind a file backup.
Fails over. If a circuit degrades or drops, traffic moves to another one, often without users noticing.
Centralizes control. Policies are set once in a central console and pushed to every site, instead of configuring routers one at a time.
Traffic between sites is encrypted, which is why SD-WAN can run over ordinary internet circuits.
Two points matter for buyers. SD-WAN is an overlay, so it rides on circuits you still have to buy. And it is not a complete security stack on its own. For the longer technical version, see our post, SD-WAN explained.
What SD-WAN as a service costs
Pricing varies by provider, site count, bandwidth, and term. We left dollar figures out on purpose: published ranges go stale and rarely match a real quote. What you can control is knowing how the price is built.
Pricing models
Per site. A flat monthly fee per location, usually covering the edge device, software license, and management. Simple to budget, but check what happens when you add, move, or close a site.
Per bandwidth tier. The license price steps up with each site's licensed throughput. A faster circuit can push a site into a higher tier, so circuit and license decisions are linked.
Hardware purchase vs. subscription. Buy the edge devices up front and pay for licenses and support separately, or pay one recurring fee that includes hardware. Purchase means owning equipment that will age; subscription usually includes replacement. How each is treated on your books is a question for your accountant.
Co-managed vs. fully managed. Co-managed means the provider runs the platform and your team keeps access to make changes. Fully managed means the provider designs, monitors, and changes everything, and you submit requests. Fully managed typically costs more and suits teams with no network engineer.
Contract terms to read closely
Whatever term you are quoted, these details shape the real cost as much as the monthly rate:
Term length, automatic renewal, and the notice window to cancel
Price changes during the term or at renewal
Whether circuit terms and SD-WAN terms end on the same date. If not, you can be free of one and locked into the other.
Early termination charges, per site and for the whole agreement
Minimum site or spend commitments if you close locations
The costs buyers miss
Circuits. SD-WAN does not replace connectivity. Each site needs at least two circuits for resilience, and they are often quoted separately.
Installation. Site surveys, shipping, on-site technicians, after-hours cutovers, and running old and new networks side by side.
Licensing renewals. If you buy hardware, licenses and support renew on their own cycle, and advanced security or reporting may sit in a higher tier.
Security add-ons. Firewalling, web filtering, and remote-user access may or may not be included.
Your team's time. Even a fully managed service needs someone to approve changes and manage the provider.
Ask every bidder for the total cost over the full term, by site, with these lines shown separately. That is the only number you can compare.
SD-WAN vs. SD-WAN as a service vs. SASE
These three get blurred in sales conversations. They are three ways to buy overlapping capabilities, not three competing products.
SASE stands for secure access service edge. Joint guidance from CISA and partner agencies describes it as a cloud architecture that combines networking, including SD-WAN, with security services such as firewalling, web filtering, and zero trust network access.
SD-WAN (self-managed) | SD-WAN as a service | SASE | |
What you buy | Devices and licenses that you own and run | A provider-run service for a recurring fee | Networking plus cloud-delivered security on one platform |
Who runs it | Your team | The provider, alone or shared with your team | The provider or your team, depending on the model |
Security | Encryption between sites; other features vary | Depends on the package; often an add-on | Built in, including secure remote access |
Circuits | You source them | Sometimes bundled, sometimes not | Varies; confirm in each proposal |
Cost pattern | Up-front hardware plus renewals | Recurring fee, typically per site | Recurring fee, often per site and per user |
Best fit | Teams with network engineers who want control | Lean IT teams with many sites | Companies also replacing remote access and firewalls |
SD-WAN as a service is also sold as managed SD-WAN, so compare scope, not labels. The industry body Mplify, formerly MEF, publishes a standard that defines an SD-WAN service, a useful reference when two proposals describe the same thing differently.
When each one fits
Running it yourself fits when you have network engineering in-house, want direct control of policy, and are comfortable owning hardware and renewals.
SD-WAN as a service fits when you have many sites, a small team, and want one party accountable for monitoring and changes.
SASE fits when the network change coincides with a security change: retiring a virtual private network (VPN), replacing branch firewalls, or supporting a large remote workforce. If aging VPN hardware is part of your trigger, our post on SSL VPN end of life covers that side.
The SD-WAN vs. SASE question is usually about timing. A staged path is common: SD-WAN first and security services later, ideally on a platform that will not force a second migration.
Is SD-WAN a fit for your business?
SD-WAN for small business: one to five sites
With a handful of locations, the case is narrower. It tends to make sense when:
Downtime at a site stops revenue, as it would at a clinic, store, or warehouse
You pay for private circuits that two internet circuits could replace
No one on staff manages routers and firewalls, and a managed service would take that on
With one or two sites and modest needs, a business-grade firewall with a second internet circuit for failover may do the job for less. Ask a provider to quote both.
Multi-site and mid-market companies
The case strengthens as site count grows, because the problems SD-WAN removes are multiplied: configuring each site by hand, uneven performance between locations, slow setup of new sites, and no single view of the network.
Plan for a project, not a product swap. In TeleGeography's survey, about 63% of enterprises had deployed SD-WAN, and deployments still averaged about a year.
It also matters where your applications are heading. If you are moving workloads between public cloud, colocation, and your own data center, as covered in our post on cloud repatriation, settle that direction first. It changes where your traffic needs to go.
When SD-WAN is not worth it
You have one site, or a few simple sites where downtime costs little.
Most locations have only one usable circuit. Without a second path, the software has little to choose between.
You are locked into circuit contracts with high exit charges, and the SD-WAN cannot run over them.
The real problem is something else, such as poor Wi-Fi or an undersized circuit. SD-WAN will not fix those.
No one will own the provider relationship. A managed service still needs a manager.
Questions to ask carriers and providers before you sign
What does the SLA cover? An SLA is a service level agreement. Ask whether it covers the SD-WAN service, the circuits, or both, how uptime is measured, and what you receive when it is missed.
Who supplies the underlying circuits? Find out whether the provider delivers them, resells another carrier's, or expects you to bring your own, and who opens the ticket when one fails.
Are the circuits truly diverse? Two circuits entering the building through the same cable fail together. Ask for different carriers and, where possible, different physical paths.
Which security features are included? Get a line-by-line list: firewall, web filtering, intrusion prevention, and remote-user access, each marked included or extra.
Who makes changes, and how fast? Ask how a change is requested, the committed turnaround, and whether changes cost extra.
Do we get access to the management console? Expect read-only visibility at a minimum, and change rights if you want a co-managed model.
What does installation include, site by site? Surveys, on-site technicians, after-hours cutovers, and a rollback plan.
What happens to pricing when we add, move, or close a site? Get the rates into the contract, not an email.
Who owns the hardware and configuration at the end? Ask what you keep, what you return, and whether you receive your documentation.
What are the exit terms? Early termination charges, notice periods, renewal mechanics, and transition help if you change providers.
Put the answers in writing and attach them to the agreement. This list is a starting point for the business conversation, not a substitute for having your attorney review the contract.
How a technology advisor helps
A vendor-neutral technology advisor does not sell a product or run the network. The role sits before and around the purchase, in three places:
Shortlisting. Turning your requirements into a short list of providers that fit your footprint, team, and security needs, so you are not taking every sales call.
Pricing comparison. Putting proposals into the same format, by site and over the full term, so easily missed costs are visible and bids can be compared.
Implementation support. Helping coordinate circuit orders, site cutovers, and escalations, so the project does not rest on one stretched IT lead.
Ask any advisor how they are paid and which providers they work with. Those two answers tell you how neutral the advice is.
SD-WAN as a service: frequently asked questions
What is SD-WAN in plain English?
It is software that connects your sites over whatever circuits are available and decides, application by application, which path to use. It replaces site-by-site router configuration with one central policy.
Is managed SD-WAN the same as SD-WAN as a service?
In most proposals, yes. Both mean a provider supplies and operates the service for a recurring fee. Scope differs by provider, so compare what is included: devices, monitoring, changes, circuits, and security.
SD-WAN vs. SASE: which do we need?
SD-WAN addresses how sites connect. SASE adds cloud-delivered security and remote-user access. If your security tools are current and the problem is connectivity, SD-WAN may be enough. If you are also replacing VPN or firewalls, evaluate SASE at the same time.
Is SD-WAN for small business worth the cost?
Sometimes. It depends on what an outage costs you and whether each site can get two circuits. For one or two simple sites, a firewall with failover is often enough.
Does SD-WAN replace MPLS?
It can, but it does not have to. Some companies keep private circuits at critical sites and add internet circuits alongside them; others move fully to internet. The right mix depends on your applications and what is available at each address.
Where to start
Before you take vendor calls, write down three things: your sites and the circuits at each one, with contract end dates; the applications that cannot go down; and who on your team will own the service. That one page makes every conversation shorter and every quote easier to compare.
If you would like a second set of eyes on your requirements, or on proposals you already have, talk with an AGI Beacon advisor.
This guide is general information, not legal, tax, or financial advice. Confirm contract, accounting, and compliance questions with your own licensed professionals.
.png)



Comments