• United States

Making sense of the SD-WAN business case

Nov 01, 20175 mins
Network Management SoftwareNetworkingSD-WAN

There is no 'one size fit all' approach to building a business case for SD-WAN – the benefits vary significantly by industry and geography.

data analytics chart money finance laptop computer
Credit: Thinkstock

As enterprises finalize budgets for 2018, a common question in IT departments is how to budget for the implementation of SD-WAN technology. The fact that these conversations are even happening is noteworthy in itself; this is a technology that has gone from being a curiosity 18 months ago to a top-5 initiative for many IT teams in recent months.

There are many variations between SD-WAN vendors and service providers on what the technology offers, how it’s paid for, and how the business case stacks up. Here are a few items to consider:

For most enterprises, SD-WAN savings are based on transport savings

One of the headline benefits of SD-WAN that attract most enterprises is the prospect of significant savings. This can mean many things, but the bulk of these savings typically comes from replacing private MPLS connectivity with Internet-based services, and using SD-WAN to glue these together. Internet “may” be poorer quality (more on that later), and may not have performance guarantees, but the path performance tracking and steering capabilities of SD-WAN can work around these limitations. This may be the case, but it isn’t universal:

  • It is highly dependent on geography: the MPLS-Internet price gap can be much smaller in North America and Western Europe than it is in Asia Pacific or Latin America.
  • You have to consider broadband to see the biggest savings: replacing a leased line MPLS connection with a fiber-based DIA service often won’t deliver any real savings, as most of the underlying infrastructure is the same. Broadband services, especially asymmetrical products, open the door to far greater savings, but come with some performance limitations.
  • Somebody has to manage these all new Internet services: this can be a big surprise for enterprises – the real savings come from contracting with in-country providers, but this creates a lot of fragmentation. This requires internal staffing or a managed service wrap to deliver a high-quality service.
  • You have to work around your contractual limitations: most MPLS networks are contracted for multiple years, often 3 to 5. A well-negotiated agreement will provide more flexibility, but you may have to start with MPLS in the transport mix, impacting savings opportunities.

Yes, there are some big potential opportunities at the transport layer, but it can be one of the hardest areas to get right. Doing a poor job here means you may not find sufficient savings to pay for the new costs of the SD-WAN layer itself.

Find a commercial model for the SD-WAN layer that works for your business

It can be nearly impossible to directly compare SD-WAN offerings, due to the variety of commercial models that are now available. Here are just a few that I’ve seen:

  • Buy the SD-WAN technology layer as an annual or monthly subscription, including the use of all hardware and software components.
  • Buy the SD-WAN appliances and pay annual maintenance and software license fees.
  • Obtain the SD-WAN technology layer as an add-on to a traditional telco service (e.g., MPLS).

Normalizing the various offers – somehow – is essential. A 3-year TCO comparison is a good start; the technology is moving too rapidly to realistically consider longer agreements. This raises an important question about buying hardware: how confident are you that the hardware you buy today will effectively run that vendor’s SD-WAN software in 12 months from now? In 24 months? Subscription-based models, even if they are not the absolute low-cost option, may shield you from the risk of buying hardware with a short life span.

All of the usual business-specific considerations on capex vs. opex also apply here –different enterprises have different tolerances and budgets for each type of spend. Depending on the SD-WAN vendor or service provider you work with, there may be some flexibility on how the transaction is structured.

Don’t lock yourself out of further savings

Traditional network services were procured on a fairly predictable 3 to 5 year contract with limited ability to track market-level changes in pricing during the term. It’s difficult to overstate how risky that approach is in a new agreement that incorporates SD-WAN. Here are some thoughts on how you can help incorporate the protections that will be needed in this fast-moving industry:

  1. Make sure your transport layer is contracted on a short-term basis. There is continuous innovation in last-mile technologies and competition continues to drive up available bandwidths and keep costs contained. The ability to access these options as they become available will prevent being locked in to high-priced, outdated services.
  2. Leverage self-service options. The traditional managed service model needs to be refreshed in an SD-WAN environment. Many changes that previously were owned by the MSP can now easily be handled by the enterprise, even with limited staff. Negotiating the ability to perform these self-service changes (and avoid expensive change fees) can help contain costs over the term.
  3. Don’t automatically reject upgrades. Many traditional networks were deployed with a single tested software image on the routers, and left that way for the term. Monthly code releases are common in an SD-WAN environment, and can bring material improvements in functionality and performance. Negotiating the ability to obtain these updates over the term is essential (including hardware refresh if needed), and making the necessary business process changes to adopt these upgrades should be part of the implementation plan.

Enterprises can derive some great benefits from this technology, but it requires a real plan, especially as it starts to displace ever-increasing portions of existing IT budgets. Recognizing the nuances of each business and avoiding a “one size fits all” approach is one of the most important first steps.


Ciaran Roche is the co-founder and CTO of Coevolve. Ciaran has worked in a range of technology leadership roles in Europe and the US. He started his career in the networking industry working in London, UK for Virtual Access, one of the first 'software-defined' networking companies before that phrase even existed. The company built a range of edge routers and a central orchestrator platform for configuration management. Ciaran was responsible for managing trials and demonstrations for customers and prospects all across Europe and North America.

In 2002 Ciaran joined Vanco, the pioneer of the Virtual Network Operator model, just as IP-based networks were starting to take over from legacy Frame Relay / ATM / X.25 on a large scale. With a strong background in Internet and MPLS technology, Ciaran developed the technical solutions for some of Vanco's largest new customers including a 1,200 site network for Avis Europe, a large VPN solution for British Airways and complex solutions for Siemens and SGS. Ciaran moved to the US in 2005, and led projects for major clients including Ernst & Young (now EY), Pfizer and Wyeth.

In 2012, Ciaran joined Pace Harmon, a boutique management consulting firm specializing in IT strategy and transformation projects for major global businesses. Ciaran led a number of significant projects for large clients including Molson Coors, Capital One Bank, CSC and several of the largest technology and media companies in the world.

As the CTO of Coevolve, Ciaran brings over 15 years of experience that spans many technologies and geographies. Ciaran has presented to, and worked with major enterprise CIOs and CFOs to deliver effective, high quality networking and cloud-based solutions. Ciaran is based in Chicago, Illinois.

The opinions expressed in this blog are those of Ciaran Roche and do not necessarily represent those of IDG Communications, Inc., its parent, subsidiary or affiliated companies.