The paperwork is the proof.
Every Apex event is documented before load-in and after the show.
Case studies here are engineering documents.
Most AV "case studies" are photographs with adjectives. Ours are the actual deliverables: the acoustic model we built before the event, the frequency plan we coordinated, and the outcome report that closed it.
When a client permits us to publish, you'll see their name. When they don't, you'll see the numbers anyway — because the engineering stands on its own.
How every entry is built.
Each published entry follows the same four parts, with a coverage plot or model rendering from the event itself.
- The stakes
- One sentence on what rode on the sound.
- What we engineered
- The acoustic model, the RF channel count and the redundancy design.
- The outcome
- Verified numbers only: intelligibility achieved, dropouts, deliverable performance.
- In their words
- A client quote, only with written approval.
Published entries
None yet. An entry goes live only when its numbers are verified from the actual event and, where a client is named, written permission is on file.
Every guarantee ever invoked, published.
We claim zero dropouts and zero unpredictable failures — so when a guarantee is invoked, we publish it here with the outcome and the refund. The moment that changes, this page changes with it. That's what "in writing" means.
Current record: no invocations to date.