Construction, Not Production
Most church leaders approach an AVL project thinking about gear: the console, the speakers, the LED wall, the cameras. That is the visible part, and it is the part everyone is excited about. But by the time a project is finished, the majority of the work and a large share of the budget will have gone into things nobody sees.
Jake Gosselin and Luke Jackson both came into AVL integration from ministry, as worship pastors who ran the systems they now design. In this conversation they walk through what they learned building Churchfront into a national integrator: an AVL project has far more in common with construction than it does with production. Understanding that difference early is what separates a project that lands on budget from one that surprises you halfway through.
Every component depends on infrastructure
A PTZ camera needs a mount anchored into the wall. A speaker array needs rigging rated for its weight. A cable needs a conduit pathway to travel through safely. As Luke puts it, every component is only as good as the infrastructure that surrounds and supports it.
For most churches, especially those in buildings constructed before modern AVL existed, that infrastructure is simply not there. Four categories come up on nearly every project:
Structural. Can the building carry what you want to hang from it? LED walls, line arrays, lighting trusses and fixtures all put real load on a roof structure that was never designed with them in mind.
Electrical. AVL systems run on electrons. High voltage feeds amplifiers and lighting fixtures. Low voltage cabling carries audio, video, data and control signals between devices. Older buildings frequently lack both the panel capacity and the conduit pathways to route any of it properly. Free-running cable through a ceiling is common, but it is neither safe nor professional.
Architectural. Does the room itself serve the experience you want? Redesigning a stage may mean adding or removing walls. A tech booth has to exist somewhere, sized for the number of operators you actually have, positioned where those operators can see and hear the room.
Mechanical. Equipment racks generate heat. They need ventilation, and they need a room large enough to service them. Churches routinely put racks in closets that are too tight to work in, and those closets fill up with cleaning supplies within a year.
This is a safety conversation before it is a quality conversation
It is easy to hear all of this as a list of nice-to-haves. It is not. Rigging load limits exist because buildings fail. Electrical panel capacity exists because circuits overload. Ventilation exists because heat shortens equipment life and starts fires. A feasibility study is not an upsell. It is the step where a structural engineer, an electrical engineer or an architect gets pulled in before anyone commits to something the building cannot safely support.
When to bring AVL into the conversation
For new construction, the right moment is as soon as the architect has schematic design or a basic building model finished. Plan views and elevations are enough. At that stage AVL can look at size, shape and sight lines, and the design can still flex in both directions before anything is locked.
Practically, that means reaching out roughly six months before your permitting deadline. That window covers programming and pre-design, plus the initial engineering drawings that go into the architect’s permit package.
Renovations move faster because the building already exists, though larger renovations that require a permit package need the same lead time.
Architects who do excellent work on buildings are not always designing for a church volunteer’s experience. Where a tech booth goes, how many people it seats, whether the rack lives backstage or beside the booth: these are user questions, not building questions, and they are much cheaper to answer on paper than in the field.
Designing for the person who actually runs the system
In most churches the end user is not the executive pastor. It is the volunteer who shows up week after week with real commitment and limited technical background. That changes the design. A system built for a full-time production director with a systems engineering background is not the same system a volunteer team can operate confidently.
Churchfront designs for both, and the conversation upfront determines which. Getting that wrong is where support relationships usually break down: a church ends up with a well-installed system that is the wrong size for its context, driving a Ferrari in second gear.
Why there is no bid without a design
A common request is a bid on an AVL system, sight unseen. The honest answer is that it cannot be done responsibly.
Luke frames it as prescribing before you diagnose. If a doctor wrote a prescription without running any tests, that would be malpractice. The same logic applies here. In construction, a bid requires bid documents: a plan set with specifications, quantities and dimensions that a contractor can price accurately. Without a design, any number is either a wild range or a guess that becomes a change order later.
What can happen in a first conversation is a realistic ballpark based on the size of your room and comparable projects. That is useful for early budgeting. It is not a bid, and Churchfront only bids its own designs.
The three phases: consult, design, build
Consult. A pre-design visit brings a Churchfront consultant to your church for a few hours with your senior pastor, executive pastor and key operators. The team surveys the space and existing system, or reviews architectural plans on a new build, and gets to know your mission, culture and goals. There are real conversations about funding, growth and what the ministry is actually trying to do.
The deliverable is a program report, not a bid. It defines the systems, explains them in language a lead pastor can follow, and sets budget parameters for equipment, materials and labor. Equipment and materials estimates target a five to ten percent range, before any drawings exist.
Design. The program report becomes the roadmap. Designers build the system in Vectorworks, a BIM platform that produces precise drawings and calculates real quantities: conduit sizes and runs, cable lengths, strut and truss requirements, rigging support. Acoustic modeling shows how the PA will behave in the room. Lighting models show coverage and lumen levels on stage and in the house. Camera angles get previsualized.
Those calculations are the difference between a smooth build and a stack of change orders. Your electrician will ask where the conduit goes, how big it needs to be and how much you need. There is no answer to that question without a design. The result is a plan set, typically a dozen pages on a smaller project and up to fifty on a full new build, detailed enough to coordinate with every other trade.
Build. This is where the final bid lands, priced against a design that already exists. Pre-installation includes project management, systems engineering (device connections, audio and video routing, network configuration) and rack fabrication at the Churchfront warehouse. Equipment is procured and stored insured until install week, so the church is not managing pallets.
Installation often runs in phases. A rough-in trip lands after framing, drywall and electrical rough-in, while rig points and cable pulls are still clean work. The main install week comes later, because AVL is largely a finish trade. When components are in and terminated, every cable is tested, verified and labeled, and the drawings are updated to as-built condition.
Commissioning closes it out. Consultants return to train your team, cover best practices across audio, video, lighting and network, and stay through the first week of operation: rehearsals, sound checks and the first services.
Partner, not supplier
Unlike an electrician, an AVL integrator does not disappear when the building opens. AVL systems are dynamic. Settings change, firmware updates break things, volunteers turn over. The question is who picks up the phone.
Churchfront staffs weekends, because that is when churches gather and when volunteers need help. A real person on the team pulls up your as-built documentation and works the problem with you. That ongoing relationship, and the consulting and training that goes with it, is the part most churches do not think to ask about during an interview and miss most afterward.
Two questions that come up constantly
“Why not hire a local integrator?” Usually the motivation is saving on travel and labor. The better questions are how many churches that firm has actually done, whether their consultants are on a commission structure tied to what is on their shelf, and whether the company will still be around in five years. A cheaper labor rate can be erased by change orders from a blind bid. On a national integrator, travel is a real premium during install, but it is a small percentage of total project cost, and it buys specialization. Churchfront works exclusively with churches.
“Our bylaws require three bids for board approval.” The instinct behind that rule is sound. The gap is what a bid actually is. Ask your board whether the church has a design yet. Without a plan set, there is nothing objective for three firms to price, and three numbers built on three different assumptions are not comparable. A more useful version of that policy is three conversations: interview three potential partners on process, church experience, portfolio and support model, the same way you would evaluate a hire.