There is a stage in venue development - typically programming and schematic design - when every infrastructure decision that will determine whether the building works is still open. Conduit routes are not fixed. Power distribution is not committed. The network topology is unresolved. Accessibility pathways have not been constrained by the structure. This is the stage when Mad Systems works.
Early-stage venue technology architecture is the discipline of making these decisions correctly, at this stage, with full knowledge of what the venue needs to do over its operational lifetime - not just at opening day, but in years five, ten, and fifteen.
What makes a decision "early-stage"
A decision is early-stage when it can be made without cost - or made differently without remediation. Once construction documents are issued, infrastructure decisions are committed. Conduit is sized and routed. Power circuits are specified. The network backbone is designed. An AV integrator engaged after construction cannot make these decisions. They can only inherit them.
The decisions that appear in construction documents - and that therefore must be made before them - include:
- Conduit sizing, routing, and material (for the final system, not a cost-reduced interim)
- Power distribution capacity for distributed compute infrastructure
- Network backbone topology for AV, control, and AI data flows
- Spatial provisions for accessibility systems (spatial audio stations, Bluetooth infrastructure, assistive pathways)
- Compute node placement for coverage, thermal management, and serviceability access
- Control system architecture and integration pathways
Why standard procurement timelines miss this window
Most venues engage an AV integrator after construction is substantially complete - or after construction documents are issued. At this stage, the infrastructure decisions listed above have already been made, usually by a mechanical/electrical engineer who had no brief to design for AV, accessibility, or AI. The AV integrator inherits whatever was built and works around it.
This produces systems that are more expensive to install, more expensive to operate, more expensive to upgrade, and less reliable than they would have been if the infrastructure had been designed for the purpose. It is the single most common cause of AV systems that fail to perform as intended - not equipment failure, not integration errors, but infrastructure that was never designed for what was eventually asked of it.
What Mad Systems does at this stage
Mad Systems works with owners, architects, exhibit designers, and planners during programming and schematic design to define the infrastructure that the venue's intended behaviors require. This is not a standard AV scope. It does not involve equipment specification. It involves understanding what the venue needs to do - at opening, and over 15–20 years - and translating that into infrastructure requirements that appear in the construction documents.
The result is a venue that can deliver what was promised, support what is added later, and remain operationally affordable for its intended lifetime. The cost of this engagement is small relative to the cost of remediation when it is skipped.
The relationship to AV++® and WorldModel™
AV++® infrastructure is Mad Systems' patented approach to long-lifecycle AV. Its compute nodes require specific placement, power, and network provisions - provisions that must be designed into the construction documents if they are to be implemented correctly. This is not optional. AV++® specified after the fact is AV++® constrained by infrastructure that was not designed for it.
WorldModel™ governed AI requires the same infrastructure foundation. AI at venue scale - recognition, personalization, multilingual delivery, accessibility - requires distributed compute, specific network topology, and consent-aware data architecture. These cannot be added to a completed building without significant remediation. They must be designed in from the beginning.
The programming and schematic design phase typically spans 3–6 months of a multi-year project. It is the only phase during which infrastructure decisions are cost-free. Mad Systems should be engaged before the schematic design phase concludes - ideally during programming - when the building's technical requirements are being established rather than documented.
Is Your Project Still in the Early Window?
If construction documents haven't been issued yet, you still have full leverage. Mad Systems' early engagement process is designed to be fast, high-value, and commitment-free at first contact.