Do you really need managed switches?

Managed switches cost several times what unmanaged ones do, and a good deal of the time that difference buys capability nobody ever configures. It is worth being honest about which situation you are in.

What the extra money actually buys

• VLANs — separating the network into isolated segments. This is the main reason, and on its own it usually justifies the decision.
• Visibility — per-port traffic statistics, error counters, and the ability to see which device is on which port. When something is misbehaving, this turns a morning of guessing into five minutes.
• PoE control — powering access points, phones and cameras with the ability to restart a device remotely by cycling its port. Anyone who has driven across town to unplug a camera values this.
• Port security — restricting which devices may connect, and shutting down a port automatically when something unexpected appears.
• Link aggregation and redundancy — combining links for capacity, and spanning tree so a loop does not take down the network.
• Quality of service — prioritising voice and video over bulk transfers.
• Monitoring integration — the switch can tell you a link failed instead of you learning it from a user.

When unmanaged is genuinely fine

• A small office, under about fifteen devices, one flat network with no separation requirement.
• Extending a few ports at a desk, downstream of a managed switch that is doing the actual work.
• A temporary or site setup where nothing is permanent.

In these cases a managed switch is money spent on a web interface nobody will open. We say so when we see it.

When you clearly need managed

• You have or should have VLANs. Guest Wi-Fi, cameras, production equipment or a server segment — all of these need separation, and separation needs managed switching.
• You run IP cameras. Cameras belong on their own VLAN, both for bandwidth and because camera firmware is not something to trust on the same segment as your file server. PoE port control is close to essential.
• You run VoIP. Voice needs its own VLAN and QoS, otherwise a large file transfer degrades calls.
• More than about twenty-five devices. Below that you can troubleshoot by unplugging things. Above it, you need to be able to see.
• Multiple switches. Once switches connect to each other, spanning tree matters — a single accidental loop between two unmanaged switches can saturate a network completely, and finding it without management is a genuinely miserable afternoon.
• Compliance or audit requirements. Segmentation and access control need to be demonstrable, not asserted.

The middle option

Smart or web-managed switches sit between the two: VLANs, basic QoS and a web interface, without full command-line management, advanced routing or the enterprise monitoring features.

For a small office that needs a guest VLAN and a camera VLAN but no more, this is frequently the right answer and costs considerably less than fully managed equipment. Check that the feature list actually includes what you need — coverage varies widely between vendors at this tier.

A practical recommendation

The pattern that works for most small and mid-sized offices: managed switches in the comms cabinet, where VLANs are defined and uplinks live, and unmanaged switches at desks where someone needs three extra ports.

You get segmentation and visibility where they matter, without paying for managed ports that will only ever carry one workstation.