I help technology professionals learn to understand, design, integrate, and troubleshoot AV and collaboration systems so the people they serve can focus on the meeting, not the technology.
We won't start by memorizing products. We'll look at the whole system, question the assumptions underneath it, find what's missing, and build a practical path you can apply to real work.
One private relationship, personalized through an assessment and applied to the systems you actually support.
Learn to see what a room is actually for before touching a spec sheet: user psychology, discovery questions that reveal real meeting workflows, operational priorities, and the honest differences among Zoom Rooms, Microsoft Teams Rooms, desktop apps, and BYOD.
Learn to design in the right order - reliability, then ease of use, then the right features. The depth is there when you need it: audio fundamentals (signal flow, acoustics, gain structure, DSP, echo cancellation), video design and camera placement, and multi-camera automation such as Q-SYS Automatic Camera Preset Recall - a Q-SYS feature, but the principles travel beyond one manufacturer.
Learn to reason about the whole signal path, not one box at a time: audio and video flow, video distribution and USB extension, Dante and video-over-IP, networking (VLANs, PoE, IP planning), control systems, GPIO, serial control, and APIs.
Learn to make failures rare, visible, and cheap: systematic troubleshooting, monitoring that catches faults before the meeting, and repairability that fixes them remotely - power control and PoE resets, remote device access, safe entry to the segregated AV network, IP documentation, credential ownership, commissioning and acceptance testing.
Why teach it this way: in rooms designed using this approach, more than 90% of issues were resolved remotely in five minutes or less, without a truck roll or on-site assistance.My installed base across 13 years building and running an AV company - evidence for the methods taught, not a promise that every learner or system will repeat it.
Private, personalized, and built around the systems and capabilities that matter to your work. A fit conversation decides the right path and duration - before anything else happens.
Mentorship or the Intensive? Mentorship develops one technology professional, weekly, over time. The IT Empowerment Intensive below is a concentrated 1-2 day intervention for an organization's whole IT team, prescribed after an inspection.
Mentorship grows capability over months. The catalog below answers the organization's question this week: what's failing, what it costs, what the quote hides, and what to do next. For organizational room problems, start with an inspection - deeper audits, intensives, and ongoing advisory are prescribed from what it finds.
By the end you’ll know what’s failing, why, what it’s costing you, and whether it’s worth fixing - in writing, the same day.
I join two of your real meetings and experience your room exactly the way your far end does.
Same inspection, in your building - for executive-room stakes or when the politics need a person present.
House rule: I never troubleshoot live. Observe, document, debrief.
Published flat-fee ranges, on the wall where an honest business keeps them - independent advice shouldn't begin with hidden pricing. Nothing below gets sold cold: the inspection decides what, if anything, comes next.
What moves a range: room count and complexity, remote versus on-site, and the size of the footprint under advisory. Exact scope and fee are confirmed in writing before work begins.
Your team comes out smarter than the people who installed it.
When the inspection finds systemic trouble, we baseline the whole footprint: every room, with your IT lead beside me - audio paths, network, configuration versus intent - explained aloud as I go.
The $250/hour integrator ticket goes away.
When the inspection finds the gap is capability, not equipment, this is the prescription: I embed with your IT department and teach what integrators never leave behind - your people drive, I coach side by side with them, on your systems.
Money kept - before the signature, not after the install.
You’re holding a $40-75K meeting-room quote. I’ll tell you what to demand before signing, which assumptions will bite at install, and how the number sits against my own pricing history across hundreds of rooms.
Rooms that just work - and stay that way.
Ongoing access to a 20-year AV pro, async: room standards, quote and design review, acceptance checklists, “what should IT own vs. the integrator,” one scheduled monthly call. I’m not your AV help desk - I’m the person who keeps your rooms from becoming expensive tribal knowledge. And when your footprint justifies a full-time hire, I’ll say so and help you hire them.
Ask IT teams where they actually wanted outside help and the answer is consistent. This August I asked an IT leader whose Zoom Rooms my old firm built - his team runs them in-house today. The rooms that hurt were the ones with audio gear nobody taught his team to set up or troubleshoot.Paraphrased from an August 2026 conversation - anonymous by design.
↳ For organizational room problems: start with the inspection. Everything else on this wall is a prescription - or it doesn’t happen.
Not sure which situation is yours yet? Three questions sort it - quote, rooms, or build →
One meeting. One verdict, in writing. If you don’t need me after that, I’ll be the one who says so.
Quote on your desk? Same form - describe the quote and your deadline. I’ll reply within one business day with a secure way to send it over.
Got it. Your note is in my queue - you’ll hear from me within one business day.
// no ticket number, no autoresponder theater. Just a reply from me.