Before you apply

It's for you if you already use ChatGPT and want to build real, reusable AI tools without becoming a programmer — curious, willing to experiment, and able to put in the reps.

It's probably not for you if you want a passive watch-and-forget video library, you're aiming to become a professional software developer, or you won't make time to actually build. The value is in doing — if you won't show up and build, you won't get much out of it, and we'd rather tell you that now.

There's nothing to fall behind on — you go at your own pace, there's no rigid schedule. Everything starts from zero, the community is open all week, live group calls let you ask in the moment, and coaching is there if you want dedicated one-on-one time.

The people who struggle aren't the non-technical ones — they're the ones who never actually build anything.

As much or as little as you like — it's self-paced. A few hours a week is a comfortable rhythm: work through a resource, build a small thing, share it in the community, and drop into the live calls that are useful to you. Do nothing between sessions and, like anything, you'll get little out of it.

No. Come with an idea you've been sitting on and you'll learn how to build it; come with none and you'll leave with several. We help you find a project as much as build one.

Five themes take you from "AI user" to "AI builder" — you go through them at your own pace:

• Get your bearings. What an LLM really is and the three ways to use one (chat, API, agents); compare Claude, ChatGPT and Gemini; use OpenRouter to see many models — and their cost per answer — in one place.
• Make AI reliable. Turn vague asks into prompts that work on purpose, and save the ones that do. You leave with reusable templates.
• Build your first real tool. The leap from chatting to building: a reusable assistant, an interactive Claude Artifact, or a no-code automation that does one job on its own.
• See where it all lives. A plain-English tour of hosting, compute and databases — how what you've built is run, and how to set spend limits so nothing surprises you.
• Work safely. The safety basics nobody teaches — keys, secrets, and what's safe to paste into AI.

Depth and pace flex to the group. See the full breakdown →

It's a capability shift, not just a single deliverable.

Before: you use AI occasionally, copy prompts you find, experiment ad hoc, and aren't sure which tool fits which job or what it costs.

After: you design repeatable workflows, build reusable tools, understand the model landscape and how to pick and price one, know how apps are hosted and how to put something live, and work safely with keys and spend limits — and, most importantly, you can take a new problem and confidently figure out how to solve it with AI. You also come away with real tools you keep using.

That you need to code — you don't; it's all no-code. But there are a few others worth clearing up:

• "AI is just ChatGPT." It's one chat interface over one company's models. There's a whole market — and three ways to use any of it.
• "I need a technical background." You need curiosity. It starts from zero.
• "I must know exactly what I'm building first." You can arrive with no idea and leave with several.
• "Building an AI tool takes months." With today's tools, a useful one can be built in an afternoon once you know how.

Your own reusable AI tools, a set of reliable prompt templates, a working understanding of the model landscape and pricing, a mental model of hosting/compute/databases, and safe-working habits you'll keep using.

Being straight: this is an early, small community, so these are examples of what's buildable in the format, not a long alumni highlight reel:

• A Claude Artifact you'd actually use — a checklist generator, meal planner, simple tracker, or decision helper.
• A no-code automation in n8n / Zapier / Make — e.g. "new form response → summarize with AI → post to Slack / email me."
• A reusable assistant (Custom GPT / Claude Project) tuned for a task you do every week.

Realistically: a genuinely useful single-job tool you use for real — not a polished commercial product. The point is crossing from "AI user" to "AI builder," then having the skills to keep going.

Yes — but let's be precise about which kind, because it matters.

What we cover — safe AI usage: setting API keys and spending limits so you never get a surprise bill; storing secrets properly (a password manager; keeping keys out of chats, docs and code); knowing what's safe and unsafe to paste into an AI tool; privacy and backups.

What we don't go deep on — application security: authentication, user-data protection, permissions models, and deployment hardening. Those are software-engineering topics beyond a no-code beginner course. You'll leave with the right instincts and vocabulary — but this isn't a software-security course.

Yes. The community and the coaching options are where you apply everything to your idea, and the projects you build are your own — not fixed assignments.

That's what the community is for — it's open all week, and asking the moment you're stuck (rather than waiting) is exactly how it's meant to be used. If you want dedicated time on your own project, that's what the coaching option is for.

Yes — the community is the hub and it's open all week. Live group calls are recorded, so if you miss one you can catch up and bring anything you missed back to the community.

A small group building alongside each other — not just a support inbox. You see other beginners' questions, builds and mistakes, which is often where the real learning is, and members share their tools for ideas and feedback. It's peers who already use ChatGPT, not a room of experts talking over your head. And being honest: it's early and growing, so think "small and personal" rather than a big alumni network.

It's by application. You fill out a short application — who you are, where you're at with AI, and what you'd like to build. We review every one personally and reply within 24 hours with the next step and the option that fits you. We keep it small on purpose.

There are a few ways to work with us — an ongoing community membership, a guided group, private 1:1 coaching, and team or workshop options. Because the right fit (and price) depends on what you're after, we talk it through after you apply rather than pushing one plan on everyone. Tell us what you want on your application and we'll point you to the option that makes sense — no pressure.

Apply now if you have a few hours a week and an itch to build. Wait if the next month is genuinely underwater — the value is in doing the work, not just having access. Applying costs nothing and doesn't commit you to anything; it just starts the conversation.

YouTube has infinite content and zero accountability, feedback, or a person to unblock you — most people never finish. ChatGPT can answer questions but won't give you a path that builds, catch what you don't know to ask, or show you the whole landscape (it'll mostly point back at itself).

This is beginner-only, no-code, and hands-on — you build real tools with a community and coaching around you. The structure and accountability are the point, not the raw content.

Common and fine. Part of this is pressure-testing ideas cheaply, and you can pivot — the skills transfer to whatever's next. If a project turns out hard, you scope it down to a single achievable job, with help from the community and coaching. Shipping something small and real beats a stalled big idea.

Not building. Watching, reading, and lurking feels like progress but isn't — the learning sticks when you make something. Treat it as watch-only and you'll get the least out of it, which is also who it's honestly not for.