Software engineering and AV systems work from one practice, so the people who write the code have also commissioned the hardware it talks to. Engagements range from a one-week review to multi-year platform ownership.
PHP 8, Laravel and Eloquent, Node.js, and plain modern JavaScript. We build the internal tools that run a department and the customer-facing portals that represent a company — with the same discipline either way: version control from day one, automated tests where they pay for themselves, and a CI/CD pipeline so a deploy is a non-event.
Recent work includes a multi-user project-management and financial-tracking platform now in its 27th major release, a QR-driven mobile inventory system for a broadcast-facility buildout, and a stack of smaller line-of-business tools that replaced spreadsheets and e-mail chains.
PostgreSQL, SQL Server, MySQL — plus the places data goes when it outgrows a single database: Databricks and Delta Lake for archival and analytics, graph and vector stores when relationships or similarity matter more than rows. Schema design, index and query tuning, audit infrastructure (triggers, computed columns, change logs), and phased migrations that keep the old system serving users until the new one is proven.
AVIXA CTS-I credentialed, with manufacturer training across QSC Q-SYS, Biamp Tesira, Crestron DMC, Extron, BSS, Polycom, Shure and Dante. Two decades of field engineering on enterprise and broadcast installations means the programming is done by someone who has also pulled the cable, commissioned the DSP, and sat in the room at 2 AM making the blend seamless.
The space between products is where most organizations lose time. We write the connectors: REST and OAuth integrations with ERP and ticketing systems (Dynamics 365, ConnectWise, ServiceDesk Plus), scheduled data pipelines, import tools that convert one vendor's export into another's format, and the small adapters that let software talk to hardware.
A short, fixed-scope engagement: read the code, map the data model, run the deploy, and come back with a written assessment — what is solid, what will hurt at scale, and what to fix first. Useful before a launch, after an acquisition, or when the original developer has moved on.
Microsoft Access and VBA applications to web stacks. FileMaker and Excel workflows to real databases with real audit trails. Legacy ERP data into its successor. The unglamorous middle of every "we need to modernize" project is where we do our best work — phased cut-overs, parallel running, and no big-bang weekends.