SMB UniFi Build for a 50-Person Office

Fifty people is the size where a network stops forgiving improvisation. At ten users you can run a prosumer router and a couple of unmanaged switches and nobody notices; at fifty, the same shortcuts turn into daily tickets — the video call that stutters every afternoon, the guest Wi-Fi that somehow reaches the accounting VLAN, the switch that reboots itself and takes half the floor down. UniFi has become the default answer for offices this size because it delivers managed networking with a single controller and a coherent hardware line, at a price that a fifty-seat business can actually approve. This is a build sheet for that office: what to specify, why, and how it all lands in the rack.

The numbers here are a starting template, not a survey substitute. Every office has its own square footage, wall construction, and density quirks, and a real deployment still wants a walk-through and ideally a site survey. But the shape of a 50-person UniFi build is consistent enough to plan against, so we will size each layer — gateway, switching, wireless, cameras, and power — from the user count outward.

The mount for this build:

19" Unifi USW-Lite-8 PoE Rack Mount - 1U (Modular)

Sizing from the headcount

Start by translating fifty people into device and traffic load, because that is what the hardware actually serves. The rule of thumb that holds up: budget two to three connected devices per knowledge worker — laptop, phone, and often a desk peripheral or soft-phone — which puts a 50-person office somewhere between 100 and 150 client devices once you count the printers, TVs, and the inevitable pile of things nobody admits to plugging in.

That client count drives three decisions at once. It sets your wireless capacity (concurrent clients per radio), your switch port count (wired seats plus infrastructure), and your gateway's session and throughput ceiling. The honest planning move is to size for the busy hour, not the average — the network has to be comfortable at 10 a.m. on a Monday with everyone on a video call, not merely survivable at the daily mean. Undersizing to the average is the single most common reason a technically "adequate" SMB network feels slow.

The gateway

The gateway is the one device where a 50-person office should not economize into the consumer tier. It routes, runs the firewall, terminates the VPN, and — if you enable it — performs the deep packet inspection that IDS/IPS requires. That inspection is the expensive workload: a gateway that routes multi-gig cleanly with inspection off can fall to a fraction of that with full threat management on. So the sizing question is not "what is the WAN port speed" but "what is the inspected throughput, and does it exceed our internet plan."

For an office this size, specify a rack-mount UniFi gateway from the Pro tier or higher — the models built for exactly this: multi-gig WAN, hardware headroom for IDS/IPS at business-internet speeds, and in the Pro-and-up chassis, the option of onboard storage for cameras. Confirm the current inspected-throughput figure on Ubiquiti's spec sheet against your actual and near-future internet speed, because a business that is on 500 Mbps today and eyeing symmetrical gig next year should buy for the gig. The gateway also becomes your UniFi OS Console, hosting the Network controller on-device, which removes the need for a separate Cloud Key for networking — one fewer box to power and patch.

Core and edge switching

Switching for fifty seats is a two-layer job: a core switch that aggregates and feeds the infrastructure, and edge switches that fan out to the desks. Trying to serve every wired seat plus every access point plus the uplinks from a single switch is how you end up one port short on install day.

Size the ports honestly. Fifty wired seats — and many offices are back toward wired desks for reliability — plus the access points, cameras, the gateway uplink, and inter-switch links push you into the range of a 48-port switch at the edge with a smaller aggregation or PoE switch alongside it. The specification that trips up SMB builds is the PoE budget, not the port count. Every access point, every camera, every PoE phone draws from a shared power budget measured in watts, and a switch advertised as "48-port PoE" may not sustain full 802.3at on all 48 at once. Add up the worst-case draw — Wi-Fi 6/7 APs can pull 20-30 W each under load, cameras and phones less — and confirm the switch's total PoE budget covers it with margin. Put the access points and cameras on the switch with the healthy PoE budget, and use a 10G or 25G link between switches so the trunk between them is never the bottleneck.

