Claude Code for solo founders.
A short, opinionated course for one-person teams who want to ship the software they have been carrying in their head. You leave with a real product running in production, the eval suite that says it works, and a way of working with Claude Code you keep using long after the course is over.
// the outcome
One product. Live. Yours.
By the end you have a working product running in production. Not a tutorial repo. The thing you came in wanting to build, scoped down to a first useful version that real people can use.
- 01Spec the smallest useful version
An agent or a tool that does one job for one kind of user. We cut everything that does not earn its place in the first version.
- 02Pair with Claude Code, on your stack
Setup, prompts, hooks, sub-agents, and the few rituals that make Claude Code feel like a teammate rather than a slot machine.
- 03Write the evals before the agent
The eval suite is the contract. We write it first so you know, every day, whether the build is getting better or worse.
- 04Ship to production
Deploy, observability, the on-call rituals a one-person team actually has time for, and the tripwires that catch the failure modes you cannot watch for in person.
- 05Hand it to a real user
The course is not done until your build is in front of someone who is not you, and you have written down what you saw.
// who it is for
- +Solo founders shipping their first or second product.
- +Operators leaving a job to build something on their own.
- +Consultants who want to turn a service into a product.
- +Engineers who can write code but want a teammate-shaped way to work with Claude Code, not a chat-shaped one.
// who it is not for
- ×Teams of five or more. The rituals here assume one person is making every call.
- ×Anyone hoping to ship a product without writing a single line of code or reading a single error message.
- ×People looking for a survey of every AI tool. This is one tool, used well, on one build.
// shape
Four weeks. Small cohort.
Four weeks, capped at thirty people. Two live sessions a week. Async review on your build between sessions. One private call with me in the third week to unstuck whatever is stuck.
// waitlist
Get the cohort one announcement first.
One email when applications open. Date, price, application link. Waitlist gets first read on the thirty seats.