OperatorIQSign in
The practice · owner to owner

AI Consulting.

That’s the noisy name, and we’ll say it once — it’s the door you came in through. What’s behind the door is different: an operator who built his own AI working environment, with live products and measured receipts, teaching other operators the discipline underneath it. Not prompts. Not another subscription. The structure that decides whether AI compounds in your business or just adds noise.

Start the conversation →

Understand the tool before you use the tool

Most shops meet AI the same way: buy the subscription, watch the demos, get a week of wow and a month of drift. That’s not a tool problem. The models are the easy part — you have the same ones I do. Building with AI runs on what you believe before what you buy: what the tool actually is, where it’s strong, where it lies, and how your team holds it accountable. Get that structure right and every hour spent with AI leaves something the next hour builds on. Get it wrong and you’re renting magic tricks.

What I teach

Six commitments. Every engagement runs on them — and every one of them was built in the field before it was ever taught.

Understand before you operateWhat the tool actually is and does, before it touches your workflow. Ground truth first: read the live system, not the sales page.
Infrastructure that compoundsWorking sessions that open and close like job sites, records that carry forward, protocols your whole team runs. Value that stacks instead of evaporating.
Concepts, not commandsYour team learns to think in the concepts, not copy prompts. Discovery creates owners; prescription creates dependents. I teach the first kind.
Methodologies and protocols, not just promptsHow work opens, how it closes, how a claim gets verified before anyone trusts it. The prompt is the last ten percent.
What → How → Who → WhySettle what is true, then how it works, then who owns it — never in reverse. And keep asking why you're building at all. First principles, not fashion.
Questions of force, not opinionStructured questions that pull out what your organization already knows but has never said out loud. Discovery, not brainstorming. The answers were already yours.

I got here by building. The field agrees.

I built my practice first and read the field second. It turns out the published literature has names for most of what I was already running — and where it has none, I kept my own. That’s the credential worth checking: not that I read about these ideas, but that I arrived at them independently, in production, and can show the receipts.

the field
observability-drivenGround truth firstCheck the live system before trusting any document about it. The document lies politely; the system doesn't.
the field
evidence-graded promotionOne is an event, two is a pattern, three is a practiceNothing becomes a rule in my shop until it has proven itself three times. Enthusiasm is not evidence.
the field
separation of dutiesClean handsThe mind that decides is never the hand that executes. Some workers get zero judgment on purpose.
the field
secure by designDesigned absenceThe safest way to keep a capability from being misused is to not build it. Absence is a feature you can ship.
the field
negative testingAsserted vs. enforcedA control described in a document is not a control. It counts once you've run the attack and watched it fail.
the field
context persistenceThe close writes the next openNo session ends without recording what shipped, what's owed, and where the next one starts. Momentum is a system, not a mood.

The receipts

Counts, not adjectives — measured 2026-08-08, every number reproducible by a recorded command.

8
live domains · products in market
measured 2026-08-08
12
production repositories · 3,100+ commits
measured 2026-08-08
620K+
lines of hand-written TypeScript
measured 2026-08-08
9 days
fastest build · first commit to revenue
measured 2026-08-08
Ask to see a measurement and I’ll show you the command, not a slide. That’s rather the point.

Ask a consultant about their failures

If you get a shrug, they haven’t operated anything. Here’s one of mine, told straight.

This spring I built a quality gate whose entire job was catching fabricated claims. Its own documentation carried one — it described a guard that had never been built, and the test suite stayed green while I attacked the exact thing it claimed to protect. The fix wasn’t a patch. It was a standing rule that now governs every build in this house: a control doesn’t exist until you’ve run the attack and watched it fail. I keep a named and dated library of failures like that one, and it’s the most valuable asset I own. You trust the tools in your shop that earned their handles by breaking. Same principle.

How it works

The first conversationno deckOwner to owner: where AI already sits in your building, where the confusion is, what compounding would look like in your operation. If I'm not the right fit, I'll say so and point you at something honest.
Working sessionsconcept-firstYour real workflows on the table, your team in the room. They leave owning the ideas, not renting mine.
The environment installfor teams ready to buildStanding up the working structure — the protocols, the records, the verification habits — in your own accounts, tuned to your operation.
You own everything. Everything lands in your accounts and your documents. If we stop working together, all of it keeps working.
Concepts transfer; dependence doesn't. The engagement is designed to make me less necessary every month, not more.
No inflated claims. Every number I show you is measured and dated, and I'll show the measurement. Expect the same standard pointed at your vendors.

Talk first. Everything else follows.

There’s no deck and no proposal template, which tells you most of what you need to know.

Start the conversation →