fair questions. honest answers.

Honestly? Good. Around 60% of our builders couldn't code when they started either. The tools handle the syntax now — or as Karpathy put it, “the hottest new programming language is English”. The real skill is knowing what to build and being able to tell good work from bad. If you can write a clear paragraph, you can write a spec. And the spec is the job.

You don't need one to start. We keep a Problem Bank full of real, validated, employer-neutral problems — pick one and go. And Week 1 is built for exactly this: it takes you from "no idea" to a spec worth building.

It's about 12 hours a week. 10 live sessions across the six weeks, on weekends, and everything's recorded if you miss one. Here's the thing, though — you won't find the hours lying around. You'll trade them in from the tutorials you're already watching.

No prerequisites. A laptop, an internet connection, and English. Everything else — three free accounts and three candidate problems — is light pre-work sent ten days ahead, and it takes about ten minutes. Your included Claude seat switches on in Week 2, when building starts. The installs that break are Session 1's job, not yours.

No. Builder Compute is included in your seat: Claude Code and the Claude app run on our plan for all build weeks, Week 2 onward, with an allowance sized for the build. Week 1 is problem judgment and research — brains before agents, by design. The prototype tools run on free tiers, and Cursor is optional and bring-your-own.

One shared time, worldwide. Live sessions run once — the same time for everyone, wherever you are — on weekends, so they're easier to protect around a full-time job. And every session is recorded, so a missed one is never a missed week.

You get a product, which beats a certificate. We do issue a completion credential you can put on LinkedIn, and the L&D kit includes proper invoicing and completion documentation for your employer.

Usually not, and here's the honest guidance nobody else in this category gives you. Build off-hours, on your own equipment. Pick a problem unrelated to your employer's business — the Problem Bank is curated to be employer-neutral for exactly this reason. Charging users is an optional path in the curriculum, not a requirement. And read your employment contract's IP clause before Week 1, because we'd rather you know now than at Demo Day.

You keep lifetime access to your cohort space, and Week 6’s “own your stack” session moves you onto your own subscriptions so nothing you built depends on us. One month of Builders’ Club* is reserved for you for whenever that membership opens.