Nine weeks. You build something every week. A recipe shelf, two pacing lanes, two live calls a week, and one keystone build that anchors everything else.
What follows: the week-by-week, the two pacing lanes, the felt-sense timeline of the experience, and the four things you keep that don’t show up in the deliverables.
Each week, one ship. Architecture on Monday, build through the week, demo by Friday.
The frame. AI as super intelligence, not toddler. Solutioning as a skill. Design before you build. Dev environment up. You ship your first small recipe. A personal context file, or you wire Claude into a tool you already use. Small, real, yours.
The anchor build begins. Supabase, vector storage, embeddings, schema. We start the spine of everything else. By Friday you have an MCP skeleton running. Barely working, but yours.
Wire in your data. Notion, journal, project history, whatever’s yours. Retrieval, semantic search, tuning. The first time your data flows through your AI on your terms. Nobody owns it but you.
You scope your second build from the recipe library. Solutioning session in 1:1. We look at your life, pick the recipe (or recipes) that fit. Fast lane: pick two. Steady lane: pick one and go deep. I pressure-test before you write a line.
Build the recipe. Debug with the group. Architecture review on Monday, solo build through the week, ship by Friday. Async support all week.
Cron, webhooks, agentic workflows. Things that run when you’re not watching. AI safety basics: prompt injection, secret management, what to keep out of your stack. Plus the gambling mechanics of building, and how to not lose your evenings to an agent loop.
You scope your own build. Entirely your idea. Something neither of us has built before. We design it together: tradeoffs, modular architecture, when AI is the wrong tool, cost management. You start building.
The room picks the topic. Candidates: writing your own MCP server, agentic coding stack, voice and transcription, financial automation deep-dive, autonomous personal agents. Whatever the cohort needs most.
Each person demos to the cohort. Architecture walkthrough, what worked, what broke, what you’ll build next. You leave with three systems you own and a written field note for each.
The cohort is small enough that both lanes get the support they need. Nobody gets dragged. Nobody gets lost.
You ship the MCP in week 3 and stack 2–3 recipesthrough weeks 4–6. By week 9 you’ve shipped five or six things and the third one is ambitious.
You ship the MCP and one recipe deep. Week 7 is your own build. Three systems, shipped, owned. That’s the promise, and that’s enough.
The receipt is the three systems. The shift is what you keep.Here’s what the nine weeks actually feel like.
You’re nervous. The terminal is open. You’re worried you don’t know enough. You don’t yet.
Your second brain works. You query it from Claude and your own thoughts come back to you. Your data, in your AI.
You’re building. Then it breaks. But you don’t feel frustration this time. The problem is interesting.
You demo to fourteen other people. They watch you walk through your architecture. They ask sharp questions. You answer them.
A friend asks how you’ve been spending your time. You tell them. They look at you differently.
Something has shifted in how you carry yourself when the topic of technology comes up. You’re not bracing anymore.
That’s the real deliverable. The systems are real. But the felt-sense shift is what you’re actually paying for.
The three deliverables are the receipt. This is what you’re actually paying for.
Choosing, imagining, weighing tradeoffs. The reflex to look at any problem and ask: what’s the system? What gets built once and runs on its own?You’ll apply this to every problem you have from week four forward, and to every system you build for the rest of your life.
Open the editor, write the thing, debug it, ship it. By week four it’s automatic. The thing that used to feel impossible takes you forty minutes. It’s part of the offering, not a side effect.
Async support, real architecture review, builds-in-progress visible to the room. Nobody at this scale gets lost. The community space stays open after the cohort ends. The room you build in is the room you keep.
Your tools, your data, model-agnostic. When the next model drops, you swap a config line. Nothing you build depends on a single vendor. Nothing you build depends on me.
Two live calls a week. Two hours each.
Monday 6:00 PM CT for the main session. Architecture, teaching, design review.
Saturday 12:00 PM CTfor Q&A and lab work.
Recordings within 24 hours. Async support from me, not a bot, between calls. A build each week.
Length: 8 weeks plus bonus week 9, voted by the cohort.