I ran a moving company for nine years. I started it with one truck and grew it to 25 people doing hundreds of moves a year around Portland, and I handled everything from dispatch and hiring to quotes and payroll.
Running it showed me where service businesses lose time and money, so now I build the automation that fixes that. I design the systems, write the specs and acceptance criteria, and direct AI coding agents to build them. Then I test and verify everything before it ships.
The biggest thing I've built is a self-hosted controller that lets AI agents like Claude safely use around 690 tools across four servers, with a build, test and security gate in front of every release. The build log is at gocontroller.app.
What's here: the memory platform that gives my AI tools long-term memory (helix-memory-platform) and the Chrome extension that feeds it (membrain-extension), the pipeline I use to find and qualify leads for my automation work (lead-sourcing-pipeline), and the MCP servers that connect Claude to the tools my businesses run on (business-mcp-servers). Those four are public copies of private working repos, with the secrets and server addresses taken out.
I also built a gate and blind-review loop that pushes the sites I build until they read as hand-made (website-refinement-loop).
Smaller pieces: a discovery scanner in Go (paving-agent), an MCP tool for git operations (git-agent), a health daemon for my servers (hostinger-watchdog), local push-to-talk dictation for Windows (whisper-ptt), my MCP gateway design (mcp-tool-flow), and the skill files I use to run Claude sessions (claude-skills).
I'm studying for CompTIA Security+ and looking for work in AI implementation, automation, solutions engineering or technical project management, remote or around Daytona and Orlando. LinkedIn

