ProgramsVibe Producting
The product path · build products with AI

Vibe Producting

Build products with AI — for product managers and product-minded builders. Take an idea to a live, secure, instrumented AI product without being a deep engineer. This is not a framework course; it is a shipping course.

4 levels
L0 → L3
3 → 120 hrs
Per level
Cursor · Claude Code · v0
Mastery stack
A shipped product
Capstone output
§ 01Choose your level

Four rungs. Start where you are, finish at Mastery.

Sessions are always 2 hours. The hours are fixed; the calendar flexes — the same level runs daily, alternate-day, evenings, or as an intensive. Prices shown are student prices; professional pricing is on the pricing page.

L0Discover
3 hours · one sitting, a single day

Idea to a working thing, in one afternoon

Describe a product out loud and watch it become a working prototype in front of you — then see exactly where the AI helps and where a human still has to think.

L1Foundation
12 hours · 6 sessions · about 1 week

The AI-assisted building workflow

Spec-first prompting, steering an AI builder, and reading what it wrote well enough to trust it or reject it. You leave with a prototype that runs.

L2Practitioner
40 hours · 20 sessions · about 1 month

Your first shipped AI product

From prototype to a real MVP with data, auth and an LLM in the loop — deployed to a public URL that other people can actually use.

L3Mastery
120 hours · 60 sessions · about 3 months

A live, secure, instrumented AI product

Product thinking, AI-assisted building, deployment, security, and an AI harness of evals, guardrails and observability. Full syllabus below.

Three AI streams — which is yours? This one is for people who want to ship products with AI; product sense matters more than deep coding. Deep Learning with LLM is for building and training the models themselves. Gen AI Mastery is pure no-code applied use, with no product-building.
§ 02L0–L2 · published syllabus

What the levels below Mastery cover

Our ladder is a spiral, not a straight line. L0 and L1 are outcome-first: you make something impressive on the first day and no theory gets in the way. L2 is where the foundations genuinely begin. L3 then deliberately re-covers 60–70% of L2 at real depth before going past it — the overlap is a feature, not repetition. You earn the "why" only once you are invested in the "what".

L0 · 3 HRS
Curiosity

A demo and a guided first build. No theory at all — just a win you can point at.

L1 · 12 HRS
Confidence

Bigger builds, same spirit. Concepts appear only where a build actually needs them.

L2 · 40 HRS
Foundations begin

The first real grounding in how and why — taught applied, ending in a project.

L3 · 120 HRS
Depth

Re-covers L2's foundations at full depth, then goes well beyond into advanced work.

L0 · Discover · 3 hours · free

"I shipped an app by describing it — today."

See it: Real products built with AI in minutes rather than months.

Make it, guided: Describe an app in plain English to an AI builder (Lovable, Bolt or v0), watch it appear, tweak it, and deploy it to a public URL.

An AI app builder in the browser — nothing to install. No assessment.

L1 · Foundation · 12 hours · 6 sessions

Six sessions, six things you built

  1. Build an app by describing it (Lovable, Bolt) — a simple useful tool
  2. Add features and iterate with AI — make it do more
  3. Make it real — add data and a form
  4. Add AI to your product — an LLM-powered feature
  5. Ship it — deploy, get a public URL, share it
  6. Your own mini product, from an idea you choose, plus a showcase

You leave with a live little product that you built with AI. Assessed on completion and the showcase.

L2 · Practitioner — 40 hours, where the foundations begin

The first real grounding — product thinking, AI foundations, the vibe-coding workflow, and building and shipping an MVP with the basics of security.

UnitWhat you learn and buildSessionsHours
U1 · Product Thinking BasicsProblem and users, a simple PRD, scoping an MVP, product metrics36
U2 · AI Foundations for BuildersHow LLMs work at an applied level, prompting, model choice, cost versus quality36
U3 · Vibe Coding — Building with AIAI builders and coding tools (Cursor, Claude Code, v0, Bolt, Lovable); building an app; steering and reviewing AI output510
U4 · Making it a Real ProductData, auth, an LLM-powered feature, UX for AI48
U5 · Ship & Security BasicsDeploy to a public URL, secrets and API keys, a security and safety checklist, an intro to evals36
U6 · Product ProjectShip a small AI product, presented as a product demo24
Total2040

Project: A shipped, live AI product — idea to MVP to deployed — presented as a product with a metric.

Tools: AI builders (Cursor, Claude Code, v0, Bolt, Lovable) · LLM APIs · a cloud host (Vercel/Netlify) · a managed backend (Supabase/Firebase) · analytics.

Assessment: Continuous labs 25% · product artifacts — PRD, MVP, deploy — 35% · project 40%.

Overlap into L3: U1–U5 are the foundations L3 deepens — it adds AI product security in depth, the full AI harness of evals, guardrails and observability, growth and monetization, agents in products, and a shipped capstone.

§ 03L3 · Mastery · published syllabus

120 hours, unit by unit

This is the complete Mastery syllabus — the ceiling of the stream, and what every level below builds toward.

