01
Weeks 1–4 · Days 1–20
Product Prototype
Find a real user problem, model the product, create a visual prototype, test it, and tell a clear founder story.
A tested product prototype and evidence-based full-stack build decision.8 weeks · 40 guided weekdays · online-first
Build your AI product one clear day at a time.
Every lesson combines a short briefing, a written guide, practical work, a concrete deliverable, and answers to the questions students most often ask.
Your daily rhythm
- LearnWatch the briefing or use the complete written guide.
- BuildComplete a focused task in your own product.
- CheckSave one visible deliverable before moving on.
- UnblockUse the Q&A and prepare a precise mentor question.
The complete journey
Two programmes. One working product.
Start with the problem and prototype before moving into protected records, roles, workflows, AI controls, testing, and deployment.
02
Weeks 5–8 · Days 21–40
Full-Stack Build
Use the protected course platform to connect real records, roles, workflows, safe automation, validation, and deployment.
A deployed, explainable product with a remote-ready demo and responsible next-step plan.Designed for live or remote learning. Most days take 60–90 minutes. If you miss a session, the written lesson, tasks, Q&A, and checkpoint remain available here.
Your course progress
40 guided learning days
Join the course to unlock lessons and save progress across devices.
0% complete
Week1
Programme 1 · Product Prototype
Find a problem worth solving
Start with people, not technology. Weekly outcome: A focused problem statement grounded in a specific user and real situation.
Day 1
Welcome and choose your course goal
Understand the eight-week journey, how daily lessons work, and what you will have built by the end.
Output: Your personal course goal and weekly study rhythm.Open lessonDay 2
Observe users and everyday friction
Learn to notice repeated, costly, or frustrating moments in a person’s day.
Output: A list of at least five observed problems or workarounds.Open lessonDay 3
Compare and choose one problem
Score your candidate problems by frequency, impact, access to users, and course feasibility.
Output: One selected problem with a short reason for choosing it.Open lessonDay 4
Define the target user and situation
Turn a broad audience into one precise primary user in one clear situation.
Output: A target-user statement and a one-paragraph problem description.Open lessonDay 5
Problem checkpoint
Test whether another person can understand the user, problem, evidence, and safety boundary without extra explanation.
Output: A reviewed problem brief with evidence and a clear out-of-scope list.Open lessonWeek2
Programme 1 · Product Prototype
Model the product
Make the behaviour clear before drawing screens. Weekly outcome: A user journey, data model, roles, and workflow that describe how the product works.
Day 6
Map the end-to-end user journey
Describe the steps from the user’s trigger to a useful result, including what can go wrong.
Output: A numbered primary user journey.Open lessonDay 7
Name the core entities and fields
Identify the records your product needs and the minimum information each record contains.
Output: An entity list with required and optional fields.Open lessonDay 8
Connect relationships and roles
Define how records belong together and which roles can view or change them.
Output: A relationship map and role/access table.Open lessonDay 9
Design the workflow and states
Turn meaningful business progress into named states and controlled transitions.
Output: One complete state machine with allowed roles.Open lessonDay 10
Model checkpoint
Walk through the journey using your entities, relationships, roles, and workflow to expose missing decisions.
Output: A reviewed model diagram and list of open questions.Open lessonWeek3
Programme 1 · Product Prototype
Prototype the experience
Turn the approved model into a believable interface. Weekly outcome: A connected visual prototype covering the main journey and its important states.
Day 11
Prepare the Lovable product brief
Translate your problem, journey, model, and visual direction into a focused prototype brief.
Output: A reviewed prototype brief ready for Lovable.Open lessonDay 12
Build navigation and information hierarchy
Create a simple product structure that makes the user’s next action obvious.
Output: A connected navigation shell and page map.Open lessonDay 13
Prototype the primary flow
Build the central create, decide, or complete flow using realistic demo-safe content.
Output: A clickable happy-path prototype.Open lessonDay 14
Add loading, empty, error, and success states
Make the prototype explain what is happening when the ideal path is not immediately available.
Output: A prototype with four non-happy-path states.Open lessonDay 15
Prototype review
Test whether a new person can complete the main journey without coaching.
Output: A prioritised prototype revision list.Open lessonWeek4
Programme 1 · Product Prototype
Validate and tell the story
Prove that the idea is understandable, safe, and worth building. Weekly outcome: A tested prototype, safety boundary, and concise product story for the Programme 1 showcase.
Day 16
Run a structured usability test
Use a short scenario, observation notes, and consistent questions to evaluate the prototype.
Output: Usability notes with evidence, severity, and proposed change.Open lessonDay 17
Review accessibility and clarity
Check keyboard use, contrast, labels, text size, focus order, and plain language.
Output: An accessibility review and completed fixes.Open lessonDay 18
Define the safety and data boundary
State what data, users, decisions, and external actions are allowed in the course demo.
Output: A visible safety boundary and out-of-scope statement.Open lessonDay 19
Build the founder story and pitch
Connect the user evidence, product decision, prototype, and next test in one short explanation.
Output: A three-minute prototype pitch and demo script.Open lessonDay 20
Programme 1 showcase
Present the product prototype, receive structured feedback, and decide what should enter the full-stack build.
Output: A reviewed Programme 1 showcase and full-stack build decision.Open lessonWeek5
Programme 2 · Full-Stack Build
Understand and prepare the platform
Learn the safe foundation before adding product code. Weekly outcome: A configured local and hosted project with clear authentication, access, and data responsibilities.
Day 21
Tour the course platform
Understand which capabilities the framework already provides and where student product code belongs.
Output: A capability map for your product.Open lessonDay 22
Complete guided setup and accounts
Prepare the workstation, provider accounts, repository, Supabase project, and deployment through the guided setup.
Output: A passing setup check with accounts owned by the correct person.Open lessonDay 23
Understand sign-in, roles, and access
Trace how GitHub sign-in, recovery, application roles, and Row-Level Security protect records.
Output: A tested role/access matrix.Open lessonDay 24
Configure the project model and Supabase
Move your reviewed entities, fields, relationships, roles, workflow, and compliance decisions into the project model.
Output: A valid project model and linked Supabase environment.Open lessonDay 25
Platform readiness checkpoint
Confirm the project builds, signs in, enforces access, reaches the database, and has a healthy deployment.
Output: A recorded green readiness checklist or a precise blocker report.Open lessonWeek6
Programme 2 · Full-Stack Build
Implement the product journey
Connect the approved design to protected platform behaviour. Weekly outcome: A working primary journey with records, workflow transitions, automation rules, and verified access.
Day 26
Synchronise and migrate the approved design
Bring the reviewed Lovable snapshot into the framework without replacing protected platform code.
Output: A documented first design migration with deferred items made explicit.Open lessonDay 27
Connect forms and protected records
Replace prototype data with validated record creation and role-scoped reading.
Output: One end-to-end protected record flow.Open lessonDay 28
Connect workflow transitions
Make state-changing actions use the configured workflow and allowed roles.
Output: A working state machine in the product interface.Open lessonDay 29
Add deterministic automation rules
Connect safe, explainable triggers to record or workflow events without pretending external side effects run.
Output: One tested trigger with an audit or notification outcome.Open lessonDay 30
Primary journey integration test
Run the complete journey across the interface, API, database, workflow, access policy, and teacher view.
Output: A passed primary-journey test or prioritised defect list.Open lessonWeek7
Programme 2 · Full-Stack Build
Make the build trustworthy
Use AI deliberately, design recovery, and prove the system works. Weekly outcome: A bounded, tested, accessible deployment with clear AI, error, cost, and safety behaviour.
Day 31
Decide whether the product needs AI
Compare a deterministic implementation with an AI-assisted one before enabling a prompt.
Output: An AI use/no-use decision with reasons.Open lessonDay 32
Bound prompts, data, and budget
When approved, configure a server-side prompt with input limits, budget, logging, and an off switch.
Output: A reviewed AI prompt and budget record, or a confirmed non-AI design.Open lessonDay 33
Design errors, empty states, and recovery
Make every important action explain failure, preserve user effort, and offer a safe next step.
Output: A recovery matrix for the primary journey.Open lessonDay 34
Test the model, APIs, and interface
Add proportional automated tests and complete manual checks for accessibility, mobile use, and role boundaries.
Output: A passing test record with known limitations.Open lessonDay 35
Deploy and verify the online product
Publish the validated build, verify runtime configuration, and test the real hosted journey.
Output: A healthy deployment URL and online smoke-test record.Open lessonWeek8
Programme 2 · Full-Stack Build
Explain, review, and showcase
Make the product understandable without the developer in the room. Weekly outcome: A complete remote-ready handoff with demo data, technical explanation, fallback video, and reviewed next steps.
Day 36
Prepare reliable demo data
Create a small synthetic scenario that demonstrates the main value, workflow, and safety boundary every time.
Output: A repeatable demo dataset and reset path.Open lessonDay 37
Write the technical explanation
Explain the users, model, roles, workflow, automation, AI, safety, and deployment in plain language.
Output: A reader-friendly technical explanation document.Open lessonDay 38
Record the remote demo video
Create a concise fallback recording so the project can be reviewed asynchronously.
Output: A tested demo video link with captions or transcript.Open lessonDay 39
Complete mentor and viability review
Review readiness, risk, evidence, and the next experiment with a mentor before the final showcase.
Output: An updated report card, viability verdict, and prioritised next-step list.Open lessonDay 40
Final showcase and next steps
Present the user problem, working journey, system explanation, evidence, and responsible next step.
Output: A completed showcase, handoff package, and 30-day next-step plan.Open lesson