Every session, you re-explain who you are, what you're working on, and what you've already tried. A Personal AI OS ends that — permanently.
Most people use Claude or ChatGPT like a search engine. Ask a question, get an answer, close the tab. Next session — same person, same projects, same reality — you start from zero again.
You explain your industry. Your clients. What you've already tried. Why the obvious answer won't work. The AI gives a generic response. You tweak it manually. It was faster to just do it yourself.
This is not an AI problem. It's a setup problem. And it has a fix.
Same result. Different amount of your time and mine.
You follow the prompt. Claude builds your OS in one session. 45 minutes or 15 — your call.
A focused session where I guide you through building your OS live. You walk out with a working system — not a to-do list.
You show up. I build. I interview you, extract your context, build every file, and set up your first workflows — while you watch and ask questions.
Every session from setup day compounds. Here's what the ongoing lifecycle looks like.
Every Claude Code session opens your OS and reads it. No briefing, no re-explaining. You open the app and start working.
Run /tend-machine. It asks what changed — new project, ended client, belief shifted. Answers update your files. The OS stays current automatically.
You change your own oil. You don't rebuild your own engine. A professional audit — every file checked, broken workflows repaired, new capabilities added. Free health scan to start; $47 one-time, or $280/year.
"What configuration of context is most likely to generate the model's desired behavior?"— Anthropic Engineering: Effective Context Engineering for AI Agents
I'm a strategy and AI consultant. I've worked with public companies, startups, and mid-market firms across fintech, health tech, legal, and construction. Ex-Microsoft.
I built my own AI OS before most people knew this was possible — because I needed it. I run it daily through real consulting work with real clients and real stakes.
This is not a course I built to sell. It's infrastructure I built to work — and then decided to share.
The setup prompt I give you is the same system I run on. When I build your OS, I'm doing what I'd do to my own.
No. Claude Code is a desktop app — available on Mac and Windows. You paste a prompt, Claude does the rest. If you can send an email, you can do this.
Claude Pro ($20/month) is enough for most people. Claude Code is free for Claude Pro subscribers. You don't need a separate Claude Code subscription to start.
The main setup prompt is built for Claude Code. A version for OpenAI (Codex/Cursor) exists and is available on request. The underlying concepts work in any AI coding tool — the prompts are just optimized for Claude.
As long as you tend it. The weekly /tend-machine routine takes 3 minutes and keeps your context current. A mechanic session once or twice a year keeps the system sharp as your work evolves.
No — the setup works on an existing folder too. If you have files already, we audit what you have and build from there. That's exactly what the Done-For-You session is designed for.
In the workshop, you build your own OS while I guide you live — small group, shared session, questions answered in real time. In the done-for-you session, I interview you 1:1 and build everything myself while you watch. Workshop: you do the work with support. Done-for-you: I do the work, you get the result.
Pick the version that fits. The self-serve prompt is coming soon — or build it with me now.