On one of our house of worship projects, part of the scope was a camera mounted above the sanctuary seating, looking out over the room. Positioning it — deciding exactly where it would point, what it would take in, what it would miss — got one of our technicians thinking about Genesis 16:13, and Hagar’s name for God after she was seen in the wilderness: El Roi, “the God who sees me.”
We want to be careful with that. We’re not comparing a camera to God. The comparison only works because of the contrast. A camera sees exactly one thing, from exactly one angle, for exactly as long as it has power, a network connection, and storage to write to. Point it the wrong way and it sees nothing that matters. It has no awareness outside its lens. What the moment actually pointed to is simpler and more useful for our work: a camera is only as good as the thinking that went into where it’s pointed.
The question we ask before “how many”
Most conversations about security cameras start with a number. A client tells us the square footage, and somewhere in the conversation someone asks how many cameras that “needs.” It’s the wrong first question, because a number without a purpose behind it just tells you a system exists — not whether it works.
Before we talk about count, we ask:
- What actually needs to matter here — what’s the thing that, if it went wrong, this camera should have caught?
- Where are the blind spots, once you actually walk the space instead of looking at a floor plan?
- What perspective would actually be useful if something happened — not just “was someone there,” but a view that holds up as evidence?
- Will this camera produce something usable, or does it just prove a camera was installed?
That last question is the one that gets skipped most often. A camera pointed at a wall, or angled so a hat brim covers every face that passes under it, or backlit by a window all afternoon, technically “covers” that area. It just doesn’t do anything when you need it to.
What we actually assessed
The sanctuary itself shaped a lot of this. It’s a room built for people to gather, not for surveillance — good sightlines from the pulpit, a balcony and production booth at the back, an aisle wide enough to move a lift through during installation without disrupting the building’s normal use. All of that mattered for where equipment could go and how it needed to look once it was there. A dome camera reads very differently in a sanctuary than it does in a stockroom, and the client cared about that.
The brief we were solving for was specific: protect the space and the people in it, without the building feeling like it had been converted into something it isn’t. That ruled out a few obvious approaches — no bank of visible cameras at the entrance, nothing that reads as “under surveillance” the moment you walk in.
What we implemented
The camera above the seating was one piece of a broader system — access control, video surveillance, and a Wi-Fi network built to support all of it — designed so the building could stay welcoming during services and locked down the rest of the week without anyone having to think about which mode it was in. The placement decisions came out of walking the actual space with the people who use it every week, not out of a spec sheet.
What this means if you’re planning your own system
If you’re speccing out a security system — a sanctuary, a retail floor, an office, doesn’t matter — start with what you actually need a camera to see if something goes wrong, not with a target number. Walk the space. Ask where someone would actually stand, what they’d be facing, what’s behind them. A smaller number of cameras placed with real intent will consistently outperform a larger number placed to “cover the room.”
If you want to talk through what that looks like for your building, that’s the same process we’d start with — see our security services page, or reach out and we’ll walk the space with you.