Agentic AI consulting · 25+ years building software

I build things.

Currently helping teamsship with AI agents

For over 25 years, I've been building software, launching companies, and shipping open source. These days I spend my time on AI agents — running them in production, measuring what they really cost, and learning where they don't belong. From genetic algorithms to agentic AI, I follow the interesting problems.

Brian McQuay

What I Do

01

Consolidate scattered AI efforts

Three teams, three experiments, no shared strategy, and nothing in production. I've done this cleanup before: find the duplicated work, kill it, and leave the org with one direction instead of five.

02

Cut what your AI is costing you

Most teams are burning several times what they need to and can't see it. This is telemetry, context budgeting, and architecture — not prompt tweaking. I've taken a single task down 70% without losing anything.

03

Keep quality from drifting

Agents still make bad architectural calls, and the slop compounds quietly until it's everywhere. Quality gates, ticket contracts, and regression tests for work that isn't deterministic — so your standards actually hold when output goes up.

04

Know where AI doesn't belong

Half of what teams route through an LLM should be a script. Getting that boundary right is usually the cheapest win on the table, and nobody selling you AI will say it out loud.

What are you stuck on?

Tell me what your team is trying to do with AI and where it's going wrong. A few sentences is plenty to start.

If it's something I can help with, I'll say so. If it isn't, I'll say that too.

Or find me elsewhere: