I build AI systems for the conversations
that matter most.

Most people who build AI tools have a technology background. I have something different: twenty years inside complex organizations — Amazon, Inc., Sam’s Club, a division of Walmart, Inc., industrial field workforces across pipeline and logistics operations — watching what happens when systems meet real people in complicated circumstances.

That experience shapes how I build.

The populations I design for aren’t edge cases. They’re the majority of the people organizations are trying to reach — skeptical of institutions, not reliably connected, not reading the email, not downloading the app. Getting AI to work for them isn’t a matter of better technology. It’s a matter of understanding why they’re not responding and building the conversation architecture around that reality.

I hold a doctorate in Engineering Management. I apply that discipline to prompts the same way an engineer applies it to a system: structured, testable, built to hold up under pressure. Not generated. Engineered.

Anchor — my proprietary voice AI platform — is the proof of concept. It runs on a controlled architecture, accessible by phone, with no app required. The first application of that architecture to a public health engagement context is underway. It won’t be the last.

If your organization is trying to reach people that existing tools keep missing, that’s the problem I’m built for.