From Network Chaos to Seamless Sunday Morning

The Call

The call came in with a wild story. The church had two separate internet connections, at least three different WiFi networks, and none of them would roam properly across the building. iPads were constantly dropping off the network. Staff couldn't reliably find the label printers unless they were connected to a very specific network — and even then, it wasn't always working.

The access points were half a decade old or more, and coverage in the sanctuary — the most important room in the building — was barely functional.

What I Found On-Site

When I went out for the discovery visit, the picture came into focus. Both modems were feeding into the same switches — two routers on the same network, which creates a conflict over which one handles client traffic. This is a classic setup that grows organically over time, often starting with a second connection added for redundancy or speed, and I've seen it in plenty of buildings. It's not a sign of carelessness — networks accumulate layers, and without dedicated IT oversight, it's easy for things to compound quietly. The result, though, was that devices were getting confused about where to send traffic, and things were stopping working in ways that seemed random but had a clear underlying cause.

The access points were mostly UniFi hardware that had been set up manually at some point and left running. Without a UniFi controller in place — which is a separate piece of the ecosystem that a lot of people don't know exists — each AP just held its original configuration independently, with no coordination for roaming between them. That's a totally understandable gap. UniFi's controller isn't obvious if no one's walked you through the platform.

Following cables through the drop ceiling turned up some additional APs and switches that had been added over the years and weren't part of any current documentation. That's extremely common in buildings with rotating volunteers and no formal IT handoff process. Churches run lean, and infrastructure knowledge often lives in one person's head.

The Plan

I proposed a full replacement of all networking hardware from the ISP modems inward. Clean slate. One internet connection at dramatically better speeds — they'd been grandfathered into a slow cable plan for years, paying $400 a month for it. By consolidating to a single modern Spectrum plan, we cut that bill to $100 a month. The network rebuild paid for itself faster than anyone expected.

We'd also design proper VLAN segmentation from day one — giving each category of device its own isolated network, something most small organizations never get around to setting up until a problem forces the conversation.

Coverage Planning

Before a single cable was run, we used UniFi's planning tools to map the building and simulate AP placement. The heat maps below tell the story clearly — the before shows the existing coverage with fewer, older APs, heavy dead zones in the sanctuary and hallways. The after shows the planned full-building coverage with modern APs properly placed throughout.

Green = strong signal. Yellow = adequate. Orange/red = weak or no coverage.

The Install

Over three days, a small team ripped out every piece of old hardware, pulled new Cat6a cable to the access point locations and office spaces, ran fiber to the sanctuary, and stood up the entire new infrastructure. Every connected device — iPads, printers, TVs, staff computers — was configured on its proper VLAN and tested.

Sunday was the next morning. I was on-site.

A Note on Guest WiFi for Churches

One thing worth highlighting for any church reading this: UniFi's captive portal feature lets you broadcast a guest network with no password at all. Visitors connect, accept terms of use, and they're online — bible apps, giving portal, whatever they need. Guest clients are isolated from your internal network and from each other. You never have to post a password on a sign, change it when someone leaves, or field the question "what's the WiFi password?" during the service.

It sounds like a small thing, but for churches it's a genuinely useful change.

Empowered, Not Dependent

One of the things I'm most proud of with this project is how we wrapped up. They didn't want a black-box system they'd have to call me every time something came up — they wanted to understand what they had. We made sure of it. Their team can now log into the UniFi dashboard, track down issues, see what's connected to what, and get push notifications to their phones when something critical happens.

That's how IT should work for a church. You shouldn't need a consultant to tell you why your printer isn't working on a Sunday morning. You should be able to look it up yourself. My job is to build the system, document it, train your people, and then be available when you need something I can actually help with.

This was a success, and I'm proud to count them as an ongoing client. One of the things that makes a well-built UniFi network such a strong foundation is where it can go from here — the UniFi ecosystem extends into physical security, access management, and more, all managed from the same platform, with no ongoing subscription fees. When the time is right, the infrastructure is already there to grow into it.

If you're interested in what moving to a UniFi network could do for your business or house of worship, schedule a free consultation call — no pressure, just a conversation.