Straight answers - the kind you can forward to whoever signs the check.
You do. The configuration, the documentation, the cue data - it's your church's. The platform runs in a cloud account you can be given access to, and the on-prem pieces run on machines in your building. This is a craftsman building you a thing, not a landlord renting you one.
The system doesn't need him to run. It's built the opposite way: everything is documented - a runbook per device that names failure modes in plain language, a self-documenting weekly pipeline, and volunteer surfaces designed so nobody has to hold the system in their head. The monitoring layer is read-only by design, so even a total tooling failure leaves your rig running exactly as-is. Handing off well isn't an afterthought here; it's one of the five engagement steps.
Yes. The partnership buys watching, updates, and a builder on call - not permission for the system to keep running. Cancel it and Sunday still fires.
No. The platform reads from your planning system - any service-planning software or church database with an API works. If your team plans the service somewhere, the system can read the plan there.
Usually very little - the point is making your existing rig behave like one instrument. Typical additions are small: a Stream Deck, maybe a mini PC for the on-prem relay, a game controller if the youth booth wants one. If something genuinely needs replacing, you'll hear it straight, with the reason - Bezalel doesn't sell hardware and takes no dealer margin, so there's no incentive to pad a rack.
The platform already speaks to Ross switchers, ETC/Hog lighting, ProPresenter, Yamaha consoles, Shure wireless, Blackmagic decks, Resi encoders, LED processors, and more - about twenty protocols in production today. If your device has a control surface, an API, or a network port, it's a candidate. The walk-the-rack assessment answers this exactly, for your room, before you commit.
A typical build runs two to four months from the first walk-through to hand-off, with most of the work done remotely and on-site weeks for install and training. Your services don't stop - the system comes up alongside what you already do, and you cut over when it's proven.
A scoped build agreement (fixed price from the assessment - see what it costs), then a simple month-to-month partnership you can cancel anytime. No multi-year lock-in.
Your service data stays yours. The monitoring layer reads gear health, not people. And the volunteer-facing tools carry hard rules built into the software - no volunteer leaderboards, no scoring anyone's off-air work - the same standards on the volunteers page.
Because this is white-glove by design. Each build gets the builder himself - in your building, on your gear, with your people. The trade is intentional: fewer clients, deeper systems, ones that hold up for years.