Who I Am

← Back to Home

// The Origin Story

I didn’t come up through CS programs or Silicon Valley incubators. I came up through sales floors, business development trenches, and the kind of client-facing work that teaches you very quickly where the friction is — and what it costs when it doesn’t get fixed.

Years of working in business development gave me an instinct for process: where workflows break, where human time gets consumed by tasks that are really just pattern-matching, and where the real leverage lives. That instinct didn’t go away when I transitioned into technology. It sharpened.

// The Transition

The move into physical security was the first pivot — designing and deploying residential and commercial systems, understanding how layered defense actually works in practice. Not theoretical. Real systems protecting real people.

The move into AI was the second pivot, and it happened the same way the first one did: I watched a technology mature to the point where it could actually solve the problems I’d been watching accumulate for years, and I moved toward it.

2026 is the year AI agents stop being demos and start being infrastructure. I intend to be on the right side of that line.

// What I Actually Believe

Most expensive business problems aren’t technical. They’re operational — manual workflows that grew by accident, human time consumed by tasks that have no business requiring a human, and processes that calcified before anyone thought to question them.

AI agents are the lever. A well-built agent doesn’t replace your team — it multiplies them. One person with the right agent fleet does the operational work of ten. The companies building that muscle now will be the ones setting the pace in three years.

I operate in two worlds simultaneously: physical security (the meatspace layer) and autonomous AI (the digital layer). Both are about the same thing at the core — resilient systems that work without you having to think about them.

// Philosophy

Complexity is not a feature. The best systems are the ones that make hard things look effortless. That means doing the unglamorous work up front — the discovery, the architecture, the testing — so that by the time something goes live, it just works.

I have no interest in impressive demos that don’t survive contact with reality. I build things that run in production.