TPA · 01 · /FAQ · FREQUENTLY ASKED

Frequently asked.

Fourteen questions worth answering directly. If yours isn’t here, email me. That’s the address that reaches me, not a contact form.

  1. Q · 01

    I've never written code. Am I in?

    If you’ve used Claude or ChatGPT daily for a few months, yes. The cohort isn’t about syntax. It’s about designing systems, then having the model write the code. We pair-build through week 1.

  2. Q · 02

    I'm worried my situation is too unique.

    That’s what the 1:1 intake is for. 60–90 minutes before week 1, and we won’t be rushed. We look at your actual setup, your actual stack, your actual list of someday-builds, and we pick a first-build path that fits you. Nobody walks in cold.

  3. Q · 03

    Time commitment?

    Two two-hour live calls per week + 3–6 hours of building. If you can’t protect 6–9 hours a week for nine weeks, this is the wrong cohort. Wait for cohort 02 or follow my writing.

  4. Q · 04

    What if I fall behind?

    Recordings posted within 24 hours. Async support in the community space. The cohort is small enough that you won’t get lost in it.

  5. Q · 05

    What stack do you teach?

    Foundation Models (Claude / ChatGPT) with autonomous coding agents. We let the AI drive the stack in collaboration with our real-world needs, both effort and cost. Built around tools you can audit and data you own. Model-agnostic by design.

  6. Q · 06

    Will you teach me to build a SaaS?

    No. These are personal systems for your life. If you find a wedge that becomes a SaaS later, that’s yours.

  7. Q · 07

    Why no application?

    I scrapped it. The application was a 48-hour speed bump in front of paying. The 1:1 architecture intake before week 1 is the real conversation, and the refund guarantee covers fit. If you want to talk before deciding, email me →. Otherwise hold your seat.

  8. Q · 08

    Hardware requirements?

    A laptop with admin rights to install software, ideally less than five years old. macOS, Windows, or Linux all work. No special GPU needed. 16GB RAM is comfortable, 8GB will work for most of what we do.

  9. Q · 09

    International / time zones?

    Welcome. Recordings posted within 24 hours. Async support is the same regardless of where you’re based. Live calls land at 6:00–8:00 PM CT Monday and 12:00–2:00 PM CT Saturday. Workable for most of the US, EU evening, harder for Asia / Pacific.

  10. Q · 10

    What about API and tool costs during the cohort?

    Plan for $50–100 over the nine weeks. We’ll use Claude or ChatGPT subscriptions you may already have, plus modest API credits for the things you build. Supabase has a free tier that covers most personal use. No hidden costs.

  11. Q · 11

    How private is my MCP and personal data?

    Everything runs on infrastructure you control, your Supabase project, your machine. Your journal, notes, and personal data aren’t shared with the cohort or with me. We work on the architecture together. Your data stays yours.

  12. Q · 12

    Do I need to know how to use a terminal?

    You’ll learn enough in week 1. We pair-build through the early friction. By week 2 the basics feel natural.

  13. Q · 13

    What happens after the cohort ends?

    Lifetime access to the cohort community space, recordings, and curriculum updates. The system you build in week 8 isn’t the last system you’ll build, and the room you build it in stays with you.

  14. Q · 14

    What if my use case isn't on the recipe shelf?

    It probably is, even if it doesn’t look like it at first. The 1:1 intake is partly for this. We map your situation onto the shelf, and if it doesn’t fit any recipe directly, your week 7 build covers it. Something neither of us has built before is the actual brief for System 03.

Still have a question? Email me →

Hold your seat →← Back to main