My approach
Start with the work. The tools come second.
Most AI consulting starts with the technology and works backward to your job. I do the opposite — twenty years of UX practice taught me that anything built without understanding the work first ends up unused.
The shape of an engagement
Understand, build, hand over.
Whatever the package or engagement, the arc is the same.
01
Understand the work
Before any tool gets opened: what does your week actually look like? Where do the hours go? What has to stay exactly as it is? This is UX research applied to your own operation.
02
Build on real tasks
Setups get built against your live work, not demo scenarios. If a workflow can't survive contact with a real Tuesday, it doesn't ship. We iterate until it holds.
03
Hand it over, properly
You own the system when we're done — you understand it, you can maintain it, you can change it. Dependency isn't a business model I'm interested in.
Principles
The lines I hold.
The voice stays yours
Every setup is calibrated against how you actually sound — your phrases, your rhythm, your taste. If the output could belong to anyone, it's not done.
Assist, don't replace
AI takes the drag out of the work — the formatting, the first drafts, the busywork. The judgment calls stay human. That's not a limitation; it's the design.
Plain language, always
If I can't explain a recommendation without jargon, I don't understand it well enough to make it. You'll never need a glossary to work with me.
Honest fit, both directions
If a free tutorial, a cheaper tool, or "not yet" is the right answer, that's the answer you get. The long game is trust, not billable hours.
Why design rigor matters here
AI adoption is a design problem wearing a technology costume.
The hard part was never the tools. It's fitting them to how people actually work — which is what design has been doing all along.
Sound like how you'd want to work?
Tell me what you're working on and we'll find the right starting point.
Start a project