A network refresh looks simple on the surface: rip out old switches, put in new ones, done. But experienced MSPs know the reality — a project scoped at $18,000 bleeds out to $26,000 because nobody accounted for the after-hours window, the firmware update marathon, or the client's ancient patch panel that needs to be completely replaced.

Under-scoping network refreshes is one of the most common ways IT consultants lose money. Here's how to stop it.

Why Network Refreshes Get Under-Scoped

The root problem is that clients (and sometimes engineers) think in terms of hardware, not hours. A client hears "replacing 8 switches and a firewall" and mentally pictures a Saturday morning job. They don't see:

Firmware and configuration prep work — staging Cisco IOS updates, pre-building config templates, validating spanning tree topology — can add 6–10 hours before you've touched a single live device
Cabling surprises — that "clean" server room often hides unlabeled cable bundles from 2009, and the moment you start tracing them the whole schedule shifts
After-hours requirements — most clients can't go down during business hours, so your 8-hour installation becomes a 10pm–4am job with overtime implications
ISP coordination — if the refresh involves a new edge router or firewall, the ISP may need to update routing tables, BGP peering, or provision new handoff equipment. ISP lead times run 15–45 days and coordination is a separate workstream

Each of these is a legitimate line item. The SOW is where you make that visible.

The 10 Sections Every Network Refresh SOW Needs

1. Executive Summary

Two to three paragraphs explaining why the project is happening, what the outcome looks like, and what success means. Clients often share this with their board or finance team — write it for a non-technical audience.

2. Current State

Document what's being replaced: switch model/count, firewall, AP infrastructure, existing cabling category, current VLAN design, WAN circuit details. Include a network diagram if possible. This section protects you if the client later claims "we told you about that extra closet."

3. Proposed Solution

What hardware is going in, from which vendor, at what model/line. Be specific — "Cisco Catalyst 9200 series" instead of "new managed switches." If you've standardized on Fortinet FortiGate for firewalls or Ubiquiti for SMB wireless, say so here. Include firmware versions you'll deploy.

4. Scope of Work

The heart of the document. Break this into phases:

Phase 1: Pre-deployment — equipment staging, firmware updates, configuration build-out, documentation of existing environment
Phase 2: Installation — rack and stack, cable runs (patch cables only, see exclusions), configuration push, VLAN migration
Phase 3: Validation — connectivity testing per device, failover testing, performance baseline, client sign-off

Each phase should list deliverables, not just activities.

5. Bill of Materials

Line-itemize hardware, licensing, and third-party services. Clients should be able to cross-reference this against the invoice. If equipment is customer-provided versus MSP-provided, flag it here.

6. Labor Estimate

Break down labor by role (see estimation section below). Include a not-to-exceed total. Vague "T&M" language in a fixed-bid engagement is a recipe for disputes.

7. Project Timeline

Milestone-based, not calendar-based. "Equipment staging complete" → "On-site installation window" → "Validation and sign-off." Include lead time for equipment procurement (Cisco lead times have ranged from 4 weeks to 6+ months post-pandemic — build in buffer).

8. Assumptions

What you're assuming is true about the client's environment. Examples: "Existing patch panel supports Cat6 connections," "Client will provide after-hours building access," "WAN circuits remain unchanged." Every assumption that turns out to be wrong is a change order.

9. Exclusions

Explicitly list what is NOT included (see the exclusions section below). This is the most underused section in most MSP proposals.

10. Acceptance Criteria

Define what "done" looks like. "All network devices reachable via management IP, all VLANs routing correctly, throughput baseline matches pre-project measurement within 10%." Without this, clients can hold sign-off indefinitely.

Common Exclusions People Forget

Exclusions aren't a hedge — they're honest scoping. Write them clearly:

ISP coordination and circuit provisioning — if the WAN handoff needs to change, that's a separate workstream with its own lead time
Electrical work — dedicated circuits for server rooms, UPS installation, and outlet placement are licensed electrical contractor territory
Structured cabling beyond patch cables — running new Cat6A from IDFs to workstations or pulling cable through conduit is a separate cabling quote
Permit fees — some jurisdictions require permits for low-voltage cabling work; those fees are pass-through costs not included in labor
Third-party vendor coordination — if the client has a VoIP provider, CCTV vendor, or building automation system that connects to the network, coordinating with those vendors is out of scope
End-user support — the refresh is infrastructure work; "why is my computer slow now?" tickets post-deployment are covered by existing helpdesk agreements, not this project

How to Estimate Labor

Break labor into roles with realistic per-task hour estimates:

Network Engineer (senior, $150–200/hr)

Pre-deployment config build: 6–10 hrs
On-site installation and validation: 8–14 hrs (depending on switch count and complexity)
Post-installation documentation: 2–4 hrs

Project Manager

Scheduling, vendor coordination, status updates: 4–8 hrs across the project lifecycle

Cabling Technician (if in-house)

Patch cable runs, labeling, patch panel terminations: 2–6 hrs

Add a 10–15% contingency buffer and state it explicitly. Clients respect transparency about buffer more than a mysteriously inflated quote.

For a mid-sized client (50 users, 2 IDFs, 1 MDF, Cisco Catalyst stack + Fortinet firewall), a realistic labor estimate is 35–50 hours total. At blended rates, that's $5,250–$8,500 labor on top of a hardware BOM that might run $15,000–$40,000. If your quote is significantly below that, you're leaving yourself exposed.

Build Better Network Refresh Scopes in Minutes

ScopeDrafts generates all of this automatically. Select "Network Refresh," enter your project details — client site, hardware count, VLAN complexity, after-hours requirements — and get a professional scope document with all 10 sections, pre-populated exclusions, and a labor breakdown in minutes.

Stop losing money to under-scoped network projects. Try it free at scopedrafts.com.

How to Scope a Network Refresh Without Missing Anything