Business Wi-Fi and network refresh guide

Signs your network needs a refresh

Not every complaint is a network problem, and not every network problem needs new hardware. These patterns suggest the infrastructure itself is the limit rather than a single fault.

• Complaints cluster by location (a back office, a warehouse aisle, a conference room) rather than by person or application.
• Video calls degrade predictably when the office is full, and recover when it empties.
• Devices connect but move data slowly, or drop and reconnect as people walk between areas.
• Access points or switches are old enough that firmware updates are no longer published for them.
• The network was designed for a headcount, device count, or floor plan you have since outgrown.
• Guests, staff, payment devices, and cameras all sit on the same flat network.
• Nobody can produce a current diagram, and changes are made by trial and error.

Assess the current state before buying anything

A refresh planned from a device catalog tends to solve the wrong problem. Collect facts first.

• Count devices rather than people. Include laptops, phones, tablets, printers, scanners, cameras, sensors, point-of-sale terminals, and anything else that connects.
• Note where each device type is used, and which ones move around during the day.
• Record the model and age of every switch, access point, firewall, and modem, plus firmware versions and support status.
• Map dead zones by walking the space at the times complaints happen rather than on a quiet morning.
• Identify what is wired versus wireless today, and which wired runs are unlabeled or untested.
• Check your internet service: contracted speed, actual observed speed, and whether the connection or the internal network is the bottleneck.
• Look for the physical problems that cause intermittent faults: unlabeled patching, damaged cable, consumer-grade gear in a closet, no uninterruptible power.

Plan coverage and capacity separately

Coverage means signal reaches the space. Capacity means the space can carry the traffic of everyone in it. Adding access points for coverage without planning capacity often makes performance worse.

Wired backbone and switching

Wireless performance is limited by what is behind it. The backbone deserves attention even in a project people describe as a Wi-Fi upgrade.

• Verify cabling category and condition on the runs feeding access points, and replace runs that will not support the speeds you are buying.
• Size switch ports for today plus growth, and confirm power over Ethernet budget across all powered devices as well as port count.
• Plan uplinks between closets and floors so the path back to the firewall is not the bottleneck.
• Put network equipment on uninterruptible power, and decide what should stay up during a short outage.
• Standardize on manageable switches you can see into. Unmanaged gear hides the problem you will eventually need to find.
• Label patch panels and document the diagram as part of the project rather than as an afterthought.

Security segmentation

Separating traffic is one of the higher-value, lower-cost parts of a refresh. The goal is that a compromised device on one segment cannot reach everything else.

• Put guest access on its own segment with internet-only access, its own credentials, and no route to internal resources.
• Keep staff devices on a separate segment with access appropriate to their role.
• Isolate payment devices where applicable, and confirm what your payment processor and card obligations require.
• Separate cameras, door controllers, thermostats, and other connected equipment, which are frequently the least-patched devices in a building.
• Restrict management interfaces for switches, firewalls, and access points to a controlled path, and change every default credential.
• Keep firmware current on network equipment, and set a schedule rather than doing it only after an incident.
• Decide how remote access works: who connects, from what, and with multi-factor authentication.

Choosing when to refresh versus patch

Both answers are legitimate. The distinction is whether the current design can meet what the business needs next year.

Working with a technology partner

These are the things worth insisting on, with internal staff or with outside help.

• Ask for an assessment of the current state before any product recommendation, and expect the recommendation to reference what was found.
• Require a written design: coverage plan, device counts, segment layout, and what happens to the existing equipment.
• Confirm what is included (cabling, configuration, installation, testing, documentation) and what is billed separately.
• Ask for post-installation testing evidence, including coverage verification in the areas that were problematic.
• Get the documentation handed over in a form you keep: diagrams, addressing, credentials stored securely, and support contacts.
• Understand who supports the equipment afterward, how issues are reported, and what response you can expect.
• Keep vendor neutrality in the conversation. The right platform depends on your building, device mix, and who will manage it, rather than on a single preferred line.