Work With Me / Vibe Coding & Automation Intensive
Rolling enrollment · next 1:1 slot open Fig. 05 — Vibe Coding Intensive

You’ll leave with a working thing you’ll actually use.
Not a plan. not a syllabus. A thing.

Three 90-minute 1:1 sessions over 3–4 weeks. Claude Code, multi-step automations, context engineering — we build the real thing together and you keep the repo.

Book the Intensive — $1,300 See the 3-week arc or 3 × $435 · payment plan
Past Shipments

What past clients actually walked away with.

Proposal generator Client onboarding automation Content pipeline Internal dashboard Data scraper + Notion sync Custom GPT for sales calls Weekly digest bot
!
This one assumes you’re comfortable prompting. If you’re still figuring out how to get good output from Claude, start with the AI Fluency Intensive. This one moves fast — we’re in Claude Code, GitHub, and deploy pipelines from session one.
Try Fluency first
Fig. 05b — Three sessions, one shipped tool

The 3-week arc. Setup → ship → polish.

Each session is 90 minutes, 1:1, live screen share. You drive; I navigate Claude Code with you.

1
Week 1 · Setup & first build

Claude Code installed, configured, running end-to-end.

We pick the tool you’re building, get the repo cloned, claude.md drafted, and the first working slice deployed by the end of session one.

CLI installclaude.mdGitHub authFirst deploy
2
Week 2 · Automations & context

Multi-step automations & context engineering.

Prompts that don’t break. Context files Claude can actually use. The pattern for chaining steps without hand-holding every run.

Sub-agentsSlash commandsHooksMCP
3
Week 3–4 · Ship something useful

The polish pass — edge cases, real inputs, deployment.

You close the laptop with a working tool you’ll use next week. Not a prototype, not a demo. The thing.

Edge casesProd deployHand-off doc
Fig. 05c — What you walk away with

Everything included. No upsells.

One price, three sessions, one shipped tool. Recordings and the starter repo are yours forever.

Three 90-minute 1:1 sessions over 3–4 weeks
Session recordings you keep
Claude Code starter repo
Between-session async email support
One shipped tool (yours to keep and extend)
10-minute fit check at the top — if it’s not a match, no charge
Fig. 05½ — Build Session vs. Intensive

Already booked a Build Session? Here’s what’s different.

One sitting

Build Session

$450 · 90 min

One thing built in one sitting. That’s the whole promise. You come in stuck, you leave unstuck, you have a thing.

A practice — recommended

Vibe Coding Intensive

$1,300 · 3 × 90 min

Three 90-minute sessions across 3–4 weeks, recordings you keep, a starter Claude Code repo, and email access between sessions. The shape of it is “we build together until it becomes the way you work.”

If you need the thing: Build Session. If you need the habit: Intensive.

Field Note — Client 04

“I shipped the thing. Not a prototype. Not a demo. The actual tool my team uses now. Three sessions.”

Vibe Coding Intensive · Operations lead, design studio
Fig. 05e — FAQ

Questions, honestly answered.

Anything not covered? Drop me a note — I read everything.

— h.
Do I need to know how to code?
No, but you need to be okay reading code Claude writes, and comfortable following along in a terminal. If that feels like too much, start with AI Fluency first.
What will I actually build?
Whatever you need. Past tools: proposal generators, client onboarding automations, content pipelines, internal dashboards, data scrapers. We pick in session one — you’ll get a short brief from me 48 hours before to narrow it down.
What’s the payment plan?
$1,300 up front, or 3 × $435 spread across the three sessions. Same access, same deliverables either way.
Do I own the code?
Yes. The starter repo is yours to keep, extend, and use however you want. No licensing, no catches. I keep no rights to anything we build together.
What if it’s not the right fit?
First 10 minutes of session one is a fit check. If I’m not the right person to help you, you don’t pay. No pitch, no pressure.
Not ready to book?

Get the weekly field notes.

One short email each Friday — what I’m building, what’s breaking, what’s actually working with Claude.