BEZALEL.ONE

Built once. Built right. Built to repeat.

Nobody in the seats knows what a Bank 2 CC is. They just experience a clean, seamless service. The work lives underneath - and the goal is always the same: make it hold up long after the builder has moved to the next fire.

The builder
Jeff Reed

Jeff has spent twenty-plus years at the intersection of the church and its technology - as a pastor, a technologist, and for most of that time both at once. He founded Humble Disruption, a studio that builds software for ministries, and spent years leading a national conversation on digital ministry - writing, podcasting, and coaching churches through the shift to hybrid church.

Every Sunday he runs weekend production at a multi-campus church in Miami - the room where everything on this site was built, broken, rebuilt, and proven. The platform isn't a product he designed for other people's rigs; it's the system he depends on himself, every single week, with real volunteers at the controls.

Bezalel.one takes a small number of churches at a time. When you work with Bezalel, you work with Jeff - in your building, on your gear, with your people.

01

Three things every build has to be.

01
Built for the unseen work
Infrastructure people never admire directly - keyer chains, custom controls, signal routing - done so the visible experience just works.
02
Skilled across many crafts
Audio, video, lighting, show control, automation - one person, many disciplines, one system that behaves as a whole.
03
Built to outlast the moment
Volunteer-repeatable workflows: build it once, build it right, so it holds up week after week - even on deadline, it submits to rhythm.
Built to last means built to watch itself.
The newest layer of the work is a read-only health system that keeps eyes on the gear, the power, and the weather all week - so a failing fan or a brown-out gets caught on a Thursday, not discovered at 9:58 on a Sunday morning. Reliability isn't bolted on at the end. It's what "built to outlast the moment" actually costs.
The person nobody sees, doing the work everyone feels.
02

How an engagement works.

01
Walk the rack
Understand the gear, the volunteers, and where the friction actually is.
02
Map the signal
Document the flow end to end, then design the one system it should become.
03
Build & wire
Custom controls, dashboards, fire surfaces - integrated and tested against a real service.
04
Hand off
Documented, volunteer-runnable, and built to keep working without you.
05
Keep watching ONGOING
Health monitoring, updates, and a system that stays alive - not a binder on a shelf.
03

What it costs.

Straight numbers, because you're budgeting real money. Every engagement is scoped to your room and your gear - but this is the honest shape of it.

The build
$20-45k
Scope-dependent, one time. The walk-the-rack assessment, the system design, the integration work, the volunteer surfaces, the documentation, and the hand-off. On your gear - this is not a hardware bid.
The partnership
$750-1,750/mo
The "keep watching" layer: health monitoring on your rig, platform updates as they ship, remote support, and a builder who still knows your room. Cancel anytime - the system keeps running without it.
For scale: a traditional integrator's control-room proposal routinely lands at $150k+ and hands you gear your volunteers still can't run. A full-time technical director is $60-85k a year, every year - if you can find one. This is a different shape: build the system once, keep it watched, and let volunteers run it.

The room, built so worship can happen.

Start a conversation See the work →