The whole office network, handled.
Every office location with network equipment receives a Managed Site plan. Your network — the firewall, switches, and wireless — is the foundation everything else runs on. Three tiers sized to actual environments, with real onsite hours built into every plan.
Nobody notices a network that works.
A good network is the only piece of technology in your building that succeeds by being forgotten. Here is what keeping it that way looks like across one ordinary month — the overnight work, the thing that broke at 10am, and the hours somebody spends standing in your server closet.
The firmware window.
Firewall and switch firmware gets applied when the building is empty and on a schedule we tell you about first — because the update that closes a vulnerability is also the update that drops every connection for ninety seconds. Doing it at 2am is not a convenience. It is the difference between maintenance and an outage.
The corner that dropped.
Wi-Fi goes strange in one part of the building — the far conference room, the corner where the new shelving went in. Monitoring has already flagged the access point that is retrying, so the conversation starts with what we can see rather than “are you sure it’s not your laptop.” Most of these end before anybody files anything.
Hands on the hardware.
One, three, or six hours onsite depending on your tier, spent on the work that genuinely needs a person in the room: the printer that argues with the shared folder, the conference-room TV that will not see a laptop, the switch port that needs to come up, the cable somebody unplugged to charge a phone.
The honest capacity talk.
The site health review is where we say what the network can and cannot take: whether the segmentation still matches how you actually work, what is out of support, whether that second internet line is worth it yet. And where we coordinate with your internet and telecom providers, so their hold music is ours and not yours.
We will be there when it matters. The point of the model is that it rarely has to come to that.
Three site tiers.
The right tier depends on what’s actually behind the firewall: how many switches, how many APs, whether there’s segmentation, whether the location has compliance requirements. We’ll walk through your environment on the discovery call and pick the tier that fits — no upselling, no padding.
Light infrastructure: a small office with one firewall, a switch or two, and a handful of wireless access points. No dedicated server.
Our most common tier. Fits most small business locations: firewall, up to 4 managed switches, up to 8 APs, single-network configuration.
Larger offices, multi-building campuses, or compliance-driven (CJIS, HIPAA): redundant or multi-WAN firewalls, multiple switches with segmentation, 10+ APs, advanced routing.
Every Managed Site plan includes.
- Firewall management, monitoring, and firmware updates
- Switch and wireless access point management
- Network performance monitoring and alerting
- Network segmentation oversight
- Vendor coordination with internet and telecom providers
- Hands-on troubleshooting and hardware checks during onsite hours
- Quarterly site health review
How the onsite hours work.
Onsite hours are sized to the tier — 1 hour for Small, 3 for Standard, 6 for Complex — and used for the work that needs hands at the desk: a misbehaving printer, a conference-room TV that won’t see the laptop, a switch port that needs to come up. Hours over the included pool are billed at our member hourly rate (well below our standard rate), and the calculator folds it into your estimate.
Service-level commitments
When hours are too slow.
Most businesses are fine recovering data over a few hours. Some are not — and the ones that are not usually know it, because they can put a number on what an hour of being closed costs.
Backup Appliance
An onsite appliance taking full image-level captures with local redundancy, sized in 2TB blocks. The difference from Cloud Backup is not quality, it is what gets recovered and how fast. Cloud Backup brings your files back over a few hours. The appliance brings the whole system back — operating system, applications, configuration, the lot — and can stand in for a failed server while the real one is being rebuilt.
That is why it is priced the way it is, and why we do not put it on every server by reflex. It belongs on the machines where downtime has a running cost: domain controllers, the line-of-business system your day is built around, and environments carrying a compliance or downtime requirement such as CJIS or HIPAA.
The server that everything logs into does not come up. On a file-level backup, that Monday is a hardware order, a rebuild, a restore, and a day or two of a business running on paper. On the appliance, the workload fails over onto the appliance itself and people log in — annoyed about something else entirely, because they never found out.
The rebuild still happens. It just happens on a Tuesday evening, on our schedule, with everybody working the whole time.
