Most businesses under a hundred people have a network that was installed once, works, and is never thought about until it does not. That is a defensible position and it has two specific failure modes: nothing is patched, and there is no second way out of the building. Both are cheap to fix while the network is working and expensive to discover on the morning it stops, so they are worth deciding about deliberately rather than by default.
What management means month to month
Firmware kept current on switches, access points and the firewall, because network equipment is a target and an unpatched appliance is the way in. Configuration backed up, so a failed device can be replaced in an hour rather than rebuilt from memory. Monitoring that notices a device is offline before a person reports it. And a periodic review of the rules and the wireless, because both accumulate settings that nobody can explain. Ask which of those four are in the fee and how often the fourth happens.
A new office, and what setting one up involves
Cabling and its testing, a comms cabinet with power and ventilation, switches sized for what will actually plug in, wireless designed by walking the floor rather than by guessing, a circuit ordered early because carriers are the long pole, and a cutover plan for the day people arrive. Ask for it quoted as a project with a named list of equipment, and ask specifically how many weeks the circuit takes, because that single number decides the move date more often than anything else.
Redundancy: what it costs and when it earns it
A second internet circuit from a different carrier on a different physical path, with a router that fails over automatically, typically costs a modest monthly amount and removes the single most common cause of a lost day. It earns its money if the business cannot work without connectivity, which for a firm running everything from cloud services now means most of them. Inside the building, duplicate switches and power matter far less at this size, and are usually not worth it.
When the network becomes a cloud question
As services move to a cloud tenant, the network's job narrows to getting people out of the building reliably and keeping the wireless honest. The controller for the wireless may itself move into a cloud console, which is convenient and means an outage there is now on your dependency list. Ask where each management console lives, what happens to the network if it is unreachable, and whether anything continues to work locally when it is.
Questions people ask about network management
How often should network equipment be patched?
Firmware on firewalls and access points should be reviewed at least quarterly and applied sooner for anything with a known exploited flaw. Ask what the provider's schedule actually is.
What does setting up an office network cost?
It is a project, not a monthly line. Get it quoted with a named equipment list, and ask how many weeks the circuit takes, since that usually sets the date.
Is a second internet line worth it?
For most businesses now running on cloud services, yes. It removes the most common cause of a lost working day for a modest monthly cost.
Do we need a network consultant?
For a move, a new site or a redesign, a bounded piece of consulting is usually cheaper than having a managed provider improvise it. For the running of it, a contract is the right shape.