One day. You leave with your site in GitHub, Claude Code running, and an agent doing real work.
A full working day with me, on your machine, on your business. $5,000, and it credits toward everything else.
You've read about all of this. You haven't done any of it.
- You use Claude in a browser tab and suspect you're using 5% of it.
- Your website's source code isn't anywhere you can find.
- You've heard "just put it in GitHub" and nodded.
- You've watched somebody demo Claude Code and thought that looks like it's for engineers.
- You have three tasks a week that are obviously automatable and still doing them by hand.
- You don't want a course. You want the thing set up and working by tonight.
Five things, one day, in order.
1. Claude Code, installed and authenticated
On your machine, not a demo of mine. Running, logged in, connected to your work. If a terminal isn't your thing, we set up the desktop app instead. Both work.
2. Your site in version control
Your website's code pulled into a GitHub repository you own. Every change from here forward is tracked, reversible, and reviewable. This is the single highest-leverage hour of the day, and it's the one nobody does on their own.
3. Claude connected to the repo
Claude reads your actual codebase. Not a description of it, not a paste of one file. It sees the whole thing and can change it.
4. Your first change, live
You describe a change in plain English. Claude writes it. You review it. It ships. You do this yourself, with me watching, before the day ends. The point is that you've done it once, so you believe you can do it again.
5. One agent, built and running
We pick this on the prep call from a short menu, so the afternoon is building instead of deciding. Options include a content agent that drafts in your voice from your own material, a research agent for prospects or competitors, a reporting agent that pulls your numbers on a schedule, an inbox triage agent, or a site agent that keeps a section of your website current.
Nine to four, with a break.
One day, hour by hour. The prep call is the week before; every other block is you at your own keyboard.
We confirm access, pick your agent, and I log into a thing or two myself, so we find the problems now instead of at 9:15.
Install and authenticate. Accounts, permissions, the boring foundational hour.
Your site into GitHub, connected to Claude.
Break.
Your first change. Written by Claude, reviewed by you, shipped by you.
Build the agent, on a task you actually have.
Written notes, your repo, your accounts, and what to do next week.
Two weeks of email support. Then either you are running on your own, or you move onto the Autopilot, or you book another day.
Four of the five working blocks are marked your hands because that is the product. If I drive, you have watched a demo.
There's a checklist, and it's not optional.
A full day dies in the first two hours if we're chasing a registrar password nobody has. Everything that can be done before the day must be done before the day.
You'll get the requirements checklist when you book. It has three tiers. The blocking items have to be confirmed 48 hours before, or we reschedule. That rule protects your money more than mine.
Read the full requirements checklist →
If you can't get registrar access in time, we still run the day. We build everything in GitHub and stage it, and cut over later once you've recovered the login.
What you leave with
- Claude Code installed, authenticated, and working on your machine
- A GitHub repository you own, containing your site
- One change you wrote, shipped by you, live
- One agent, running, doing a real task
- Written handover notes, in plain language
- Two weeks of email follow-up for when something breaks
$5,000.
Includes the prep call, the full day, the handover, and two weeks of follow-up.
Also includes your first month of the Autopilot at the entry tier, and waives its $1,500 onboarding. By the end of the day your site is already in the repo, which is most of that onboarding done. If you don't want the retainer, don't take it. Nothing rolls over without you saying yes.
Credits in full toward the Map, like everything else here.
In person, at your place, travel included. The price covers me getting there — no separate expense line, wherever you are. It is your machine, your network and your team in the room, which is the point: a setup that works on my laptop is not the deliverable.
This teaches you to do it yourself. That's the actual product.
Most of what I sell puts me in the loop. This one takes me out of it.
Some people finish the day, love it, and run with it. Some finish the day, realize they don't want to live in a terminal, and take the Autopilot so somebody else does. Both are fine outcomes. I'd rather you know which one you are after a day than after a year.
What this is not: a course, a webinar, a strategy session, or a day of me building while you watch. Your hands are on the keyboard most of the day. That's the part that makes it stick.
Questions
- Do I need to know how to code? No. You need to be able to follow instructions and not panic at a terminal window. If a terminal is genuinely off the table, we use the desktop app and the day works the same.
- What if my site is on Squarespace or Wix? Then the GitHub step looks different. We export what's exportable and set up the repo around it, or we stage a static version. We work this out on the prep call, not on the day.
- Can I bring my team? Two people maximum, and one of them drives the keyboard the entire day. Three or more turns it into a demo, and demos don't stick.
- Is one day really enough? For these five things, yes, if the prep is done. That's the whole reason the checklist has teeth.
- What if we finish early? We build a second agent.
- What happens after? Two weeks of email support. Then either you're running on your own, or you're on the Autopilot, or you book another day.
Read the requirements first. Then book.
The Install. $5,000, one day.
Most people who book without reading it end up rescheduling. The requirements checklist →