The Journey
Why I Build
How a car lot operator became an AI systems architect — and why that combination is rarer than either alone.
Gemini TTS · Aoede voice
Chapter 01
The Car Lot Problem
I ran a 100-vehicle dealership on the Willamette River and watched hours disappear into manual processes that machines could handle. Every title, every recon job, every lead response — done by hand. The inefficiency wasn't a problem. It was an invitation.
Chapter 02
The First Bot
The first automation was a lead response system that could handle basic inquiry routing without a human in the loop. It worked. It saved time. And it showed me something more important: the constraint wasn't the technology. It was my understanding of the problem it was solving.
Chapter 03
The Regulatory Insight
Operating inside Oregon's automotive regulatory framework — DMV compliance, title law, construction licensing — I understood something most AI engineers never will: compliance isn't a checkbox. It's architecture. Every system I build works within constraints that have legal consequences. That changes how you design.
Chapter 04
The Shift to Builder
I stopped automating tasks and started architecting systems. Five LLMs routed simultaneously through a vector database. A RAG diary app with 900+ entries and full contextual continuity. An iOS mechanic app targeting a national market. These were proof of what happens when operational thinking meets technical capability.
Chapter 05
The Vision
AI plus public policy equals civic infrastructure transformation. The homelessness crisis in Portland is fundamentally a massive routing, resource allocation, and compliance problem. If I can untangle Oregon DMV compliance with multi-agent AI, I can apply the same architecture to social services. Portland is the proving ground. City council is the next chapter.
"I approach every AI problem the way I approach a regulatory framework: understand the system, identify the constraints, engineer the solution, measure the result. I'm not looking to learn tech. I'm looking to apply what I've already built — at scale."
