About

Seven years deciding which companies got funding. Now I help teams decide what's worth building with AI.

I read businesses for a living and now I train teams to read AI with the same eye: what actually works, and what's just noise.

I help people and businesses build AI systems that actually work, systems that pay back in hours saved and money earned.

Why me

I don't teach AI as a tech person.

I teach it as someone who spent years learning to tell what works from what only looks like it does.

For the past seven years I worked inside startup accelerators, running programs and standing next to hundreds of founders as they built. Program after program, in the room, I watched the same thing play out: which companies actually held up, and which ones only sounded like they would.

A lot of that work was people work and my job was to take a room of nervous founders and get them asking sharper questions, trusting the process, and shipping something real.

Training a team well is the same job, because the tools are the easy part. Any team can learn the buttons. The hard part is knowing which one earns its place in the workflow, which one is a demo that falls apart by Monday, and where the real hours actually get saved. That is what I train teams to see.

How I teach

Three rules, in every class and every call.

01

No shame, no jargon

You don't need to know AI to start. If something sounds like a technicality, I explain it plainly.

02

One concrete action

Beats 47 saved tutorials you never opened. One step you can actually take, then the next, until it becomes a habit.

03

With you, not for you

You leave knowing how to do it, not depending on me. If I do it for you, you're stuck again next week.

How I work with businesses

Everything I do with companies follows the MOTOR method for AI, at three depths:

Want to talk?

Two ways in: we book the free 30-minute call, or you look at how I work first.

Book the call