One carrier and one vendor are not the same thing
Before any of this is worth arguing about, the conversation needs to separate two ideas that almost always get conflated.
A carrier is the network your traffic actually rides on. Cable, fibre, wireless, MPLS, satellite. The physical or logical path between your locations and the rest of the internet. Different carriers cover different regions, and no single carrier covers every postal code in Canada. Multi-carrier underneath is often the right answer, particularly for redundancy. Most modern SD-WAN architectures deliberately use multiple broadband access types at a single site to keep one circuit failure from taking the location offline.
A vendor is the company you have a contract with. The one you call, the one you pay, the one accountable for the result. A vendor can manage multiple carriers underneath. The traffic at one of your locations might ride on cable as primary and 4G wireless as backup, both delivered through SD-WAN, both invoiced by one company on one bill.
This distinction matters because it changes the question. The interesting argument is not single carrier versus multi-carrier. That is a technical decision and the answer is usually multi-carrier for redundancy. The interesting argument is single vendor versus multi-vendor. That is an operating decision and the answer is usually different. The ten questions worth asking any provider sit on top of this distinction, not underneath it.
How multi-site businesses end up with many vendors
Almost nobody designs a multi-vendor connectivity setup on purpose. They inherit it. Three common patterns:
Regional convenience. A new location opens in a region where the local carrier has the best footprint or pricing. Signing them up is the path of least resistance. Two years later there are seven local contracts across seven regions, each with its own renewal date, billing cycle, and support process.
Acquisitions and mergers. A growing business buys another business. That business comes with its own carrier contracts, often locked in for years. The acquirer absorbs them and moves on to more urgent integration work, never doubling back.
Vendor disruption. A long-time provider is acquired by a larger carrier, restructures, or stops being responsive. The customer brings in a second vendor to backstop the first one. The first one never gets fully removed. Now there are two.
In all three cases, the head office team ends up coordinating between vendors instead of operating a network. The IT lead becomes the integration layer. The integration layer is one person with a full inbox.
What one vendor, many carriers actually looks like
The right model for most multi-site businesses is one vendor managing multiple carriers behind a single relationship.
At every site, the underlying connectivity might use whichever carrier provides the best service in that region. Cable in one city. Fibre in another. Wireless backup everywhere. SD-WAN ties them together at the management layer. The customer does not see that complexity directly. What they see is one invoice, one support number, and one team accountable for the result.
Frontier's SD-WAN explicitly leverages multiple broadband access types, including fibre, cable, ADSL or VDSL, EoC, and 4G wireless. The point is not that any specific access type is best. The point is that the right one can be selected per site without changing the vendor relationship. Multi-carrier underneath. Single vendor on top. Voice can run on the same model: TrueVoice, Frontier's Canadian-hosted cloud PBX, integrates with the rest of the stack on one bill.
This is what "one vendor, one bill, one support number" actually means in practice. It does not mean one carrier. It means one accountable team.
When multiple vendors might be the right answer
The honest answer is that single vendor is not always right. A few cases where multiple vendors actually make sense:
Specialty requirements that no single vendor covers well. If part of your estate needs something genuinely specialized that no full-service provider does, a specialist makes sense alongside a primary vendor. The specialist owns the specialty. The primary vendor owns everything else.
Deliberate redundancy at the vendor level. Some businesses with extreme uptime requirements run a second vendor in parallel, not just a second carrier. That is a defensible architecture, though it doubles the operational overhead and is rarely necessary outside critical infrastructure.
Active transition. During a phased migration from one provider to another, you will have two vendors for a period. That is not a steady state, it is a transition. It should end.
Outside these cases, the operational cost of multi-vendor almost always outweighs the diversification benefit people think they are getting.
The cost question, in the right order
The cost argument for consolidation is real. It is also usually second.
The accountability argument is first. When something breaks at one location, who do you call? With multiple vendors, the answer depends on which carrier serves that site, which is on the master spreadsheet that is hopefully current. With one vendor, you call one number. The vendor figures out which underlying carrier is involved. The customer does not carry that complexity.
Once accountability is in place, the cost benefits follow. A vendor with combined volume across your entire estate has more pricing leverage than three vendors splitting it three ways. Field service is included rather than billed per truck roll. Billing is consolidated rather than spread across multiple invoices, each with its own reconciliation. New site openings happen on one process instead of three. These are real, but they accrue over time.
The mistake is to lead with the cost spreadsheet. The cost spreadsheet rarely closes the deal, because most CFOs are skeptical of headline savings claims from a connectivity vendor. The accountability argument closes deals, because the IT team has lived the alternative and knows what it costs them in time and attention.
Where Frontier fits
Frontier's customer base is multi-site businesses that consolidated, often after years of trying to make multi-vendor work. The customer stories on our case studies page describe the model across very different scenarios. One national retailer consolidated thousands of sites from multiple carriers onto a single managed relationship. Another retailer migrated three regional carriers onto one vendor over three years, contract by contract, without breaking a single existing agreement.
The Frontier model behind those stories is consistent. One vendor managing the entire estate, nationwide. SD-WAN with multiple underlying carriers as the technical architecture. One bill. One support number. We handle the break up with your existing vendor and pay your final bill. No finger-pointing between vendors when something needs fixing. 0 to 4 hour resolution objective. No field service charges. When something needs attention, we call you, not the other way around. Canadian-based support. Our own national backbone (AS7311) and our own NOC sit behind all of it.
What to do next
If you are running a multi-site business and you do not have a current map of your vendors, your contracts, and your accountability gaps, that is the first project. It does not have to be a formal audit. A one-page list of every vendor, every regional coverage area, every renewal date, and who in your team owns the relationship is enough to start.
If you want to walk through what consolidating onto one vendor would actually look like for your estate, let's talk. No formal RFP required for an initial conversation. Walk us through your environment and we will tell you what we would do, where we would fit, and where we would not.
