Business Internet and SD-WAN: A Multi-Site Buyer's Guide for NJ, NY, PA and CT

Your organization runs out of six buildings. Two were connected years ago by whoever the previous landlord recommended, one sits on a circuit nobody has reviewed since the lease was signed, and the newest location is still waiting on an installation date that has moved twice. Nothing is broken badly enough to be an emergency, and nothing works well enough to stop coming up in leadership meetings. That is the normal starting position for a multi-site healthcare practice, nonprofit or school in New Jersey, New York, Pennsylvania or Connecticut, and it is not a planning failure. It is simply what happens when connectivity is bought one site at a time.

If you are already collecting quotes for several addresses, ask us for a multi-site connectivity review first — 30 minutes, no charge, no pitch. We go address by address through your circuits, contracts and renewal dates before anyone compares a price; if it is easier to start with a conversation, the number is (646) 517-1438.

This guide is written for the operations or information technology (IT) leader at an organization of roughly 100 to 500 staff who is about to compare business internet and wide-area network (WAN) service providers for several locations at once. It covers what the terms mean, what to ask, and where the advice you will find online quietly assumes you only have one office.

What a multi-site organization actually needs — and why single-site advice misleads

Almost every published guide to choosing business internet is written for a single address. Pick a speed, compare the monthly cost, check the reviews, sign. At one location that advice is roughly right. Across six or twelve it produces a network that nobody can operate.

Three things change the moment you have more than one building. The first is variance: your sites will not be served by the same infrastructure, the same provider, or even the same technology, because what is available at a suburban medical office in Bergen County is not what is available at a storefront program site in Philadelphia. The second is dependency. Once your locations share an application — a scheduling system, a case management platform, a phone system, a student information system — a problem at one site becomes an organization-wide problem, and the person who has to explain it is you. The third is operational load. Six contracts, six renewal dates, six support numbers and six escalation paths consume real staff time, and that time is invisible on every quote you will receive.

So the question is not “which circuit is fastest at each address?” It is “what does every site need to be able to do, and what is the smallest set of commitments that delivers it?” That reframing is the difference between a network you own and a folder of contracts you inherited.

Dedicated internet access versus broadband, and when each is right

Two categories of connection will appear on nearly every quote you receive, and they are not variations of one product.

Business broadband — cable, or fiber-to-the-premises sold on a shared plan — is delivered on a best-effort basis. Capacity is shared with other subscribers in the area, upload speed is usually far lower than download speed, and the provider commits to carry your traffic when it can rather than within a defined performance budget. It is widely available, it installs quickly, and for many sites it is genuinely the right answer.

Dedicated internet access (DIA) is a circuit provisioned for your organization alone. Bandwidth is symmetrical, meaning upload matches download, and the capacity you buy is the capacity you get regardless of what your neighbors are doing. Because it is dedicated, the provider can commit contractually to availability and, on a well-written agreement, to latency and packet loss as well. It costs more, and it usually takes considerably longer to install, because it often requires new fiber construction to the building. Our companion piece on the reasons organizations switch to dedicated internet access covers that trade in more depth.

The practical answer at most multi-site organizations is neither one nor the other, but a deliberate mix. Sites that host something — a server room, a main phone system, the video endpoints used for telehealth or remote instruction — are the ones where symmetrical, committed capacity earns its cost. Smaller sites that only consume cloud applications are often well served by good broadband, particularly when a second, independent connection is available as backup. What matters is that the choice at each site is made against a stated requirement rather than against a price sheet.

What software-defined wide-area networking does, and does not, solve

A software-defined wide-area network (SD-WAN) is an overlay: appliances or software at each site that treat every available connection as part of one managed network, steer each application down the path that suits it, and fail traffic over when a path degrades. Managed centrally, software-defined wide-area networking replaces per-site device configuration with policy applied everywhere at once, and it gives you something most multi-site organizations have never had — a single view of how each location is actually performing.

That is a real advance, and it solves genuine problems. It lets a cheap secondary connection carry useful load instead of sitting idle. It moves a voice call or a clinical application off a degrading link before staff open a ticket. It gives you evidence when a provider tells you the circuit is fine.

Here is what it does not do. It cannot create capacity that is not there; steering traffic intelligently across two saturated connections still leaves you saturated. It cannot rescue a site with only one physical path into the building, because there is nothing to fail over to. It does not replace security controls, though many products bundle them, and bundling is not the same as configuring. And it does not decide which of your applications matter most when bandwidth is scarce — that prioritization list is a business decision your leadership has to make. Our guide to multi-site network connectivity for healthcare organizations works through how those design choices and the contract terms have to agree with each other.

How to evaluate providers: the questions that separate the quotes

Once you have a design, every provider will tell you they can deliver it. These are the questions that produce different answers.

On the service level agreement (SLA). Ask what is actually committed, in writing: availability alone, or availability plus latency, jitter and packet loss? How is an outage measured, and when does the clock start — when the circuit fails, or when you report it? What is the remedy, and is it automatic or does someone on your team have to claim it? A credit you have to chase is worth less than one that appears on the bill.

On installation lead times. Ask for a written, per-site delivery date, and ask whether that date is based on a completed site survey or on an estimate from a coverage map. Ask what happens if construction is needed, who pays for it, and whether your pricing changes when it turns out the building needs new fiber. Lead times on dedicated circuits are routinely measured in months, and a project plan built on optimistic dates fails at the worst site, not the easiest one.

On per-site support. Ask who answers at two in the afternoon when one location is down and the rest are fine. Ask whether support is regional or national, whether your account has a named escalation path, and — the question that matters most in a mixed network — who owns the fault when the circuit provider and the SD-WAN provider disagree about whose problem it is. Get that answer before you sign, not during your first cross-vendor outage.

Two more worth writing into the contract: what it costs to add and to remove a site mid-term, and what the renewal notice period is. Multi-site organizations open and close locations. Contracts written as though the footprint is fixed become expensive the first time it is not.

What changes when clinical systems, donor data or student records ride the same links

Everything above applies to any multi-site organization. Regulated data adds a layer.

If patient information crosses your network, ask each vendor whether they will sign a business associate agreement and have your counsel review it before implementation rather than after. If you hold donor records, your obligations come from your funders, your state charity regulator and your own privacy commitments, and those should be written into the vendor requirements rather than assumed. Schools carry student record obligations of their own. In every case the practical question is the same: what does this provider touch, what do they log, where does that log live, and who at their organization can see it?

Regulated workloads also change the design conversation. A site that cannot pause — an intake desk, a clinic floor, a testing center — needs genuinely diverse paths, meaning two physically separate routes into the building rather than two services delivered over the same fiber. Ask providers to confirm diversity physically, not on paper. And when a site does go down, the question of who notices and who responds is an IT support question, not a carrier question; our guide to multi-site IT support for healthcare and nonprofits in New Jersey covers what that agreement should include.

A sensible place to start

Before you request a single quote, build the inventory: every site, every circuit, every contract end date, every monthly charge. Organizations doing this for the first time regularly find services still billing for locations they have left. Then state, per site, what the location has to be able to do on its worst day. Only then go to market, and go with the same written requirement to every provider so the responses are comparable.

TVG Tech works with healthcare, nonprofit and education organizations across NJ, NY, PA and CT on exactly this decision — running the site survey, translating provider answers into terms your board will recognize, and staying involved after the installation. We are not a carrier, and we do not rank vendors; the right answer depends on what is physically available at your addresses.

If you are facing a renewal, opening a location, or working with a network that is no longer holding up, tell us about your multi-site setup and we will walk through it with you.