What you can do at the end

The outcome

You can take a product from idea to a live, secure, instrumented AI application — writing PRDs, building with AI-assisted tooling, deploying it, securing it, and wrapping it in an "AI harness" of evals, guardrails and observability so it holds up in the real world.

Format

How it runs

120 hours · 60 sessions × 2 hours · about 3 months. Prerequisite: Vibe Producting L2, or a placement check. Product sense helps; deep coding is not required. This is the fastest-moving stream we run, so it is rewritten every cohort.

Tools & environment

CursorClaude Codev0 · Bolt · LovableReplitOpenAI · Claude · Gemini APIsVercel / Netlify / RenderSupabase / FirebasePostHogEvals & loggingSecurity toolingMCPPRDs & roadmaps
Deliberately out of scope: LangChain, LangGraph and CrewAI, and framework-heavy multi-agent engineering. Agents are covered as a product decision — when you actually need one and what it costs — not framework by framework. If you want that depth, it lives in the engineering streams.
UnitWhat you learn and buildSessionsHours
U1 · Product Thinking for AIProduct discovery and problem framing · what makes a good AI product rather than a feature · PRDs and specs for AI · user research · product metrics and a north star · scoping an AI MVP48
U2 · AI Foundations for BuildersHow LLMs and generative AI work at an applied level · the model landscape and how to choose · capabilities, limits, hallucinations · prompt engineering and structured output · cost, latency and quality trade-offs — enough to make real product calls48
U3 · Vibe Coding — Building with AIAI-assisted development with Cursor, Claude Code, v0, Bolt, Lovable and Replit · the spec-driven "vibe coding" workflow · turning an idea into a working app fast · reading, reviewing and steering AI-generated code · when to trust it and when not to714
U4 · Building the ProductFrom prototype to MVP · integrating LLM APIs into a product · data, auth and storage on managed backends · UX for AI — streaming, feedback, empty and error states · the AI product stack714
U5 · Deploying & ShippingDeployment on Vercel, Netlify or cloud · domains, environments and secrets · web versus app-store shipping · CI/CD basics · analytics and product instrumentation · release and iteration loops612
U6 · AI Product SecurityPrompt injection and jailbreaks · data privacy (DPDP, GDPR) and PII handling · API-key and secret management · auth, rate limiting and abuse prevention · a safe-deployment checklist · compliance basics for AI products612
U7 · The AI HarnessEvals — LLM-as-judge, test sets, regression suites · guardrails and safety filters · observability and monitoring — traces, logging, cost · prompt and version management · quality, reliability and drift · human-in-the-loop and feedback loops714
U8 · Agents in ProductsWhat agents and multi-agent systems are, and when a product actually needs one · tool use and function calling at the product level · MCP for connecting tools and data · cost, latency and reliability trade-offs — conceptual plus light hands-on, no framework deep-dive48
U9 · Growth, Analytics & MonetizationProduct analytics and instrumentation · activation and retention · A/B testing AI features · pricing and payments integration510
U10 · Advanced AI Product PatternsVoice and multimodal AI products · scaling and cost at volume · reliability patterns · advanced UX for AI510
U11 · Capstone — Ship a ProductConceive → build → secure → deploy → instrument → ship a real AI product, with a product story and metrics510
Total60120

The capstone

Ship a real, live AI product. Conceive it with a PRD and a metric, build it with AI-assisted tooling, secure it, deploy it to a public URL, and wrap it in a basic AI harness — evals, logging and at least one guardrail.

You deliver: the live product, a short product document covering the problem, your decisions, the metrics and what you would do next, and a demo. It is judged like a product, not a coding exercise.

How you're assessed

Continuous lab work25%
Product artifacts (PRD, MVP, deploy, security, evals)30%
Capstone (rubric)35%
Product demo & viva10%

Syllabus is a working draft — hours per unit are indicative and validated by the practitioner who teaches the stream. AI builder tools rotate quickly; the stream is refreshed every cohort.

§ 06Practitioner-instructors

Who will teach you

Every instructor is currently building in the field they teach — and is certified on our level template before taking a cohort alone. Subject expertise is the entry ticket, not the job.

Practitioners, not lecturers

Every instructor is currently building in the field they teach. If they stop practising, they stop teaching that stream.

Trained on our template

Subject knowledge is the entry ticket, not the job. Every instructor is certified on the CEFTA level template before they take a cohort alone.

Standardized delivery

The same module runs the same way in every centre and every partner campus. That consistency is the product.

Named instructor profiles go up as each cohort's trainer is confirmed — we publish people, not stock photographs. We're hiring practitioner-instructors →

Dates for Vibe Producting

Tell me when the next batch opens

One email when a cohort is published for this stream. Nothing else, ever.

One email when a batch opens. No newsletter, no drip sequence, unsubscribe in one click.

Stop writing specs for other people to build.

Start with the free 3-hour L0 Discover session — take one of your own ideas from a sentence to something that runs.