The person behind
the work.

I'm an engineer who's spent my career in the gap between technical teams and the humans they serve. CS, Solutions Engineering, Support, TAM — I've built them from scratch, scaled them, and learned what actually works (and what doesn't).

Now those orgs are being rebuilt around AI, and most of the advice comes from people who have never run one. The questions boards and executive teams are actually asking — do we need Forward Deployed Engineers, do the Solutions Architects become that, how does Support migrate without breaking trust — are operating questions, not tooling questions. That's the work I do.

And I build. Not as a side hobby, but because shipping is how I stay honest — AI products, simulations, books that double as working software. Some of it is proof of the work. Some of it lives in the Lab because I couldn't not build it. The instinct is the same either way: make the complicated thing usable.

Four books, thirteen products, hires in the hundreds. I know what the table looks like from every side. Now building for the AI era without fear.