Production AI systems, from the person who builds them.
Three rungs: map the work with the Intensive, build the agent or the system, keep senior direction on retainer. Every build is an AI agent you own, not a per-resolution subscription.
Priced and scoped up front. Straight answer on fit either way.
An agent you own, not a subscription.
Seven ways in. One ladder.
The Intensive is the front door. When it is time to build, the work runs through one of these.
Map the work before you spend on it.
The systems themselves, priced and scoped up front.
Senior AI direction that stays accountable.
The AI Systems Intensive. Two ways to run it.
A working day with the operator who ships the systems, not a strategy presentation handed off.
Pressure-tested against your real stack, real constraints, and real team. You leave with the map and the plan, not a deck.
Anywhere in the world. This is how most US teams run it.
A sharper, distraction-free day on-site.
From the brief to a plan you can ship.
Each stage de-risks the next: the audit feeds the day, the day produces the map, and the follow-up keeps the plan honest while you execute.
Stage 01 starts the moment you book.
Pre-work audit
I review your stack, workflows, and goals before the day, so we start deep, not at zero.
Live working day
A full day, just us, mapping AI systems and pressure-testing them against your real constraints.
Plan + map
You leave with a clear systems map and a sequenced 30-day priority plan.
14-day follow-up
Two weeks of async access for course-corrections as you start executing.
Operator, not consultant. The map comes from the practice.
I build AI products first, then bring the patterns that survive to your work. Most AI pilots stall because they're designed in slide decks, by people who have never had to deploy under real constraints. MIT Project NANDA's 2025 State of AI in Business put numbers on it.
67%
of externally-built AI reaches deployment.
MIT NANDA · 2025
~95%
of AI pilots show no P&L return.
MIT NANDA · 2025
16+
years designing and shipping software.
Operator practice
7
live properties running the patterns.
The ventures
No slide decks.
The day ends in a systems map and a sequenced plan, not a presentation handed off to someone else.
Operator, not consultant.
Live products run on the patterns you get. What breaks in mine never reaches yours.
Compressed, not stretched.
One day plus follow-up, built to deliver a long discovery phase's clarity in a fraction of the time.
Built, not claimed. The systems behind the pitch.
Who this is for. And who it isn't.
Three signals each way. If the left column reads like you, book the call.
Past the should-we question.
You're a founder or operator who has stopped debating whether to use AI. You need a concrete plan to ship it.
You want operator clarity.
From the person who actually ships the systems, not a slide-deck consultant or a Big-4 analyst.
You can act on the plan.
Decision-maker authority. Once the plan lands, you can move on it without a six-month committee detour.
You want done-for-you.
Skip the Intensive and go straight to the engagement that matches your work. The builds are listed above.
AI isn't a priority yet.
Early-stage or exploring? Read the blog first, and come back when shipping the systems becomes the goal.
You want long discovery.
This is a one-day intensive, built to compress a long discovery phase into a day, not stretch it out.
Start with a short call. Straight answer either way.
We confirm fit, scope the pre-work, and put a date on the calendar. The call is the application.
Before you book
One letter, every Sunday. Working systems, not hot takes.
Build logs, working systems, and field notes from running a portfolio of AI ventures.