From Chatbot to Builder · Founding cohort

Four weeks. One shipped tool.
A habit that sticks.

A live, hands-on cohort for PMs, operators, and indie builders who have touched Claude Code and want to actually ship with it. Next cohort starts May 12.

Reserve your seat See the curriculum
Founding cohort · 6 of 30 seats taken

From Chatbot to Builder

Four weeks of live, hands-on sessions. You bring a real idea you want to ship. You leave with it live, a prompt system you actually use, and the habit to keep building without me.

  • One 90-min working session (Tue 6pm ET) + one 60-min office hour (Thu 6pm ET), all recorded
  • Private Discord, weekly ship checkpoint, async "I'm stuck" support
  • Spec-first workflow with CLAUDE.md, plan mode, and the one-change rule
  • Graduation: your first real shipped tool, a prompt library you own, and a next-project brief
Reserve a seat Is this for me? →
Curriculum · 4 weeks · Week 0 pre-flight included

What we build, week by week

  1. Week 00 Pre-flight · before May 12

    Get the stack ready before we start

    Setup is where beginners lose momentum, so we separate it from the real work. One short video, one checklist, one readiness gate. Show up to Week 1 with the tools actually working.

    • Claude Code + desktop app
    • GitHub + Vercel
    • Secrets 101
    • CLAUDE.md starter
  2. Week 01 May 12 – May 18

    Pick, spec, and ship v1

    The project you pick this week is the one you ship. We protect scope on purpose. By Sunday you have a real URL and a spec Claude can read before every session.

    • Four project lanes
    • CLAUDE.md spec
    • Plan mode + one-change rule
    • Deploy v1 to Vercel
  3. Week 02 May 19 – May 25

    Debug without spiraling

    The ugly middle stays in. You learn to read errors without panicking, debug with screenshots instead of descriptions, and use /clear when the session gets weird. Also: the Codex or Cursor fallback for when Claude Pro limits bite.

    • Error triage
    • Screenshot debugging
    • /clear + context reset
    • Codex or Cursor fallback
  4. Week 03 May 26 – Jun 1

    Make it look real

    Move from "it works" to "someone else can use this." Basic product taste, UI copy rewrites, and a silent watch session with one real user. Pick three fixes and ship them.

    • Hierarchy, spacing, contrast
    • UI copy pass
    • Watch one real user
    • Polish ship
  5. Week 04 Jun 2 – Jun 8

    Build the habit

    Finish strong and leave with momentum. Public build story, personal prompt library, a named map of what's next (Skills, subagents, MCP), and a next-project brief you already approve of. Demo day closes the cohort.

    • Build-story writeup
    • Personal prompt library
    • Skills + subagents + MCP (named, not taught)
    • Demo day
Who this is for

The right fit, and the wrong one

Right fit

  • You're a PM, operator, consultant, or indie builder
  • You've opened Claude Code (or Cowork) at least once and want to actually ship with it
  • You have an idea you'd build if you weren't stuck in "I need a developer" mode
  • You can commit 2 to 3 hours of live time per week for four weeks

Not the right fit

  • You're looking for a tour of every AI tool, framework comparison, or model architecture primer
  • You've never opened Claude Code. Start with the free 60-minute portfolio guide first
  • You want a passive, watch-and-learn video library
  • You need enterprise compliance, SSO, or team-wide rollout support. Let's talk consulting instead
Questions

FAQ

Do I need to know how to code?

No, but you need to have opened Claude Code or Cowork at least once. If you haven't, start with the free 60-minute portfolio site guide, then come back.

What's the time commitment?

One 90-minute working session (Tuesday 6pm ET), one 60-minute office hour (Thursday 6pm ET), plus about 2 hours of your own work between sessions. Around 5 hours a week for four weeks.

What if I can't make a live session?

Every session is recorded and posted within 24 hours. The Discord stays active for async questions, and the "I'm stuck" template gets you a real answer inside of a day.

Will I hit Claude Pro usage limits?

Probably, late in the cohort. Week 2 covers the Codex or Cursor fallback so you're never blocked. Claude Pro is the minimum. If you're building heavily, the Max plan is worth it, not required.

What stack will I use?

Claude Code as the spine. GitHub for version control. Vercel for deployment. Codex or Cursor introduced in Week 2 as a fallback. All free or near-free tiers work for the month.

Is there a refund policy?

Full refund through the end of week one, no questions asked. After that, a 50% refund through week two. The founding cohort is limited, so I want you fully in or fully out.

Can my company pay?

Yes. Invoice with a W-9 and a line-item receipt. Most students expense this as professional development.

Will there be another cohort if I miss this one?

Yes, monthly. Future cohorts run $697+. The founding-cohort price and direct access are first-cohort only.

Founding cohort

24 seats left. Future cohorts run $697+.

Founding-cohort pricing and direct access to Vince are locked for this cohort only.

Reserve your seat