Wireless coverage and density

Wireless is where user experience is actually won or lost, and it is sized by two independent constraints: coverage and density. Coverage is about square footage and walls; density is about how many clients share a radio. In an open-plan office you can cover a lot of floor with few APs, but if all fifty people sit under two access points, each radio is straining under the client load regardless of signal strength.

The planning target most SMB deployments land on is one access point per 1,500 to 2,500 square feet, or per roughly 25-30 concurrent clients, whichever is denser — which for a typical 50-person office means four to six APs rather than two. Erring toward more APs at lower transmit power beats fewer APs shouting: it reduces co-channel interference, shortens the distance every client radio has to reach, and gives you roaming that actually hands off cleanly. Ceiling-mount the APs centrally over the space rather than tucking them at the walls, put them on Wi-Fi 6 at minimum (Wi-Fi 7 if the budget and client fleet justify it), and give guest traffic its own network and VLAN so visitors never share broadcast space or subnet with the business.

Cameras, NVR, and the closet control plane

If the office runs UniFi Protect cameras — and at fifty people, physical security usually enters the conversation — remember that cameras need storage, and storage is what a bare gateway console does not have. The recorder has to be a device with disks: a gateway from the Pro tier with an onboard drive bay for a modest camera count, or a dedicated network video recorder for anything serious. Size the storage to your retention requirement: resolution, frame rate, and days of retention multiply into a capacity number, and thirty days of several 4K streams is a lot more disk than a weekend of 1080p. Decide retention first, then buy the drives.

Keep the camera recording workload deliberately separate from the routing plane where you can. On a busy office network, a recorder writing gigabytes of video all day is happier on its own appliance than sharing a chassis with the firewall — the isolation is worth the rack space. This is also the moment to confirm your PoE budget one more time, since the cameras draw from the same switch power you already allocated to the access points.

The rack, mounting, and power

All of this has to live somewhere, and in a 50-person office that is usually a wall-mount or small floor cabinet in a dedicated closet. Specify the rack with a few honest allowances. Leave a spare U or two — every network grows — and budget for the airflow: a closet packed with a PoE switch under load, a gateway doing inspection, and a recorder writing continuously is shedding real heat, and a closet with no ventilation will run hot enough to shorten the life of everything in it. A vent, a small exhaust fan, or at minimum a door louver is not optional at this device count.

Mounting is where a UniFi build either looks like infrastructure or looks like a shelf someone gave up on. The gateway, the recorder, and the smaller UniFi devices are not natively rack-width, so each wants a proper 1U or 2U mount that presents it flush to the rails, with the port side accessible and the cabling dressed. Getting every device onto the rails — rather than stacking half of them on a shelf — is what makes the closet serviceable a year later when someone who is not you has to trace a cable. Size each device's mount to give it a little thermal breathing room rather than cramming the closet to save a U; a fanless device pressed against a hot neighbor throttles silently, and silent problems are the ones that page you at the worst time. Finish with a UPS sized to carry the gateway, core switch, and recorder through a short outage and signal a graceful shutdown — the whole build is worth little if a brief power blip corrupts the controller database or a camera write.

Wrap-up

A 50-person UniFi build is a sizing exercise before it is a shopping list. Translate the headcount into 100-150 client devices, then work outward: a Pro-tier gateway sized by inspected throughput rather than WAN port speed, a core-plus-edge switching layer sized by port count and — more importantly — PoE budget, four to six access points placed for density rather than bare coverage, and a camera recorder with real storage kept off the routing plane.

Then respect the closet. Ventilate it, put every device on the rails with a proper mount and a little thermal margin, and back the critical gear with a UPS that shuts things down gracefully. Do that and a fifty-seat office gets a network that behaves like infrastructure — quiet, serviceable, and boring in the way good networks are — instead of a pile of capable hardware fighting its own closet. The parts are the easy part; the sizing and the mounting are what make it last.

Mounts in this build