Engineer first. A team of nine behind him.

I grew up in Cave Creek, Arizona. I studied software engineering at ASU while working at Starbucks, and Starbucks ended up paying for the degree. That turned into an internship as a software application developer, then a full-time job, then a move to Seattle.

I spent four years there writing software inside a very large company. Then the mass layoffs came, and I came home to Arizona.

Through all of it I ran All For One on the side, building websites for local businesses. Now it is the main thing.

The work has grown a long way past websites since then. These days I spend most of my time on the systems behind the site: checkout logic, customer data, scheduling, follow-up, the admin screens nobody else builds. I'm an API and database kind of person. The parts of a business where the numbers have to be right are the parts I like best.

I run my own business on AI every day. My operation runs across three machines that share one memory: every client, every open question, every decision written down where the next session can find it. It drafts, checks, researches and reminds. It does not get the final say.

That is the same setup I build for clients, with the same rules, because I learned the hard way where AI needs guardrails:

• Numbers come from your systems, never from the model. A plausible fake number is worse than no number.
• A person presses send. Nothing reaches your customer without someone on your team deciding it should.
• Fail loudly. When something breaks, it says so, out loud, before a customer finds it.
• Read what you have before you build. Most projects start by reading your data, and that is often where the money is.

Mostly local service businesses and e-commerce stores. Recent work: irrigation, HVAC, shutters, home care, shop equipment, publishing and nonprofits. Owners who have outgrown the tools they started with and are tired of being told to switch everything.

You get the engineer, not a queue.