How This Course Works
Overview · From Idea to First Paying Customer
What this is: the map - 5 modules, 25 lessons, 6 artifacts, each module’s output feeding the next module’s input, from rough idea to signed paid pilot. Read it once before Module 1, come back when you need to see where you are.
This course takes a non-technical founder from a rough idea to a signed paid pilot - on evenings and weekends, with or without engineers. Each chapter names the tool it uses and what the tool costs at that step; most tools have a free tier. Below: the flow, the tools, the artifacts you’ll compile, and how the stages connect.
Calendar reality - full-time vs evening-only. The per-module wall times below assume a founder with daytime availability. An evening-only founder (2-4 hr/week, the pattern this course is built for) typically needs 1.5-3x the calendar at each module. Build your plan against the evening-only band; finishing early is a bonus.
Your first 20 minutes. Lesson 1.1’s first sitting takes 15-20 minutes: a blank note and your idea. Skim this map for orientation, then start there. Every tool below appears in the lesson that uses it, and most have free tiers.
Take this course if #
- You are a first-time founder with an idea
- You want the fastest route from that idea to your first paying customer
- You can read a Stripe invoice but not a GitHub commit
- You have never systematically validated a business before
- You might have tinkered with no-code tools, but you want a structured path instead of guessing
Skip this course if you want to learn to code or hand off founder judgment to someone else. And if what you need most is cohort deadlines and peers, YC Startup School runs free - this course is the self-paced, artifact-first alternative.
The Big Picture #
5 modules. 25 lessons. 6 artifacts you can hand to an investor or a co-founder. Each module’s output is the next module’s input.
The 5 Modules at a Glance #
Module 1 - Hypothesis & Smoke Test #
You have: a rough idea or instinct. You walk away with: a one-sentence Founding Hypothesis + a live landing page with a Stripe price button. Time: ~7 days full-time; 2-3 weeks at an evenings-and-weekends pace.
| Step | What You Do | Key Tool |
|---|---|---|
| 1.1 | Write your Founding Hypothesis | Notebook + kitchen timer |
| 1.2 | Build a smoke-test landing page | Mixo or Carrd (the 1.3 tracking step may need the builder’s small paid tier) |
| 1.3 | Wire tracking before traffic starts | Microsoft Clarity + GA4 (free visitor-tracking tools) |
| 1.4 | Run 300 cold visitors and read the signal | Ad platform of choice |
| 1.5 | Add a Stripe price button to measure payment intent | Stripe Payment Links |
→ Mia’s Module 1: spent $400 on Meta ads, 300 cold visitors, 6.5% conversion, six pre-orders at $99 each - before a line of product code. Full walkthrough →
Before you write the hypothesis: spend 30 minutes with Perplexity (an AI search engine that answers questions with cited sources). Ask it to find the top 5 user complaints about existing solutions in your niche, citing reviews from G2 and Capterra (the two big business-software review sites). Use the exact vocabulary from real complaints in your hypothesis blanks. If nobody is complaining about the problem anywhere online, the hypothesis is already in trouble.
Trend Seeker (free tier, in the optional tools list below) runs a similar sweep across Reddit and forums if you want a second source before you commit to the hypothesis.
Module 2 - Validate the Problem #
You have: a Founding Hypothesis. You walk away with: 10 Mom Test interview transcripts + a validated problem statement + a clickable prototype tested with 5 people. Time: ~3-5 weeks full-time - booking the 10 interviews is the long pole (Lesson 2.3 plans 2-4 calendar weeks for that step alone).
| Step | What You Do | Key Tool |
|---|---|---|
| 2.1 | Learn the 5 Mom Test rules (ask about past, not future) | Mom Test Interview Script |
| 2.2 | Rehearse your questions with an AI persona (optional - skip if you’ve run customer interviews before) | Claude or ChatGPT |
| 2.3-2.4 | Find and book 10 ICP interviews (ICP = Ideal Customer Profile - the specific kind of person your hypothesis names) | Reddit, LinkedIn, X |
| 2.5 | Score the transcripts and make the build / pivot / kill call | Mom Test Synthesis page |
| 2.6 | Build a throwaway 3-screen clickable prototype | Lovable |
→ Mia’s Module 2: rehearsed questions with an AI persona, booked 10 interviews from a 30-name list, scored the transcripts to reach “build,” and tested a clickable prototype with five parents. Full walkthrough →
The Mom Test is irreplaceable. AI tools can tell you what people say online, but they cannot tell you whether a specific human will open their wallet. Without the interviews, you’re building features for a problem nobody confirmed exists.
After the interviews and before the brief, you can run your refined hypothesis through IdeaProof (free tier to start); it stress-tests your business logic and catches legal, economic, and competitive blind spots you haven’t considered.
Module 3 - Design from Evidence #
You have: 10 interview transcripts + prototype feedback. You walk away with: a one-page Product Brief written from real customer vocabulary. Time: ~3-5 days on the calendar - about one evening of writing plus a lunch-break quality check, with a night’s sleep between drafts.
| Step | What You Do | Key Tool |
|---|---|---|
| 3.1 | Write a one-page Product Brief - “Vibe PRD” (PRD = Product Requirements Document; the “Vibe” version is a one-pager an AI builder can act on, not a 30-page spec for a 6-person team) | Vibe PRD Template |
| 3.2 | Quality-check: rewrite features as outcome-shaped job stories | Claude or ChatGPT |
→ Mia’s Module 3: turned ten scored transcripts into a one-page product brief where every feature traced back to something a parent actually said. Full walkthrough →
The brief is the handoff document. It goes to Lovable, a hired developer, or a fractional CTO. It prevents over-engineering because it describes what the customer needs to accomplish, not what features to build. Every feature in the brief must trace back to a verbatim quote from a Module 2 interview.
Module 4 - Build It Yourself #
You have: a one-page Product Brief. You walk away with: a build decision + a live MVP at a real URL, with you owning every account. Time: ~2-4 weeks.
| Step | What You Do | Key Tool |
|---|---|---|
| 4.1 | Decide: self-serve, fractional CTO (a part-time senior engineer who owns architecture but doesn’t write all the code), or hired team | Build Path Decision Worksheet |
| 4.2 | Lock ownership: GitHub, AWS, domain, database in your name | Ownership Checklist |
| 4.3 | Set up the stack and pre-flight rules: Lovable + Supabase + Stripe | Lovable + Supabase + Stripe |
| 4.4 | Walk the 4 build phases to a live MVP at a real URL | Same stack + a domain in your name |
| 4.5 (optional) | Spot the 5 ceiling signals that mean it’s time to graduate beyond no-code | Monthly calendar block |
→ Mia’s Module 4: chose self-serve, locked ownership of every account, walked the four build phases, and shipped TutorMatch on Lovable + Supabase + Stripe - her spouse signed up in Phase 2. Full walkthrough →
Before you write code: the $0 Concierge MVP. If you’re not ready to commit to a full Lovable build, use Tally + Zapier (or Make.com) + Airtable to simulate your product’s backend. Collect customer requests through a Tally form, route them to Airtable via Zapier, and process them manually. The customer experiences a working product. You validate demand before writing a line of code. All three tools have free tiers.
Module 5 - First Paying Customer #
You have: a live MVP at a real URL. You walk away with: one signed paid pilot with a real deposit ($500+ standard; 5.6 covers the low-price exception) + a repeatable outbound channel. Time: ~2-4 weeks.
| Step | What You Do | Key Tool |
|---|---|---|
| 5.1 | Run the Sean Ellis PMF test (PMF = Product-Market Fit; one survey question: “how would you feel if you could no longer use this product?” 40%+ “very disappointed” = signal) on your earliest users | PMF survey template |
| 5.2 (optional) | Pick one outreach channel and commit before scaling | Channel selection framework |
| 5.3 | Build the 50-name warm list, sorted into 4 outreach buckets | One spreadsheet |
| 5.4 | Write the 4 bucket messages + a 90-second Loom | Loom |
| 5.5 | Send in sequence, track replies, book demos | The same spreadsheet |
| 5.6 | Sign a Design Partner Agreement - “DPA” (a short contract where a customer pays a deposit to test your product as a co-design partner; cheaper and faster than a full enterprise contract) - with a deposit (refunded in full if you cancel; forfeited if the customer cancels early) | DPA template + Stripe |
| 5.7 (optional) | Go cold outbound: 30 filtered messages, book 1-2 pilots | LinkedIn Sales Navigator or manual |
→ Mia’s Module 5: sent her DPA to the warmest lead from her champion bucket - the $1,200 deposit cleared before she built anything new. Full walkthrough →
Important distinction: your warm network is the right place to sell your first paid pilot, and the wrong place to validate the problem. Friends and other founders will tell you your idea is great because they’re being polite. Only cold strangers who describe the problem in their own words and pay money produce a real signal.
Going further: After your first paid pilot, the course has continuation chapters for churn triage, pivot-or-persevere decisions, hiring, agency oversight and management (Friday Demo Rule, Weekly Dev Report), and AI-era topics (token bill auditing, slopsquatting, agency AI questions). Once you’ve passed the Module 5 gate, they live with their read-this-when triggers in the First-Paying-Customer Operating Kit.
The Tool Stack: When to Use What #
Four tools carry the whole linear path - the landing page, the checkout, the app builder, and the backend. Most have free tiers sufficient for the validation stage. Tool pricing and free-tier limits change often; the Cost column tells you which tier to look for, and the tool’s own pricing page is the source of truth on the day you sign up.
| Tool | What It Does | When to Use | Cost |
|---|---|---|---|
| Mixo / Carrd | One-page landing page builder | Smoke test (Module 1) | Free tier (subdomain) |
| Stripe Payment Links | Hosted checkout without writing code | Price hypothesis test (Module 1), paid pilot deposit (Module 5) | Pay-as-you-go (per-transaction fee) |
| Lovable | AI app builder from text prompts | Clickable prototype (Module 2), MVP build (Module 4) | Free tier |
| Supabase | Hosted Postgres + auth + realtime | MVP backend (Module 4) | Free tier |
Every other tool appears in the lesson that uses it - the module tables above carry the per-lesson tools (Clarity + GA4 in 1.3, Loom in 5.4); the expander below collects the optional research helpers and alternate paths.
Optional research tools and alternate paths - 8 entries
| Tool | What It Does | When to Use | Cost |
|---|---|---|---|
| Perplexity | AI search engine that answers with cited sources, aggregates competitor complaints | Map the market before Module 1, find what users hate about existing solutions | Free tier |
| Trend Seeker | Semantic search across Reddit/forums for demand signals | Confirm people are actually searching for solutions to your problem | Free tier |
| Reddinbox | Automated Reddit/Quora search for high-commercial-intent phrases | Find posts where people explicitly ask “how to automate X” or “sick of doing Y” | Setup required |
| ValidatorAI | Dialog-based AI advisor, rates your idea and finds blind spots | Rapid “devil’s advocate” feedback before interviews | Free tier |
| IdeaProof | AI cross-check of your business logic | After Mom Test interviews, before writing the Product Brief | Free tier |
| Preuve AI | Evidence-based idea scoring from live data sources, with citations | Before building, when you need a data-backed viability check | Free tier |
| Bolt.new | AI app builder, an alternative to Lovable | Same jobs as Lovable, if you prefer it | Free tier |
| Tally + Zapier + Airtable | “Wizard of Oz” no-code stack (a fake-it-till-you-make-it pattern: the customer thinks software is running, but you do the work by hand behind the scenes to test demand before you build the real thing) | Concierge MVP before committing to a code build (Module 4 alt path) | Free tiers |
The Course’s Rule: Kill Bad Ideas Fast #
Every module has a gate. If the data doesn’t support your hypothesis, you stop and either pivot or kill the idea.
| Module | The Gate | Signal to Proceed |
|---|---|---|
| 1 | Landing page conversion | ≥6% of cold visitors submit the email form (the “Promising” band in the 1.4 decision table; 3-6% = iterate the message, under 3% = kill or pivot) |
| 2 | Mom Test interviews | ≥7 of 10 interviewees have spent time or money on the problem |
| 3 | Product Brief quality check | Every feature traces back to a verbatim interview quote |
| 4 | MVP at a real URL | You own every account; the app loads; one core flow works end-to-end |
| 5 | First paid pilot | Signed DPA + Stripe deposit received ($500+ standard; low-price path in 5.6) |
If you fail a gate, the system requires you to go back, not forward. Failing at the gate costs you a few weeks and a few hundred dollars of ad spend; failing after the build costs founders years and tens of thousands of dollars on something nobody wants.
Start Here #
Read the overview once. Then start at Module 1, Lesson 1.1: Form Your Founding Hypothesis. Come back to this page when you need to see where you are in the full route.
If you’re not at the idea stage - you’re already building, or paying someone to build for you - see Already started building? below.
Done when: You have read the full route and know which module to start with. Next click: 1.1 · Form Your Founding Hypothesis If blocked: If your idea is too vague to fill the hypothesis blanks, Lesson 1.1’s “If this fails” section shows how to anchor the blanks with real customer complaints from Reddit and G2.
Already started building? #
If you just have an idea or a half-built prototype you’re tinkering with, skip to Module 1. If you are already typing, or paying someone an hourly rate to type for you, start with the ownership audit in Lesson 4.2 · Who Owns Your GitHub, AWS, and Database? - it carries the full pre-flight list to run before you approve any more work.
Who built this #
Built by JetThoughts. We’ve run a Rails-first dev shop since 2008, and we have sat on the receiving end of enough first builds gone wrong to know which mistakes repeat: a 15-page wishlist spec where a one-page brief should have been, or a GitHub account registered to a contractor who stopped replying. This course is the desk reference we wish those founders had before their first build decision.
Why free? A founder who validates before building makes a better future client than one we meet mid-disaster, and there is nothing to buy inside the course.
Updated July 2026. Recent changes:
- Lesson 1.1 split into two short sittings - write first, score later
- Hand-drawn diagrams added across all five modules
- Printable worksheets shipping module by module
This page tracks the live course.
Built by JetThoughts as part of the From Idea to First Paying Customer curriculum. Research sources: June 2026 AI validation tools market analysis, 29 sources across Indie Hackers, Reddit, Product Hunt, and VC.ru.