How It Works

A method, not a magic box.

Four deliberate phases. Your company's knowledge does the work; your engineers stay in control.

A hand drawing a process diagram with a black marker on a glass whiteboard.

The four phases

  1. Mapping where the hours goEach department's week laid out as a bar — programming, service and project management — with the repetitive blocks that never needed human judgment highlighted.ProgrammingServiceProject mgmtrepetitiveneeds judgment
    Phase 01

    Understand

    We map where your team's hours go — and which never needed human judgment.

    • Workflow review with each team
    • Inventory of repetitive tasks
    • A look at your platforms and files

    You get: A prioritized list of what's realistic to automate.

  2. Your knowledge, organizedPast projects, programming standards and service logs flow into a single knowledge base that belongs to your company, with access agreed up front.ProjectsStandardsService logsYourknowledgeaccess agreed
    Phase 02

    Learn

    The system is built on your company's knowledge, not a generic idea of AV.

    • Past projects and standards
    • Service history, manuals and notes
    • Agreed limits on what it can access

    You get: A knowledge foundation that belongs to your company.

  3. Tools with a review stepYour company AI powers assistants for programming, service lookup and documentation. Every output passes through a person who approves it before it's used.Your AIProgramLookupDocsYou approve
    Phase 03

    Build

    Tools that live inside the platforms and files your team already uses.

    • Programming, service or docs assistants
    • Integrations with your current tools
    • Review steps — people approve output

    You get: Working tools your team uses on real projects.

  4. A loop that compoundsTools in use generate feedback from your engineers and techs; their fixes and new projects fold back into the knowledge base, which makes the tools better on the next pass.Tools in useFeedbackKnowledgeNewjobscompounds
    Phase 04

    Improve

    It gets more useful as your knowledge grows, with your people refining it.

    • Feedback from engineers and techs
    • New projects and fixes folded back in
    • Regular reviews of what to automate next

    You get: A system that compounds instead of going stale.

The system

Your knowledge in. Useful tools out.

Built on what your company already knows, delivered into the tools your team uses.

AV Method // Company AI Platform
Your Environment
Programming Standards
Project Files
Documentation
Service History
Company AI
Tools For Your Team
Programming Assistant
Service Assistant
Estimator
Knowledge Search
Documentation
Before / After

Spend your engineering time on engineering.

A new programming project, from kickoff.

Starting a new programming project, before and afterBefore: the programmer spends most of the project setting up by hand — creating folders, copying logic from a past project, searching old programs, building initialization, adding standard modules, checking naming and writing documentation — leaving a small slice of time for craft. After: AI builds the foundation from company standards, the programmer reviews it, and most of the time goes to custom UI, complex automation, user experience and system optimization.BEFOREAFTERFoldersCopy logicSearchInitModulesNamingDocsCraftAI buildsfoundationReviewCraftCustom UIAutomationUXOptimizationPROJECT TIME
Ecosystem

Built around the tools your team already uses.

No new platform. We plug into the systems you already run.

Control & AV platforms

  • Crestron
  • Q-SYS
  • Control4
  • Savant
  • Lutron

Design, estimating & productivity

  • D-Tools
  • Jetbuilt
  • Microsoft 365
  • Google Workspace
  • Slack
  • Teams

Your internal systems

  • Internal documentation
  • Project files
  • CRM
  • Ticketing systems

Platform names indicate the environments we work alongside. They do not imply partnership or endorsement.

FAQ

Common questions

Does this replace our programmers or technicians?

No. The goal is leverage, not replacement. AI takes the first pass on repetitive work — scaffolding, lookups, documentation — and your people review, decide and ship. Nothing runs production work unattended.

What do we need to have in place before starting?

Less than most companies expect. Past projects, standards documents (even informal ones), service tickets and manuals are all useful. Part of the first phase is working out what you already have and what's worth organizing.

Which AV platforms do you work with?

We work with integrators across Crestron, Q-SYS, Control4, Savant, Lutron and others. The system is built around your projects and standards, so it follows the platforms your team actually uses.

What happens to our company data?

Your projects, standards and processes are treated as confidential. We agree up front on what the system can access, and the knowledge it's built on stays your company's. See our Privacy Policy for how we handle information shared with us.

How do we get started?

Book an AI Workflow Review. It's a focused, no-obligation conversation about where your team's time goes and what AI could realistically take off their plate.

Book an AI Workflow Review

See what this process looks like for your company.

Phase one starts with a conversation about where your team's time goes.

How a workflow review worksThree steps: we talk about your team's work, map the repetitive tasks, and give you a plan of what AI can realistically automate.TalkMapPlan
  • 30 minutes with someone who knows AV
  • An honest read on what's automatable
  • No obligation, no slide deck

Fields marked * are required.

No obligation. We use your details only to respond — see our Privacy Policy. Or email hello@av-method.com.