I build things. All kinds of things.

My background is in mechanical engineering and industrial fabrication — designing and building custom automation systems for production environments. I spent years solving problems the hard way: in person, on-site, with metal and motors and deadlines.

Over time, that work expanded into software and AI. I started building infrastructure to support my engineering business — automation tools, data pipelines, AI agents to handle research and scheduling. What started as productivity tooling became its own discipline.

Today I run a fleet of AI agents on self-hosted infrastructure, build custom automation systems for clients through St. Louis Solutions, and work on the kinds of problems that require both a wrench and a terminal.

Practical First

I don’t design in a vacuum. Every solution is built around real constraints — budget, timeline, environment, and the people who have to operate it. The best system is the one that actually gets used.

Depth Over Breadth

I’d rather go deep on a problem than spread thin across ten. Whether that’s spending a week understanding a production line or months building a reliable AI infrastructure — the work deserves real attention.

Own What You Build

I self-host everything. I prefer tools I can fully understand and control. This isn’t just a philosophy — it shapes how I design for clients. If you can’t own and maintain it, it’s a liability.