diff --git a/content/course/tech-for-non-technical-founders-2026/_index.md b/content/course/tech-for-non-technical-founders-2026/_index.md
index 6623fbd14..31a1c7c02 100644
--- a/content/course/tech-for-non-technical-founders-2026/_index.md
+++ b/content/course/tech-for-non-technical-founders-2026/_index.md
@@ -69,7 +69,7 @@ Skip this course if you want to learn to code or hand off founder judgment to so
## Module map
-Read the modules in order. Each module's output is the next module's input, and each leaves you with at least one fill-in-the-blank artifact - the **"You leave with"** line on every card below. The {{< course-stat artifacts >}} artifacts bundle into a single Google Drive folder - your **Founder OS** - that doubles as your decision log. If you ever raise, the same folder is the evidence pack investors fund.
+Read the modules in order. Each module's output is the next module's input, and each card's **"You leave with"** line names its output; together with the fill-in templates they total {{< course-stat artifacts >}} artifacts, which bundle into a single Google Drive folder - your **Founder OS** - that doubles as your decision log. If you ever raise, the same folder is the evidence pack investors fund.
@@ -125,11 +125,11 @@ Read the modules in order. Each module's output is the next module's input, and
- 4.1 Should You Hire? The 2026 Decision Tree
- 4.2 Who Owns Your GitHub, AWS, and Database?
- - 4.3a The Self-Serve MVP Stack: Tools & Setup
- - 4.3b The Self-Serve MVP Stack: Build Phases
- - 4.4 Vibe Coding Done Right: 5 Ceiling Signals optional
Skip on first pass. Come back when your no-code build hits a wall - a feature you can't add, a query you can't tune, an auth flow Lovable can't handle.
+ - 4.3 The Self-Serve MVP Stack: Tools & Setup
+ - 4.4 The Self-Serve MVP Stack: Build Phases
+ - 4.5 Vibe Coding Done Right: 5 Ceiling Signals optional
Skip on first pass. Come back when your no-code build hits a wall - a feature you can't add, a query you can't tune, an auth flow Lovable can't handle.
-
+
You leave with: a live MVP at a real URL that you built and you own - every account in your name from Day 1.
@@ -140,14 +140,14 @@ Read the modules in order. Each module's output is the next module's input, and
Start here if your MVP is live but you don't have a paying customer with a signed pilot.
- 5.1 Your First Customer Is Not a Marketing Problem
- - 5.2 Choose Your Channel Before You Send One Message optional
Skip if you already have a channel in mind (LinkedIn, cold email, or personal network). The core path is 5.3a→b→c (personal network) → 5.4 (paid pilot).
- - 5.3a Build Your 50-Name Network List
- - 5.3b Write the Outreach Message
- - 5.3c Send, Track, and Read the Replies
- - 5.4 Charge Before You Ship: The Paid Pilot Contract
- - 5.5 Going Outbound Without a Sales Team optional
Skip if your personal network in 5.3a→c produced your first 10 customers. This is the systematic path for when warm intros run out.
+ - 5.2 Choose Your Channel Before You Send One Message optional
Skip if you already have a channel in mind (LinkedIn, cold email, or personal network). The core path is 5.3-5.5 (personal network) → 5.6 (paid pilot).
+ - 5.3 Build Your 50-Name Network List
+ - 5.4 Write the Outreach Message
+ - 5.5 Send, Track, and Read the Replies
+ - 5.6 Charge Before You Ship: The Paid Pilot Contract
+ - 5.7 Going Outbound Without a Sales Team optional
Skip if your personal network in 5.3-5.5 produced your first 10 customers. This is the systematic path for when warm intros run out.
-
+
You leave with: a signed paid pilot and your first dollar from a customer, not a favor.
diff --git a/content/course/tech-for-non-technical-founders-2026/build-path-decision-worksheet/index.md b/content/course/tech-for-non-technical-founders-2026/build-path-decision-worksheet/index.md
index c9d71cdf6..530ddadd2 100644
--- a/content/course/tech-for-non-technical-founders-2026/build-path-decision-worksheet/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/build-path-decision-worksheet/index.md
@@ -32,7 +32,7 @@ related_posts: false
## Why this exists
-A wellness-coaching founder we picked up in Q1 2026 had spent four months building a Lovable MVP, then panicked and signed a $24K-per-month agency contract because three advisors told her "you need a real team now." Two of the advisors had never seen her validation data. The third had not asked.
+A wellness-coaching founder who came to us in early 2026 had spent four months building a Lovable MVP, then panicked and signed a $24K-per-month agency contract because three advisors told her "you need a real team now." Two of the advisors had never seen her validation data. The third had not asked.
She showed us the contract on a Tuesday. By Friday we had walked her through the same 5 questions on this worksheet and the matrix said Path 3 (Fractional CTO at $2,400/mo, 8 hours/week), not Path 4 (the agency at $24K/mo). She paid the agency a kill fee and saved 14 months of runway. The decision was already in the data she had. The advisors had not run the worksheet. Cheaper to spend 30 minutes with this page than to spend a quarter undoing a contract somebody else's instinct signed for you.
diff --git a/content/course/tech-for-non-technical-founders-2026/channel-selection-before-outbound/index.md b/content/course/tech-for-non-technical-founders-2026/channel-selection-before-outbound/index.md
index 393c4aba2..110854bb9 100644
--- a/content/course/tech-for-non-technical-founders-2026/channel-selection-before-outbound/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/channel-selection-before-outbound/index.md
@@ -30,11 +30,13 @@ canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2
related_posts: false
---
-> **Module 5 · Step 2 of 5** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 5 · Lesson 5.2 · [OPTIONAL] - skip if you already know your channel** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
-> **Input:** 10 Mom Test interview transcripts from Module 2 + your live MVP from Module 4 (Ch 4.3b) + the ICP (Ideal Customer Profile - the specific kind of person your hypothesis names; introduced in Ch 1.1) you sharpened across Modules 1-2
+> **Input:** 10 Mom Test interview transcripts from Module 2 + your live MVP from Module 4 (Ch 4.4) + the ICP (Ideal Customer Profile - the specific kind of person your hypothesis names; introduced in Ch 1.1) you sharpened across Modules 1-2
>
> **Output:** one channel hypothesis committed long enough to read the signal
+>
+> **Progress:** M5 · 2 of 7 · [OPTIONAL] - run this only if you don't yet know which channel your buyers actually use
> **TL;DR:** Pick one channel from your interview evidence and commit for a full send/reply/follow-up arc. Channel-hopping is the most common newbie mistake - you can't read a signal you never let stabilize.
@@ -42,8 +44,6 @@ The channel-flailing pattern: switch every 10 days - LinkedIn for two weeks, col
The fix is rarely "find a smarter channel." It's pick one channel from your interview evidence and stick with it through a full send/reply/follow-up arc. Same six weeks on LinkedIn alone produces 11 conversations, 2 paid pilots, and a clear hypothesis about what to test next.
-The pattern: four channels, no commitment, and no way to tell which channel had worked because none of them had been run long enough to read.
-
You ran 10 interviews in [Module 2](/course/tech-for-non-technical-founders-2026/find-10-people-with-problem-outreach-2026/). Your interviewees told you exactly how they find tools like yours. They just did not use the word "channel" when they said it.
This chapter is about listening to what they actually said and committing to one channel before you try anything else.
@@ -97,7 +97,7 @@ At this stage you are choosing from four options. Here is what each one actually
| Channel | Best for | Requires | Red flag |
|---------|----------|----------|----------|
| **LinkedIn DM** | B2B SaaS/services, professional buyers, job-title filtering, $200+/mo | 1-2 hrs/week; Sales Navigator trial or Apollo.io free tier (credit-based free tier); one clear filter (title + company + industry) | Buyer is not a professional (freelancer, solo creator, non-employee) |
-| **Cold email** | Any B2B with verified work emails; cheaper at volume | Separate sending domain; free tool ([Instantly](https://instantly.ai) / [Smartlead](https://smartlead.ai)); 30-50 emails from [Apollo](https://apollo.io) / [Hunter](https://hunter.io) (free tier available) | Open rate <20% after first batch = domain rep or subject lines broken; fix before scale |
+| **Cold email** | Any B2B with verified work emails; cheaper at volume | Separate sending domain; free tool ([Instantly](https://instantly.ai) / [Smartlead](https://smartlead.ai)); 30-50 emails from [Apollo](https://apollo.io) / [Hunter](https://hunter.io) (free tier available) | Open rate (share of recipients who open your email) <20% after first batch = domain rep or subject lines broken; fix before scale |
| **Community outreach** | B2B and prosumer where buyers already gather in Slack/Discord/forum | Must be a genuine participant first; one signal-quality post per sprint (not per week); spend 2 weeks commenting before posting product or get banned permanently | Joining this week then immediately selling = permanent ban from the community |
| **Social organic** | B2C and prosumer, visual products (apps, productivity tools, demos); buyer discovery from peers/influencers | A sustained posting cadence; format shows product working (screen recordings, before/after, results) | Never posted before AND can't commit to the early low-visibility stretch |
| **Engineering as Marketing** | Any B2B or prosumer where your ICP searches for tactical solutions; zero-CAC organic SEO | One free no-code micro-tool (calculator, checklist, grader, template) that solves one micro-problem for your ICP; build it on Carrd/Tally/Notion in an afternoon | Your ICP doesn't search for tactical tooling (they buy via referral or sales call); the micro-tool solves a toy problem nobody actually has |
@@ -144,8 +144,6 @@ The prompt is a forcing function, not a crystal ball. The real data comes from r
>
> **The real gate:** ≥9/12 channel-fit score + a full send/reply/follow-up arc with reply rate >5%.
>
-> **Optional: auto-parse social media for leads.** [WorthBuild](https://worthbuild.io) (free tier available) scans Reddit, Twitter/X, and LinkedIn for posts matching your ICP's problem description and returns a list of named people publicly complaining about the thing you solve. Use it to seed your outreach list when the manual reading in Ch 2.3-2.4 didn't produce enough names. The free tier is metered - save it until you have exhausted your hand-picked list and need fresh contacts.
-
## Channel Selection Worksheet
Fill this out before you send message one. It prevents the wasted-effort cycle of channel-hopping.
@@ -228,17 +226,13 @@ With 30 focused messages you get a reply rate you can diagnose; with 10 messages
Pick the channel your interviews point to, write it down, and give it a real run before you question it.
-The first place to apply this is your personal network in [Chapter 5.3a (Build Your 50-Name Network List)](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/). Once that is exhausted, [going outbound without a sales team](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) covers the tactics for running the channel you just chose: the filter, the script, the Calendly-to-Stripe pipeline, and what the reply rate actually means.
+The first place to apply this is your personal network in [Chapter 5.3 (Build Your 50-Name Network List)](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/). Once that is exhausted, [going outbound without a sales team](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) covers the tactics for running the channel you just chose: the filter, the script, the Calendly-to-Stripe pipeline, and what the reply rate actually means.
## What to do tomorrow
1. Open the worksheet above and score each of the 4 channels against your customer interview answers. Pick the one that maps to the most evidence.
2. Write the channel name + your commitment statement in a Notion doc. The clock starts the day you send your first outbound message.
-3. Read [Chapter 5.3a - Build Your 50-Name Network List](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) before your first send - that's the playbook for getting the first conversations on the channel you just picked.
-
-> **Module 5, Step 2 of 5** - channel selection is the decision before any outreach tactic. Finish the worksheet above before you open a single sales tool.
-> Next: [5.3a · Build Your 50-Name Network List](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/)
-> Course: [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+3. Read [Chapter 5.3 - Build Your 50-Name Network List](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) before your first send - that's the playbook for getting the first conversations on the channel you just picked.
Pick the channel your interviews already named, commit to it long enough to read the signal, and stop running pilots against your own attention.
@@ -249,18 +243,16 @@ Pick the channel your interviews already named, commit to it long enough to read
- Andrew Chen, [The Law of Shitty Clickthroughs](https://andrewchen.com/the-law-of-shitty-clickthroughs/) - why every channel degrades over time and why early-stage founders need to pick the channel that works now, not the channel that worked for a more established company 3 years ago.
- First Round Capital, [From 1 to 1,000 Users](https://review.firstround.com/from-1-to-1000-users-tactics-from-airbnb-tinder-etsy-reddit-and-more/) - channel selection stories from Airbnb, Tinder, Etsy, Reddit, including how each picked their first acquisition channel based on where their early customers actually lived online.
-> **Done when:** Your worksheet is filled, one channel is chosen, and you have written your commitment statement (channel name + why + evaluation criteria).
+> **Done:** your worksheet is filled, one channel is chosen, and you have written your commitment statement (channel name + why + evaluation criteria).
>
-> **Next click:** [5.3a · Build Your 50-Name Network List](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/)
+> **You have now:** a committed channel (5.2) chosen from your interview evidence. The 50-name list to run it on is next.
>
-> **If blocked:** If no channel scores ≥9/12, your interview transcripts are missing channel signal. Re-read the transcripts looking for "how do you find tools like this" and "what tools do you use every day" - the answers are already in there.
-
-> **Case Study: Tomas & Mia**
->
-> **Tomas**: Channel scoring: LinkedIn (9/12 - controllers are there), cold email (8/12), Reddit (5/12). Commits to LinkedIn + cold email. Scoring: 8.0/10.
+> **Next:** [5.3 · Build Your 50-Name Network List](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) - the personal-network list you'll run this channel on first.
>
-> **Mia**: Channel scoring: Facebook groups (9/12 - parents are there daily), school referrals (7/12), Instagram (5/12). Commits to Facebook groups + school district referrals.
+> **If blocked:** If no channel scores ≥9/12, your interview transcripts are missing channel signal. Re-read the transcripts looking for "how do you find tools like this" and "what tools do you use every day" - the answers are already in there.
---
+*See it in action: [Module 5 walkthrough: Mia gets paid](/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/)*
+
*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/index.md b/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/index.md
index 162160cba..41f9dff34 100644
--- a/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/index.md
@@ -48,7 +48,7 @@ Those signals do not measure the same thing.
After this lesson you will be able to: **watch 5 real customers try to use your solution before it exists - and score what they do, not what they say.**
-A founder we advised had run 8 Mom Test interviews that came back strong: workaround evidence, named monthly costs, real frustration language. She moved to Lovable (an AI app builder; see the gloss in [Chapter 4.3a](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/)) and built a working app over several weeks.
+A founder we advised had run 8 Mom Test interviews that came back strong: workaround evidence, named monthly costs, real frustration language. She moved to Lovable (an AI app builder; see the gloss in [Chapter 4.3](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/)) and built a working app over several weeks.
When she had 5 of the same interviewees log in to try the live app, several stalled on screen 2 - they recognised the problem the app was solving but could not figure out which button to click next. Validating the problem had not validated whether the interface shape was something they could navigate.
@@ -58,7 +58,7 @@ A throwaway prototype run in front of 5 of your interview subjects would have su
>
> You will build 3 throwaway screens, show them to 5 of your Mom Test interviewees, watch what they do without coaching, then archive everything. The only outputs that carry forward into Module 3 are (a) the pass/fail signal and (b) the exact words your users used when describing what they saw. The prototype CODE is discarded.
>
-> If you try to polish this prototype into your MVP later, you'll spend much longer on it, carry every throwaway compromise into production, and invalidate the shape test. The actual MVP is a fresh build in Module 4 ([Ch 4.3a](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) defines the stack, [Ch 4.3b](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/) walks the phases), started from the one-page brief (Chapter 3.1) with real auth, real Stripe, real domain.
+> If you try to polish this prototype into your MVP later, you'll spend much longer on it, carry every throwaway compromise into production, and invalidate the shape test. The actual MVP is a fresh build in Module 4 ([Ch 4.3](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) defines the stack, [Ch 4.4](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/) walks the phases), started from the one-page brief (Chapter 3.1) with real auth, real Stripe, real domain.
## Why a Clickable Prototype Catches What Interviews Miss
@@ -335,7 +335,7 @@ After finishing Ch 2.1-2.6, you have five artifacts. Each one feeds a specific d
|---|---|
| **Validated Problem Statement** (Ch 2.5 synthesis applied to your Ch 2.3-2.4 transcripts) | Ch 3.1 Section 1 - copy verbatim. This is the PRD's foundation. (PRD = product requirements document, the one-page spec a team or AI agent builds from.) |
| **Pass/fail prototype log** (5 sessions from this chapter) | Reference doc: did we get the shape right? If yes, write the brief. If no, the table above routes you to a revision or restart. |
-| **Verbatim "describe in one sentence" vocabulary** (closing answers from this chapter) | Ch 3.1 Section 3 ("what you're building") + Ch 4.3 (a + b) Lovable prompts. The user's words beat your marketing copy. |
+| **Verbatim "describe in one sentence" vocabulary** (closing answers from this chapter) | Ch 3.1 Section 3 ("what you're building") + Ch 4.3-4.4 Lovable prompts. The user's words beat your marketing copy. |
| **10 raw transcripts** (Ch 2.3-2.4 interview recordings + notes) | Archive. Reference if you ever pivot - they hold the language for a re-targeted ICP. |
| **30 raw verbatim sentences** (Ch 2.3-2.4 step 2, Reddit/forum complaints) | Reference for Ch 3.1 Section 1 supplementary evidence + the bank for Ch 2.3-2.4 cold-message subject lines in any future round 2. |
diff --git a/content/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/index.md b/content/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/index.md
index a95613be9..861fdd99f 100644
--- a/content/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/index.md
@@ -108,8 +108,8 @@ flowchart TD
B -->|All segments under 25%
and roughly the same| C[Decision 3 - KILL THE SKU
Sunset gracefully + pivot]
B -->|All segments around 20-35%
and roughly the same| D[Decision 1 - FIX THE PRODUCT
Rebuild one workflow]
B -->|One segment over 50%
others under 20%| E[Decision 2 - CHANGE THE SEGMENT
Refund the wrong half]
- C --> CK[Go to chapter 7.6
Pivot or Persevere]
- D --> DK[Go to chapter 8 / 9
When things break]
+ C --> CK[Go to Pivot or Persevere
in Going Further]
+ D --> DK[Go to the rescue chapters
Going Further]
E --> EK[Re-run Module 5 outreach
aimed at the right segment]
classDef redbox fill:#fff5f5,stroke:#cc342d,stroke-width:2px;
@@ -132,7 +132,7 @@ The fix is to stop adding features and rebuild one workflow until it actually wo
One segment retains at 50%+ while others languish under 20%. The product works; the audience is wrong. R.'s case from the opening was Decision 2 - 71% retention for 3-person teams, 8% for solo founders, two-thirds of her customers paying for a product that did not fit their job.
-The fix has two parts. First, fire the wrong segment - refund their last 30 days, recommend an alternative tool, and remove them from the customer list. Second, double down on the right segment - rewrite the landing page headline for 3-person teams, redirect ad spend to that audience, and re-run [Chapter 5.3a personal-network outreach](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) within the segment that retains.
+The fix has two parts. First, fire the wrong segment - refund their last 30 days, recommend an alternative tool, and remove them from the customer list. Second, double down on the right segment - rewrite the landing page headline for 3-person teams, redirect ad spend to that audience, and re-run [Chapter 5.3 personal-network outreach](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) within the segment that retains.
R. did this on a Friday afternoon. By the following Friday she had 11 paying customers (the right ones) and a refund tab of $5,800 (the wrong ones). Her net month-end customer count went from 35 to 11, and her churn rate dropped from 65% to 14% the next 30 days. Fewer customers, less revenue, but a real business instead of a leaking one.
@@ -140,7 +140,7 @@ R. did this on a Friday afternoon. By the following Friday she had 11 paying cus
No segment retains above 25%. You have a feature, not a product. The pain is real but your build does not relieve it - users try it once, do not see the value, and never come back regardless of who they are.
-This is the hardest decision because it feels like quitting. It is not quitting; it is recovering the runway you would otherwise burn proving the same thing for another two months. Sunset the SKU. Refund the active subscribers (Stripe handles this in two API calls; your support inbox handles the rest). Move the operating decision to [chapter 7.6 Pivot or Persevere](/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/), which walks the six pivot types and the trigger conditions. The cohort data you collected in the 90-minute floor is the strongest single piece of evidence you will hand into the pivot decision.
+This is the hardest decision because it feels like quitting. It is not quitting; it is recovering the runway you would otherwise burn proving the same thing for another two months. Sunset the SKU. Refund the active subscribers (Stripe handles this in two API calls; your support inbox handles the rest). Move the operating decision to [the Pivot or Persevere chapter](/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/), which walks the six pivot types and the trigger conditions. The cohort data you collected in the 90-minute floor is the strongest single piece of evidence you will hand into the pivot decision.
The most common founder failure mode at this triage step is to refuse to pick. The cohort data says Decision 2; the founder spends six more weeks "trying to lift the solo segment retention" because saying goodbye to two-thirds of paying customers feels worse than burning $4,800/month. Six weeks later the metrics are unchanged and the runway is shorter. The triage works only if you commit to the decision in the same week you ran the cohort.
@@ -175,8 +175,8 @@ The honest trade-off: a refund-the-wrong-segment campaign cuts your customer cou
You walk out of this chapter holding one of three artifacts: a fix-the-product plan with a 4-6 week ship date, a change-the-segment plan with a refund script and a redirected outreach motion, or a kill-the-SKU verdict pointing toward a pivot decision. Pick the next move from your verdict and re-run the cohort floor every 6 weeks until the bucket stops leaking.
1. **If Decision 1 (FIX THE PRODUCT):** open the [salvage-vs-rebuild decision framework](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/) and feed it the cohort data. Use the same numbers in the brief to whoever rebuilds the workflow - dev shop, fractional CTO, or AI tooling - so they know which workflow to rebuild and which to leave alone.
-2. **If Decision 2 (CHANGE THE SEGMENT):** re-run [Chapter 5.3a - personal-network outreach](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) aimed at the high-retention segment. R.'s 11 kept customers seeded her next outreach run - she asked each for two intros to similar 3-person teams and landed 7 paid pilots in 3 weeks. Your cohort data ("we have 11 customers who look like you and they retain at 70%") is the warmest possible referral.
-3. **If Decision 3 (KILL THE SKU):** open [chapter 7.6 - Pivot or Persevere](/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/). The cohort floor numbers are the evidence the pivot framework asks for - four cohorts saying the same thing, not a hunch.
+2. **If Decision 2 (CHANGE THE SEGMENT):** re-run [Chapter 5.3 - personal-network outreach](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) aimed at the high-retention segment. R.'s 11 kept customers seeded her next outreach run - she asked each for two intros to similar 3-person teams and landed 7 paid pilots in 3 weeks. Your cohort data ("we have 11 customers who look like you and they retain at 70%") is the warmest possible referral.
+3. **If Decision 3 (KILL THE SKU):** open [Pivot or Persevere](/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/). The cohort floor numbers are the evidence the pivot framework asks for - four cohorts saying the same thing, not a hunch.
## Further reading
diff --git a/content/course/tech-for-non-technical-founders-2026/faq/index.md b/content/course/tech-for-non-technical-founders-2026/faq/index.md
index 18e6c4178..7584d52bc 100644
--- a/content/course/tech-for-non-technical-founders-2026/faq/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/faq/index.md
@@ -87,15 +87,15 @@ Your Section 3 is too vague. Rewrite every feature as a "When / I want / So I ca
**Q: I don't know whether to hire or build myself.**
-Run the [Ch 4.1 decision tree](/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/). The default answer for a first-time solo founder with a validated brief: build it yourself with Lovable + Supabase + Stripe. Hiring triggers when you hit a [Ch 4.4 ceiling signal](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/) - not before.
+Run the [Ch 4.1 decision tree](/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/). The default answer for a first-time solo founder with a validated brief: build it yourself with Lovable + Supabase + Stripe. Hiring triggers when you hit a [Ch 4.5 ceiling signal](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/) - not before.
**Q: The 12 rules checklist is overwhelming. Where do I even start?**
-Only 3 rules need to be true before you open Lovable: (1) your one-page brief passed the Ch 3.2 quality-gate, (2) you scoped one workflow for one persona, (3) GitHub sync is on in Lovable Settings. The other 9 rules fire inline during the build. Read the [Ch 4.3a chapter](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) for the full list.
+Only 3 rules need to be true before you open Lovable: (1) your one-page brief passed the Ch 3.2 quality-gate, (2) you scoped one workflow for one persona, (3) GitHub sync is on in Lovable Settings. The other 9 rules fire inline during the build. Read the [Ch 4.3 chapter](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) for the full list.
**Q: Lovable generated a sprawling admin panel from my one-page brief.**
-Your brief's Section 3 is feature-shaped. Go back to [Ch 3.2](/course/tech-for-non-technical-founders-2026/stop-specifying-features-start-outcomes/) and rewrite every feature as a "When / I want / So I can" outcome before you re-prompt Lovable. Then use the AI critic block in [Ch 4.3a](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) to audit your build against your brief.
+Your brief's Section 3 is feature-shaped. Go back to [Ch 3.2](/course/tech-for-non-technical-founders-2026/stop-specifying-features-start-outcomes/) and rewrite every feature as a "When / I want / So I can" outcome before you re-prompt Lovable. Then use the AI critic block in [Ch 4.3](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) to audit your build against your brief.
---
@@ -103,11 +103,11 @@ Your brief's Section 3 is feature-shaped. Go back to [Ch 3.2](/course/tech-for-n
**Q: I'm terrified of asking for money. How do I start?**
-The deposit is a test of whether the problem is real - not a test of whether you deserve to be paid. Send the [DPA template](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/#dpa-template) to your warmest lead first. A refundable deposit at kickoff is easier to ask for than a full-price sale. The [Ch 5.4 chapter](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/) has the exact contract template.
+The deposit is a test of whether the problem is real - not a test of whether you deserve to be paid. Send the [DPA template](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/#dpa-template) to your warmest lead first. A refundable deposit at kickoff is easier to ask for than a full-price sale. The [Ch 5.6 chapter](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/) has the exact contract template.
**Q: My personal network only has 5 names. What do I do?**
-Five is enough to start. Message all five before you try cold outbound - people who already know you reply and close at many times the rate of cold strangers, which is why [Ch 5.3a](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) runs the warm list first. If your network truly has zero applicable names, skip to [Ch 5.5 cold outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/).
+Five is enough to start. Message all five before you try cold outbound - people who already know you reply and close at many times the rate of cold strangers, which is why [Ch 5.3](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) runs the warm list first. If your network truly has zero applicable names, skip to [Ch 5.7 cold outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/).
**Q: The customer wants to start free and convert later. Should I accept?**
diff --git a/content/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/index.md b/content/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/index.md
index b620c22be..a2a5f8a29 100644
--- a/content/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/index.md
@@ -167,7 +167,7 @@ Aim for 30 hand-picked people in one focused sitting.
If you run out of named posters before you hit 30, [Apollo](https://apollo.io)'s free tier (credit-based, no credit card - a small monthly allowance of email and export credits) lets you filter on role + industry + company size and export the rest (the monthly export allowance is small, so this fills the gap over several weeks, not one sitting). Treat it as backfill, not the source - the hand-picked names always perform better.
-> **Save the Apollo filter and whatever contacts your monthly export credits cover (a small monthly allowance on the free tier) to a tab named "Module 5 cold seed" in your outreach spreadsheet.** You will reuse this exact filter in [Ch 5.5 cold outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/).
+> **Save the Apollo filter and whatever contacts your monthly export credits cover (a small monthly allowance on the free tier) to a tab named "Module 5 cold seed" in your outreach spreadsheet.** You will reuse this exact filter in [Ch 5.7 cold outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/).
Filter the final list on six dimensions:
diff --git a/content/course/tech-for-non-technical-founders-2026/find-10-people-with-problem-outreach-2026/index.md b/content/course/tech-for-non-technical-founders-2026/find-10-people-with-problem-outreach-2026/index.md
index 01649d40d..48f699c7f 100644
--- a/content/course/tech-for-non-technical-founders-2026/find-10-people-with-problem-outreach-2026/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/find-10-people-with-problem-outreach-2026/index.md
@@ -39,11 +39,11 @@ related_posts: false
> **TL;DR:** Send 30 staggered messages referencing specific posts you read, using a 3-message sequence (Day 0 intro + Day 3 bump + Day 7 close). Reply rate runs 20-30% when each message names a specific post; 1-5% when it doesn't. Plan to extend the list once or twice before all 10 calls are booked.
-> **This is Part 2 of 2.** [Part 1: Where to Look](/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/) covers the ICP mapping, reading threads, and building the 30-name list. You need the list from Part 1 before the templates below will work - generic openers collapse to 1-5% reply rates.
+> **Read [Chapter 2.3 - Where to Look](/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/) first.** It covers the ICP mapping, reading threads, and building the 30-name list. You need that list before the templates below will work - generic openers collapse to 1-5% reply rates.
> **How this chapter relates to Ch 2.6:** this chapter recruits 10 fresh interviewees and runs PAST-BEHAVIOR interviews about whether the problem is real. [Ch 2.6](/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/) takes the 5 strongest-signal interviewees from these 10 and runs a DIFFERENT kind of session - silent observation while they click through a throwaway Lovable prototype. Same recruitment pool; different methodology; sequential, not parallel. Run Ch 2.3-2.4 first to validate THE PROBLEM, then Ch 2.6 to validate THE SOLUTION SHAPE.
-This is interview recruitment, not sales. You're asking for time and insight, not money - different message template, different channels, different reciprocity. Don't use the Chapter 5.5 cold-email script here; it scares interview subjects who don't yet know you have a product.
+This is interview recruitment, not sales. You're asking for time and insight, not money - different message template, different channels, different reciprocity. Don't use the Chapter 5.7 cold-email script here; it scares interview subjects who don't yet know you have a product.
After this lesson you will be able to: **send outreach that names something the person actually wrote - and book 10 interviews from your 30-name list.**
@@ -188,7 +188,7 @@ The chain of artifacts the booked calls produce:
4. **Pick the 5 strongest-signal interviewees** (Mom Test score ≥ 7) for Ch 2.6 prototype sessions.
5. **Two artifacts now flow into Module 3 + later modules:**
- The Validated Problem Statement (Section 1 of the Ch 3.1 one-page brief, lifted verbatim)
- - The 5 strongest-signal interviewees (Ch 2.6 input - and later, your Module 5 onramp invitees in Ch 4.3 (a + b), plus your warm-list seed in Ch 5.3)
+ - The 5 strongest-signal interviewees (Ch 2.6 input - and later, your Module 5 onramp invitees in Ch 4.3-4.4, plus your warm-list seed in Ch 5.3)
If fewer than 7 of 10 calls score ≥ 7, the problem is too weak for this ICP. Re-evaluate the ICP, the problem framing, or the question wording before booking another 10 calls. The full kill / iterate / proceed decision lives in the [Mom Test Synthesis](/course/tech-for-non-technical-founders-2026/mom-test-synthesis-build-pivot-kill/) page.
diff --git a/content/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/index.md b/content/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/index.md
index d1661572d..7fb34c669 100644
--- a/content/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/index.md
@@ -62,13 +62,13 @@ flowchart TB
### 1. 50-name network list template (Google Sheets)
-The fill-in spreadsheet from [Chapter 5.3a](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/). Six columns - Name, Company, Role, Bucket, Relationship strength, Last contact date - plus four progress columns for tracking replies and demos. Pre-sorted by bucket: 5 champions on top, then 10 hot, 15 warm, 20 cold. Three blank rows in each bucket for week-2 additions.
+The fill-in spreadsheet from [Chapter 5.3](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/). Six columns - Name, Company, Role, Bucket, Relationship strength, Last contact date - plus four progress columns for tracking replies and demos. Pre-sorted by bucket: 5 champions on top, then 10 hot, 15 warm, 20 cold. Three blank rows in each bucket for week-2 additions.
In practice: turns a vague "I should reach out to people" instinct into 50 named messages going out by Friday EOD.
### 2. Cold-email scripts (3 variants)
-The verbatim 4-line scripts from [Chapter 5.4](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/). Three sector-specific versions:
+The verbatim 4-line scripts from [Chapter 5.7](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/). Three sector-specific versions:
- **B2B SaaS Rails context** - the script for founders who built on Rails and are selling to operators in the same space.
- **B2B services** - for fractional CTOs, consultancies, and managed-services founders who sell time rather than license.
@@ -80,7 +80,7 @@ Why it matters: removes the "what do I say in the email" friction so you spend 6
### 3. Design Partner Agreement template (one-page LOI + paid pilot)
-The one-page DPA from [Chapter 5.4](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/). Six sections plus signature block. Plain English, mutual-edit document, no lawyer required for v1. Comes in three formats: Google Docs (default), PDF (for customers who want to print), DocuSign-import (for customers who want to e-sign with audit trail).
+The one-page DPA from [Chapter 5.6](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/). Six sections plus signature block. Plain English, mutual-edit document, no lawyer required for v1. Comes in three formats: Google Docs (default), PDF (for customers who want to print), DocuSign-import (for customers who want to e-sign with audit trail).
Two annotated examples: a $1,500 B2B SaaS pilot DPA and a $5,000 B2B services pilot DPA, both based on real (anonymized) 2026 founder deals.
@@ -169,7 +169,7 @@ Result: 24 hours from "I should run the test" to a scored result you can act on.
### 6. The "First 10 Customers" Airtable tracker
-The Airtable base from [Chapter 5.4](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/). Pre-filled columns - Name, Company, Bucket, Loom sent, Reply, Demo, DPA sent, Deposit - with color-coded bucket pills (champion / hot / warm / cold) and date stamps on every progress column. Filters: "Replied this week," "Demo this week," "Pilot landed this month."
+The Airtable base from [Chapter 5.7](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/). Pre-filled columns - Name, Company, Bucket, Loom sent, Reply, Demo, DPA sent, Deposit - with color-coded bucket pills (champion / hot / warm / cold) and date stamps on every progress column. Filters: "Replied this week," "Demo this week," "Pilot landed this month."
diff --git a/content/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/index.md b/content/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/index.md
index ddd5faad0..0f597768e 100644
--- a/content/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/index.md
@@ -1,5 +1,5 @@
---
-title: "5.3a · Build Your 50-Name Network List"
+title: "5.3 · Build Your 50-Name Network List"
description: "Build a 50-name list of people who already know you and sort them into 4 outreach buckets."
date: 2026-07-07
draft: false
@@ -15,17 +15,25 @@ tags:
- non-technical-founder
- first-paying-customer
categories: ["Founders"]
+cover_image: cover.png
+metatags:
+ image: cover.png
+ og_title: "5.3 · Build Your 50-Name Network List"
+ og_description: "Sort 50 names into 4 outreach buckets so you know exactly who to message first. Lesson 5.3 of the From Idea to First Paying Customer course."
+cover_image_alt: "JetThoughts course cover for Lesson 5.3 - the 50-name network list sorted into 4 outreach buckets"
canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/"
related_posts: false
---
-> **Module 5 · Lesson 5.3a · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 5 · Lesson 5.3 · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
> **Input:** must-have-user persona + 1 named segment from [Chapter 5.1](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/)
>
> **Output:** 50 names sorted into 4 outreach buckets
>
-> **Progress:** M5 · 3a of 7 · Results so far: must-have segment + channel commitment
+> **Progress:** M5 · 3 of 7 · Results so far: your first users answered the 40% test (5.1) - this page builds the 50-name list for the first sales push
+
+> **TL;DR:** Build a 50-name list from people who already know you, sorted into 4 buckets - champions, hot, warm, cold. Lenny Rachitsky's research on fast-growing B2B startups found the personal network was the number-one source of first customers. One focused sitting.
---
@@ -35,7 +43,7 @@ After this lesson you will be able to: **sort 50 names into 4 outreach buckets s
---
-In 2021, Lenny Rachitsky asked 21 of the fastest-growing B2B companies (Figma, Stripe, Slack, Notion) where their first 10 customers came from. [The answer](https://www.lennysnewsletter.com/p/how-todays-fastest-growing-b2b-businesses): ~60% from personal network, ~35% from cold outbound, only 5% from inbound or launch events.
+Lenny Rachitsky asked today's fastest-growing B2B companies (Figma, Stripe, Slack, Notion among them) where their first 10 customers came from. [The answer](https://www.lennysnewsletter.com/p/how-todays-fastest-growing-b2b-businesses): the personal network came first for nearly every company, cold outbound was the recurring second theme, and inbound barely registered at that stage.
You are not asking friends to buy. You are asking them to be first to try something that solves a problem they already have, at a steep discount, while you fix the rough edges they catch.
@@ -55,8 +63,8 @@ Open a Google Sheet. Six columns: Name, Company, Role, Bucket, Relationship stre
> | Count | What this means | Your path |
> |---|---|---|
> | **30+** | Standard warm motion works. | Continue below. |
-> | **15-29** | Reduced warm motion. Build smaller buckets: 2 champions + 5 hot + 8 warm + 5 cold. You'll need cold outbound ([Ch 5.5](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/)) in parallel. |
-> | **Under 15** | Your network doesn't contain the ICP segment. | Skip to [Ch 5.5](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) cold outbound. |
+> | **15-29** | Reduced warm motion. Build smaller buckets: 2 champions + 5 hot + 8 warm + 5 cold. You'll need cold outbound ([Ch 5.7](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/)) in parallel. |
+> | **Under 15** | Your network doesn't contain the ICP segment. | Skip to [Ch 5.7](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) cold outbound. |
---
@@ -70,7 +78,7 @@ Open a Google Sheet. Six columns: Name, Company, Role, Bucket, Relationship stre
---
-**If this fails: your network is under 15 names after filtering.** **Why:** your must-have segment isn't represented in your professional network. **Fix:** skip to [Ch 5.5 cold outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/). Use community fallbacks (Indie Hackers, sector Slack, Reddit) as warm-cold hybrid messages.
+**If this fails: your network is under 15 names after filtering.** **Why:** your must-have segment isn't represented in your professional network. **Fix:** skip to [Ch 5.7 cold outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/). Use community fallbacks (Indie Hackers, sector Slack, Reddit) as warm-cold hybrid messages.
---
@@ -80,12 +88,14 @@ Count your champions out loud. That's the number of people who've already told y
> **Done:** 50 names sorted into 4 buckets, champions identified.
>
-> **You have now:** must-have segment (5.1) + channel commitment (5.2) + sorted 50-name list (5.3a). The message is next.
+> **You have now:** must-have segment (5.1) + your sorted 50-name list (5.3), plus a channel commitment if you took the optional 5.2 detour. The message is next.
>
-> **Next:** [5.3b · Write the Outreach Message](/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/) - turns your bucket list into 4 message templates with a recorded Loom.
+> **Next:** [5.4 · Write the Outreach Message](/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/) - turns your bucket list into 4 message templates with a recorded Loom.
>
> **If blocked:** see "If this fails" above.
---
-*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) free curriculum.*
+*See it in action: [Module 5 walkthrough: Mia gets paid](/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/)*
+
+*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/index.md b/content/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/index.md
index b6a3cd0ee..6731f8f08 100644
--- a/content/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/index.md
@@ -1,5 +1,5 @@
---
-title: "5.3b · Write the Outreach Message"
+title: "5.4 · Write the Outreach Message"
description: "The 4-part message template that turns your 50-name list into warm outreach, plus the 90-second Loom script."
date: 2026-07-07
draft: false
@@ -15,21 +15,29 @@ tags:
- non-technical-founder
- first-paying-customer
categories: ["Founders"]
+cover_image: cover.png
+metatags:
+ image: cover.png
+ og_title: "5.4 · Write the Outreach Message"
+ og_description: "4 outreach message variants (one per bucket) plus a 90-second Loom that gets replies. Lesson 5.4 of the From Idea to First Paying Customer course."
+cover_image_alt: "JetThoughts course cover for Lesson 5.4 - the 4-part outreach message and Loom"
canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/"
related_posts: false
---
-> **Module 5 · Lesson 5.3b · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 5 · Lesson 5.4 · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
-> **Input:** a 50-name list sorted into 4 buckets from [Lesson 5.3a](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/)
+> **Input:** a 50-name list sorted into 4 buckets from [Lesson 5.3](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/)
>
> **Output:** 4 message templates (one per bucket) + one 90-second Loom recording
>
-> **Progress:** M5 · 3b of 7 · Results so far: must-have segment + channel + sorted list
+> **Progress:** M5 · 4 of 7 · Results so far: 50 names in 4 buckets (5.3) - this page writes the 4 messages
+
+> **TL;DR:** One 4-part message with a different opener per bucket, plus one 90-second [Loom](https://www.loom.com) (a screen-recording tool - record your screen and voice, share a link). Keep it to 5-7 sentences. "Quick chat?" gets zero replies; a specific reference plus a Loom gets the meeting.
---
-The message most founders write first says "quick chat?" and gets zero replies. The message that works is 5-7 sentences with one specific reference, one line on the problem, and a Loom.
+The instinctive first message - "quick chat?" - gets zero replies. The message that works is 5-7 sentences with one specific reference, one line on the problem, and a Loom.
After this lesson you will be able to: **write 4 outreach message variants (one per bucket) and record a 90-second Loom that gets replies.**
@@ -44,13 +52,13 @@ Every message follows the same 4-part structure. What changes by bucket is the o
| **Warm** | "Hey [name], have not caught up since [the last specific touchpoint]. Working on something I think you might have a take on." |
| **Cold** | "Hey [name], a true one-line reference ('we were both in the Acme batch')." |
-If no real reference exists for a cold-bucket name, move them to [Ch 5.5 cold outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) instead.
+If no real reference exists for a cold-bucket name, move them to [Ch 5.7 cold outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) instead.
**Part 2: One line on the problem, in their language.** Use the verbatim Q3 answers from your [Chapter 5.1 survey](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/). "I am building a tool that lets B2B marketers run an end-to-end attribution model without an analyst."
**Part 3: A Loom video, not a paragraph.** Record one 90-second Loom. The free tier covers this batch. Show your product in 60 seconds, you on camera for the other 30. The Loom script comes directly from your Ch 5.1 verbatims. Read the Q2-Q3 quotes aloud, then point at the product feature that addresses the pain they describe.
-**Part 4: A specific ask.** "15 minutes to walk you through it and see if it solves [the problem]? Open to a paid pilot if it does. Calendly: [link]." The "paid pilot" teaser is load-bearing. Full mechanic lives in [5.4](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/).
+**Part 4: A specific ask.** "15 minutes to walk you through it and see if it solves [the problem]? Open to a paid pilot if it does. Calendly: [link]." The "paid pilot" teaser is load-bearing. Full mechanic lives in [5.6](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/).
**Total length:** 5-7 sentences. Anything longer and the recipient skims and forgets.
@@ -58,7 +66,7 @@ If no real reference exists for a cold-bucket name, move them to [Ch 5.5 cold ou
> **Write:**
>
-> 1. Open the Google Sheet from 5.3a. Write one opener for your #1 champion. Reference the exact thing they complained about.
+> 1. Open the Google Sheet from 5.3. Write one opener for your #1 champion. Reference the exact thing they complained about.
> 2. Copy the Part 2 line from your Ch 5.1 survey verbatims. Do not rewrite in your own voice.
> 3. Record one 90-second Loom: 60 seconds product, 30 seconds you on camera. Use the Ch 5.1 verbatims as your script.
> 4. Fill in Part 4 with your Calendly link.
@@ -69,7 +77,7 @@ If no real reference exists for a cold-bucket name, move them to [Ch 5.5 cold ou
**If this fails: the message still reads generic after 2 rewrites.** **Why:** you're writing in your marketing voice, not your Ch 5.1 verbatim quotes. **Fix:** paste the exact Q3 answers from your survey into Part 2. If the words are not theirs, swap until they are.
-**If this fails: you can't find a real reference for a cold-bucket name.** **Why:** they should not be in your cold bucket. **Fix:** move them to [Ch 5.5](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) cold outbound. The playbook there is designed for zero-context outreach.
+**If this fails: you can't find a real reference for a cold-bucket name.** **Why:** they should not be in your cold bucket. **Fix:** move them to [Ch 5.7](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) cold outbound. The playbook there is designed for zero-context outreach.
---
@@ -79,12 +87,14 @@ Read your champion opener aloud to yourself. If you wouldn't send it to that per
> **Done:** 4 message templates written and one 90-second Loom recorded.
>
-> **You have now:** sorted 50-name list (5.3a) + 4 message templates + Loom (5.3b). Time to send.
+> **You have now:** sorted 50-name list (5.3) + 4 message templates + Loom (5.4). Time to send.
>
-> **Next:** [5.3c · Send, Track, and Read the Replies](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/) - sends your messages in the right order and teaches you to read the replies.
+> **Next:** [5.5 · Send, Track, and Read the Replies](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/) - sends your messages in the right order and teaches you to read the replies.
>
> **If blocked:** see "If this fails" above.
---
-*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) free curriculum.*
+*See it in action: [Module 5 walkthrough: Mia gets paid](/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/)*
+
+*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/index.md b/content/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/index.md
index 8d823754a..7afb70ce3 100644
--- a/content/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/index.md
@@ -1,5 +1,5 @@
---
-title: "5.3c · Send, Track, and Read the Replies"
+title: "5.5 · Send, Track, and Read the Replies"
description: "Send your 50 outreach messages in the right order, track the replies, and diagnose what the responses tell you."
date: 2026-07-07
draft: false
@@ -15,17 +15,25 @@ tags:
- non-technical-founder
- first-paying-customer
categories: ["Founders"]
+cover_image: cover.png
+metatags:
+ image: cover.png
+ og_title: "5.5 · Send, Track, and Read the Replies"
+ og_description: "Send 50 messages in the right sequence, track replies in one spreadsheet, and diagnose what a no actually means. Lesson 5.5 of the From Idea to First Paying Customer course."
+cover_image_alt: "JetThoughts course cover for Lesson 5.5 - send, track, and read the replies"
canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/"
related_posts: false
---
-> **Module 5 · Lesson 5.3c · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 5 · Lesson 5.5 · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
-> **Input:** 4 message templates + Loom from [Lesson 5.3b](/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/)
+> **Input:** 4 message templates + Loom from [Lesson 5.4](/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/)
>
> **Output:** 50 messages sent, replies tracked, "no" responses diagnosed
>
-> **Progress:** M5 · 3c of 7 · Results so far: must-have segment + channel + sorted list + message templates + Loom
+> **Progress:** M5 · 5 of 7 · Results so far: messages written (5.4) - this page sends, tracks, and reads the replies
+
+> **TL;DR:** Send champions first, cold last, and track every reply in your Sheet. Expect 15-25 replies from 50 messages. A "no" from a cold name is noise; a "no" from a champion is the most useful feedback in this course - always ask why.
---
@@ -41,7 +49,7 @@ The send sequence in one glance:
2. Send the 15 warm messages a day or two later.
3. Send the 20 cold messages once the first replies are in.
-You will hear back from 15-25 of the 50 messages once replies settle. A 30-50% response rate is normal on a properly built personal-network list. It is the highest response rate you will ever see as a founder.
+You will hear back from 15-25 of the 50 messages once replies settle. Expect far more replies than any cold list will ever give you - these are people who know you. It is the warmest outreach you will run.
Add four tracking columns to your Sheet: Reply received (date), Reply sentiment (yes/maybe/no/silent), Demo booked (date), Pilot proposed (yes/no).
@@ -68,24 +76,26 @@ A "no" from a cold-bucket name is a non-event. They were never the right name. M
---
-**If this fails: you get fewer than 5 replies.** **Why:** your openers aren't specific enough, or your network is too small for warm motion. **Fix:** tighten the opener on your next 5 messages. If the next 5 still produce under 2 replies, your network is exhausted. Move to [Ch 5.5 cold outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/).
+**If this fails: you get fewer than 5 replies.** **Why:** your openers aren't specific enough, or your network is too small for warm motion. **Fix:** tighten the opener on your next 5 messages. If the next 5 still produce under 2 replies, your network is exhausted. Move to [Ch 5.7 cold outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/).
**If this fails: a champion says no.** **Why:** the problem moved, the buying motion is wrong, or you missed the brief. **Fix:** reply with a single question from the table above. A "no" from a champion is the most expensive feedback you'll get all year. Extract the signal before you move on.
---
-A "no" from cold is noise. A "no" from a champion is the single most useful piece of feedback in this course. Always reply. Always ask why.
+So when a champion says no, reply and ask why - that answer is worth more than the sale.
---
> **Done:** 50 messages sent, replies tracked, "no" responses diagnosed.
>
-> **You have now:** warm-network outreach complete (5.3a/b/c). Your first paid pilots are one conversation away.
+> **You have now:** warm-network outreach complete (5.3-5.5). Your first paid pilots are one conversation away.
>
-> **Next:** [5.4 · Charge Before You Ship: The Paid Pilot Contract](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/) - the one-page DPA and Stripe deposit that converts a demo into a signed pilot.
+> **Next:** [5.6 · Charge Before You Ship: The Paid Pilot Contract](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/) - the one-page DPA and Stripe deposit that converts a demo into a signed pilot.
>
-> **If blocked:** see "If this fails" above. If your warm network produced fewer than 3 demos, move to [Ch 5.5](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) cold outbound in parallel, not sequentially.
+> **If blocked:** see "If this fails" above. If your warm network produced fewer than 3 demos, move to [Ch 5.7](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) cold outbound in parallel, not sequentially.
---
-*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) free curriculum.*
+*See it in action: [Module 5 walkthrough: Mia gets paid](/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/)*
+
+*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/five-tech-words-stop-nodding-at/index.md b/content/course/tech-for-non-technical-founders-2026/five-tech-words-stop-nodding-at/index.md
index bbef5aa96..3fc397536 100644
--- a/content/course/tech-for-non-technical-founders-2026/five-tech-words-stop-nodding-at/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/five-tech-words-stop-nodding-at/index.md
@@ -156,10 +156,10 @@ The five words above are dev-shop jargon - vocabulary you'll hit in Modules 4-5
| **ICP** | Ideal Customer Profile - the specific kind of person your hypothesis names | Ch 1.1, 2.3 |
| **PMF** | Product-Market Fit - the survey question "would you be very disappointed if you could no longer use this?" 40%+ "very disappointed" = signal | Ch 5.1 |
| **JTBD** | Jobs To Be Done - what a customer "hires" your product to do (instead of feature list) | Ch 3.1, 3.2 |
-| **MRR** / **ARR** | Monthly / Annual Recurring Revenue - what one customer pays per month or year | Ch 1.1, 5.4 |
-| **ACV** | Annual Contract Value - what one customer pays in year one (deposit math is 10-30% of ACV) | Ch 5.4 |
-| **CAC** / **LTV** | Customer Acquisition Cost / Lifetime Value - what you spend to land one customer vs what they pay you over their lifetime | Ch 5.2, 5.4 |
-| **DPA** | Design Partner Agreement - a one-page contract where a customer pays a deposit to test your product as a co-design partner | Ch 5.4 |
+| **MRR** / **ARR** | Monthly / Annual Recurring Revenue - what one customer pays per month or year | Ch 1.1, 5.6 |
+| **ACV** | Annual Contract Value - what one customer pays in year one (deposit math is 10-30% of ACV) | Ch 5.6 |
+| **CAC** / **LTV** | Customer Acquisition Cost / Lifetime Value - what you spend to land one customer vs what they pay you over their lifetime | Ch 5.2, 5.6 |
+| **DPA** | Design Partner Agreement - a one-page contract where a customer pays a deposit to test your product as a co-design partner | Ch 5.6 |
| **SOW** | Statement of Work - the contract that defines what an agency is paid to deliver | _index, rescue chapters |
| **PRD** / **Vibe PRD** | Product Requirements Document - the "Vibe" version is a one-pager an AI builder can act on, not a 30-page spec | Ch 3.1 |
| **TAM** / **SAM** / **SOM** | Total / Serviceable / Serviceable-Obtainable Market - investor-pitch math, not builder math | _index pitch sections only |
@@ -169,7 +169,7 @@ The five words above are dev-shop jargon - vocabulary you'll hit in Modules 4-5
| **Unit economics** | Revenue per customer minus cost to serve per customer - whether the math works at scale | Ch 1.1 Money lens |
| **Runway** | Months of cash until you must show paying customers or close the company | Ch 4.1 Q3 |
| **SWOT / PESTEL / Porter's Five Forces** | Three classic strategy-school checklists - VenturusAI runs all three on your hypothesis | Ch 1.1 sidebar |
-| **Wizard of Oz** | A no-code pattern - customer thinks software is running, but you do the work by hand behind the scenes to test demand before building | Ch 4.3a Concierge MVP |
+| **Wizard of Oz** | A no-code pattern - customer thinks software is running, but you do the work by hand behind the scenes to test demand before building | Ch 4.3 Concierge MVP |
## What to do tomorrow
diff --git a/content/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/index.md b/content/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/index.md
index be3474688..bbe9d6bc7 100644
--- a/content/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/index.md
@@ -90,7 +90,7 @@ Score each lens 1-5. Be honest - this is for you, not an investor deck.
> 2. Fill each blank with the most specific noun you can. If a blank says "small businesses," rewrite it until it names one person in one industry.
> 3. Score your sentence using the four lenses above.
> 4. **✅ Success check:** total ≥14/20 (or ≥11/15 if Money is blank) AND no lens below 2.
-> 5. Save the sentence to a Google Doc titled `Founding Hypothesis - [today's date]`. You'll paste it verbatim into Lessons 1.2, 1.4, and 1.5. Module 2 uses it too - to choose who you interview and what you ask about - but you never read it to an interviewee.
+> 5. Save the sentence to a Google Doc titled `Founding Hypothesis - [today's date]`, inside a new Google Drive folder called `Founder OS` - every module adds an artifact to that folder, and by the course's end it is your evidence pack. You'll paste it verbatim into Lessons 1.2, 1.4, and 1.5. Module 2 uses it too - to choose who you interview and what you ask about - but you never read it to an interviewee.
---
diff --git a/content/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/index.md b/content/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/index.md
index cac9ab9d3..d8b1d955e 100644
--- a/content/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/index.md
@@ -29,11 +29,13 @@ canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2
related_posts: false
---
-> **Module 4 · Step 2 of 4** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 4 · Lesson 4.2 · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
> **Input:** a build-path decision from Chapter 4.1 (self-serve or hire)
>
> **Output:** a Day-1 audit confirming you own your code, cloud, and domain before the build starts (or a recovery plan if you don't)
+>
+> **Progress:** M4 · 2 of 5 · Results so far: build path chosen (4.1) - this page locks ownership before anything gets built
> **TL;DR:** Before you hire anyone, run this 12-item audit. It takes 45 minutes. If you skip it, the story below is how it ends: the founder who spent 14 months before discovering the AWS root password was in someone else's Gmail.
@@ -43,7 +45,7 @@ related_posts: false
> 2. **Lovable + Supabase + Stripe**: signed up with your personal email, billed to your card. (Not a co-founder's, not a friend's.)
> 3. **Domain (if purchased)**: registered to your name in your registrar account.
> 4. **No shared admin passwords**: only you have the master password to each.
-> 5. **2FA on all four** (GitHub, Supabase, Stripe, domain registrar): turned on.
+> 5. **2FA on all four** (GitHub, Supabase, Stripe, domain registrar): turned on. 2FA (two-factor authentication) is the 6-digit code your phone shows at login, a second proof on top of your password.
>
> Pass all 5? You can skim the rest of the chapter as a future reference. Fail any? Fix that one before continuing - the 12-item audit below is the deeper version.
@@ -53,7 +55,7 @@ Here's what happens if you skip it. A founder we saw last year: fourteen months
*Ownership*: who controls the GitHub org, the AWS root account, the domain registrar, and the prod database. A Day-1 audit means you can switch contractors Tuesday without losing access to your own codebase Wednesday.
-Open the AWS console. Top-right corner. Click your account name. Read the email address on the root user. Whose inbox does that land in tonight?
+Open the AWS console and click your account name in the top-right corner. Read the email address on the root user. Whose inbox does that land in tonight?
## The 2026 credential trap looks different
@@ -67,13 +69,13 @@ The financial damage is rarely the headline number on the contractor invoice. It
## What good looks like vs what bad looks like
-Every item rhymes the same way when it passes: an email on a domain you control, billing on a card you own, MFA on a phone in your pocket, and a password in a vault you can read. Failure rhymes too: somebody else's email, somebody else's card, and "let me ask Marcus" as the answer to "who can rotate this?"
+Every item rhymes the same way when it passes: an email on a domain you control, billing on a card you own, MFA (the same two-factor login code) on a phone in your pocket, and a password in a vault you can read. Failure rhymes too: somebody else's email, somebody else's card, and "let me ask Marcus" as the answer to "who can rotate this?"
Three pairs that come up most often in ownership audits.
**Item #4 - AWS root account email**
-> Bad: Root email is `aws@bigdevshop.com`. The bill goes to their AmEx ending 4421. You have an IAM user but have never logged in as root.
+> Bad: Root email is `aws@bigdevshop.com`. The bill goes to their AmEx ending 4421. You have an IAM user (a limited-permission login, not the all-powerful root account) but have never logged in as root.
> Good: Root email is `aws@mycompany.com`. The password is in your 1Password. MFA is on your phone with backup codes in your office safe. Bill goes to your company card.
If the contractor controls the root email, AWS support will treat them as the account holder, not you. The incorporation paperwork in your filing cabinet does not matter to AWS until support has worked through their recovery process - which takes 3-5 business days after you have proven who you are.
@@ -84,6 +86,7 @@ If the contractor controls the root email, AWS support will treat them as the ac
> Bad: "Marcus has it. Slack him and he can DM it to you."
> Good: "I opened AWS Secrets Manager just now and read it myself. I rotated it once in March when we offboarded the previous DBA."
+
The Marcus answer means you have a single point of failure. It does not matter whether Marcus is honest, kind, or available - one person holding the prod DB password is one person away from a production outage you cannot fix. Firing Marcus does not fix it. Putting the credential in a store you administer, with Marcus pulling read access from there, does.
**Item #10 - Domain registrar**
@@ -97,12 +100,12 @@ A domain transfer is the slowest recovery on the list. [ICANN's transfer policy]
Those three pairs anchor the pattern; the table below is the fill-in-the-blank version - 12 items, the exact pass criterion for each, the recovery steps when one fails. The full audit lives at the [GitHub / AWS / Database Ownership Checklist](/course/tech-for-non-technical-founders-2026/ownership-checklist/).
-> **Acronyms in the table below:** IAM = Identity and Access Management (AWS's user-permissions system, separate from the root account). MFA = Multi-Factor Authentication (the 6-digit code your phone shows when you log in - a second proof beyond your password). WHOIS = the public registry that shows who legally owns a domain. ICANN = the global body that enforces domain-transfer rules (the source of the 14-day wait if your registrar lock isn't released).
+> **Acronyms in the table below:** IAM = Identity and Access Management (AWS's user-permissions system, separate from the root account). MFA = Multi-Factor Authentication (the 6-digit code your phone shows when you log in - a second proof beyond your password). WHOIS = the public registry that shows who legally owns a domain. ICANN = the global body that enforces domain-transfer rules (the source of the 5-day transfer-approval window and the 60-day post-registration lock). DNS = Domain Name System (the address book that points your domain at your servers; the "A record" is the one line that says which server answers).
| Zone | Item | Pass Criterion |
|---|---|---|
| **Code** | GitHub org owner | Your company email, not the agency's |
-| | Repo collaborators | Can be removed by you alone, without permission |
+| | Repo (code repository) collaborators | Can be removed by you alone, without permission |
| | Branch protection on main | Enabled and you can override in an emergency |
| **Cloud** | AWS root account email | Sits on a domain you control |
| | Billing card | Yours and you can download every invoice yourself |
@@ -114,31 +117,31 @@ Those three pairs anchor the pattern; the table below is the fill-in-the-blank v
| | DNS provider | Logged in under your account with MFA, ready to add an A record now |
| | Third-party API keys | (Stripe, SendGrid, Twilio, OpenAI, Plaid) on your account, your card |
-Two of those twelve are existential. AWS root email controls whether a contractor can lock you out in ten minutes. Domain registrar turns into a 14-day ICANN-mandated wait if someone else will not release the auth code. The other ten matter; these two end the company if they go wrong.
+Two of those twelve are existential. AWS root email controls whether a contractor can lock you out in ten minutes. Domain registrar turns into a 14-day practical buffer (approval itself takes about five days; the 60-day post-registration lock is the ICANN rule) if someone else will not release the auth code. The other ten matter; these two end the company if they go wrong.
```mermaid
%%{init: {'theme':'base', 'themeVariables': {'fontFamily':'Caveat, Patrick Hand, cursive', 'primaryColor':'#f5f5f5', 'primaryBorderColor':'#666', 'lineColor':'#333', 'primaryTextColor':'#1a1a1a'}}}%%
flowchart TD
Start(["Friday afternoon. Alone.
Credit card + Notion doc."])
- Start --> Code{Code: Are you
GitHub org Owner?}
- Code -->|Yes| Cloud{Cloud: Is the AWS
root email yours?}
+ Start --> Code["Code: Are you
GitHub org Owner?"]
+ Code -->|Yes| Cloud["Cloud: Is the AWS
root email yours?"]
Code -->|No| FixCode[Slack the lead engineer.
Self-serve org transfer]
- Cloud -->|Yes, with MFA| Sec{Secrets: Can you read
the prod DB password
tonight without asking?}
+ Cloud -->|Yes, with MFA| Sec["Secrets: can you read the prod
DB password without asking?"]
Cloud -->|No| FixCloud[Self-serve email change
or 3-5 day AWS support
recovery with corp docs]
- Sec -->|Yes, from your vault| Dom{Domain: Does WHOIS
show your name +
renewal email?}
+ Sec -->|Yes, from your vault| Dom["Domain: WHOIS shows
your name + email?"]
Sec -->|"'Marcus has it'"| FixSec[Set up Secrets Manager
or 1Password vault tonight.
Migrate this sprint]
Dom -->|Yes, on your card| Pass[Audit clean.
Quarterly recurring block.
Email investor / board.]
- Dom -->|No| FixDom[Initiate registrar transfer.
Budget 14 days minimum.
Escalate to ICANN if blocked]
+ Dom -->|No| FixDom[Initiate registrar transfer.
Budget 14 days as a practical buffer.
Escalate to ICANN if blocked]
FixCode --> Recovery[Recovery plan
started this Friday]
FixCloud --> Recovery
FixSec --> Recovery
FixDom --> Recovery
- Recovery --> Escalate{Did the contractor
cooperate within 7 days
code / 14 days cloud /
auth code at all?}
+ Recovery --> Escalate["Contractor cooperated within
7 days code / 14 days cloud?"]
Escalate -->|Yes| Pass
Escalate -->|No| Lawyer[Retain lawyer.
$2K-$5K beats
a stalled checkout]
@@ -192,16 +195,16 @@ Ownership audit done right means no Marcus stands between you and a 9pm Tuesday
- Will Larson (via First Round Review), [Engineering leadership anti-patterns from Stripe, Uber, Carta](https://review.firstround.com/unexpected-anti-patterns-for-engineering-leaders-lessons-from-stripe-uber-carta/) - on ownership and accountability in engineering teams, including who holds the keys to production.
- AWS, [Reset a lost or forgotten root user password](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_passwords_change-root.html) - the support process and timeline if you need to recover a root account where someone else controls the email.
-> **Done when:** All 12 items on the ownership checklist are audited, failures are documented, and a recovery plan exists for each failure.
-> **Next click:** [4.3a · The Self-Serve MVP Stack: Tools & Setup](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/)
-> **If blocked:** If the AWS root email belongs to someone else and they won't cooperate, start the AWS support recovery process immediately (3-5 business days). Do not build on an account you don't own.
-
-> **Case Study: Tomas & Mia**
+> **Done:** All 12 items on the ownership checklist are audited, failures are documented, and a recovery plan exists for each failure.
>
-> **Tomas**: Audits all 12 items. Finds GitHub under his personal email (good), but no AWS account (creates one). Domain auto-renewing on a registrar he forgot the password to. Spends a Friday fixing all three. Now owns everything.
+> **You have now:** a quality-checked one-page brief (3.2) + a build-path decision (4.1) + a passed ownership audit, all saved in your `Founder OS` folder.
>
-> **Mia**: Audits all 12 items. Owns her domain (good), has personal GitHub but no org (creates one). No secrets manager - creates a 1Password vault. Spends a Friday afternoon. Now owns everything.
+> **Next:** [4.3 · The Self-Serve MVP Stack: Tools & Setup](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) - it builds on the accounts you now own.
+>
+> **If blocked:** If the AWS root email belongs to someone else and they won't cooperate, start the AWS support recovery process immediately (3-5 business days). Do not build on an account you don't own.
---
+*See it in action: [Module 4 walkthrough: Mia ships TutorMatch](/course/tech-for-non-technical-founders-2026/module-4-walkthrough-mia/)*
+
*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/index.md b/content/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/index.md
index d89a69518..ef1308ce8 100644
--- a/content/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/index.md
@@ -159,20 +159,20 @@ Most "Fractional CTO" listings on LinkedIn are either career CTOs in transition
### The Fractional CTO's first 4 weeks (parallel to your Module 5 first-paying-customer push)
-**Read this before you decide whether to hire** - it shows what the FCTO's first 4 weeks look like alongside your Module 5 work, so you can evaluate whether the timing makes sense and what you should expect from the engagement. The FCTO arrives the week one or two Ch 4.4 ceiling signals flip red (Ch 4.4 has a 5-signal scoreboard; "red" means a signal has been firing for 4+ weeks). They are NOT building features alongside you - they are reading what already shipped, naming what is about to break, and deciding salvage vs rebuild. The four-week onboarding runs in parallel to your Module 5 outreach so neither stream blocks the other:
+**Read this before you decide whether to hire** - it shows what the FCTO's first 4 weeks look like alongside your Module 5 work, so you can evaluate whether the timing makes sense and what you should expect from the engagement. The FCTO arrives the week one or two Ch 4.5 ceiling signals flip red (Ch 4.5 has a 5-signal scoreboard; "red" means a signal has been firing for 4+ weeks). They are NOT building features alongside you - they are reading what already shipped, naming what is about to break, and deciding salvage vs rebuild. The four-week onboarding runs in parallel to your Module 5 outreach so neither stream blocks the other:
| Week | Fractional CTO ships | You ship | Why parallel |
|------|----------------------|----------|--------------|
| **Week 1** | One-page architecture assessment in a shared Notion doc: "the shed is holding" OR "we need a house in 8 weeks." Names the highest-risk ceiling signal and the patch cost. | Send the 50-name personal-network outreach from Ch 5.3. | The architecture verdict is the input to your runway math; your outreach is the input to your revenue math. Both need to happen before week 5. |
| **Week 2** | Watch Supabase logs for RLS violations, slow queries, error rates as your first 10 invited interviewees create accounts. Patches one critical bug ONLY if data-corruption risk. | Book the first 2-3 demo calls from Ch 5.3 replies. Run them. | The Fractional CTO reads the signal of your first 10 real users; you read the signal of your first 2-3 demo prospects. |
-| **Week 3** | Ships ONE small hardening change to staging: faster dashboard query, fixed RLS policy, or webhook idempotency check. Not a feature - a stabilizer. | Send the first Ch 5.4 Design Partner Agreement to a hot lead. | One stabilization stream + one revenue stream = the founder gets paid pilots without the contractor getting tempted into feature work. |
-| **Week 4** | Friday-coaching call: "based on the first 4 weeks, here is the 90-day plan." Either (a) keep self-serve + Fractional CTO bridge for 3 more months, (b) hire a full engineer this month, or (c) rebuild from scratch on Rails/Django/Laravel in 8-12 weeks. | Close the first paid pilot from Ch 5.4. Stripe deposit clears. | Both streams converge: the Fractional CTO's 90-day plan and your first revenue are the two inputs to the next hire decision. |
+| **Week 3** | Ships ONE small hardening change to staging: faster dashboard query, fixed RLS policy, or webhook idempotency check. Not a feature - a stabilizer. | Send the first Ch 5.6 Design Partner Agreement to a hot lead. | One stabilization stream + one revenue stream = the founder gets paid pilots without the contractor getting tempted into feature work. |
+| **Week 4** | Friday-coaching call: "based on the first 4 weeks, here is the 90-day plan." Either (a) keep self-serve + Fractional CTO bridge for 3 more months, (b) hire a full engineer this month, or (c) rebuild from scratch on Rails/Django/Laravel in 8-12 weeks. | Close the first paid pilot from Ch 5.6. Stripe deposit clears. | Both streams converge: the Fractional CTO's 90-day plan and your first revenue are the two inputs to the next hire decision. |
The trap to avoid: the Fractional CTO who arrives in Week 1 and immediately recommends "rewrite the whole thing in Rails." That candidate sees vibe-coded MVPs as broken not salvageable; the recommendation usually means they want the bigger billable engagement. Push back: "what is the ONE ceiling signal we can patch in Supabase this week to give us 90 more days to decide?" A real Fractional CTO has the patch ready by Friday.
### The monthly architecture review habit (the one thing the Fractional CTO does every month)
-First Monday of every month, 60 minutes, the Fractional CTO and you read the Ch 4.4 5-signal scoreboard together. The standing agenda:
+First Monday of every month, 60 minutes, the Fractional CTO and you read the Ch 4.5 5-signal scoreboard together. The standing agenda:
1. Re-score the 5 signals against last 30 days of usage data, OpenAI invoice, support tickets, schema changes, and customer security/compliance asks. 20 minutes.
2. Compare to last month's score. Did any signal flip from green to yellow, or yellow to red? Did any flip back? 10 minutes.
diff --git a/content/course/tech-for-non-technical-founders-2026/how-this-course-works/index.md b/content/course/tech-for-non-technical-founders-2026/how-this-course-works/index.md
index ba5feca77..ef1ff1747 100644
--- a/content/course/tech-for-non-technical-founders-2026/how-this-course-works/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/how-this-course-works/index.md
@@ -109,8 +109,9 @@ The brief is the handoff document. It goes to Lovable, a hired developer, or a f
|---|---|---|
| 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 | Ship the MVP: Lovable + Supabase + Stripe | Lovable + Supabase + Stripe (free tiers) |
-| 4.4 | Spot the 5 ceiling signals that mean it's time to graduate beyond no-code | - |
+| 4.3 | Set up the stack and pre-flight rules: Lovable + Supabase + Stripe | Lovable + Supabase + Stripe (free tiers) |
+| 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 |
> **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.
@@ -118,16 +119,18 @@ The brief is the handoff document. It goes to Lovable, a hired developer, or a f
### Module 5 - First Paying Customer
**You have:** a live MVP at a real URL.
-**You walk away with:** one signed paid pilot ($500+ deposit) + a repeatable outbound channel.
+**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 | Pick one outreach channel and commit before scaling | Channel selection framework |
-| 5.3 | Convert warm personal network into first paid pilots | Personalized DMs |
-| 5.4 | 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 refundable deposit | DPA template + Stripe |
-| 5.5 | Go cold outbound: 30 filtered messages, book 1-2 pilots | LinkedIn Sales Navigator or manual |
+| 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 (free tier) |
+| 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 refundable deposit | DPA template + Stripe |
+| 5.7 (optional) | Go cold outbound: 30 filtered messages, book 1-2 pilots | LinkedIn Sales Navigator or manual |
**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.
@@ -171,7 +174,6 @@ These are the tools the course references - AI research tools, no-code builders,
| **Lovable / Bolt.new** | 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 |
| **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 |
-| **WorthBuild** | Auto-parses social media for leads, generates personalized outreach messages | After validation, setting up first-customer pipeline (Module 5) | Free tier |
@@ -187,7 +189,7 @@ Every module has a gate. If the data doesn't support your hypothesis, you stop a
| 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 + $500+ Stripe deposit received |
+| 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.
diff --git a/content/course/tech-for-non-technical-founders-2026/module-4-walkthrough-mia/index.md b/content/course/tech-for-non-technical-founders-2026/module-4-walkthrough-mia/index.md
new file mode 100644
index 000000000..5f6e30986
--- /dev/null
+++ b/content/course/tech-for-non-technical-founders-2026/module-4-walkthrough-mia/index.md
@@ -0,0 +1,61 @@
+---
+title: "Module 4 Walkthrough: Mia Ships TutorMatch"
+description: "Follow Mia through Module 4 as she routes herself to the self-serve path, locks ownership before building, and walks the four build phases from her one-page brief to a live MVP with real parents on it."
+date: 2026-07-10
+draft: false
+slug: module-4-walkthrough-mia
+---
+
+> **Module 4 walkthrough · Mia** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+>
+> *Illustrative composite based on patterns from real founder builds, not a single client story. Mia's earlier runs are in the [Module 1](/course/tech-for-non-technical-founders-2026/module-1-walkthrough-mia/), [Module 2](/course/tech-for-non-technical-founders-2026/module-2-walkthrough-mia/), and [Module 3](/course/tech-for-non-technical-founders-2026/module-3-walkthrough-mia/) walkthroughs.*
+
+Mia arrived at Module 4 with a quality-checked one-page brief and a strong opinion she hadn't examined: that a "real" marketplace needed a real engineering team. Module 4 exists to test opinions like that against a worksheet.
+
+---
+
+## [Lesson 4.1: Should You Hire?](/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/)
+
+The five questions took her twenty minutes. Q1, validation: ten interviews with eight strong signals, plus six founding members who had already paid $99 - yes, with receipts. Q2, backend weight: her v1 had no real-time anything, no background queues, no regulated data - a curated list, parent accounts, and one request button. Light. Q3 said runway was not forcing her hand. Q4 was the one she had to think about - a senior engineer for one architecture hour a month - until she remembered a former colleague who had offered exactly that over coffee. Q4 = yes, and the worksheet routed her to Path 2 - self-serve.
+
+The opinion didn't survive contact with her own answers. The agency quotes she had been collecting went into a folder named "later."
+
+---
+
+## [Lesson 4.2: Who Owns What](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/)
+
+The ownership audit was twenty minutes of green checkmarks - solo self-serve founders mostly pass by default, since every account gets created in their own name - with one exception. Her domain still lived inside the smoke-test site builder from Module 1, on a plan she could stop paying for at any moment. She transferred it to a registrar account in her own name the same evening and pointed it nowhere yet. The checklist's line stuck with her: the day you need the domain is the wrong day to discover who owns it.
+
+---
+
+## [Lessons 4.3 and 4.4: The Build](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/)
+
+Setup first: Lovable, Supabase, Stripe, all on her accounts, pre-flight rules read twice. Then she pasted Section 3 of her brief - the outcome-shaped one, with the hand-curated shortlist line - into Lovable, exactly as written in Module 3.
+
+The [four phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/) took her nine build evenings spread across ten calendar weeks - the part-time pace Chapter 4.4 tells you to plan for. The UI phase went fastest because the prototype had already settled the layout arguments: search by the kid's need, profiles with reviews, credentials, response time, and the session rate the fifth test parent had gone looking for. Auth was parent accounts with the same magic-link sign-in her brief specified. Stripe was the founding-member checkout she had been running manually since Module 1, now wired into the product. The deploy phase ended with her domain - the one she now owned - pointing at a live TutorMatch.
+
+The scare came from the AI audit prompt in the build rules. She pasted her Supabase table definitions and row-level security policy into Claude and asked whether a logged-in parent could read another parent's rows. The answer was yes - the policy she had accepted from a Lovable default checked that a user was signed in, not which user they were. One corrected policy later, the check came back clean. It was the cheapest security review she will ever run.
+
+She ended the module the way the lesson closes: fifteen hand-onboarded tutors, an invite email to her eleven waitlist parents and eight interviewees, and a weekly demo recording nobody asked her for yet.
+
+---
+
+## [Lesson 4.5: The Ceiling Check](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/)
+
+She read the five signals once, put a recurring monthly block on her calendar titled "ceiling check," and closed the tab. First run: scheduled for thirty days after launch. That is the whole lesson at this stage.
+
+---
+
+## What Mia Walked Away With at the End of Module 4
+
+- **A live MVP at a domain she owns**, built from her brief - every screen traceable to a parent quote, the session rate on the profile where the prototype said it belonged.
+- **Ownership locked before launch**: registrar, GitHub, Supabase, Stripe, all in her name. One domain transfer was the only fix the audit demanded.
+- **A build-path decision with a paper trail** - self-serve, chosen by worksheet answers instead of by the fear that "real products need agencies."
+- **One security hole caught on paper**: the row-level security fix from the AI audit prompt, before any parent's data was ever at risk.
+- **A seeded user base waiting**: fifteen tutors onboarded by hand, nineteen warm invitations out.
+
+**Next: [Module 5, where Mia finds out whether anyone would miss TutorMatch](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/)** - and turns the answer into her next ten customers.
+
+---
+
+*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) free curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/index.md b/content/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/index.md
new file mode 100644
index 000000000..da24c17d2
--- /dev/null
+++ b/content/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/index.md
@@ -0,0 +1,68 @@
+---
+title: "Module 5 Walkthrough: Mia Gets Paid"
+description: "Follow Mia through Module 5 as she runs the 40% test on her first users, works a 50-name warm list, and signs a group pilot with a deposit - the first money TutorMatch earns from someone who isn't a founding member."
+date: 2026-07-10
+draft: false
+slug: module-5-walkthrough-mia
+---
+
+> **Module 5 walkthrough · Mia** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+>
+> *Illustrative composite based on patterns from real founder builds, not a single client story. Mia's earlier runs: [Module 1](/course/tech-for-non-technical-founders-2026/module-1-walkthrough-mia/) · [Module 2](/course/tech-for-non-technical-founders-2026/module-2-walkthrough-mia/) · [Module 3](/course/tech-for-non-technical-founders-2026/module-3-walkthrough-mia/) · [Module 4](/course/tech-for-non-technical-founders-2026/module-4-walkthrough-mia/).*
+
+Mia entered Module 5 with a live product and a number that could embarrass her: nineteen invitations sent, and no idea whether anyone who clicked would actually miss TutorMatch if it disappeared. Her six founding members had paid for a promise back in Module 1 - pre-sold, face to face, before the product existed. Module 5 asks the harder question: what does the product earn from people who never made that early bet on Mia herself?
+
+---
+
+## [Lesson 5.1: The 40% Test](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/)
+
+Two weeks after the invites went out, she sent the one-question survey to everyone who had used the product: how would you feel if TutorMatch went away? Sixteen answered. Across all of them the "very disappointed" count landed at 6 of 16 - 38% - just under the bar, the kind of number that invites self-deception in both directions.
+
+The segment cut told the real story. Among parents of kids with learning differences - her interview cohort's profile - six of eleven said very disappointed: 55%. Among the five generic-tutoring parents who had wandered in from the waitlist: zero. The lesson's instruction held her still: below 40% overall is not a kill, it is a "wrong segment mixed in" signal. The must-have segment was narrow: parents who had already exhausted the local options and were still looking.
+
+She wrote the niche into the top of her operating doc and stopped apologizing for it.
+
+---
+
+## [Lesson 5.2: Channel Selection](/course/tech-for-non-technical-founders-2026/channel-selection-before-outbound/)
+
+Skipped, honestly. The lesson is optional for founders who already know where their buyers live, and Mia had known since Module 2: the learning-differences communities where her interviewees came from. She moved on.
+
+---
+
+## [Lessons 5.3-5.5: The Warm Fifty](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/)
+
+The 50-name list assembled itself faster than the Module 2 stranger list had, because this time she wasn't a stranger: eight interviewees who had asked to see the finished thing, eleven waitlist parents, her fifteen tutors - each of whom knew families - and the community connections she had built reading those groups for half a year. Four buckets, champions on top.
+
+The [messages](/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/) were one paragraph each, bucket by bucket, plus a 90-second Loom (a quick screen-recording video) of the search flow: type "dyslexia," see three vetted profiles, session rate visible. She [sent them in sequence](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/) over two weeks, champions first, tracked in the same spreadsheet shape she had used for interviews. Twenty-two replies. Nine demos. Her interviewees converted at the highest rate - they had co-designed the thing without knowing it.
+
+---
+
+## [Lesson 5.6: The Paid Pilot](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/)
+
+The champion bucket produced the surprise. One of her demo calls was with the organizer of a regional parent group for learning differences - a woman who had spent years fielding "does anyone know a good tutor?" posts. She didn't want one account. She wanted TutorMatch for her member families.
+
+Mia's first instinct was to say yes and figure out payment later, which is precisely the free-pilot trap the lesson opens with. Instead she adapted the one-page Design Partner Agreement: an annual group plan for twenty member families at $2,400 - modest next to the $70-$120 those families already pay tutors per single session - with a $600 refundable deposit (25% of year one, inside the lesson's 10-30% band) through a Stripe payment link before she lifted a finger on the group onboarding. The organizer signed the same week - people who have waited years for a solved problem don't haggle over a refundable deposit.
+
+The deposit cleared a few days later - a small number, but the first money TutorMatch had earned from someone who found Mia through the product rather than through her.
+
+---
+
+## [Lesson 5.7: Cold Outbound](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/)
+
+Unopened, deliberately. The warm fifty had produced a signed pilot and nine demos, and the lesson's own trigger conditions - list exhausted, replies dry - hadn't fired. She bookmarked it as the playbook for the month the warm well runs dry.
+
+---
+
+## What Mia Walked Away With at the End of Module 5
+
+- **A niche with numbers behind it**: 55% "very disappointed" in her learning-differences segment - and a written decision to stop chasing the other kind of parent.
+- **A signed Design Partner Agreement and a cleared deposit** - a pilot with a group organizer she met through the product, not through friends.
+- **A repeatable warm-outreach motion**: 50 names, 4 buckets, 22 replies, 9 demos, tracked in one spreadsheet.
+- **The complete Founder OS folder**: hypothesis, smoke-test data, validated problem statement, one-page brief, live MVP, and now a signed pilot - the evidence pack the course promised on page one.
+
+**Mia's run ends here.** From a sentence in a notebook to a stranger's money in five modules of work - with every artifact traceable back to something a real parent said. The [First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/) is what she runs from here.
+
+---
+
+*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) free curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/index.md b/content/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/index.md
index 758151bad..3158564d9 100644
--- a/content/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/index.md
@@ -1,7 +1,7 @@
---
title: "5.1 · Your First Customer Is Not a Marketing Problem"
aliases: ["/blog/must-have-segment-pmf-test/"]
-description: "Before spending a dollar on ads, run the Sean Ellis 40% test against your earliest users. The non-technical founder's pre-paid-traffic gut check."
+description: "Before you buy traffic, run the Sean Ellis 40% test against your earliest users. The non-technical founder's pre-paid-traffic gut check."
date: 2026-05-13
draft: false
course_chapter: true
@@ -23,30 +23,32 @@ cover_image: cover.png
metatags:
image: cover.png
og_title: "5.1 · Your First Customer Is Not a Marketing Problem"
- og_description: "Before spending a dollar on ads, run the Sean Ellis 40% test against your earliest users. The non-technical founder's pre-paid-traffic gut check."
+ og_description: "Before you buy traffic, run the Sean Ellis 40% test against your earliest users. The non-technical founder's pre-paid-traffic gut check."
cover_image_alt: "JetThoughts blog cover showing a Sean Ellis 40% gauge with a red threshold line separating product problem from must-have user"
canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/"
related_posts: false
---
-> **Module 5 · Step 1 of 5** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 5 · Lesson 5.1 · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
> **Input:** a live MVP + 10-30 users who touched it. **Don't have 10-30 yet?** Invite your Module 2 Mom Test interviewees + your [1.4 smoke-test email list](/course/tech-for-non-technical-founders-2026/smoke-test-landing-page-7-day-demand-test/) (typically 15-50 signups) to your staging URL as the warm seed. If under 10 users still touched it, run [Ch 2.4 outreach](/course/tech-for-non-technical-founders-2026/find-10-people-with-problem-outreach-2026/) for 10 more before re-attempting this survey.
>
> **Output:** a written must-have-user persona with 3 verbatim quotes and one named segment to target
+>
+> **Progress:** M5 · 1 of 7 · Results so far: live MVP with your first users on it (4.4) - this page tests whether they'd miss it before you spend on ads
-> **TL;DR:** Before spending a dollar on ads, survey your earliest users. If fewer than 40% would be "very disappointed" if your product vanished, you have a product problem, not a marketing problem.
+> **TL;DR:** Before you buy traffic, survey your earliest users. If fewer than 40% would be "very disappointed" if your product vanished, you have a product problem, not a marketing problem.
-Your Lovable MVP went live last month. Forty people from your beta list poked at it. The dashboard says 0.4% conversion on $4,200 of Meta ads, and the instinct says "scale the top of funnel."
+Here is the failure mode this lesson exists to prevent. A founder's Lovable MVP goes live. Forty people from a beta list poke at it. The dashboard says 0.4% conversion on $4,200 of Meta ads, and instinct says "scale the top of funnel."
-The dashboard will tell you the same thing it would have told you if you had called five of those forty users first: most never opened the app twice. The $4,200 bought you a number you could have gotten for free.
+The dashboard tells that founder what five phone calls would have said for free: most users never opened the app twice. You are two weeks and zero ad dollars away from that fork - this lesson is how you take the other path.
The real question after the MVP ships is whether the people who already touched it would notice if it vanished tomorrow. If less than 40% would be very disappointed, no amount of ad spend will turn that group into customers. Paid traffic does not fix a product problem; it routes more users into something they will not return to.
> **What your first-pass numbers will probably look like (and that is not a failure signal).** An idea-stage founder with 4-6 onramp users typically sees one of three patterns on the first survey run:
> - All "somewhat disappointed" or "not disappointed" → that segment is not must-have; do not scale it. Run more interviews before re-attempting.
-> - 2-3 "very disappointed" out of 6 → directional MAYBE. Almost certainly a sample-size problem, not a product problem; book 5-10 more users.
-> - 4+ "very disappointed" out of 6 → directional YES. Advance to M5.2 with the caveat above.
+> - 3-4 "very disappointed" out of 6 → directional MAYBE. Almost certainly a sample-size problem, not a product problem; book 5-10 more users.
+> - 5+ "very disappointed" out of 6 → directional STRONG YES. Advance to M5.3 with the caveat above.
>
> A 25-40% reading at small sample size is not a failure. It is the normal state of a brand-new product with a brand-new founder. The Sean Ellis test is calibrated for ≥ 20 respondents with months of usage; your first-pass run is a forecast, not a verdict. Treat looping back to M2.3 outreach for more user sessions as the default first-pass move, not a setback.
@@ -60,7 +62,7 @@ Sean Ellis ran growth at Dropbox, LogMeIn, and Eventbrite. While he was building
You just shipped your first Lovable MVP and 40 people from your beta list poked at it. The natural urge is to start collecting traction numbers immediately - surveys feel like a delay, ads feel like progress. And because you cannot read the codebase, "the conversion rate is 0.4%" sounds like a UX problem (a thing you can act on) instead of a product problem (a thing you cannot diagnose). Ad spend feels safer than going back into the build.
-The Twitter threads make it worse. On day 90 after launch, every thread is some growth marketer explaining that the founder of a now-public company spent $4M on Meta in the first six months. The threads do not mention that the founder ran the 40% test in week one and got 56% on a sample of 22.
+The Twitter threads make it worse. On day 90 after launch, every thread is some growth marketer explaining that the founder of a now-public company spent $4M on Meta in the first six months. The threads do not mention that the founder ran the 40% test in week one, cleared the bar, and then spent on ads.
Ask yourself the must-have rate before you ask anything else. The pattern across the burned-thousands-on-paid-ads stories is the same: a number that was never measured. Sometimes the rate is under 25% overall - genuine "no must-have user" territory. Sometimes one segment scores high and another scores low, but the ad targets the wrong half because the high-need segment is harder to reach. Knowing the number before the ad spend is the difference between an expensive lesson and a cheap one.
@@ -76,7 +78,7 @@ You need enough responses from people who have used your product recently to spo
- Your beta waitlist if it converted to active users.
- The trial list if you ran paid trials.
-If you only have ten users, that is fine. Sean Ellis has written that even ten responses are directional. Ten of ten "very disappointed" is a louder signal than 40 of 100. You are not running a peer-reviewed study; you are looking for a dividing line.
+If you only have ten users, that is fine. Treat anything under ten responses as directional only. Ten of ten "very disappointed" is a louder signal than 40 of 100. You are not running a peer-reviewed study; you are looking for a dividing line.
Strip out two groups before you send:
@@ -145,7 +147,7 @@ flowchart TD
A[Run the 5-question survey] --> B{Overall must-have %}
B -->|Under 25%| C[Stop. Product problem.
Talk to 5 'very disappointed' users.
Find what you missed.]
B -->|25-40%| D{Any segment over 40%?}
- B -->|Over 40%| E[You have a must-have user.
Chapter 5.2 outreach starts here.]
+ B -->|Over 40%| E[You have a must-have user.
Chapter 5.3 outreach starts here.]
D -->|Yes| F[Target that segment.
Rebuild the persona on those quotes.]
D -->|No| G[Refine the product first.
Re-run after the next release.]
classDef redbox fill:#fff5f5,stroke:#cc342d,stroke-width:2px;
@@ -161,7 +163,7 @@ flowchart TD
> **Sample under 10 respondents (special case):** segment-slice math does not work. Do NOT classify by 25-40% bands. Instead:
> - **0-2 "very disappointed"**: treat as directional NO. Book more user sessions before re-running.
> - **3-4 "very disappointed"**: directional MAYBE. Book 5-10 more users, re-run.
-> - **5+ "very disappointed" out of 6**: directional STRONG YES. Advance to M5.2 but caveat your channel decisions - the segment language is hypothesis, not verified.
+> - **5+ "very disappointed" out of 6**: directional STRONG YES. Advance to M5.3 but caveat your outreach decisions - the segment language is hypothesis, not verified.
## What "under 40%" actually means
@@ -169,7 +171,7 @@ Under 40% means you have a product problem, not a marketing problem, and the Q2-
| Pattern | Diagnostic | Fix | Re-entry point |
|---|---|---|---|
-| **You built for the wrong segment** | The product works, but the people you onboarded do not have the pain. Your Q5 slice shows: one segment is at 55%, the rest are at 5%. | Stop selling to the audience and start selling to the segment. | [Chapter 5.3a](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) personal-network outreach to the right segment. |
+| **You built for the wrong segment** | The product works, but the people you onboarded do not have the pain. Your Q5 slice shows: one segment is at 55%, the rest are at 5%. | Stop selling to the audience and start selling to the segment. | [Chapter 5.3](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) personal-network outreach to the right segment. |
| **You built the right thing, but it is not finished** | The Q3 verbatims are hedged ("it is nice to have," "I would use it if it had X"). The main benefit answers lack conviction. | Go back into the build and finish the thing. | Schedule a [Friday demo](/course/tech-for-non-technical-founders-2026/friday-demo-rule-founder-progress/) with the next release. |
| **The pain is real, but your product is not the relief** | The Q4 verbatims name a workaround that is already 80% of the job (a spreadsheet, an existing tool, a person they pay). | Either niche into the 20% the workaround does not cover, or pivot. | [Chapter 2.5](/course/tech-for-non-technical-founders-2026/mom-test-synthesis-build-pivot-kill/) validated-problem statement. |
| **The product solves the pain, but the workflow is too long** | Users say "very disappointed" but session logs show they bailed before the payoff. Funnel collapses between signup and the "30-minute save" moment. | UX cut, not a strategy pivot. Shorten the path to the first win. | Retest after shortening the funnel; re-run the 40% test after the next UX release. |
@@ -198,8 +200,8 @@ Under 40% means you have a product problem, not a marketing problem, and the Q2-
| **1** | Export your users CSV. Strip the friends-and-family and the never-returned users. Open Typeform or Tally. Type the five questions verbatim. | Typeform/Tally survey ready to send |
| **2** | Send the email to the list. Subject: *"Quick 90-second question about [product]"*. Re-send a few days later to non-openers. | 30-50% response rate expected |
| **3** | Export the responses CSV. Compute overall must-have % and per-segment must-have % (by job title and company size). | One-page scorekeeping: headline %, top segment %, three verbatim quotes |
-| **4** | Paste three Q2-Q3 verbatims from your top segment into a Google Doc. Review which segment hit 40%+ (or if none did). | Persona writeup ready for Chapter 5.2 or decision on pivot |
-| **5** | If above 40% in any segment, move to [Chapter 5.3a personal-network outreach](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/). If below 40% across all segments, book five "very disappointed" user calls and re-read [Chapter 2.1 Mom Test](/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/). | Decision made; next chapter unlocked OR product refinement scheduled |
+| **4** | Paste three Q2-Q3 verbatims from your top segment into a Google Doc. Review which segment hit 40%+ (or if none did). | Persona writeup ready for Chapter 5.3 or decision on pivot |
+| **5** | If above 40% in any segment, move to [Chapter 5.3 personal-network outreach](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/). If below 40% across all segments, book five "very disappointed" user calls and re-read [Chapter 2.1 Mom Test](/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/). | Decision made; next chapter unlocked OR product refinement scheduled |
The full survey template (the 5 questions in a Typeform-import-ready format, the per-segment scoring spreadsheet, and the persona-writeup template) ships in [the First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/).
@@ -214,16 +216,16 @@ Treat the answer as a stop sign rather than a market-research instrument. Under
- Rahul Vohra, [How Superhuman built an engine to find product-market fit](https://review.firstround.com/how-superhuman-built-an-engine-to-find-product-market-fit/) - the segment-isolation playbook layered on top of the 40% test.
- Rob Fitzpatrick, [*The Mom Test*](https://www.momtestbook.com/) - the pre-launch validation companion. Once your 40% test is above the line, the Mom Test questions are the ones you ask the 10 must-have users on their next call.
-> **Done when:** You have run the 5-question Sean Ellis survey, computed the overall and per-segment must-have %, and have 3 verbatim Q2-Q3 quotes from your top segment.
-> **Next click:** [5.2 · Choose Your Channel Before You Send One Message](/course/tech-for-non-technical-founders-2026/channel-selection-before-outbound/)
-> **If blocked:** If under 10 users responded, your sample is too small to read. Book 5-10 more user sessions using the Ch 2.3-2.4 outreach playbook and re-run the survey.
-
-> **Case Study: Tomas & Mia**
+> **Done:** you have run the 5-question Sean Ellis survey, computed the overall and per-segment must-have %, and have 3 verbatim Q2-Q3 quotes from your top segment.
>
-> **Tomas**: Runs the Sean Ellis survey on his 24 smoke-test signups. Segments by firm size: 50-150 employee firms score 45% "very disappointed" without it. 150-200 employee firms score 28% - they have in-house tools. Narrows to 50-150 employee firms.
+> **You have now:** a live MVP (4.4) + a written must-have-user persona with 3 verbatim quotes and one named segment (5.1). You know whether your earliest users would miss the product, and which segment to sell to - but you have not reached out to anyone yet.
>
-> **Mia**: Runs the Sean Ellis survey on her 21 smoke-test signups. Segments by child age: parents of kids 8-14 with dyslexia score 52% "very disappointed." Parents of kids 14+ score 31% - they've found workarounds. Narrows to parents of kids 8-14 with dyslexia/ADHD.
+> **Next:** the core path continues at [5.3 · Build Your 50-Name Network List](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) - it turns the named segment into the first 50 people you will message. If you are not sure where your buyers actually spend their time, read the optional [5.2 · channel selection](/course/tech-for-non-technical-founders-2026/channel-selection-before-outbound/) first.
+>
+> **If blocked:** if under 10 users responded, your sample is too small to read. Book 5-10 more user sessions using the Ch 2.3-2.4 outreach playbook and re-run the survey.
---
+*See it in action: [Module 5 walkthrough: Mia gets paid](/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/)*
+
*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/one-page-product-brief-vibe-prd/index.md b/content/course/tech-for-non-technical-founders-2026/one-page-product-brief-vibe-prd/index.md
index 478d9b748..7ce465f61 100644
--- a/content/course/tech-for-non-technical-founders-2026/one-page-product-brief-vibe-prd/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/one-page-product-brief-vibe-prd/index.md
@@ -143,7 +143,7 @@ The classic trap is writing a traditional PRD for a junior or an AI agent. The 5
## When a paid cohort course is worth it
-Drew Falkman runs ["Vibe Coding Data-Enabled AI Apps" on Maven](https://maven.com/), a multi-week live cohort (paid - check the course page for current pricing and format). The course teaches the same five-section Vibe PRD template, plus the Lovable + Supabase + Stripe + GitHub stack, plus live community and 1:1 instructor feedback.
+Drew Falkman runs "Vibe Coding Data-Enabled AI Apps" on Maven, a multi-week live cohort (paid - check the course page for current pricing and format). The course teaches the same five-section Vibe PRD template, plus the Lovable + Supabase + Stripe + GitHub stack, plus live community and 1:1 instructor feedback.
| Scenario | Maven cohort is worth it | This template is enough to start |
|---|---|---|
@@ -171,13 +171,13 @@ Skipping the brief and going straight into prompting is the most common way a no
You now have two validated artifacts: a one-page problem statement (from your Chapter 2.5 synthesis) and a one-page Vibe PRD (from this chapter). Two more steps before Lovable touches your brief:
1. **[Chapter 3.2 - Quality-check your brief: features to outcomes](/course/tech-for-non-technical-founders-2026/stop-specifying-features-start-outcomes/)** - stress-test Section 3 ("what you're building") by rewriting feature nouns as outcome-shaped job stories. This is the quality gate on the brief you just wrote, not a separate writing exercise.
-2. **[Chapter 4.1 - Should You Hire? The 2026 Decision Tree](/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/)** - a 5-question decision tree that routes you to one of 4 build paths (validate without code / self-serve / fractional CTO / hire). The default for a non-technical founder is self-serve ([Chapter 4.3a · Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) + [4.3b · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/)), but only after the decision gate confirms it's right for YOUR runway and YOUR problem. Chapter 4.1 explicitly requires the outcome-shaped brief from Chapter 3.2 as its input.
+2. **[Chapter 4.1 - Should You Hire? The 2026 Decision Tree](/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/)** - a 5-question decision tree that routes you to one of 4 build paths (validate without code / self-serve / fractional CTO / hire). The default for a non-technical founder is self-serve ([Chapter 4.3 · Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) + [4.4 · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/)), but only after the decision gate confirms it's right for YOUR runway and YOUR problem. Chapter 4.1 explicitly requires the outcome-shaped brief from Chapter 3.2 as its input.
A Vibe PRD is what's left when you remove everything an AI agent or a hired junior cannot act on by tomorrow morning.
## Further reading
-- Drew Falkman, [Vibe Coding Data-Enabled AI Apps on Maven](https://maven.com/) - the paid live cohort that teaches the Vibe PRD with instructor feedback. Recommended if accountability is your blocker.
+- Drew Falkman, "Vibe Coding Data-Enabled AI Apps" on Maven - the paid live cohort that teaches the Vibe PRD with instructor feedback. Recommended if accountability is your blocker.
- Marty Cagan, [Good Product Manager / Bad Product Manager](https://www.svpg.com/good-product-manager-bad-product-manager/) - the canonical essay on what a PRD is for. The Vibe PRD is the AI-era compression of the same shape.
- Marty Cagan, [Product vs Feature Teams](https://www.svpg.com/product-vs-feature-teams/) - why the brief shapes what gets built. The no-go list is the part feature teams ignore.
- Jake Knapp and John Zeratsky, [Foundation Sprint (Click, April 2025)](https://www.thesprintbook.com/foundation-sprint) - the 2-day version of the same artifact for teams that have 2 days. The Foundation Sprint workbook is freely sampled from the book site.
diff --git a/content/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/index.md b/content/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/index.md
index c02fcae0b..44564fb7c 100644
--- a/content/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/index.md
@@ -1,5 +1,5 @@
---
-title: "5.5 · Going Outbound Without a Sales Team"
+title: "5.7 · Going Outbound Without a Sales Team"
aliases: ["/blog/outbound-without-sales-team/"]
description: "Once the network is exhausted, customers 11-20 come from filtered cold outbound. The Filter -> Loom -> Calendly -> Stripe pipeline, 4-line scripts."
date: 2026-05-13
@@ -22,28 +22,30 @@ categories: ["Founders"]
cover_image: cover.png
metatags:
image: cover.png
- og_title: "5.5 · Going Outbound Without a Sales Team"
+ og_title: "5.7 · Going Outbound Without a Sales Team"
og_description: "Once the network is exhausted, customers 11-20 come from filtered cold outbound. The Filter -> Loom -> Calendly -> Stripe pipeline, 4-line scripts."
cover_image_alt: "JetThoughts blog cover showing a cold-outbound pipeline funnel from filtered list through Loom and Calendly to a signed Stripe invoice"
canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/"
related_posts: false
---
-> **Module 5 · Step 5 of 5** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 5 · Lesson 5.7 · [OPTIONAL] - the systematic path when warm intros run out** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
-> **Input:** network exhausted, ~10 customers in from [Chapter 5.3c](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/) and [Chapter 5.4](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/)
+> **Input:** network exhausted, ~10 customers in from [Chapter 5.5](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/) and [Chapter 5.6](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/)
>
> **Output:** 30 cold messages sent, 3-5 demo calls booked, 1-2 paid pilots cleared once replies mature
+>
+> **Progress:** M5 · 7 of 7 · [OPTIONAL] - the systematic cold path; run it only after the warm-network pass in 5.3-5.5
-> **TL;DR:** Once your network is exhausted, 30 filtered cold messages with a specific personalization per name will book 1-2 paid pilots. Customers 11-20 come from cold outbound, not from launch events.
+> **TL;DR:** Once your network is exhausted, 30 filtered cold messages with a specific personalization per name put roughly one paid pilot in reach per batch - more as batches compound. Customers 11-20 come from cold outbound, not from launch events.
-> **Stop here if you have not exhausted your personal network.** This chapter covers cold outbound to strangers - it assumes you have already converted the people who know you through [Ch 5.3c](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/).
+> **Stop here if you have not exhausted your personal network.** This chapter covers cold outbound to strangers - it assumes you have already converted the people who know you through [Ch 5.5](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/).
>
-> If you still have warm names in your network who fit your ICP, close them first. Cold outbound is harder, slower, and lower-converting than warm outreach.
+> If you still have warm names in your network who fit your ICP (ideal customer profile - the specific buyer you're targeting), close them first. Cold outbound is harder, slower, and lower-converting than warm outreach.
>
> Reading this chapter before your network is dry is the most common sequencing mistake founders make in Module 5 - it feels like progress, but you are skipping the higher-converting path for the lower one. The chapter will still be here when your network is done.
-> **$0 outbound stack.** Apollo's free tier (credit-based - check the current allowance) + a Google Sheet + Gmail mail-merge add-on (free) + Loom free + Calendly free covers the entire pipeline at zero monthly cost. You ship the same 30-message batch, you just enrich the list manually in a sheet instead of automating it through Smartlead. Upgrade to Apollo's or Smartlead's paid tiers only when you're sending 100+ messages a week and the manual enrichment is the bottleneck.
+> **$0 outbound stack.** Apollo's free tier (credit-based - check the current allowance) + a Google Sheet + a Gmail mail-merge add-on (sends the same email to many recipients at once, free) + Loom + Calendly covers the entire pipeline at zero monthly cost. You ship the same 30-message batch, you just enrich the list manually in a sheet instead of automating it through Smartlead. Upgrade to Apollo's or Smartlead's paid tiers only when you're sending 100+ messages a week and the manual enrichment is the bottleneck.
This chapter is sales outbound asking buyers for money, which is a different motion from the interview-recruitment outreach in [Chapter 2.4](/course/tech-for-non-technical-founders-2026/find-10-people-with-problem-outreach-2026/) where you were asking for 30 minutes of their time.
@@ -65,7 +67,7 @@ The four-line cold-email sequence below is what customer five answers in week th
This is the closing chapter of Module 5 (First Paying Customer). Once your personal network is exhausted, the next 10 customers come from filtered cold outbound, not from launch events.
-Figma's first customer 11-20 cohort came from cold DMs to influential designers identified via Twitter data. Retool filtered Crunchbase by funding recency. Your Rails MVP customer 11-20 cohort will come from LinkedIn Sales Navigator (or Apollo, or both) feeding the four-line script below.
+Figma's first customer 11-20 cohort reportedly came from cold DMs to influential designers; Retool reportedly filtered Crunchbase by funding recency. Your Rails MVP customer 11-20 cohort will come from LinkedIn Sales Navigator (or Apollo, or both) feeding the four-line script below.
## Why Product Hunt is the wrong lever for a B2B SaaS product
@@ -83,10 +85,10 @@ The cold-outbound pipeline in one glance:
1. **Filter** - LinkedIn Sales Navigator or Apollo.io. Pull 100-150 raw rows, strip to 30 clean names.
2. **Personalize** - 60-90 seconds per name. Read the profile and the last post, find one specific reference.
-3. **Loom** - Same product Loom from [Chapter 5.3b](/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/). No re-record per prospect.
+3. **Loom** - Same product Loom from [Chapter 5.4](/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/). No re-record per prospect.
4. **Send** - LinkedIn DM or 4-line email. One personalized opener + the same body for everyone.
5. **Calendly** - 15-min demo slot, auto-confirm. No back-and-forth scheduling.
-6. **Stripe** - DPA + deposit from [Chapter 5.4](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/). Money on the table before you start work.
+6. **Stripe** - DPA + deposit from [Chapter 5.6](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/). Money on the table before you start work.
The five tools and their 2026 pricing:
@@ -194,7 +196,7 @@ All three variants follow the same shape: a specific reference earns the open, o
```mermaid
%%{init: {'theme':'base', 'themeVariables': {'fontFamily':'Caveat, Patrick Hand, cursive', 'primaryColor':'#fff5f5', 'primaryBorderColor':'#cc342d', 'lineColor':'#333', 'primaryTextColor':'#1a1a1a'}}}%%
flowchart TB
- W1[Stage 1
Send 30 messages
3-5 replies expected]
+ W1[Stage 1
Send 30 messages
1-4 replies expected]
W2[Stage 2
Run 3-5 demos
2-3 DPAs sent]
W3[Stage 3
1-2 deposits cleared
Pilot kickoffs scheduled]
W4[Stage 4
Send next 20
Hold for reply tail]
@@ -209,7 +211,7 @@ flowchart TB
class W3,W7 conv;
```
-Expect a 10-20% reply rate on a properly filtered, properly personalized 30-message batch. That is 3-6 replies, of which 2-4 will agree to a 15-minute demo. Of the demos, 1-2 will agree to a paid pilot. Of the pilots, the [Chapter 5.4](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/) deposit-to-year-one conversion math holds.
+Expect 3-8% replies on a realistic first batch - 1-2 replies per 30 messages - and treat 10-15% as what a tightly filtered, heavily personalized batch can reach: 3-4 replies, of which 1-2 agree to a 15-minute demo, of which one becomes a paid-pilot conversation. Of the pilots, the [Chapter 5.6](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/) deposit-to-year-one conversion math holds.
The 30-message batch is not a one-time event. Run fresh 30-message batches until you have 20 customers. The second and third batches will outperform the first by 30-50% because you will have learned which reference patterns earn replies and which do not.
@@ -227,7 +229,7 @@ A 30-message batch with zero replies is rare and almost always indicates a filte
3. **Is the reference real?** Look at the first paragraph of your last 10 sent messages. If the "specific reference" sentence sounds generic ("noticed you work at [Company] in [role]"), it was not specific enough. Real specificity means the prospect can verify the claim - a date, a post title, a name, an event.
-10-15% reply rate is the baseline for a well-filtered, well-personalized batch in 2026.
+3-8% replies is the realistic first-batch band; 10-15% is the ceiling a well-filtered, well-personalized batch can reach.
> **Stop / continue / accelerate, by reply rate band.**
> - **<5% reply rate** → STOP after batch 1. Diagnose before batch 2: filter is wrong, domain reputation is dead, or script reads generic. Sending batch 2 over a broken upstream stage wastes the next 30 best-fit names on the same broken funnel.
@@ -249,14 +251,14 @@ A 30-message batch with zero replies is rare and almost always indicates a filte
| Step | Action | Output |
|---|---|---|
| **1** | Open your `Module 5 cold seed` tab from Ch 2.3-2.4 - the Apollo filter is already saved and 8-12 contacts may already be exported. Top up to 30-50 high-fit names using the same filter. Drop bottom 20 into a "later batch" tab in your Sheet. Pick one of three message variants and customize deposit + product description. | 30-50 target list built. Message template ready. |
-| **2** | Spend 60-90 minutes personalizing the first 30 messages. One specific reference per prospect (recent post, hire milestone, role change). Send via LinkedIn DM or cold email tool ([Smartlead](https://smartlead.ai), [Instantly](https://instantly.ai)). | 30 messages sent. 3-6 replies expected. |
+| **2** | Spend 60-90 minutes personalizing the first 30 messages. One specific reference per prospect (recent post, hire milestone, role change). Send via LinkedIn DM or cold email tool ([Smartlead](https://smartlead.ai), [Instantly](https://instantly.ai)). | 30 messages sent. 1-4 replies expected. |
| **3** | Tally replies once they settle. Book demos. Follow up with non-responders once only. | 2-4 demo calls booked. Next batch ready. |
The full cold-email scripts (3 variants: B2B SaaS shipped-MVP, B2B services, B2C app), the filter checklist, and the Apollo + Sales Navigator setup guide all ship in [the First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/).
## Advanced (optional sidebar)
-Once you have closed 5-10 paid pilots from cold outbound and want to layer on sales-system rigor, read the [First Round Capital sales scripts collection](https://review.firstround.com/category/sales/), Sahil Bloom's ["The First 10 Customers"](https://www.sahilbloom.com/newsletter/the-first-10-customers) playbook, and the [Y Combinator library on early sales](https://www.ycombinator.com/library/4f-startup-sales-the-fastest-way-to-find-your-first-customers). Once you cross customer 30, the sales playbooks designed for solo founders give way to operator manuals: Mark Roberge's *The Sales Acceleration Formula* for hiring your first AE, Mike Weinberg's *New Sales. Simplified.* for the manager handbook. The main path above gets you from customer 11 to customer 20. The advanced versions matter after that.
+Once you have closed 5-10 paid pilots from cold outbound and want to layer on sales-system rigor, read the [First Round Capital sales scripts collection](https://review.firstround.com/category/sales/), Sahil Bloom's ["The First 10 Customers"](https://www.sahilbloom.com/newsletter/the-first-10-customers) playbook, and the [Y Combinator library on early sales](https://www.ycombinator.com/library/4f-startup-sales-the-fastest-way-to-find-your-first-customers). Once you cross customer 30, the sales playbooks designed for solo founders give way to operator manuals: Mark Roberge's *The Sales Acceleration Formula* for hiring your first AE (account executive - a dedicated salesperson), Mike Weinberg's *New Sales. Simplified.* for the manager handbook. The main path above gets you from customer 11 to customer 20. The advanced versions matter after that.
> **Module 5 closes here.** → Download the [First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/) (the full 6-piece template bundle). Now you have a paying pilot, the rest of the course is about keeping the build honest while you ship more: the [oversight rhythm](/course/tech-for-non-technical-founders-2026/engineering-org-chart-non-technical-founder/) sets up the weekly Friday demo + standup + report cadence. Or revisit the [course landing page](/course/tech-for-non-technical-founders-2026/) to pick the next chapter.
@@ -284,18 +286,16 @@ Module 5 closes with a deposit in your Stripe account. Everything from here is k
- Y Combinator Library, [Startup Sales: The Fastest Way to Find Your First Customers](https://www.ycombinator.com/library/4f-startup-sales-the-fastest-way-to-find-your-first-customers) - YC's collection on founder-led sales including the filter-and-personalize cold-outreach motion.
- Sahil Bloom, [The First 10 Customers](https://www.sahilbloom.com/newsletter/the-first-10-customers) - playbook framing the relationship-to-cold transition that closes the personal-network gap.
-> **Done when:** 30 cold messages are sent, replies are tracked in your spreadsheet, and 1-2 paid pilots are booked from the replies.
->
-> **Next click:** [Course landing page](/course/tech-for-non-technical-founders-2026/) - course complete. See continuation chapters for [churn triage](/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/), [pivot decisions](/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/), and [hiring](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/).
+> **Done:** 30 cold messages are sent, replies are tracked in your spreadsheet, and 1-2 paid pilots are booked from the replies.
>
-> **If blocked:** If reply rate is under 5% after batch 1, diagnose before batch 2: is the filter wrong (wrong ICP), is your domain reputation dead (cold email deliverability), or is the personalization too generic? Fix the root cause before sending the next batch.
-
-> **Case Study: Tomas & Mia**
+> **You have now:** the full arc in hand - a validated hypothesis, a signed problem statement, a one-page brief, a live MVP, and at least one paying customer, plus a repeatable cold-outbound motion for customers 11-20. That is the whole course: idea → validated problem → brief → live MVP → paying customer. Keep the [First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/) open to keep the build honest as you ship past customer 10.
>
-> **Tomas**: Runs LinkedIn cold outreach to 30 controllers NOT in his network. 12% reply rate (4 replies). Books 2 pilot conversations. 1 signs at $2,500. Total: 3 paid pilots (2 from network, 1 from cold). Annualized: $30,000 in committed pilot revenue.
+> **Next:** [Course landing page](/course/tech-for-non-technical-founders-2026/) - the core course is complete. When a problem shows up, the continuation chapters cover [churn triage](/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/), [pivot decisions](/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/), and [hiring](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/).
>
-> **Mia**: Runs Facebook group cold outreach to 30 parents NOT in her network. 28% reply rate (8 replies), 5 pilot conversations, 2 sign at $50 - total: 6 paid pilots at $300/mo recurring.
+> **If blocked:** If reply rate is under 5% after batch 1, diagnose before batch 2: is the filter wrong (wrong ICP), is your domain reputation dead (cold email deliverability), or is the personalization too generic? Fix the root cause before sending the next batch.
---
+*See it in action: [Module 5 walkthrough: Mia gets paid](/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/)*
+
*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/index.md b/content/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/index.md
index 0f99af79d..f9a820c97 100644
--- a/content/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/index.md
@@ -1,5 +1,5 @@
---
-title: "5.4 · Charge Before You Ship: The Paid Pilot Contract"
+title: "5.6 · Charge Before You Ship: The Paid Pilot Contract"
aliases: ["/blog/paid-pilot-charge-before-ship/"]
description: "A verbal yes is not a paid pilot. A refundable Stripe deposit signed before kickoff is. The one-page Design Partner Agreement and a Stripe Checkout setup."
date: 2026-05-13
@@ -22,18 +22,20 @@ categories: ["Founders"]
cover_image: cover.png
metatags:
image: cover.png
- og_title: "5.4 · Charge Before You Ship: The Paid Pilot Contract"
+ og_title: "5.6 · Charge Before You Ship: The Paid Pilot Contract"
og_description: "A verbal yes is not a paid pilot. A refundable Stripe deposit signed before kickoff is. The one-page Design Partner Agreement and a Stripe Checkout setup."
cover_image_alt: "JetThoughts blog cover showing a one-page Design Partner Agreement with the deposit clause highlighted"
canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/"
related_posts: false
---
-> **Module 5 · Step 4 of 5** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 5 · Lesson 5.6 · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
-> **Input:** 3-5 warm leads from [Chapter 5.3c](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/)
+> **Input:** 3-5 warm leads from [Chapter 5.5](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/)
>
> **Output:** 1 signed paid pilot before any new code ships
+>
+> **Progress:** M5 · 6 of 7 · Results so far: demos booked from your warm list (5.3-5.5) - this page turns one into a signed pilot with money attached
> **TL;DR:** A verbal yes is not a paid pilot. A signed DPA (Design Partner Agreement - a one-page co-design pilot contract) with a refundable Stripe deposit is. Charge 10-30% of year-one ACV (annual contract value - what one customer pays in year one) before kickoff - it puts the CFO question on Week 0 instead of Week 8.
@@ -86,7 +88,7 @@ The **scope of pilot** section is where new founders over-spec. Keep it to three
The **pilot fee and deposit** clause is what makes everything else work. The deposit lands at 10-30% of projected year-one annual contract value (ACV), paid via Stripe before pilot kickoff and credited dollar-for-dollar against the year-one invoice on conversion. If the customer cancels before week 4, they forfeit the deposit (their commitment). If the founder cancels for any reason, the founder refunds 100% (your commitment). Pricing math is below.
-The **success criteria** clause is what makes the DPA a real contract instead of a handshake. Pick three measurable outcomes the pilot is supposed to produce (for example, hours saved per week, errors avoided per month, or revenue lifted per quarter), worded in the customer's verbatim language from the [Chapter 5.3c replies](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/).
+The **success criteria** clause is what makes the DPA a real contract instead of a handshake. Pick three measurable outcomes the pilot is supposed to produce (for example, hours saved per week, errors avoided per month, or revenue lifted per quarter), worded in the customer's verbatim language from the [Chapter 5.5 replies](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/).
If two of three are hit by week 6, the year-one contract auto-converts unless the customer opts out in writing. If fewer than two are hit, both parties walk and the founder retains the deposit as paid consideration for the pilot work.
@@ -167,7 +169,7 @@ Two annotated worked examples (a $1,500 B2B SaaS pilot and a $5,000 B2B services
## The pricing math
-> **From Ch 1.5 smoke-test price to year-one ACV.** Take the monthly price you tested in [Chapter 1.5](/course/tech-for-non-technical-founders-2026/price-hypothesis-on-smoke-test-page/) and multiply by 12 (or your actual billing period). Example: a $97/month hypothesis → $1,164 year-one ACV. Take 10-30% of that as your deposit floor; the band table below tells you which percentage to pick by sector. If your number lands between two bands or you are unsure which to pick, **pick the midpoint of the smallest applicable band** until your customer's CFO pushes back. The deposit is a commitment device; below the floor it stops working as one. Above the band the customer needs procurement, which lengthens the timeline.
+> **From Ch 1.5 smoke-test price to year-one ACV.** Take the monthly price you tested in [Chapter 1.5](/course/tech-for-non-technical-founders-2026/price-hypothesis-on-smoke-test-page/) and multiply by 12 (or your actual billing period). Example: a $97/month hypothesis → $1,164 year-one ACV. Take 10-30% of that as your deposit floor; the band table below tells you which percentage to pick by sector. If your number lands between two bands or you are unsure which to pick, **pick the midpoint of the smallest applicable band** until your customer's CFO pushes back. The deposit is a commitment device; below the floor it stops working as one. Above the band the customer needs procurement (the formal purchasing-approval process at bigger companies), which lengthens the timeline.
The deposit number is not arbitrary. It is anchored to projected year-one ACV and to what a typical CFO will sign without a procurement review. The bands by sector:
@@ -175,9 +177,9 @@ The deposit number is not arbitrary. It is anchored to projected year-one ACV an
| Sector | Year-1 ACV | Pilot fee (10-30%) | Pilot fee notes |
|---|---|---|---|
-| B2B SaaS (per-seat, 5-10 seats) | $5K-$12K | $500-$3K | The CFO approves the deposit on email. No procurement involved. |
+| B2B SaaS (per-seat, 5-10 seats) | $5K-$12K | $500-$3K (capped under the procurement line) | The CFO approves the deposit on email. No procurement involved. |
| B2B SaaS (mid-market, 50-200 seats) | $20K-$80K | $2K-$24K | Above $10K, expect a 1-week procurement review. Plan for it. |
-| B2B Services / consultancy | $10K-$40K | $1K-$6K | Service deposit is normal in the sector. Customer expects to pay. |
+| B2B Services / consultancy | $10K-$40K | $1K-$6K (capped under the procurement line) | Service deposit is normal in the sector. Customer expects to pay. |
### The minimum: $500
@@ -203,7 +205,7 @@ The five-minute path:
2. Go to Products. Create a new product called "[Your Product Name] - Design Partner Pilot".
3. Add a one-time price for the deposit amount ($500, $2K, $6K, whatever your math).
4. Hit "Payment link" on the product detail page. Stripe generates a hosted checkout URL.
-5. Paste the URL into your DPA email. Customer clicks, pays card or ACH, you get the Stripe notification.
+5. Paste the URL into your DPA email. Customer clicks, pays card or ACH (a direct bank transfer), you get the Stripe notification.
That is the entire setup. No webhook, no Rails controller, no Django view, no Laravel route. If you want to log paid pilots into your existing app, you can - but you do not have to. The CSV export from Stripe is enough for a Module 5 first-pilot motion.
@@ -227,7 +229,7 @@ If you do want to wire the payment into a Rails app for record-keeping later, th
## The conversation script
-You have a warm lead from [Chapter 5.3c](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/) who booked a 20-minute demo, the demo went well, and they said something close to "yes, I would love to try this with my team." The default first-time-founder move is to soften here. The 15-second script that does not soften:
+You have a warm lead from [Chapter 5.5](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/) who booked a 20-minute demo, the demo went well, and they said something close to "yes, I would love to try this with my team." The default first-time-founder move is to soften here. The 15-second script that does not soften:
> "Glad it resonates. Quick word on how I am setting up pilots - I am running them as paid design partnerships, so the customer has skin in the game and I have a real signal. The deposit is [$500-$6K], credited toward year one on conversion. Refunded in full if I cannot deliver on the success criteria. Want me to send the one-pager?"
@@ -250,9 +252,9 @@ The five responses below show up once you start talking to enterprise buyers or
**"Can you do net-30 instead of upfront?"**
-*Means:* Common ask from enterprise buyers; the deposit-before-kickoff rule loses its commitment function on net-30.
+*Means:* Common ask from enterprise buyers; the deposit-before-kickoff rule loses its commitment function on net-30 (paying 30 days after the invoice instead of upfront).
-*Say back:* "The deposit is structured upfront on purpose - it is the signal that this is a real pilot, not a sales call. I can offer net-15 from invoice date, but the kickoff timer starts when the deposit clears. If net-30 is a hard requirement on your end, the alternative is a paid PoC with a smaller scope I can deliver before invoicing for the full pilot."
+*Say back:* "The deposit is structured upfront on purpose - it is the signal that this is a real pilot, not a sales call. I can offer net-15 from invoice date, but the kickoff timer starts when the deposit clears. If net-30 is a hard requirement on your end, the alternative is a paid PoC (proof of concept - a small paid trial) with a smaller scope I can deliver before invoicing for the full pilot."
**"My legal team needs to review any contract."**
@@ -287,14 +289,14 @@ The paid pilot is the default, but it has three honest exceptions.
| Step | Action | Output |
|---|---|---|
| **1** | Copy the [DPA template above](#dpa-template) into a Google Doc, fill the 6 bracketed sections, pick deposit number from the sector table above, set up Stripe product + payment link. Optional: the [First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/) has annotated worked examples + DocuSign-importable format. | Stripe link ready. DPA drafted. Deposit amount locked. |
-| **2** | Send the DPA + Stripe link to 1-2 warm leads from Chapter 5.3 who booked demos recently. | 1-2 DPA emails sent. Expect 1 procurement question + 1 ready-to-sign. |
+| **2** | Send the DPA + Stripe link to 1-2 warm leads from Chapter 5.5 who booked demos recently. | 1-2 DPA emails sent. Expect 1 procurement question + 1 ready-to-sign. |
| **3** | Bank your first deposit. Schedule pilot kickoff and the first Friday demo cadence. | Deposit cleared. Kickoff scheduled. Pilot officially started. |
-**If you do not have warm demos yet**, your work is still in [Chapter 5.3a](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/). The DPA is the wrong sprint for an empty pipeline.
+**If you do not have warm demos yet**, your work is still in [Chapter 5.3](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/). The DPA is the wrong sprint for an empty pipeline.
## Advanced (optional sidebar)
-Once you have closed 2-3 paid pilots and want to layer on contract rigor, read the [Common Paper Design Partner Agreement template](https://commonpaper.com/standards/design-partner-agreement/) (a vetted v2 LOI used by hundreds of YC companies), [SaaStr's "Should we charge for pilots"](https://www.saastr.com/should-you-charge-for-a-pilot/) (Jason Lemkin's thirty-second answer is yes, always), and Ash Rust's ["Startup Sales: How to Get Pilot Customers to Pay"](https://medium.com/sharp-spear/startup-sales-how-to-get-pilot-customers-to-pay-7a9b7a48eedf) for the conversation tactics. The one-page DPA in this chapter is enough through your first 10 pilots. The advanced versions matter once you start hearing the words "procurement" and "MSA" in pilot conversations.
+Once you have closed 2-3 paid pilots and want to layer on contract rigor, read the [Common Paper Design Partner Agreement template](https://commonpaper.com/standards/design-partner-agreement/) (a vetted v2 LOI widely used by YC companies), [SaaStr's "Should we charge for pilots"](https://www.saastr.com/should-you-charge-for-a-pilot/) (Jason Lemkin's thirty-second answer is yes, always), and Ash Rust's ["Startup Sales: How to Get Pilot Customers to Pay"](https://medium.com/sharp-spear/startup-sales-how-to-get-pilot-customers-to-pay-7a9b7a48eedf) for the conversation tactics. The one-page DPA in this chapter is enough through your first 10 pilots. The advanced versions matter once you start hearing the words "procurement" and "MSA" (master service agreement - a long formal contract) in pilot conversations.
A 20% deposit at kickoff puts the CFO question on Week 0. Conversion in Week 7 becomes paperwork, not negotiation.
@@ -302,28 +304,25 @@ A 20% deposit at kickoff puts the CFO question on Week 0. Conversion in Week 7 b
## Further reading
-- Common Paper, [Design Partner Agreement template](https://commonpaper.com/standards/design-partner-agreement/) - a vetted, modern LOI used by hundreds of YC companies. The companion to your one-pager when conversations move toward MSAs.
+- Common Paper, [Design Partner Agreement template](https://commonpaper.com/standards/design-partner-agreement/) - a vetted, modern LOI widely used by YC companies. The companion to your one-pager when conversations move toward MSAs.
- SaaStr, [Should you charge for a pilot?](https://www.saastr.com/should-you-charge-for-a-pilot/) - Jason Lemkin's case for charging and the conversion-rate data behind the recommendation.
-- Ash Rust, [Startup Sales: How to Get Pilot Customers to Pay](https://medium.com/sharp-spear/startup-sales-how-to-get-pilot-customers-to-pay-7a9b7a48eedf) - tactical conversation script and pricing-band data from a former Sequoia-backed founder.
+- Ash Rust, [Startup Sales: How to Get Pilot Customers to Pay](https://medium.com/sharp-spear/startup-sales-how-to-get-pilot-customers-to-pay-7a9b7a48eedf) - tactical conversation script and pricing-band data from investor Ash Rust.
- Steve Blank, [The Four Steps to the Epiphany](https://steveblank.com/2010/01/06/the-four-steps-to-the-epiphany/) - the foundational text on Customer Validation; Blank argues paid pilots are how you separate real demand from polite enthusiasm.
- Stripe, [Payment Links documentation](https://stripe.com/docs/payment-links) - the official Stripe Checkout setup. 15-minute integration with no engineering work required.
- Lenny Rachitsky, [How to win your first 10 B2B customers](https://www.lennysnewsletter.com/p/how-to-win-your-first-10-b2b-customers) - the 7-step playbook including the design-partner pricing model from B2B founders.
-> **Done when:** One DPA is signed and the Stripe deposit has cleared in your account.
-> **Founder OS · Artifact #6 of 6:** A signed Design Partner Agreement + cleared deposit. Save the executed PDF + Stripe receipt in your `Founder OS` folder. This is the artifact investors fund; you can now point to it and say "someone who doesn't know me paid real money for this."
+> **Done:** one DPA is signed and the Stripe deposit has cleared in your account.
+>
+> **You have now:** a signed Design Partner Agreement + a cleared deposit - real money from someone who didn't know you before you asked. Save the executed PDF + Stripe receipt in your `Founder OS` folder next to the earlier artifacts (validated problem statement, Product Brief, live MVP). That completes the folder - the artifact investors fund, the one you point to and say "someone who doesn't know me paid real money for this." Converting this pilot into a year-one contract is the next test, 6-8 weeks out.
>
-> **Next click:** [5.5 · Going Outbound Without a Sales Team](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/)
+> **Next:** the optional [5.7 · Going Outbound Without a Sales Team](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) for the next 10 customers once your warm list runs dry, plus the [First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/) - worked DPA examples and Friday-demo templates that keep the build honest through the pilot.
>
> **If blocked:** If the customer says "can we start free and convert later," reframe: the deposit is year-one ACV prepaid, not added cost. If they still say no, they are not in your must-have segment - move to the next lead.
> **Stuck here?** Asking for money from someone you know is the stall point, even as a refundable deposit. **Fix:** the deposit is a test of whether the problem is real - not a test of whether you deserve to be paid. If they value the solved problem less than the deposit, their problem isn't acute enough. Send the DPA to your warmest lead first. The second one is easier.
-> **Case Study: Tomas & Mia**
->
-> **Tomas**: Signs a Design Partner Agreement with 3 accounting firms. Deposit: $2,500 each (refundable if product doesn't ship within 90 days). 2 of 3 sign and pay within 48 hours. Revenue: $5,000 in committed deposits.
->
-> **Mia**: Signs a Design Partner Agreement with 4 parents. Deposit: $50 each (refundable) - B2C marketplace convention: deposit equals roughly 2× the monthly fee ($25/mo tutoring × 2). The $500 floor in the body above is the B2B SaaS convention; consumer marketplaces work to smaller absolute numbers because the buyer signs without a CFO. 4 of 4 sign and pay. Revenue: $200. Lower deposit, higher volume - consumer math.
-
---
+*See it in action: [Module 5 walkthrough: Mia gets paid](/course/tech-for-non-technical-founders-2026/module-5-walkthrough-mia/)*
+
*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/index.md b/content/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/index.md
index 009c30518..d0099bf70 100644
--- a/content/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/index.md
@@ -22,7 +22,7 @@ categories: ["Founders"]
cover_image: cover.png
metatags:
image: cover.png
- og_title: "7.6 · Pivot or Persevere: The Decision Framework"
+ og_title: "Pivot or Persevere: The Decision Framework"
og_description: "Six pivot types, trigger conditions for each, and what to keep when you pivot. The chapter that turns the course from a one-way escalator into a discovery loop."
cover_image_alt: "JetThoughts course cover showing 6 pivot arrows branching from a center node"
canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/"
@@ -31,13 +31,13 @@ related_posts: false
> **Going further · Continuation chapter 6 of 6** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
-> **Input:** a churn-triage decision (chapter 7.5) OR a Sean Ellis 40% test result (chapter 7.1)
+> **Input:** a decision from the [churn-triage chapter](/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/) OR a Sean Ellis 40% test result ([Chapter 5.1](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/))
>
> **Output:** a pivot decision with the 6-type framework + a written list of what you keep vs what you change
## The Course Is a Loop, Not an Escalator
-A founder I rode shotgun with last quarter - a fintech founder named D. - hit chapter 7.4 with a cold-outbound conversion rate of 0.6%. He had sent 287 personal emails to CFOs of 50-200-person companies over 14 days, with 11 replies and 0 paid pilots. His instinct, the same instinct every founder gets here, was to push forward into salvage-or-rebuild territory and start managing the build harder.
+A founder I rode shotgun with last quarter - a fintech founder named D. - hit the cold-outbound stage (Chapter 5.7) with a conversion rate of 0.6%. He had sent 287 personal emails to CFOs of 50-200-person companies over 14 days, with 11 replies and 0 paid pilots. His instinct, the same instinct every founder gets here, was to push forward into salvage-or-rebuild territory and start managing the build harder.
That was the wrong move. The right move was backwards. The 0.6% conversion rate was telling him the messaging he had built off his [Founding Hypothesis](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/) sentence was not landing on the segment he had picked. Three things could be wrong: the customer (segment), the need (problem), or the channel (outbound vs PLG). Pushing forward into rebuild mode would have made him a better operator of a misaligned hypothesis. Going back to [Form Your Founding Hypothesis](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/) with a pivot decision made him a better founder.
@@ -53,7 +53,7 @@ Eric Ries catalogued ten pivot types in *The Lean Startup*; Steve Blank built on
### 1. Customer Segment pivot
-*Right product, wrong customer.* You shipped a tool that works, but the audience you targeted is not the audience that gets value from it. The signal usually comes from a churn-triage cohort slice (chapter 7.5) where one segment retains at 50%+ and others languish under 20%. Example: R. from the churn-triage chapter shipped a workflow tool to solo founders that turned out to be a 3-person-team tool. Same product, different audience.
+*Right product, wrong customer.* You shipped a tool that works, but the audience you targeted is not the audience that gets value from it. The signal usually comes from a churn-triage cohort slice (see the [churn-triage chapter](/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/)) where one segment retains at 50%+ and others languish under 20%. Example: R. from the churn-triage chapter shipped a workflow tool to solo founders that turned out to be a 3-person-team tool. Same product, different audience.
### 2. Customer Need pivot
@@ -106,7 +106,7 @@ flowchart TD
**Sean Ellis 40% under 25% across all segments** triggers a Solution pivot or a Customer Need pivot. Founders typically react by trying harder on the same product - more features, better onboarding, more polish. The right move is to ask whether the solution shape itself is wrong, or whether you targeted the wrong job.
-**Cohort retention under 30% with churn-triage Decision 3** triggers a Solution pivot. The cohort floor from chapter 7.5 already told you no segment retains. The pivot framework tells you the most likely culprit is solution shape, not audience.
+**Cohort retention under 30% with churn-triage Decision 3** triggers a Solution pivot. The churn-triage cohort floor already told you no segment retains. The pivot framework tells you the most likely culprit is solution shape, not audience.
**CAC > 3x LTV with paying customers who love the product** triggers a Revenue Model pivot. Founders typically react by trying to push CAC down (better ads, better landing pages). When the customers who do convert love the product, the issue is almost always pricing model, not acquisition cost.
@@ -122,7 +122,7 @@ A pivot is not a restart. The founders who treat pivots as restarts are the ones
-The ledger above is the template. Print it (or copy it to a Notion doc) before you declare the pivot. Walk every row. The evidence you keep includes: the validated problem statements that survived the interviews (or the disconfirmed ones - both are evidence), the customer relationships from your [Build Your 50-Name Network List](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) outreach (50 names with verified contact details and one conversation each is the most valuable B2B asset you own at this stage), the cohort retention numbers you collected for the chapter 7.5 churn triage, and your domain expertise as the founder. The hypothesis sentence, the landing page copy, and the ad creative get rewritten. The MVP code depends - the auth and billing layers usually survive; the core workflow gets rebuilt around the new hypothesis.
+The ledger above is the template. Print it (or copy it to a Notion doc) before you declare the pivot. Walk every row. The evidence you keep includes: the validated problem statements that survived the interviews (or the disconfirmed ones - both are evidence), the customer relationships from your [Build Your 50-Name Network List](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) outreach (50 names with verified contact details and one conversation each is the most valuable B2B asset you own at this stage), the cohort retention numbers you collected for the churn triage, and your domain expertise as the founder. The hypothesis sentence, the landing page copy, and the ad creative get rewritten. The MVP code depends - the auth and billing layers usually survive; the core workflow gets rebuilt around the new hypothesis.
A second founder we rode shotgun with - Anika, running a vertical SaaS for clinical-trial coordinators - ran the ledger move on a Monday afternoon. She kept her 287-person coordinator contact list (Customer Need pivot meant the segment was still right). She kept four of her eleven validated problem statements from her [Mom Test interviews](/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/) (the ones about consent-form reconciliation, not the ones about scheduling). She kept her Stripe integration and her auth flow from the Lovable build. She rewrote her hypothesis sentence around consent-form reconciliation. She rewrote her landing page headline. She kept her pricing model intact ($240/month per seat). Two weeks later she had a smoke-test landing page live, an outreach script aimed at the same 287 contacts with the new pitch, and four warm meetings booked. The pivot took 14 days because she kept everything that survived.
@@ -158,7 +158,7 @@ A Technology pivot routes you to the [salvage-vs-rebuild decision framework](/co
A persevere decision keeps you on whatever module you were on. Re-measure trigger conditions in 30 days.
-The course was always a loop. The reason it reads as a numbered sequence is that the discovery moves work the same regardless of whether you are running them for the first time or the fifth. The founders who graduate the course - the ones holding all eight Founder OS artifacts at the end - are not the founders who never pivoted. They are the founders who ran the loop three or four times and got better at each pass.
+The course was always a loop. The reason it reads as a numbered sequence is that the discovery moves work the same regardless of whether you are running them for the first time or the fifth. The founders who graduate the course - the ones holding all six Founder OS artifacts at the end - are not the founders who never pivoted. They are the founders who ran the loop three or four times and got better at each pass.
D. is on his third pivot now. He ran the original hypothesis once (audit prep), pivoted to month-end close (Customer Need), then 7 weeks later pivoted the channel from outbound to partnerships (Channel). The two pivots cost him 5 weeks of build time combined and saved him at least two quarters of running each wrong hypothesis to its conclusion. The pivot framework is what made each loop a deliberate decision instead of a flail.
diff --git a/content/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/pivot-ledger.svg b/content/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/pivot-ledger.svg
index 3f4db2cbf..10dd64d03 100644
--- a/content/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/pivot-ledger.svg
+++ b/content/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/pivot-ledger.svg
@@ -53,7 +53,7 @@
Cohort retention numbers
- Chapter 5.5 floor
+ Churn-triage floor
YES
Baseline for next cohort
diff --git a/content/course/tech-for-non-technical-founders-2026/quickstart/index.md b/content/course/tech-for-non-technical-founders-2026/quickstart/index.md
index 1caa1ab4a..ee9e1942d 100644
--- a/content/course/tech-for-non-technical-founders-2026/quickstart/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/quickstart/index.md
@@ -72,21 +72,21 @@ Skip the lessons marked "optional" on the [course landing page](/course/tech-for
- [**4.1** · Should You Hire? Decision Tree](/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/)
- [**4.2** · Own Your GitHub, AWS, and Database](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/)
-- [**4.3a** · Tools & Setup](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/)
-- [**4.3b** · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/)
+- [**4.3** · Tools & Setup](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/)
+- [**4.4** · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/)
-**Gate:** you own every account; the app loads; one core flow works end-to-end.
+**Gate:** you own every account; the app loads; one core flow works end-to-end. *(4.5, the optional monthly ceiling check, starts after launch.)*
### Module 5 - First Paying Customer
*Output: one signed paid pilot + repeatable outbound channel.*
-- [**5.1** · Your First Customer Is Not a Marketing Problem](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/)
-- [**5.3a** · Build Your 50-Name Network List](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/)
-- [**5.3b** · Write the Outreach Message](/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/)
-- [**5.3c** · Send, Track, and Read the Replies](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/)
-- [**5.4** · Charge Before You Ship: The Paid Pilot](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/)
+- [**5.1** · Your First Customer Is Not a Marketing Problem](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/) *(5.2, the optional channel-selection detour, is skip-safe on this fast path)*
+- [**5.3** · Build Your 50-Name Network List](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/)
+- [**5.4** · Write the Outreach Message](/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/)
+- [**5.5** · Send, Track, and Read the Replies](/course/tech-for-non-technical-founders-2026/first-ten-customers-send-track/)
+- [**5.6** · Charge Before You Ship: The Paid Pilot](/course/tech-for-non-technical-founders-2026/paid-pilot-charge-before-ship/)
-**Gate:** signed pilot agreement + $500+ deposit received through Stripe.
+**Gate:** signed pilot agreement + deposit received through Stripe ($500+ standard; first-month-upfront on the low-price path in 5.6).
---
diff --git a/content/course/tech-for-non-technical-founders-2026/reference/smoke-test-channel-guide/index.md b/content/course/tech-for-non-technical-founders-2026/reference/smoke-test-channel-guide/index.md
index 4fa9700de..0051a844f 100644
--- a/content/course/tech-for-non-technical-founders-2026/reference/smoke-test-channel-guide/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/reference/smoke-test-channel-guide/index.md
@@ -19,7 +19,7 @@ The dollar cost of 300 visits depends entirely on channel CPC (cost-per-click),
| Meta / Instagram | Consumer products | $0.70-$1.90 | $210-$570 |
| Reddit Ads | Developer tools, niche communities | $1.25-$3.00 | $375-$900 |
| Google Search | B2B with named search intent | $3-$8 | $900-$2,400 |
-| LinkedIn | B2B sold by job title | $5.50-$22 | $1,650-$6,600 |
+| LinkedIn | B2B sold by job title | $5.70-$22 | $1,650-$6,600 |
*Sources: [WordStream Meta benchmarks 2026](https://www.wordstream.com/blog/facebook-ads-benchmarks-2025); [WordStream Google Ads benchmarks 2026](https://www.wordstream.com/blog/2026-google-ads-benchmarks); [The B2B House LinkedIn benchmarks 2026](https://www.theb2bhouse.com/linkedin-ad-benchmarks/); [Stackmatix Reddit Ads 2026](https://www.stackmatix.com/blog/reddit-ads-cost-per-click).*
@@ -62,7 +62,7 @@ Use one of these, run it the same way until the numbers stabilize, read the resu
**Skip when:** Customer 55+ OR enterprise.
### B2B / Job-Title-Sold
-**Channel:** LinkedIn ($5.50-$22 CPC) OR Google Search ($3-$8).
+**Channel:** LinkedIn ($5.70-$22 CPC) OR Google Search ($3-$8).
**When to pick:** LinkedIn for unaware audiences; Google for active searchers.
**Skip when:** Consumer or under-25 audience.
@@ -121,7 +121,7 @@ You picked your channel above and created your ad account. Here are the settings
### LinkedIn Ads
1. **Campaign objective:** Website visits.
-2. **Budget:** $50-80/day minimum (LinkedIn CPC is $5.50-$22). If this is too steep, use the B2B budget alternatives section above instead.
+2. **Budget:** $50-80/day minimum (LinkedIn CPC is $5.70-$22). If this is too steep, use the B2B budget alternatives section above instead.
3. **Audience:** Job title + industry + company size. Use your [customer] blank literally. If your hypothesis says "CTOs at 20-50 person SaaS companies," target exactly that. Do not broaden - on LinkedIn, narrow targeting is cheaper (less competition per audience slice).
4. **Ad format:** Single image ad.
5. **Ad creative:** Intro text: your value prop (keep it professional - LinkedIn readers expect B2B tone). Headline: your landing page headline. Image: your hero image or a simple text-on-color card. CTA: "Learn More" or "Sign Up." Destination: your landing page.
diff --git a/content/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/index.md b/content/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/index.md
index f7264f114..42aa5d7a4 100644
--- a/content/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/index.md
@@ -1,6 +1,6 @@
---
-title: "4.3b · The Self-Serve MVP Stack: Build Phases"
-description: "The build plan: 4 phases from Lovable UI to live Stripe checkout. Phase exit criteria, 5 green lights, and the Module 5 handoff. Part 2 of Chapter 4.3."
+title: "4.4 · The Self-Serve MVP Stack: Build Phases"
+description: "The build plan: 4 phases from Lovable UI to live Stripe checkout. Phase exit criteria, 5 green lights, and the Module 5 handoff. Companion build guide to Chapter 4.3 (Tools & Setup)."
date: 2026-05-18
draft: false
course_chapter: true
@@ -21,30 +21,32 @@ categories: ["Founders"]
cover_image: cover.png
metatags:
image: cover.png
- og_title: "4.3b · The Self-Serve MVP Stack: Build Phases"
+ og_title: "4.4 · The Self-Serve MVP Stack: Build Phases"
og_description: "The build plan: 4 phases from Lovable UI to live Stripe checkout. Phase exit criteria, 5 green lights, and the Module 5 handoff."
cover_image_alt: "JetThoughts cover showing three hand-drawn stacked layers labeled Lovable, Supabase, and Stripe with arrows linking them, and a sticky note reading Ship by Friday week 4."
canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/"
related_posts: false
---
-> **Module 4 · Step 3b of 4** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 4 · Lesson 4.4 · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
-> **Part 2 of 2** · [Part 1: Tools & Setup](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) covers why these three tools, what each one does, the 12 rules, communities, and the AI critic block.
+> **Companion pair: read [Chapter 4.3 · Tools & Setup](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) first** - it covers why these three tools, what each one does, the 12 rules, communities, and the AI critic block.
>
-> **Input:** a Module 4 decision pointing to "self-serve" + a one-page brief + the tool knowledge from Part 1
+> **Input:** the self-serve stack set up plus the pre-flight rules from [Chapter 4.3](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) + your one-page brief from Module 3
>
-> **Output:** a live MVP at a staging URL real users can click - by week 10-12 for evening-only founders (the 2-4 hr/week pattern this course is built for), or by Friday week 4 for full-time founders
+> **Output:** a live MVP at a real URL that real users can click
+>
+> **Progress:** M4 · 4 of 5 · Results so far: stack set up + pre-flight rules locked (4.3) - this page walks the 4 build phases to a live MVP
> **TL;DR:** Four build phases with one demo each. Phase 1 ships clickable UI. Phase 2 wires Supabase auth. Phase 3 connects Stripe checkout. Phase 4 deploys to 5 ICP users. Five green lights to exit. Ship the shed, not the skyscraper.
-> **Calendar reality for the MVP build.** A full-time founder with daytime availability can hit the Phase 4 5-lights in 4-6 weeks. An evening-only founder (the 2-4 hr/week pattern this course is built for) typically needs 10-12 weeks for the same outputs. Phase 2 (Supabase wiring + RLS - Row-Level Security, the database rule that walls one customer's data off from another's) and Phase 3 (Stripe webhook - an automatic message Stripe sends your app when a payment lands - plus idempotency, the rule that says "if the same webhook fires twice, only act once") are where part-time founders lose the most calendar. Plan a 10-week version of the build, not a 4-week version. The Friday-week-4 framing in the Output line above applies to full-time founders only.
+> **Calendar reality for the MVP build.** A full-time founder with daytime availability can hit the Phase 4 5-lights in 4-6 weeks. An evening-only founder (the 2-4 hr/week pattern this course is built for) typically needs 10-12 weeks for the same outputs. Phase 2 (Supabase wiring + RLS - Row-Level Security, the database rule that walls one customer's data off from another's) and Phase 3 (Stripe webhook - an automatic message Stripe sends your app when a payment lands - plus idempotency, the rule that says "if the same webhook fires twice, only act once") are where part-time founders lose the most calendar. Plan a 10-week version of the build, not a 4-week version. The Friday-week-4 pace is a full-time-founder pace only.
-> **This chapter assumes you read Part 1 first.** Part 1 covers the $0 path, the 12 rules, what each tool does, the M2 prototype vs M4 MVP distinction, communities, and the AI critic block. The build phases below reference those concepts without re-explaining them.
+> **This chapter assumes you read Chapter 4.3 first.** It covers the $0 path, the 12 rules, what each tool does, the M2 prototype vs M4 MVP distinction, communities, and the AI critic block. The build phases below reference those concepts without re-explaining them.
## The ship plan
-> **The ship plan below is the BUILD portion only.** It assumes you already ran Modules 1-3 (hypothesis → smoke test → 10 interviews → one-page brief) and read [Part 1: Tools & Setup](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/). If you skip straight here without validation, the build often ships into the silence Modules 1-3 were designed to prevent.
+The ship plan below is the BUILD portion only. It assumes you already ran Modules 1-3 (hypothesis, smoke test, 10 interviews, one-page brief) and read [Chapter 4.3: Tools & Setup](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/). If you skip straight here without validation, the build ships into the silence Modules 1-3 were designed to prevent.
Four build phases, plus an onramp phase that hands you off to Module 5. Each phase ends with one demo to one human (a friend, an advisor, your spouse, the dog if necessary - someone who has not seen the build). The build phase ends with five real ICP users on the staging URL; the onramp phase brings the rest of your Ch 2.3-2.4 interview pool onto the product.
@@ -82,7 +84,7 @@ In Lovable, install the Supabase integration. Lovable will add the Supabase JS c
> **Self-test your RLS policy before going live (two paths).**
>
-> *No-code path (the default for a non-technical founder).* In Claude or ChatGPT, paste: *"Audit my Supabase RLS policy. Here is my schema: [paste your table definitions from Supabase Table Editor]. Here is my current RLS policy: [paste from Authentication -> Policies]. Tell me whether a logged-in user with a fake user-id can read rows that belong to other users. If yes, give me the exact policy SQL to fix it."* Paste the AI's suggested policy into Supabase Authentication -> Policies.
+> *No-code path (the default for a non-technical founder - this is copy-paste verification, not programming: the AI writes the fix, you paste it and read the answer).* In Claude or ChatGPT, paste: *"Audit my Supabase RLS policy. Here is my schema: [paste your table definitions from Supabase Table Editor]. Here is my current RLS policy: [paste from Authentication -> Policies]. Tell me whether a logged-in user with a fake user-id can read rows that belong to other users. If yes, give me the exact policy SQL to fix it."* Paste the AI's suggested policy into Supabase Authentication -> Policies.
>
> *SQL path (only if you are comfortable writing SQL).* In Supabase Dashboard -> SQL Editor, paste the test below, replacing `` with your main user-data table. The pretend user-id `999` has no real rows; if the query returns any, your policy has a hole.
>
@@ -116,12 +118,12 @@ Watch what happens. If 0 of 5 click, the cold message is wrong, not the product
> 1. **Stripe in LIVE mode** (not test mode) and a real card successfully clears the paywall at least once.
> 2. **Custom domain wired** (not a `.lovable.app` subdomain) - the URL you DM to a user must be yours.
> 3. **At least 1 ICP user who was NOT in your Ch 2.3-2.4 interviews** has clicked through to the paywall on the live URL.
-> 4. **Zero JS errors in the browser Console** on the sign-up + checkout flow (open DevTools, walk the happy path, console must stay clean).
+> 4. **Zero errors in the browser Console** on the sign-up + checkout flow. Not a coding step: press F12, click through sign-up and checkout like a user, and check that the Console tab shows no red lines.
> 5. **Friday-style weekly demo recording exists** for the last week of build (a Loom or screen-record proving the demo cadence held to the end).
>
> Advance to Module 5 only when all 5 are green. If any are red, the MVP is NOT ready for the 10-30 users Module 5 needs as input. Fix the red light first, then re-check.
-> **Pre-flight before M5.1: book up to 10 user sessions.** Phase 4's 4-6 onramp accounts are not enough for M5.1's Sean Ellis 40% test (under 10 respondents = noise, not signal). Before you start Module 5, book a second small invite wave: 5-10 more sessions from your Ch 2.3-2.4 interviewee list, your community connections, or a fresh micro-batch of cold DMs. Aim for 10-15 active users total by the time M5.1's survey ships. Without this pre-flight, you will run the 40% test on 5 people, get an ambiguous result, and falsely conclude you have a product problem when you really have a sample-size problem.
+> **Pre-flight before M5.1: book up to 10 user sessions.** The onramp phase's 4-6 accounts are not enough for M5.1's Sean Ellis 40% test (under 10 respondents = noise, not signal). Before you start Module 5, book a second small invite wave: 5-10 more sessions from your Ch 2.3-2.4 interviewee list, your community connections, or a fresh micro-batch of cold DMs. Aim for 10-30 active users by the time M5.1's survey ships - 5.1 treats 10 as directional-only and 20+ as a useful read. Without this pre-flight, you will run the 40% test on 5 people, get an ambiguous result, and falsely conclude you have a product problem when you really have a sample-size problem.
### Onramp phase - Module 5 handoff: invite your Module 2 interviewees onto the live MVP
@@ -129,7 +131,7 @@ The build phases above are the BUILD container. The onramp phase is the Module-5
Open your Ch 2.3-2.4 interview list. For each of the 10 names, write a 3-line personalized note: the workaround they described in their interview, the staging URL of the workflow that now replaces it, and one specific question they answered that the MVP now responds to.
-Send it as a [Loom](https://www.loom.com) (Loom is a free short-form screen-recording tool - the recipient watches you click through the product in their browser, no install) or a personal LinkedIn DM, not a generic email blast.
+Send it as a [Loom](https://www.loom.com) (Loom is a short-form screen-recording tool - the recipient watches you click through the product in their browser, no install) or a personal LinkedIn DM, not a generic email blast.
Expect 4-6 of the 10 to create accounts; 2-3 of those to actually log in and click around; 1-2 to become candidates for the [Ch 5.1 Sean Ellis 40% survey](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/) once you have 10-30 users total. "Create an account" is not "pay" - paid conversion happens in Module 5.
@@ -152,11 +154,11 @@ The [Module 4 post](/course/tech-for-non-technical-founders-2026/should-you-hire
Be honest about the trade-off. This stack cannot host every business. It can host yours through the first 10 paying customers, which is the only data point that earns you the right to argue about the next architecture.
-## The architectural ceiling - what's coming in Chapter 4.4
+## The architectural ceiling - what's coming in Chapter 4.5
-The stack holds until it doesn't. Five specific signals tell you the ceiling is close. The next chapter ([Chapter 4.4 - Proactive Ceiling Signals](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/)) walks through each one with the threshold to watch.
+The stack holds until it doesn't. Five specific signals tell you the ceiling is close. The next chapter ([Chapter 4.5 - Proactive Ceiling Signals](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/)) walks through each one with the threshold to watch.
-Quick preview: scale beyond roughly 10,000 users, complex data model that no longer fits a single Supabase project, real-time features the auto-generated REST API cannot serve, security or compliance scope that needs an external audit, AI inference at scale where per-request cost crosses pennies. When you see two of these, route to the [hire-track supplementary reference](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/) or to a [Fractional CTO](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge) for the architecture call. Architecture does not collapse overnight; the warning shows up in the metrics before the customer sees it. Chapter 4.4 names the metrics.
+Quick preview: scale beyond roughly 5,000 users, complex data model that no longer fits a single Supabase project, real-time features the auto-generated REST API cannot serve, security or compliance scope that needs an external audit, AI inference at scale where per-request cost crosses pennies. When you see two of these, route to the [hire-track supplementary reference](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/) or to a [Fractional CTO](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge) for the architecture call. Architecture does not collapse overnight; the warning shows up in the metrics before the customer sees it. Chapter 4.5 names the metrics.
What the stack actually costs, per published vendor pricing:
@@ -166,7 +168,7 @@ What the stack actually costs, per published vendor pricing:
| First ship | Per-tool monthly fees | Lovable + Supabase entry paid tiers + a .com domain (~$10/yr) + Resend entry tier + Stripe per-transaction fees |
| Post-launch | Scale-tier monthly fees | Lovable scale tier + Supabase paid tier + Resend/Sentry/monitoring paid tiers - check vendor pricing pages |
-The architectural ceiling tends to land at the post-launch tier - at ~10K users, route to Chapter 4.4 or a [Fractional CTO](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge). A hire-a-team build is material monthly burn before revenue; this stack ships the same first 10 paying customers on a fraction of that.
+The architectural ceiling tends to land at the post-launch tier - at ~5K users, route to Chapter 4.5 or a [Fractional CTO](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge). A hire-a-team build is material monthly burn before revenue; this stack ships the same first 10 paying customers on a fraction of that.
## What to do tomorrow
@@ -188,33 +190,29 @@ The shed build never grows that large. Either you reach the architectural ceilin
Self-serve has a ceiling. The [ceiling-signal monitoring chapter](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/) covers the 5 signals that mean it's time to bring in help. When 2+ signals fire in one monthly check, switch to the [hire-track supplementary reference](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/).
-Build the shed first. Lovable + Supabase + Stripe + a $14 domain ships your validated problem to a staging URL on per-vendor pricing. The bigger architecture is a different conversation, and you have not earned the right to have it yet.
+Build the shed first. Lovable + Supabase + Stripe + a ~$10 domain ships your validated problem to a staging URL on per-vendor pricing. The bigger architecture is a different conversation, and you have not earned the right to have it yet.
## Further reading
-- [Part 1: Tools & Setup](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) - the companion page: why these three tools, what each one does, 12 rules, communities, and the AI critic block
+- [Chapter 4.3: Tools & Setup](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) - the companion page: why these three tools, what each one does, 12 rules, communities, and the AI critic block
- [Self-Serve Stack Walkthrough](/course/tech-for-non-technical-founders-2026/self-serve-stack-walkthrough/) - day-by-day version of the build plan; print before Phase 1
- Y Combinator, [Startup School Library + 2026 Founder Resources](https://www.ycombinator.com/library/) - the YC stance on validating without code
- Rob Walling, [Vibe Coding interview on Creator Science](https://podcast.creatorscience.com/rob-walling/) - the shed vs skyscraper analogy
- Lovable, [Pricing tiers](https://lovable.dev/pricing) and [community Discord](https://lovable.dev/community)
- Supabase, [Row-Level Security guide](https://supabase.com/docs/guides/database/postgres/row-level-security)
- Stripe, [Checkout quickstart](https://docs.stripe.com/payments/checkout/quickstart) and [Pricing page](https://stripe.com/pricing)
-- Drew Falkman, [Vibe Coding Data-Enabled AI Apps on Maven](https://maven.com/)
+- Drew Falkman, "Vibe Coding Data-Enabled AI Apps" on Maven
-> **Done when:** All 5 green lights are lit: Stripe in live mode, custom domain wired, 1 ICP user tested the paywall, zero JS errors on the signup+checkout flow, and a weekly demo recording exists.
+> **Done:** all 5 green lights are lit - Stripe in live mode, custom domain wired, 1 ICP user tested the paywall, zero JS errors on the signup + checkout flow, and a weekly demo recording exists.
>
-> **Founder OS · Artifact #5 of 6:** A live MVP at a real URL, with ownership of every account in your name (per Ch 4.2's Day-1 ownership audit). Save the URL + admin login + the latest weekly demo recording in a `Live MVP` doc in your `Founder OS` folder. Module 5 invites your Module 2 interviewees + smoke-test email list to this URL as the warm seed for the first 10-30 users.
+> **You have now:** the self-serve stack set up (4.3) + a live MVP at a real URL. Save the URL, the admin login, and the latest weekly demo recording in a `Live MVP` doc in your `Founder OS` folder, with every account in your own name (per [Chapter 4.2's Day-1 ownership audit](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/)). Module 5 invites your Module 2 interviewees and your [Chapter 1.4 smoke-test email list](/course/tech-for-non-technical-founders-2026/smoke-test-landing-page-7-day-demand-test/) to this URL as the warm seed for your first 10-30 users. Paying customers are the next test.
>
-> **Next click:** [4.4 · Vibe Coding Done Right: 5 Ceiling Signals](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/)
+> **Next:** [5.1 · Your First Customer Is Not a Marketing Problem](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/) - it runs the Sean Ellis 40% test on the users this MVP collects. Bookmark [4.5 · Ceiling Signals](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/) as the optional monthly check to run when the stack starts to strain.
>
-> **If blocked:** If stuck on Phase 2 (Supabase), post your schema in the Lovable Discord. If stuck on Phase 3 (Stripe webhook), run a $1 test transaction in Stripe test mode first. The communities section in Part 1 lists free help channels.
-
-> **Case Study: Tomas & Mia**
->
-> **Tomas**: Phase 1-3 (6 weeks total with CTO): builds reconciliation dashboard, CTO sets up RLS + Stripe subscriptions + QuickBooks API via n8n. Phase 4: ships to custom domain. 5 green lights passed.
->
-> **Mia**: Phase 1-3 (4 weeks total): builds tutor search + profiles, sets up parent/tutor login, integrates Stripe booking payments. Phase 4: ships to custom domain. 5 green lights passed.
+> **If blocked:** If stuck on Phase 2 (Supabase), post your schema in the Lovable Discord. If stuck on Phase 3 (Stripe webhook), run a $1 test transaction in test mode first. The communities section in Chapter 4.3 lists free help channels.
---
+*See it in action: [Module 4 walkthrough: Mia ships TutorMatch](/course/tech-for-non-technical-founders-2026/module-4-walkthrough-mia/)*
+
*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/index.md b/content/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/index.md
index 34f4dc5d5..a235655e5 100644
--- a/content/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/index.md
@@ -1,7 +1,7 @@
---
-title: "4.3a · The Self-Serve MVP Stack: Tools & Setup"
+title: "4.3 · The Self-Serve MVP Stack: Tools & Setup"
aliases: ["/blog/self-serve-mvp-stack-lovable-supabase-stripe-2026/"]
-description: "Why Lovable + Supabase + Stripe is the dominant self-serve path. Plain-English roles, vendor pricing, 12 rules, communities. Part 1 of Chapter 4.3."
+description: "Why Lovable + Supabase + Stripe is the dominant self-serve path. Plain-English roles, vendor pricing, 12 rules, communities. Chapter 4.3 of the course; Chapter 4.4 walks the build."
date: 2026-05-18
draft: false
course_chapter: true
@@ -23,23 +23,25 @@ categories: ["Founders"]
cover_image: cover.png
metatags:
image: cover.png
- og_title: "4.3a · The Self-Serve MVP Stack: Tools & Setup"
- og_description: "Why Lovable + Supabase + Stripe is the dominant self-serve path. Plain-English roles, vendor pricing, 12 rules, communities. Part 1 of Chapter 4.3."
+ og_title: "4.3 · The Self-Serve MVP Stack: Tools & Setup"
+ og_description: "Why Lovable + Supabase + Stripe is the dominant self-serve path. Plain-English roles, vendor pricing, 12 rules, communities. Chapter 4.3 of the course; Chapter 4.4 walks the build."
cover_image_alt: "JetThoughts cover showing three hand-drawn stacked layers labeled Lovable, Supabase, and Stripe with arrows linking them, and a sticky note reading Ship by Friday week 4."
canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/"
related_posts: false
---
-> **Module 4 · Step 3a of 4** · Part 1 of 2 · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 4 · Lesson 4.3 · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
-> **Input:** a Module 4 decision pointing to "self-serve" (from [Ch 4.1](/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/)) + a one-page brief (from [Ch 3.1](/course/tech-for-non-technical-founders-2026/one-page-product-brief-vibe-prd/)) + a Day-1 ownership audit passed (from [Ch 4.2](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/))
+> **Input:** a Module 4 decision pointing to "self-serve" (from [Ch 4.1](/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/)) + a quality-checked one-page brief (from [Ch 3.2](/course/tech-for-non-technical-founders-2026/stop-specifying-features-start-outcomes/)) + a Day-1 ownership audit passed (from [Ch 4.2](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/))
>
-> **Output:** the 3 pre-flight rules locked in, tool boundaries clear, ready to start the build in [Part 2 · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/)
-
-> **Jump to:** [What each tool does](#what-each-tool-does-in-plain-english) · [12 rules checklist](#12-rules-for-a-self-built-poc-done-right) · [Communities](#communities-that-replace-a-co-founder) · [The ship plan](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/#the-ship-plan)
+> **Output:** the 3 pre-flight rules locked in, tool boundaries clear, ready to start the build in [Chapter 4.4 · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/)
+>
+> **Progress:** M4 · 3 of 5 · Results so far: build path = self-serve (4.1) + ownership locked (4.2) - this page sets up the stack and the pre-flight rules
> **TL;DR:** Lovable renders the screens, Supabase stores the data, Stripe charges the card. Three tools, three jobs. Know the boundaries before you open Lovable. Twelve rules keep the build inside the shed. All three tools have free tiers; the chapter's specific cost callouts live where each tool is introduced. Skip to [the ship plan](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/#the-ship-plan) if you already know the stack.
+> **Jump to:** [What each tool does](#what-each-tool-does-in-plain-english) · [12 rules checklist](#12-rules-for-a-self-built-mvp-done-right) · [Communities](#communities-that-replace-a-co-founder) · [The ship plan](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/#the-ship-plan)
+
> **This chapter starts FRESH from your one-page brief - do NOT iterate the Chapter 2.6 prototype.**
>
> The Chapter 2.6 prototype was a short research artifact: fake data, no auth, viewed by 5 interview subjects, archived after the shape test. This chapter is the production build: real Supabase auth, real Stripe payments, real domain, real users. The first proved users can navigate the SHAPE; the second ships the actual product. Reusing the prototype code multiplies the build effort and ships every research compromise into production.
@@ -54,9 +56,9 @@ The stack, top to bottom:
|-------|------|-----|------|
| UI | Lovable | Render the screens. Send form data down. | Free tier + paid tiers |
| Data | Supabase | Store the user, the row, the file. Listen for Stripe events. | Free tier + paid tiers |
-| Money | Stripe | Charge the card. Tell Supabase the customer is paid. | 2.9% + $0.30 per transaction |
+| Money | Stripe | Charge the card. Tell Supabase the customer is paid. | Per-transaction card fee (see Stripe pricing) |
-The buyer opens the staging URL → Lovable shows the screens → Supabase stores the data → Stripe charges the card → a Stripe webhook tells Supabase the row is now paid.
+The buyer opens the staging URL (the live web address where your work-in-progress app is visible) → Lovable shows the screens → Supabase stores the data → Stripe charges the card → a Stripe webhook (an automatic status message Stripe sends your app) tells Supabase the row is now paid.
## Why these three tools, and why they slot together
@@ -66,7 +68,7 @@ Boring is what you want for an MVP. The boring path lets one non-technical found
The cost to disprove your hypothesis is vendor free tiers and the small per-tool monthly fees in the cost table above. The cost to prove it is the same.
-> **Alternative: $0 Concierge MVP (no-code Wizard of Oz).** If you want more demand evidence before committing to Lovable code, run a Concierge MVP first: **Tally** (free form) → **Zapier or Make.com** (free routing) → **Airtable or Notion** (free storage). The customer fills the Tally form, Zapier drops the row in Airtable, you process by hand. To the customer it looks automated. Validate willingness-to-pay before committing to the build. All three tools have free tiers. This is a stepping stone, not a replacement; the Lovable + Supabase + Stripe stack is what ships in Part 2.
+> **Alternative: $0 Concierge MVP (no-code "Wizard of Oz" - you fake the automation by hand behind the curtain).** If you want more demand evidence before committing to Lovable code, run a Concierge MVP first: **Tally** (free form) → **Zapier or Make.com** (free routing) → **Airtable or Notion** (free storage). The customer fills the Tally form, Zapier drops the row in Airtable, you process by hand. To the customer it looks automated. Validate willingness-to-pay before committing to the build. All three tools have free tiers. This is a stepping stone, not a replacement; the Lovable + Supabase + Stripe stack is what ships in Chapter 4.4.
## M2 prototype vs M4 MVP - different artifacts, different rigor
@@ -90,33 +92,33 @@ Side-by-side: the Module 2 throwaway prototype vs the Module 4 production MVP.
## What each tool does (in plain English)
-Pre-seed founders ask "which framework" before they ask "which job." Three tools, three jobs. The boundaries between them are the only architecture you need to know on day one.
+It is tempting to ask "which framework" before you ask "which job." Three tools, three jobs. The boundaries between them are the only architecture you need to know on day one.
### Lovable - the UI layer
Lovable is an AI-powered builder for the screens. You describe an app in English: *"a dashboard for fitness coaches to log client check-ins, with a weekly export to CSV"*, and Lovable generates a working web frontend with proper component structure, routing, and form validation. Every save deploys to a public staging URL you can paste into a Slack message.
-[Lovable's pricing](https://lovable.dev/pricing) runs from a capped free tier through paid tiers sized by build velocity - check the pricing page for current numbers. Most paying-MVP founders settle on a mid or scale tier after the first month.
+[Lovable's pricing](https://lovable.dev/pricing) runs from a capped free tier through paid tiers sized by build velocity - check the pricing page for current numbers. Expect to move to a mid or scale tier after the first month once build velocity picks up.
The key thing it does not do well: heavy backend logic, complex auth flows, anything custom on the database side. That is what Supabase is for.
### Supabase - the data layer
-Supabase is managed Postgres + auth + file storage + row-level security in one console. Lovable's built-in storage is fine for a prototype; Supabase is what you connect when you have real users whose data has to survive a redeploy.
+Supabase is managed Postgres (a widely used database) + auth (the login and signup system) + file storage + row-level security (rules that keep each user's rows private to them) in one console. Lovable's built-in storage is fine for a prototype; Supabase is what you connect when you have real users whose data has to survive a redeploy.
-The free tier comfortably covers early-stage usage - [check Supabase's pricing page](https://supabase.com/pricing) for current limits. Most pre-seed founders never outgrow the first paid tier before they hit the architectural ceiling.
+The free tier comfortably covers early-stage usage - [check Supabase's pricing page](https://supabase.com/pricing) for current limits. Early-stage usage rarely outgrows the first paid tier before you hit the architectural ceiling.
-Supabase auto-generates a REST API and a JavaScript client on top of any table you create, which is what Lovable calls when it needs to read or write a row. [Supabase's 2026 pricing](https://supabase.com/pricing) lists the bands clearly. The auth product replaces most of what founders used to pay Auth0 or Clerk for; the row-level security policies replace what a contractor would have hand-coded over two weeks.
+Supabase auto-generates a REST API (a standard way for one program to request data from another) and a JavaScript client on top of any table you create, which is what Lovable calls when it needs to read or write a row. [Supabase's 2026 pricing](https://supabase.com/pricing) lists the bands clearly. The auth product replaces most of what founders used to pay Auth0 or Clerk for; the row-level security policies replace what a contractor would have hand-coded over two weeks.
### Stripe - the money layer
Stripe processes the payment. The 2026 default integration for a Lovable app is [Stripe Checkout](https://docs.stripe.com/payments/checkout) (a hosted page Lovable can link to with one line) plus a webhook into Supabase that updates the user's subscription status when the charge succeeds.
-The fee is the standard [2.9% + $0.30 per transaction](https://stripe.com/pricing) for cards in the US; international, Klarna, ACH, and other rails have their own bands. There is nothing custom about this in 2026. Every founder hits the same Checkout integration; the documentation has been refined over a decade of pre-seed founders running the exact same setup.
+The fee is the standard [per-transaction card processing rate](https://stripe.com/pricing) for cards in the US (a small percentage plus a flat per-charge amount); international, Klarna, ACH, and other rails have their own bands. There is nothing custom about this in 2026. Every founder hits the same Checkout integration; the documentation has been refined over a decade of the exact same setup.
### GitHub for version control
-Free for solo founders on the Free plan. You will not write much code yourself, but Lovable can sync to a GitHub repo on every save. Two reasons this matters: (a) you have a backup if Lovable goes down or you cancel the subscription, (b) when you eventually hire a contractor or a Fractional CTO, the code is already in a place they can read. Set this up in Lovable's Settings on day one. Skipping this is the most common reason founders we pick up six months later cannot retrieve the source.
+Free for solo founders on the Free plan. You will not write much code yourself, but Lovable can sync to a GitHub repo (short for repository - the online folder that stores your code) on every save. Two reasons this matters: (a) you have a backup if Lovable goes down or you cancel the subscription, (b) when you eventually hire a contractor or a Fractional CTO, the code is already in a place they can read. Set this up in Lovable's Settings on day one. Skipping this is the most common reason a founder cannot retrieve the source six months later.
> **Module 4 AI critic/simulator block**
>
@@ -147,13 +149,13 @@ Free for solo founders on the Free plan. You will not write much code yourself,
> **What AI cannot prove or substitute:**
> - Whether real users can navigate the workflow (only uncoached ICP users can)
> - Whether the Stripe webhook idempotency is correct (only test-mode charges can)
-> - Whether the architecture will hold at scale (only real traffic + Ch 4.4 ceiling signals can)
+> - Whether the architecture will hold at scale (only real traffic + Ch 4.5 ceiling signals can)
>
-> **The real gate:** 5 green lights (Phase 4 exit criteria in [Part 2](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/)) + weekly demo to one non-PRD-reader human.
+> **The real gate:** 5 green lights (Phase 4 exit criteria in [Chapter 4.4](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/)) + weekly demo to one non-PRD-reader human.
-## 12 rules for a self-built PoC done right
+## 12 rules for a self-built MVP done right
-> **How to read this list.** 3 rules need to be true BEFORE you open Lovable. The rest fire inline during the Phase 1-4 build in [Part 2](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/). If you internalize ONLY the 3 pre-Lovable rules + the Phase 4 exit criteria, you ship a working MVP. The other rules are inline reminders, not a homework checklist.
+> **How to read this list.** 3 rules need to be true BEFORE you open Lovable. The rest fire inline during the Phase 1-4 build in [Chapter 4.4](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/). If you internalize ONLY the 3 pre-Lovable rules + the Phase 4 exit criteria, you ship a working MVP. The other rules are inline reminders, not a homework checklist.
Synthesis of every rule scattered across Module 4 and the supplementary references. Print this page, tape it next to the laptop, re-read before every weekly demo.
@@ -165,14 +167,14 @@ Synthesis of every rule scattered across Module 4 and the supplementary referenc
4. **Weekly demo to one non-PRD-reader human.** Spouse, advisor, dog if necessary. Keep a ship-something-visible cadence every week. The demo IS the data; the screens are not.
5. **Do NOT iterate the Ch 2.6 throwaway prototype.** Start the M4.3 build fresh from your one-page brief. The prototype answered "do users know what to click"; the MVP answers "do users pay."
6. **Set up GitHub sync in Lovable Settings on day 1.** Lovable can drop the work; GitHub is your backup. Skipping this is the #1 reason founders cannot retrieve their source.
-7. **Enable Row-Level Security on every Supabase table from day 1.** RLS is the rule that says "Coach A can only read Coach A's rows." Skipping it ships the cross-tenant data leak that ends pilots (see Ch 4.4 Signal 4).
+7. **Enable Row-Level Security on every Supabase table from day 1.** RLS is the rule that says "Coach A can only read Coach A's rows." Skipping it ships the cross-tenant data leak that ends pilots (see Ch 4.5 Signal 4).
8. **Stripe webhook handler must be idempotent.** Idempotent means "safe to run twice without breaking anything" - Stripe sometimes sends the same payment event more than once, and your handler must not double-charge or double-activate. Check `WHERE event_id = $1 AND processed = true` before re-running the update. (See production hardening section of [hire-track reference](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#production-hardening-checklist-what-your-fractional-cto-will-look-for) for details.)
9. **Budget envelope: vendor free tiers + per-tool monthly fees.** Lovable free, Supabase free, Stripe transaction fees, domain registration. Upgrade Lovable to a paid tier only when build velocity demands it.
10. **Ship before scope creep, then a short stabilization phase.** Build the smallest end-to-end thing, then a stabilization phase before paid-pilot conversations. Sits inside the multi-month journey to first paying customer.
-11. **Monthly Ch 4.4 ceiling-signal check once the live MVP is up.** Even if everything is green, the habit catches the 5 architectural break-points before they become rebuilds.
+11. **Monthly Ch 4.5 ceiling-signal check once the live MVP is up.** Even if everything is green, the habit catches the 5 architectural break-points before they become rebuilds.
12. **Do not scale a Lovable stack past ~5K users or 2 ceiling signals at red.** When you hit either limit, graduate to a Fractional CTO bridge (see [hire-track reference](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge)). The shed is not the house; pouring skyscraper foundations into a shed slab does not build a skyscraper.
-Each of the 12 rules is taught in depth somewhere across this chapter, the [self-serve stack walkthrough](/course/tech-for-non-technical-founders-2026/self-serve-stack-walkthrough/), [Ch 4.4 ceiling signals](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/), or the [hire-track supplementary reference](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/). The list above is the index; the surrounding chapters are the depth.
+Each of the 12 rules is taught in depth somewhere across this chapter, the [self-serve stack walkthrough](/course/tech-for-non-technical-founders-2026/self-serve-stack-walkthrough/), [Ch 4.5 ceiling signals](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/), or the [hire-track supplementary reference](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/). The list above is the index; the surrounding chapters are the depth.
## Communities that replace a co-founder
@@ -184,13 +186,13 @@ You are about to hit a wall: a Lovable prompt that produces the wrong component,
| **[Indie Hackers](https://www.indiehackers.com/)** | Bootstrap-focused | Honest revenue posts + shipping logs; Friday-demo accountability rhythm | Free + paid tier (varies) |
| **[No Code Founders (NCF Slack)](https://www.nocodefounders.com/)** | Full no-code stack (Bubble, Webflow, Glide, Softr) | If Lovable is wrong for your UI shape; worth membership even if you stay on Lovable | Free membership |
| **r/nocode + r/vibecoding (Reddit)** | Free, indexable | Lower signal-to-noise than Slack; search before post | Free |
-| **[Buildspace + Maven cohorts](https://maven.com/)** | Drew Falkman's "Vibe Coding Data-Enabled AI Apps" | Peer cohort + office hours; for founders who ship harder under deadline | Paid - check the course page |
+| **[Buildspace + Maven cohorts](https://maven.com/)** | Drew Falkman's "Vibe Coding Data-Enabled AI Apps" | Peer cohort + office hours; best when a deadline is what makes you ship | Paid - check the course page |
None of these is JetThoughts. None of them sells you a service. They are the founder peer pool the YC stance on co-founders [now points at](https://www.ycombinator.com/library/) instead of the 50%-equity hire.
## Further reading
-- [Part 2: Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/) - the companion page: 4 build phases, exit criteria, shed-vs-skyscraper, and the architectural ceiling
+- [Chapter 4.4: Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/) - the companion page: 4 build phases, exit criteria, shed-vs-skyscraper, and the architectural ceiling
- Y Combinator, [Startup School Library + 2026 Founder Resources](https://www.ycombinator.com/library/) - the YC stance on validating without code and the changing role of the technical co-founder
- Rob Walling, [Vibe Coding interview on Creator Science](https://podcast.creatorscience.com/rob-walling/) - the shed vs skyscraper analogy that frames the architectural ceiling. 35-minute listen.
- Lovable, [Pricing tiers](https://lovable.dev/pricing) and [community Discord](https://lovable.dev/community)
@@ -199,20 +201,18 @@ None of these is JetThoughts. None of them sells you a service. They are the fou
- DHH, [The One-Person Framework](https://world.hey.com/dhh/the-one-person-framework-711e6318)
- Veracode, [GenAI Code Security Report 2025](https://www.veracode.com/blog/genai-code-security-report/)
-> **Done when:** You understand what each of the three tools does, why the boundaries between them matter, and the 3 pre-flight rules are locked in (brief quality-gate passed, one workflow scoped, GitHub sync on). Ready to open [Part 2: Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/).
->
-> **Next click:** [4.3b · The Self-Serve MVP Stack: Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/)
->
-> **If blocked:** If the tools don't click yet, skim the Lovable Discord or Indie Hackers to see real founders shipping with this exact stack. The communities section above lists free help channels.
-
> **Stuck here?** The 12 rules list feels like a homework checklist and you haven't opened Lovable yet. **Fix:** read ONLY the 3 pre-Lovable rules at the top of the list. The other 9 fire inline during the build - they're reminders, not prerequisites. Open Lovable and paste your brief's Section 3. Ship one screen tonight.
-> **Case Study: Tomas & Mia**
+> **Done:** you understand what each of the three tools does, why the boundaries between them matter, and the 3 pre-flight rules are locked in (brief quality-gate passed, one workflow scoped, GitHub sync on).
+>
+> **You have now:** a validated problem statement (2.5) + a quality-checked one-page brief (3.2) + a self-serve build decision (4.1) + a passed Day-1 ownership audit (4.2) + the three-tool stack mapped and the 3 pre-flight rules locked (4.3). The build itself is the next test.
>
-> **Tomas**: Fractional CTO greenlights the self-serve stack: Lovable (UI), Supabase (auth + DB), Stripe (payments), n8n (QuickBooks API connector). CTO writes the RLS policies and API patterns. Tomas builds the UI.
+> **Next:** [4.4 · The Self-Serve MVP Stack: Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/) - takes the 3 pre-flight rules and the stack you just mapped into the Phase 1-4 build.
>
-> **Mia**: Picks the full self-serve stack: Lovable (UI), Supabase (auth + DB), Stripe (booking payments). Reads the 12 rules checklist. Passes all 12 rules. Starts building.
+> **If blocked:** If the tools don't click yet, skim the Lovable Discord or Indie Hackers to see real founders shipping with this exact stack. The communities section above lists free help channels.
---
+*See it in action: [Module 4 walkthrough: Mia ships TutorMatch](/course/tech-for-non-technical-founders-2026/module-4-walkthrough-mia/)*
+
*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/self-serve-stack-walkthrough/index.md b/content/course/tech-for-non-technical-founders-2026/self-serve-stack-walkthrough/index.md
index dfcf9d6fb..d8d3b3999 100644
--- a/content/course/tech-for-non-technical-founders-2026/self-serve-stack-walkthrough/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/self-serve-stack-walkthrough/index.md
@@ -25,7 +25,7 @@ canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2
related_posts: false
---
-📋 Template companion to [Chapter 4.3a · The Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) and [4.3b · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/). Print Monday morning. Ship by Friday week 4.
+📋 Template companion to [Chapter 4.3 · The Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) and [4.4 · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/). Print Monday morning. Ship by Friday week 4.
# Self-Serve Stack Walkthrough - 4 Weeks, 3 Tools, 1 Staging URL
@@ -379,9 +379,9 @@ The bad pattern ships an MVP where any user with the right URL pattern can fake
- **If 1+ paid signups**: continue. The hypothesis is alive. Build the second feature in weeks 5-8 using the same one-feature-per-month rhythm. Re-read the [three-questions standup chapter](/course/tech-for-non-technical-founders-2026/three-questions-turn-standup-into-proof/) for the weekly oversight rhythm once you bring in a contractor.
- **If 0 paid signups but 3+ signups**: the product clicks but the price or the paywall is wrong. Run two A/B tests in week 5: lower price ($19 vs $29), and earlier paywall (paid from day 1 vs 14-day trial). Pick the winner. Re-send to 5 new ICP prospects.
- **If 0 signups**: the cold message and the landing screen are both wrong, OR the [Module 2](/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/) validation was a false positive. Re-read your Mom Test transcripts. Are the buyers who said "yes I'd pay" the same buyers ignoring your cold message? If yes, the validation was polite, not real. Loop back to Module 2 for ten more interviews before you build feature two.
-- **Watch for the architectural ceiling**: when any of the [5 ceiling signals](/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/) appears (covered in detail in Chapter 4.4), pause feature work and route to the [Fractional CTO bridge](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge). The shed does not collapse overnight, but you stop adding load once you see the signal.
+- **Watch for the architectural ceiling**: when any of the [5 ceiling signals](/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/) appears (covered in detail in Chapter 4.5), pause feature work and route to the [Fractional CTO bridge](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge). The shed does not collapse overnight, but you stop adding load once you see the signal.
-If you want the doctrine in long form, [Chapter 4.3a](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) walks through what each tool does, the role boundaries, the cost reality, and the architectural ceiling preview.
+If you want the doctrine in long form, [Chapter 4.3](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) walks through what each tool does, the role boundaries, the cost reality, and the architectural ceiling preview.
## Appendix - reference code
diff --git a/content/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/index.md b/content/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/index.md
index cefd5670a..a5e5cc4ab 100644
--- a/content/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/should-you-hire-2026-decision-tree/index.md
@@ -28,15 +28,17 @@ canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2
related_posts: false
---
-> **Module 4 · Step 1 of 4** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 4 · Lesson 4.1 · [CORE]** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
> **Input:** a one-page brief + outcome-shaped feature spec (from Module 3)
>
> **Output:** a 4-way build-path decision (validate / self-serve / fractional-CTO / hire) + the [Build Path Decision Worksheet](/course/tech-for-non-technical-founders-2026/build-path-decision-worksheet/)
+>
+> **Progress:** M4 · 1 of 5 · Results so far: a quality-checked one-page brief (3.2) - this page decides who builds from it
> **TL;DR:** Default: self-serve with Lovable + Supabase + Stripe. Hiring is a ceiling-signal trigger, not the first decision. Five questions route you to one of four build paths.
-Self-serve with Lovable + Supabase + Stripe is the default for a non-technical founder in 2026. Hiring (whether a full team or a Fractional CTO - a part-time senior engineer who owns architecture but doesn't write the code) is what you do when you hit a specific ceiling signal, not the first decision after the Brief. This chapter is the decision tree: when does the default end, and what triggers the switch?
+Self-serve with Lovable (an AI app builder that turns a plain-English prompt into a working web app), Supabase (the database that stores what the app records), and Stripe (the service that takes the payments) is the default for a non-technical founder in 2026. Hiring (whether a full team or a Fractional CTO - a part-time senior engineer who owns architecture but doesn't write the code) is what you do when you hit a specific ceiling signal, not the first decision after the Brief. This chapter is the decision tree: when does the default end, and what triggers the switch?
Pre-seed founders hiring engineering before a single paying customer is confirmed is the most common build-decision mistake at the idea stage. The brief was right - we taught the brief in [The One-Page Product Brief](/course/tech-for-non-technical-founders-2026/one-page-product-brief-vibe-prd/) and quality-checked it as outcomes in [Ch 3.2](/course/tech-for-non-technical-founders-2026/stop-specifying-features-start-outcomes/).
@@ -58,7 +60,7 @@ All three are research signals, not builds. The one-page brief (Chapter 3.1) doc
## The Airbnb test
-Brian Chesky and Joe Gebbia did not write code first. They blew up an air mattress in their living room, took photos with a digital camera, posted three nights at $80 on a hand-rolled WordPress page, and waited. Three guests showed up. They made $240.
+Brian Chesky and Joe Gebbia did not write code first. They blew up an air mattress in their living room, took photos with a digital camera, posted three nights at $80 on a simple hand-built page, and waited. Three guests showed up. They made $240.
The product was a website with a payment link. The validation was three strangers paying real money. Paul Graham later wrote about the same instinct in [*Do things that don't scale*](https://paulgraham.com/ds.html): the founders who win are the ones who do the unscalable, manual experiment that proves demand before they industrialize it.
@@ -66,7 +68,7 @@ The 2026 version of the Airbnb test takes one afternoon: a Carrd page with a Str
-The signal you are looking for is small. Two paying buyers from 35 cold outreach hits is enough to flip the build switch.
+The signal you are looking for is small. Two paying buyers from 30 cold outreach hits is enough to flip the build switch.
We know a B2B SaaS founder who sold five annual contracts at $1,800 each via a Stripe link and a Notion doc before she wrote a line of code. By the time her contractor delivered the v1 web app eight weeks later, she had $9,000 in pre-revenue and a customer-feedback loop already running. The build was constrained by what she had already promised the five buyers, which is the cheapest scope-control mechanism that exists.
@@ -84,7 +86,7 @@ Most build-vs-hire posts give you one answer. The honest answer is four answers,
| Path | Cost shape | When to pick / Failure mode |
|---|---|---|
-| **1. Validate without code** | Per-vendor pricing (Carrd, Stripe, Notion). Optional ad spend. | **Pick when** no MVP, untested hypothesis, no paying buyers. **Fails when** zero clicks from 35 prospects - pitch/price/timing is wrong. |
+| **1. Validate without code** | Per-vendor pricing (Carrd, Stripe, Notion). Optional ad spend. | **Pick when** no MVP, untested hypothesis, no paying buyers. **Fails when** zero clicks from 30 prospects - pitch/price/timing is wrong. |
| **2. Self-serve build** | Per-tool monthly pricing (Lovable + Supabase + Stripe + Resend). | **Pick when** validated problem, one workflow, one persona, simple backend. **Fails when** architectural ceiling hits at ~5K users or second integration. |
| **3. Fractional CTO bridge** | Fractional hourly rate, $0 equity. | **Pick when** validated, real data model, no runway for a full hire. **Fails when** fractional CTO drifts from oversight into coding features. |
| **4. Hire a team** | Material monthly burn before revenue (team salaries + tooling). | **Pick when** backend-heavy, integration-rich, compliance scope, multi-month runway secured. **Fails when** team builds a spaceship for the wrong moon. |
@@ -97,7 +99,7 @@ Use this path when you have no MVP yet, a single untested hypothesis, and no con
Pick this path when the problem is validated (10+ Mom Test interviews with ≥7 strong-signal scores per the Ch 2.5 synthesis rubric + a Ch 1.4 smoke test that cleared the 6%+ "Promising" band - pre-orders and paid pilots are produced LATER in Module 5, do not require them as the gate), the scope is one workflow for one persona, and the backend requirements are simple - no real-time collaboration, no complex refund flows, no compliance scope.
-This week: paste your [one-page brief](/course/tech-for-non-technical-founders-2026/vibe-prd-template/) into [Lovable](https://lovable.dev) (an AI app builder - free trial available), ship the smallest end-to-end thing it generates, and connect [Supabase](https://supabase.com) (database + auth, free tier) + Stripe + Resend on top. Tooling is per-vendor pricing across the stack. Watch one failure mode: hitting the architectural ceiling when the app crosses ~5,000 users or your second integration. [5 Ceiling Signals](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/) tells you when to move up.
+This week: paste your [one-page brief](/course/tech-for-non-technical-founders-2026/vibe-prd-template/) into [Lovable](https://lovable.dev) (free trial available), ship the smallest end-to-end thing it generates, and connect [Supabase](https://supabase.com) (free tier) + Stripe + Resend (the service that sends your app's emails) on top. Tooling is per-vendor pricing across the stack. Watch one failure mode: hitting the architectural ceiling when the app crosses ~5,000 users or your second integration. [5 Ceiling Signals](/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/) tells you when to move up.
### 3. Fractional CTO bridge ([The Fractional CTO Bridge](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge))
@@ -114,18 +116,18 @@ Five questions feed the matrix. Answer them alone with a printed worksheet, writ
```mermaid
%%{init: {'theme':'base', 'themeVariables': {'fontFamily':'Caveat, Patrick Hand, cursive', 'primaryColor':'#fff5f5', 'primaryBorderColor':'#cc342d', 'lineColor':'#333', 'primaryTextColor':'#1a1a1a'}}}%%
flowchart TD
- Start(["Default: self-serve with Lovable + Supabase + Stripe.
Work through the ceiling-signal questions to see if that holds."])
- Start --> Q1{"Q1: Problem validated?
10+ Mom Test calls + ≥7 strong signals + Ch 1.4 smoke test ≥6%?"}
- Q1 -->|No| Validate["Step back: Validate without code first.
Run the Airbnb test this week."]
- Q1 -->|Yes| Q2{"Q2: Backend-heavy?
Real-time / queues / compliance / 5+ integrations?"}
- Q2 -->|No| Q3{"Q3: Runway tight?
Less than 4 months to show paying users?"}
- Q2 -->|Yes| Hire["Hire a team.
Material monthly burn. Read the SOW first."]
- Q3 -->|No| Q4{"Q4: Senior engineer available
for 1 hr/month architecture review?"}
+ Start(["Default: self-serve.
Five questions test it."])
+ Start --> Q1["Q1: Problem validated?
10+ calls, 7+ signals, smoke test 6%+"]
+ Q1 -->|No| Validate["Step back: validate without code.
Airbnb test this week."]
+ Q1 -->|Yes| Q2["Q2: Backend-heavy?
Real-time / queues / compliance?"]
+ Q2 -->|No| Q3["Q3: Runway under 4 months?"]
+ Q2 -->|Yes| Hire["Hire a team.
Read the SOW first."]
+ Q3 -->|No| Q4["Q4: Senior engineer for a
monthly architecture review?"]
Q3 -->|Yes| Validate
- Q4 -->|Yes| SelfServe["Default confirmed: Self-serve.
Paste one-page brief into Lovable."]
- Q4 -->|No| Q5{"Q5: Monthly engineering budget?"}
- Q5 -->|"Fractional rate"| Fractional["Fractional CTO bridge (see [hire-track reference](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/)).
Buys the architecture review commercially. $0 equity."]
- Q5 -->|"Full team burn"| Hire
+ Q4 -->|Yes| SelfServe["Self-serve confirmed.
Paste your brief into Lovable."]
+ Q4 -->|No| Q5["Q5: Monthly engineering budget?"]
+ Q5 -->|Fractional rate| Fractional["Fractional CTO bridge.
Architecture review, bought. $0 equity."]
+ Q5 -->|Full team burn| Hire
classDef start fill:#f0f9f0,stroke:#2e7d32,stroke-width:2.5px,color:#1a1a1a
classDef question fill:#fff5f5,stroke:#cc342d,stroke-width:2px,color:#1a1a1a
@@ -147,7 +149,7 @@ The Mermaid above is the worksheet. The five questions live in the diagram. The
| Route | What it means | Next chapter to read |
|---|---|---|
| **Validate (Q1=No or Q3 tight)** | The Module 1-3 evidence chain isn't done. Pre-orders and paid pilots come in Module 5 - do NOT skip ahead. LinkedIn likes don't count; "they said they would buy" doesn't count. | Back to [the Module 1 smoke test (Lessons 1.2-1.5)](/course/tech-for-non-technical-founders-2026/smoke-test-build-page/) or [Ch 2.3 recruitment](/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/) |
-| **Self-serve (Q2=No, Q4=Yes)** | Default for non-technical founders. Lovable renders the screens, Supabase stores the data, Stripe charges the card. The senior engineer in your network is the cheap monthly insurance. | [Ch 4.3a · Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) + [4.3b · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/) |
+| **Self-serve (Q2=No, Q4=Yes)** | Default for non-technical founders. Lovable renders the screens, Supabase stores the data, Stripe charges the card. The senior engineer in your network is the cheap monthly insurance. | [Ch 4.3 · Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) + [4.4 · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/) |
| **Fractional CTO (Q4=No, Q5=fractional)** | Same self-serve build, but the architecture review is bought commercially instead of borrowed from your network. 0% equity. | [hire-track supplementary reference](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/) |
| **Hire a team (Q2=Yes OR Q5=full team)** | Backend-heavy OR runway gives you 12+ months. Material monthly burn. Read the SOW first. | [SOW reading guide](/course/tech-for-non-technical-founders-2026/sow-reading-guide/) before signing anything |
@@ -157,7 +159,7 @@ The Mermaid above is the worksheet. The five questions live in the diagram. The
**Q3 ("runway?")** is months of cash until you must show paying customers. Under 4 months: route to Validate regardless of Q1. 4-12 months: self-serve or fractional are both viable. 12+ months: hire a team becomes safe to consider.
-**Q5 ("engineering budget?")**: fractional rate fits the Fractional CTO route (typically $200/hr or $8-15K/mo at time of writing); full team salaries fit the Hire route. Skip the path you cannot fund through the runway window.
+**Q5 ("engineering budget?")**: fractional rate fits the Fractional CTO route (an $80-$120/hour market band for a competent Fractional CTO, per Bolster and Toptal marketplace data, which lands around $400-$600/week for 5 hours); full team salaries fit the Hire route. Skip the path you cannot fund through the runway window.
A printable [worksheet](/course/tech-for-non-technical-founders-2026/build-path-decision-worksheet/) lays out these five questions in checkbox form and writes your verdict at the top of the page. Print it. Fill it in alone. Take the result to one peer or advisor for a sanity check.
@@ -186,23 +188,21 @@ Two refundable deposits beat 200 LinkedIn likes.
- Paul Graham, [*Do Things That Don't Scale*](https://paulgraham.com/ds.html) - the YC essay that named the Airbnb-style validation pattern. The first section is the Airbnb story; the rest is the manual that founders skip.
- Paul Graham, [*The Airbnbs*](https://www.paulgraham.com/airbnbs.html) - PG's own short note on the Airbnb founders' early experiments. 6-minute read.
- Sophia Matveeva, [*The Non-Technical Founder's Guide to Hiring*](https://www.amazon.com/Non-Technical-Founders-Guide-Hiring-Product-ebook/dp/B0B7WRLBZF) - the long-form companion to this post. Heavy on hiring, light on the validate-without-code path that comes first.
-- Drew Falkman, [*Vibe Coding Data-Enabled AI Apps* on Maven](https://maven.com/) - the paid live cohort that teaches the self-serve stack (Path 2). Recommended if accountability is your blocker.
+- Drew Falkman, *Vibe Coding Data-Enabled AI Apps* on Maven - the paid live cohort that teaches the self-serve stack (Path 2). Recommended if accountability is your blocker.
- Y Combinator, [Startup School: Customer Discovery](https://www.ycombinator.com/library/) - YC's distilled take on validating before building. The path-1 reading list.
- DHH, [The One Person Framework](https://world.hey.com/dhh/the-one-person-framework-711e6318) - the Rails case for keeping the architecture small enough that one developer can ship outcomes end-to-end. Reading for Path 2 and Path 3 founders.
- Veracode, [GenAI Code Security Report 2025](https://www.veracode.com/blog/genai-code-security-report/) - 45% of LLM-generated code shipped at least one exploitable security flaw. Context for why Path 2 needs the 1-hour-a-month architecture review.
-> **Done when:** You have answered the 5 questions on the worksheet and your build path is written at the top.
->
-> **Next click:** [4.2 · Who Owns Your GitHub, AWS, and Database?](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/)
+> **Done:** You have answered the 5 questions on the worksheet and your build path is written at the top.
>
-> **If blocked:** If your answer routes you to "hire a team" but your runway is under 4 months, you are reading the wrong path. Default to self-serve (Ch 4.3 (a + b)) and revisit hiring when a ceiling signal fires in Ch 4.4.
-
-> **Case Study: Tomas & Mia**
+> **You have now:** a quality-checked one-page brief (3.2) + a build-path decision (validate / self-serve / fractional CTO / hire), saved in your `Founder OS` folder.
>
-> **Tomas**: Runs the decision tree. Validated? Yes. Mid-complexity? Yes - needs Stripe + QuickBooks API. Has $200K+ runway? No - $80K savings. Routes to Fractional CTO bridge (Path 3). Builds core himself in Lovable with 5 hrs/week CTO oversight.
+> **Next:** [4.2 · Who Owns Your GitHub, AWS, and Database?](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/) - lock ownership before anything gets built on the path you just chose.
>
-> **Mia**: Runs the decision tree. Validated? Yes. Simple MVP? Yes - search + profiles + booking. 4-8 weeks free? Yes. Routes to self-serve build (Path 2). Builds everything herself in Lovable + Supabase + Stripe.
+> **If blocked:** If your answer routes you to "hire a team" but your runway is under 4 months, you are reading the wrong path. Default to self-serve (Ch 4.3-4.4) and revisit hiring when a ceiling signal fires in Ch 4.5.
---
+*See it in action: [Module 4 walkthrough: Mia ships TutorMatch](/course/tech-for-non-technical-founders-2026/module-4-walkthrough-mia/)*
+
*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/content/course/tech-for-non-technical-founders-2026/smoke-test-landing-page-7-day-demand-test/index.md b/content/course/tech-for-non-technical-founders-2026/smoke-test-landing-page-7-day-demand-test/index.md
index ddadb4024..5c865d864 100644
--- a/content/course/tech-for-non-technical-founders-2026/smoke-test-landing-page-7-day-demand-test/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/smoke-test-landing-page-7-day-demand-test/index.md
@@ -40,7 +40,7 @@ After this lesson you will be able to: **make a go / iterate / kill decision on
**Pick your ad channel** based on who your hypothesis names in the [customer] blank. The dollar ranges below are **CPC** (cost-per-click - what one ad click costs you):
- **Selling to individual people** → [Meta Ads](https://business.facebook.com/) ($0.70-$1.90 CPC). Best when the product is visual and the audience is broad.
-- **Selling to businesses, by job title** → [Google Search](https://ads.google.com/) ($3-$8 CPC) if your customer Googles the problem; [LinkedIn](https://www.linkedin.com/campaignmanager/) ($5.50-$22 CPC) if they don't.
+- **Selling to businesses, by job title** → [Google Search](https://ads.google.com/) ($3-$8 CPC) if your customer Googles the problem; [LinkedIn](https://www.linkedin.com/campaignmanager/) ($5.70-$22 CPC) if they don't.
- **Developer tools** → [Reddit Ads](https://ads.reddit.com/) ($1.25-$3 CPC) in r/programming, r/webdev, r/SaaS.
- **Niche vertical** → Google Search long-tail ($1-$5 CPC) - real estate, dentists, contractors Googling pain.
diff --git a/content/course/tech-for-non-technical-founders-2026/stop-specifying-features-start-outcomes/index.md b/content/course/tech-for-non-technical-founders-2026/stop-specifying-features-start-outcomes/index.md
index d785f6c90..c321948fe 100644
--- a/content/course/tech-for-non-technical-founders-2026/stop-specifying-features-start-outcomes/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/stop-specifying-features-start-outcomes/index.md
@@ -158,9 +158,9 @@ After finishing Ch 3.1-3.2, you have five artifacts. Each one feeds a specific d
| Artifact | Where it goes next |
|---|---|
-| **One-Page Product Brief / Vibe PRD** (Ch 3.1 output) | Ch 4.1 build-path decision (the brief is the input the worksheet routes against) + Ch 4.3 (a + b) Lovable kickoff prompt. The single source of truth Module 4 builds from. |
-| **Outcome-shaped feature list** (Ch 3.2 rewrite of Section 3 in Job Story format) | Ch 4.1 contractor SOW (Statement of Work - the document that tells a contractor exactly what to build) if you route to hire + Ch 4.3 (a + b) Lovable prompt body. Replaces the noun-shaped feature list that causes overbuild. |
-| **No-Go list** (5-8 items you explicitly cut from Ch 3.1 Section 5) | Ch 4.3 (a + b) self-serve scope guard + Ch 4.4 ceiling-signal monitoring. The written "we are not building this yet" line that prevents Module 4 scope creep. |
+| **One-Page Product Brief / Vibe PRD** (Ch 3.1 output) | Ch 4.1 build-path decision (the brief is the input the worksheet routes against) + Ch 4.3-4.4 Lovable kickoff prompt. The single source of truth Module 4 builds from. |
+| **Outcome-shaped feature list** (Ch 3.2 rewrite of Section 3 in Job Story format) | Ch 4.1 contractor SOW (Statement of Work - the document that tells a contractor exactly what to build) if you route to hire + Ch 4.3-4.4 Lovable prompt body. Replaces the noun-shaped feature list that causes overbuild. |
+| **No-Go list** (5-8 items you explicitly cut from Ch 3.1 Section 5) | Ch 4.3-4.4 self-serve scope guard + Ch 4.5 ceiling-signal monitoring. The written "we are not building this yet" line that prevents Module 4 scope creep. |
| **Audience-of-one fork** (the audience choice from Ch 3.1: AI agent / junior dev / senior team) | Ch 4.1 Q2 build-path routing. The fork decides whether the brief routes to Lovable (AI agent) or a contractor (junior or senior team). |
| **Quality-check verdict** (Ch 3.2 - peer answers "what would you build differently?" cleanly?) | Checkpoint before Module 4. If the peer cannot answer cleanly, return to Ch 3.2 and rewrite Section 3 before opening Lovable or sending the SOW. |
diff --git a/content/course/tech-for-non-technical-founders-2026/validation-tools-field-guide/index.md b/content/course/tech-for-non-technical-founders-2026/validation-tools-field-guide/index.md
index 748bff1ec..0eba0a186 100644
--- a/content/course/tech-for-non-technical-founders-2026/validation-tools-field-guide/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/validation-tools-field-guide/index.md
@@ -184,7 +184,7 @@ At the pre-interview stage, the $9 Starter is enough. You are looking for red fl
### Common mistakes
- **Paying $129 before you know what a $9 report looks like.** Run the Starter first. If it flags something specific that needs deeper investigation, upgrade.
-- **Treating it as a go/no-go decision.** The tool validates the *logic* of a business model, not the *demand*. A clean report means your idea is not obviously broken. It does not mean customers will pay. That requires Ch 1.2 (a + b)'s smoke test and Ch 2.1's interviews.
+- **Treating it as a go/no-go decision.** The tool validates the *logic* of a business model, not the *demand*. A clean report means your idea is not obviously broken. It does not mean customers will pay. That requires Ch 1.2-1.4's smoke test and Ch 2.1's interviews.
- **Ignoring the competitors it names.** The tool often surfaces competitors you did not know existed. Use these as starting points for your own manual research.
### Pro tips
@@ -288,7 +288,7 @@ No tool validates your hypothesis. Only ten strangers describing the problem in
These tools sharpen your hypothesis. They do not validate it. Specifically:
-**They cannot prove a real customer will pay.** A clean DimeADozen report and a Preuve score of 80 do not equal a signed Stripe checkout. That signal comes from Ch 1.2 (a + b)'s smoke-test landing page and Ch 5.4's Design Partner Agreement with a real deposit.
+**They cannot prove a real customer will pay.** A clean DimeADozen report and a Preuve score of 80 do not equal a signed Stripe checkout. That signal comes from Ch 1.2-1.4's smoke-test landing page and Ch 5.6's Design Partner Agreement with a real deposit.
**They cannot tell you whether the problem is real.** AI tools summarize what people have already said online. They cannot surface a problem that nobody has articulated publicly. The Mom Test interviews in Ch 2.1 surface what specific named humans actually did last Friday - a signal no AI tool can produce.
@@ -302,7 +302,7 @@ These tools sharpen your hypothesis. They do not validate it. Specifically:
- [Ch 1.1: Form Your Founding Hypothesis](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/) - write the Mad Libs sentence these tools stress-test.
- [Ch 2.1: The Mom Test - Ask About the Past, Not the Future](/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/) - validate the sharpened hypothesis with ten real interviews.
-- [Ch 1.2 (a + b): Smoke-Test the Hypothesis: The Demand Test](/course/tech-for-non-technical-founders-2026/smoke-test-landing-page-7-day-demand-test/) - the next step after these tools confirm your sentence is well-constructed.
+- [Ch 1.4 · Smoke Test: Run It and Read the Signal](/course/tech-for-non-technical-founders-2026/smoke-test-landing-page-7-day-demand-test/) - the next step after these tools confirm your sentence is well-constructed.
---
diff --git a/content/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/index.md b/content/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/index.md
index 0fb83e828..d55fb97b2 100644
--- a/content/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/index.md
+++ b/content/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/index.md
@@ -1,7 +1,7 @@
---
-title: "4.4 · Vibe Coding Done Right: 5 Ceiling Signals"
+title: "4.5 · Vibe Coding Done Right: 5 Ceiling Signals"
aliases: ["/blog/vibe-coding-ceiling-signals/"]
-description: "The 5 architectural ceiling signals that tell you the Lovable + Supabase + Stripe shed stopped holding. Two firing = graduate. Chapter 4.4 of the course."
+description: "The 5 architectural ceiling signals that tell you the Lovable + Supabase + Stripe shed stopped holding. Two firing = graduate. Chapter 4.5 of the course."
date: 2026-05-13
draft: false
course_chapter: true
@@ -23,18 +23,20 @@ categories: ["Founders"]
cover_image: cover.png
metatags:
image: cover.png
- og_title: "4.4 · Vibe Coding Done Right: 5 Ceiling Signals"
- og_description: "The 5 architectural ceiling signals that tell you the Lovable + Supabase + Stripe shed stopped holding. Two firing = graduate. Chapter 4.4 of the course."
+ og_title: "4.5 · Vibe Coding Done Right: 5 Ceiling Signals"
+ og_description: "The 5 architectural ceiling signals that tell you the Lovable + Supabase + Stripe shed stopped holding. Two firing = graduate. Chapter 4.5 of the course."
cover_image_alt: "JetThoughts cover with three hand-drawn buildings - a small shed, a two-story house, and a tall skyscraper - and a sticky note reading Two ceiling signals = graduate."
canonical_url: "https://jetthoughts.com/course/tech-for-non-technical-founders-2026/vibe-coding-ceiling-signals/"
related_posts: false
---
-> **Module 4 · Step 4 of 4** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
+> **Module 4 · Lesson 4.5 · [OPTIONAL] - a monthly review reference** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/)
>
-> **Input:** a live MVP on the self-serve stack (from [Chapter 4.3a · Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) + [4.3b · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/))
+> **Input:** a live MVP on the self-serve stack (from [Chapter 4.3 · Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) + [4.4 · Build Phases](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/))
>
> **Output:** a yes/no decision on whether to graduate to Module 5 (First Paying Customer) or hire or stay self-serve
+>
+> **Progress:** M4 · 5 of 5 · [OPTIONAL] - a recurring monthly check once your MVP is live; the core path continues at 5.1
> **TL;DR:** Five architectural signals that mean the self-serve stack is maxed out. Two firing for 4+ weeks = graduate to a fractional CTO or hire. Run this check monthly once your MVP is live.
@@ -46,17 +48,17 @@ Two of your users keep landing on each other's data because the [Supabase](https
The ceiling is visible now, but it was visible two months earlier too. That's when this check should have caught it.
-**Vibe Coding** is shipping a real product with AI-generated code from tools like Lovable, Cursor, or Bolt - no engineer, no dev shop, no months of build. The term comes from indie founder Pieter Levels and describes the 2026 default for solo non-technical founders. This chapter is about the moment the shed stops holding.
+**Vibe Coding** is shipping a real product with AI-generated code from tools like Lovable, Cursor, or Bolt - no engineer, no dev shop, no months of build. The term was coined by Andrej Karpathy in early 2025; indie founder Pieter Levels made it famous in practice and describes the 2026 default for solo non-technical founders. This chapter is about the moment the shed stops holding.
Once your build goes live, run this 5-signal check monthly. Each signal that fires earlier saves rebuilds later. This is a proactive monitoring habit, not a post-mortem - the goal is to catch the ceiling before you slam into it.
-> **This chapter is a monthly review reference, not an action-today chapter.** Your only action today: open your calendar and add a recurring monthly block titled "Vibe-coding 5-signal check." The first run is once the live MVP is up (Ch 4.3 (a + b)); until then, the chapter sits on the shelf. If you haven't shipped a live MVP yet, bookmark this and come back the moment you have real users clicking around. The morning scene above is what the ceiling looks like when it actually arrives.
+> **This chapter is a monthly review reference, not an action-today chapter.** Your only action today: open your calendar and add a recurring monthly block titled "Vibe-coding 5-signal check." The first run is once the live MVP is up (Ch 4.3-4.4); until then, the chapter sits on the shelf. If you haven't shipped a live MVP yet, bookmark this and come back the moment you have real users clicking around. The morning scene above is what the ceiling looks like when it actually arrives.
## Who this 5-signal check is for
-The Lovable + Supabase + Stripe shed from [The Self-Serve MVP Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) holds most pre-seed B2B SaaS workloads. The remainder is what this post is about.
+The Lovable + Supabase + Stripe shed from [The Self-Serve MVP Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) handles the common early-SaaS build. The builds it cannot hold are what this post is about.
Run this check monthly once your MVP is live and the ceiling shows up while it is still a tuning problem. Wait until something breaks - slow dashboard, duplicate webhooks, support tickets climbing - and you are paying late-fix prices on what was an early-fix problem.
@@ -102,11 +104,11 @@ New features take twice as long as they did in month two.
It writes a query that ignores a join, or it adds a column to one screen but not the migration. The schema decays from edits.
-**Cost of leaving it alone**: a fitness-coaching SaaS we picked up in Q1 2026 had 11,000 lines of Lovable-generated code, no foreign keys, every model named in the singular, and three customer accounts with corrupted data because a webhook had retried a Stripe charge update four times.
+**Cost of leaving it alone**: a fitness-coaching SaaS we reviewed in early 2026 had 11,000 lines of Lovable-generated code, no foreign keys, every model named in the singular, and three customer accounts with corrupted data because a webhook had retried a Stripe charge update four times.
The founder shipped six features in month four and zero in months five and six because every change surfaced something else.
-**Cost of addressing now**: a 2-hour [Fractional CTO](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge) schema review (~$400 at $200/hour). They sketch the proper entity-relationship diagram, identify the joins your current schema is missing, and tell you whether the next 10 features fit on the current schema or need a redesign. If the verdict is "rebuild on a real ORM," route to [Reading the SOW](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#reading-the-sow).
+**Cost of addressing now**: a 2-hour [Fractional CTO](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge) schema review (roughly $160-$240 - two hours at the $80-$120/hour fractional band). They sketch the proper entity-relationship diagram, identify the joins your current schema is missing, and tell you whether the next 10 features fit on the current schema or need a redesign. If the verdict is "rebuild on a real ORM," route to [Reading the SOW](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#reading-the-sow).
### Signal 3: Real-time features becoming non-negotiable (detectable: Week 4-8)
@@ -215,22 +217,22 @@ Q1 Yes + Q2 No: graduate to the [Fractional CTO bridge](/course/tech-for-non-tec
Three actions. The first is tonight.
- **Open your Lovable + Supabase admin dashboard tonight.** Pull up: the 30-day request error rate, the 30-day Stripe webhook retry log, the active user count, and last month's OpenAI / Anthropic invoice if you use one. Five minutes of dashboard time is the input to the scoreboard.
-- **Score each of the 5 signals: green / yellow / red, AND log Date first observed + Date last observed per signal.** Use the scoreboard above. Green = no symptom yet. Yellow = symptom showing in the last 30 days but recoverable. Red = symptom firing 4+ weeks AND you've patched it more than once. Without dated observation windows you cannot tell the "fired once this week" from the "fired every week for two months" signal, and the 4-week graduation rule below collapses. Keep the scoreboard as a Notion table or a sheet with columns: Signal | Status | Date first observed | Date last observed | Notes. Score green when the symptoms are firing and you arrive at the [salvage-or-rebuild thread](/course/tech-for-non-technical-founders-2026/salvage-vs-rebuild-decision-tree/) at month nine - by then the rebuild estimate is months of work you could have caught in days.
+- **Score each of the 5 signals: green / yellow / red, AND log Date first observed + Date last observed per signal.** Use the scoreboard above. Green = no symptom yet. Yellow = symptom showing in the last 30 days but recoverable. Red = symptom firing 4+ weeks AND you've patched it more than once. Without dated observation windows you cannot tell the "fired once this week" from the "fired every week for two months" signal, and the 4-week graduation rule below collapses. Keep the scoreboard as a Notion table or a sheet with columns: Signal | Status | Date first observed | Date last observed | Notes. Skip the dated logging and you arrive at the [salvage-or-rebuild thread](/course/tech-for-non-technical-founders-2026/salvage-vs-rebuild-decision-tree/) at month nine - by then the rebuild estimate is months of work you could have caught in days.
- **If 2 or more signals are red AND have been red for ≥4 consecutive weeks (per the flowchart Q1 above), start the [Fractional CTO bridge](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/#the-fractional-cto-bridge) THIS WEEK.** The 4-week window is the load-bearing qualifier; two reds in one week is a tuning problem, not a graduation signal. Not next month, not after the next sprint - once the 4-week mark hits, the Fractional CTO conversation is one Calendly invite away and the first call is usually free. The bridge holds until you have the runway clarity for a full hire.
## Artifacts you carry out of Module 4
-After finishing Ch 4.1-4.4, you have five artifacts. Each one feeds a specific downstream destination - this table is the map:
+After finishing Ch 4.1-4.5, you have five artifacts. Each one feeds a specific downstream destination - this table is the map:
| Artifact | Where it goes next |
|---|---|
-| **Build-path decision** (validate / self-serve / fractional CTO / hire - chosen and dated, from Ch 4.1) | Module 5 outbound posture. The build path determines whether you sell a live MVP (self-serve, hire) or a Carrd + Stripe pre-sale (validate path), which decides the Ch 5.2-5.5 scripts you use. |
-| **Ownership audit results** (12-item checklist - GitHub, AWS root, billing, IAM, DB credentials, secrets store, backups, domain, DNS, third-party keys, monitoring, status page - all on your company email, from Ch 4.2) | Module 5 contract foundations. The Ch 5.4 Design Partner Agreement assumes you own the production environment. If ownership is split, fix that before sending any DPA. |
-| **Shipped MVP** (live URL + first 4-6 user accounts if self-serve, OR live URL + contractor weekly demo cadence if hired, from Ch 4.3 (a + b)) | Ch 5.1 must-have test denominator. The 40% test needs 10-30 users who actually touched the MVP; the first 4-6 are the starting cohort. |
-| **Monthly ceiling-signal scorecard** (the 5 signals from Ch 4.4, first run once the live MVP is up) | Recurring monthly check from live launch onward. The scorecard is the early-warning system that decides whether you stay self-serve or graduate while you sell. |
-| **Output for Module 5: 4-6 active users as the starting cohort + a path to 10+ via Ch 2.3-2.4 outreach** (from Ch 4.3 (a + b) onboarding) | Ch 5.1 Sean Ellis 40% test input. 4-6 is the directional starting cohort - Ch 5.1's "Under-10 respondents" sidebar reads that as MAYBE, not a verdict. Re-engage your Ch 2.3-2.4 interview leads as Ch 5.1 invites to get above 10 for a confident reading. Their Q2-Q3 verbatims become the persona language for Ch 5.2-5.5 outbound. |
+| **Build-path decision** (validate / self-serve / fractional CTO / hire - chosen and dated, from Ch 4.1) | Module 5 outbound posture. The build path determines whether you sell a live MVP (self-serve, hire) or a Carrd + Stripe pre-sale (validate path), which decides the Ch 5.2-5.7 scripts you use. |
+| **Ownership audit results** (12-item checklist - GitHub org owner, repo collaborators, branch protection, AWS root, billing, IAM, DB credentials, secrets store, backups, domain, DNS, third-party keys - all on your company email, from Ch 4.2) | Module 5 contract foundations. The Ch 5.6 Design Partner Agreement assumes you own the production environment. If ownership is split, fix that before sending any DPA. |
+| **Shipped MVP** (live URL + first 4-6 user accounts if self-serve, OR live URL + contractor weekly demo cadence if hired, from Ch 4.3-4.4) | Ch 5.1 must-have test denominator. The 40% test needs 10-30 users who actually touched the MVP; the first 4-6 are the starting cohort. |
+| **Monthly ceiling-signal scorecard** (the 5 signals from Ch 4.5, first run once the live MVP is up) | Recurring monthly check from live launch onward. The scorecard is the early-warning system that decides whether you stay self-serve or graduate while you sell. |
+| **Output for Module 5: 4-6 active users as the starting cohort + a path to 10+ via Ch 2.3-2.4 outreach** (from Ch 4.3-4.4 onboarding) | Ch 5.1 Sean Ellis 40% test input. 4-6 is the directional starting cohort - Ch 5.1's "Under-10 respondents" sidebar reads that as MAYBE, not a verdict. Re-engage your Ch 2.3-2.4 interview leads as Ch 5.1 invites to get above 10 for a confident reading. Their Q2-Q3 verbatims become the persona language for Ch 5.7 outbound. |
-Two ceiling signals firing for 4+ weeks means the shed is no longer holding. Both beat watching the codebase get worse.
+Two ceiling signals firing for 4+ weeks means the shed is no longer holding. Either hire a team if you have the runway, or bridge with a Fractional CTO until you do - both beat watching the codebase get worse.
## Further reading
@@ -239,23 +241,21 @@ Two ceiling signals firing for 4+ weeks means the shed is no longer holding. Bot
- Veracode, [GenAI Code Security Report 2025](https://www.veracode.com/blog/genai-code-security-report/) - 45% of LLM-generated code shipped at least one exploitable security flaw. The data behind why the compliance signal fires.
- Supabase, [Realtime documentation](https://supabase.com/docs/guides/realtime) and [Row-Level Security guide](https://supabase.com/docs/guides/database/postgres/row-level-security) - the official boundary between what Supabase serves well and where the data-model and real-time signals begin.
- OpenAI, [Rate limits documentation](https://platform.openai.com/docs/guides/rate-limits) - the per-tier request and token caps that drive the AI-inference signal once your traffic crosses a threshold.
-- Vanta, [SOC2 readiness for early-stage SaaS](https://www.vanta.com/resources/soc-2-compliance-checklist) - the audit-surface checklist most founders see for the first time when their first enterprise customer asks for a SOC2 letter.
+- Vanta, [SOC2 readiness for early-stage SaaS](https://www.vanta.com/resources/soc-2-compliance-checklist) - the audit-surface checklist a founder usually meets for the first time when an enterprise customer asks for a SOC2 letter.
- Y Combinator, [Startup School Library + 2026 Founder Resources](https://www.ycombinator.com/library/) - the YC stance on validating without code and the changing role of the technical co-founder. Read before any framework decision.
-> **Done when:** You have scored all 5 signals (green/yellow/red) with dated observation windows and set a recurring monthly calendar block titled "Vibe-coding 5-signal check."
->
-> **Next click:** [5.1 · Your First Customer Is Not a Marketing Problem](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/)
+> **Done:** you have scored all 5 signals (green/yellow/red) with dated observation windows and set a recurring monthly calendar block titled "Vibe-coding 5-signal check."
>
-> **If blocked:** If 2+ signals are red but you are not sure whether to hire, book one free Fractional CTO call. The first call is usually free and the diagnosis alone is worth the hour.
-
-> **Module 4 closes here.** Before opening Module 5, you should have: (1) a build-path decision from the Ch 4.1 tree (self-serve / fractional CTO / hire), (2) a Day-1 ownership audit passed (Ch 4.2 - GitHub + AWS + domain all in your name), (3) a live MVP at a real URL with 5 ICP users tested + 5 green lights lit (Ch 4.3b), and (4) a monthly 5-signal ceiling check on the calendar (this chapter). All four in your `Founder OS` folder. Missing one? Go back - Module 5 invites your Module 2 interviewees + smoke-test email list to your URL; if there's no URL, there's no Module 5.
-
-> **Case Study: Tomas & Mia**
+> **You have now:** a live MVP (4.3-4.4) + a monthly ceiling-signal scorecard (4.5) that tells you, each month, whether to stay self-serve, bridge to a fractional CTO, or hire. Module 4 is done. Whether to graduate is now a dated, repeatable check instead of a guess.
>
-> **Tomas**: At ~50 firms, 2 ceiling signals fire: reconciliation matching has race conditions, n8n QuickBooks connector breaks on API changes. Graduates from self-serve → fractional CTO → hired team. CTO already in place, transition is smooth.
+> **Next:** the core path continues at [5.1 · Your First Customer Is Not a Marketing Problem](/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/) - it takes the first users on your live MVP and tests whether they would miss it before you spend on ads.
>
-> **Mia**: At ~200 parents, 2 ceiling signals fire: search takes 4 seconds, booking confirmation emails show wrong timezone. Graduates to fractional CTO at 5 hrs/week to fix the search query and timezone logic.
+> **If blocked:** if 2+ signals are red but you are not sure whether to hire, book one free Fractional CTO call. The first call is usually free and the diagnosis alone is worth the hour.
+
+> **Module 4 closes here.** Before opening Module 5, you should have: (1) a build-path decision from the Ch 4.1 tree (self-serve / fractional CTO / hire), (2) a Day-1 ownership audit passed (Ch 4.2 - GitHub + AWS + domain all in your name), (3) a live MVP at a real URL with 5 ICP users tested + 5 green lights lit (Ch 4.4), and (4) a monthly 5-signal ceiling check on the calendar (this chapter). All four in your `Founder OS` folder. Missing one? Go back - Module 5 invites your Module 2 interviewees + smoke-test email list to your URL; if there's no URL, there's no Module 5.
---
+*See it in action: [Module 4 walkthrough: Mia ships TutorMatch](/course/tech-for-non-technical-founders-2026/module-4-walkthrough-mia/)*
+
*Built by [JetThoughts](https://jetthoughts.com) as part of the [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) curriculum.*
diff --git a/data/course_banned_strings.yaml b/data/course_banned_strings.yaml
index bab256b7a..c746de31d 100644
--- a/data/course_banned_strings.yaml
+++ b/data/course_banned_strings.yaml
@@ -20,7 +20,7 @@ banned:
reason: "em-dash replacement artifact"
- string: "Case Study: Tomas & Mia"
reason: "case studies live only in module-end walkthroughs (30.03 §2.7) - applies to migrated modules M1/M2/M3; remove entries per module as each migrates"
- scope: "mom-test-|ai-persona-|find-10-|clickable-prototype|smoke-test-|form-your-founding|price-hypothesis|module-1-|module-2-|module-3-|outreach-sequence|validated-problem|one-page-product-brief|stop-specifying|vibe-prd-template"
+ scope: "mom-test-|ai-persona-|find-10-|clickable-prototype|smoke-test-|form-your-founding|price-hypothesis|module-1-|module-2-|module-3-|module-4-|module-5-|outreach-sequence|validated-problem|one-page-product-brief|stop-specifying|vibe-prd-template|should-you-hire|github-aws-database|self-serve-mvp-stack|vibe-coding-ceiling|must-have-segment|channel-selection|first-ten-customers|paid-pilot-charge|outbound-without"
- string: "<5 of 10 scored"
reason: "gate is 7+/4-6/<4 (canonical: mom-test-synthesis)"
- string: "fewer than 5 scores"
@@ -146,3 +146,65 @@ banned:
reason: "second fake-specific 17 on the 3.1 page"
- string: "founder I spoke with ended up with 17"
reason: "Sarah's 3.1 anecdote must not be re-attributed anonymously"
+ - string: "Artifact #5 of 6"
+ reason: "hardcoded artifact index retired in 4.4 v2 footer (2026-07-10)"
+ - string: "Artifact #6 of 6"
+ reason: "hardcoded artifact index retired in 5.6 v2 footer"
+ - string: "typically $200/hr"
+ reason: "single-point fractional rate presented as the norm; bands with sources are fine"
+ - string: "at $200/hour"
+ reason: "single-point fractional rate; use hedged band (quoted dialogue rates are fine)"
+ - string: "$8-15K/mo"
+ reason: "inflated year-stamped fractional monthly rate"
+ - string: "35 cold outreach"
+ reason: "outreach-count drift; canon is the 30-name list"
+ - string: "from 35 prospects"
+ reason: "outreach-count drift; canon 30"
+ - string: "3a of 7"
+ reason: "retired letter-suffix progress label"
+ - string: "3b of 7"
+ reason: "retired letter-suffix progress label"
+ - string: "3c of 7"
+ reason: "retired letter-suffix progress label"
+ - string: "outreach complete (5.3-5.7)"
+ reason: "warm arc is 5.3-5.5"
+ - string: "Module 5, Step 2 of 5"
+ reason: "stale 5-lesson count; M5 is 7 lessons"
+ - string: "2.9% + $0.30"
+ reason: "hardcoded Stripe rate; capability language + pricing link"
+ - string: "Most paying-MVP founders"
+ reason: "cohort-generalization near-miss"
+ - string: "Most pre-seed founders"
+ reason: "cohort-generalization near-miss"
+ - string: "founders we pick up"
+ reason: "rescue framing in course bodies (off-ICP)"
+ - string: "Chapter 5.2 outreach starts here"
+ reason: "outreach is 5.3; 5.2 is optional channel selection"
+ - string: "Advance to M5.2"
+ reason: "core path routes 5.1 to 5.3"
+ - string: "most founders see"
+ reason: "lowercase cohort-generalization dodge"
+ scope: "vibe-coding-ceiling|should-you-hire|self-serve-mvp-stack|must-have-segment|channel-selection|first-ten-customers|paid-pilot-charge|outbound-without|module-[1-5]-|mom-test-|find-10-|smoke-test-|form-your-founding|price-hypothesis|one-page-product|stop-specifying"
+ - string: "pre-seed B2B SaaS workloads"
+ reason: "quantified workload claim (any phrasing)"
+ - string: "we picked up in Q"
+ reason: "rescue framing + quarter-stamp in course bodies (Going Further rescue chapters exempt)"
+ scope: "mom-test-|ai-persona-|find-10-|clickable-prototype|smoke-test-|form-your-founding|price-hypothesis|module-[1-5]-|one-page-product-brief|stop-specifying|should-you-hire|github-aws-database|self-serve-mvp-stack|vibe-coding-ceiling|must-have-segment|channel-selection|first-ten-customers|paid-pilot-charge|outbound-without|build-path-decision"
+ - string: "spending a dollar on ads"
+ reason: "voice-guide banned defensive cost-anxiety phrasing"
+ - string: "Part 1 of Chapter 4.3"
+ reason: "4.3/4.4 are separate lessons; Part framing retired"
+ - string: "Part 2 of 2"
+ reason: "lettered lessons are gone; Part framing retired course-wide"
+ scope: "self-serve-mvp-stack|find-10-people|first-ten-customers|smoke-test-"
+ - string: "$400 refundable deposit"
+ reason: "below the $500 pilot-deposit floor (5.6 canon)"
+ - string: "56% on a sample of 22"
+ reason: "fabricated-precision stat on an unnamed company"
+ - string: "Module 5, Step 2 of 7"
+ reason: "stale off-template mini-footer (Step vocabulary retired)"
+ - string: "called eleven places in March"
+ reason: "M2 walkthrough owns this canon quote; no reuse in other walkthroughs"
+ scope: "module-1-|module-3-|module-4-|module-5-"
+ - string: "It is the highest response rate you will ever see"
+ reason: "every/never claim + fabricated precision"
diff --git a/data/course_sequence.yaml b/data/course_sequence.yaml
index fceecb77c..5307949a4 100644
--- a/data/course_sequence.yaml
+++ b/data/course_sequence.yaml
@@ -107,18 +107,18 @@ sequence:
goal: "Confirm you own your code, cloud, domain, and database before any build starts."
- slug: self-serve-mvp-stack-lovable-supabase-stripe-2026
- title: "4.3a · The Self-Serve MVP Stack: Tools & Setup"
- module: "Chapter 4.3a"
+ title: "4.3 · The Self-Serve MVP Stack: Tools & Setup"
+ module: "Chapter 4.3"
goal: "Understand why Lovable + Supabase + Stripe is the dominant self-serve path and lock in the 3 pre-flight rules."
- slug: self-serve-mvp-stack-build-phases
- title: "4.3b · The Self-Serve MVP Stack: Build Phases"
- module: "Chapter 4.3b"
+ title: "4.4 · The Self-Serve MVP Stack: Build Phases"
+ module: "Chapter 4.4"
goal: "Execute the 4 build phases (Lovable UI → Supabase auth → Stripe checkout → live deploy) and pass the 5 green lights."
- slug: vibe-coding-ceiling-signals
- title: "4.4 · Vibe Coding Done Right: 5 Ceiling Signals"
- module: "Chapter 4.4"
+ title: "4.5 · Vibe Coding Done Right: 5 Ceiling Signals"
+ module: "Chapter 4.5"
goal: "Spot the 5 architectural signals that mean it's time to graduate beyond no-code."
- slug: must-have-segment-pmf-test
@@ -132,26 +132,26 @@ sequence:
goal: "Pick one outreach channel you'll commit to before scaling."
- slug: first-ten-customers-network-list
- title: "5.3a · Build Your 50-Name Network List"
- module: "Chapter 5.3a"
+ title: "5.3 · Build Your 50-Name Network List"
+ module: "Chapter 5.3"
goal: "Sort 50 names into 4 outreach buckets so you know exactly who to message first."
- slug: first-ten-customers-outreach-message
- title: "5.3b · Write the Outreach Message"
- module: "Chapter 5.3b"
+ title: "5.4 · Write the Outreach Message"
+ module: "Chapter 5.4"
goal: "Write 4 outreach message variants (one per bucket) and record a 90-second Loom that gets replies."
- slug: first-ten-customers-send-track
- title: "5.3c · Send, Track, and Read the Replies"
- module: "Chapter 5.3c"
+ title: "5.5 · Send, Track, and Read the Replies"
+ module: "Chapter 5.5"
goal: "Send 50 messages in the right sequence, track replies in a spreadsheet, and diagnose what a no actually means."
- slug: paid-pilot-charge-before-ship
- title: "5.4 · Charge Before You Ship: The Paid Pilot Contract"
- module: "Chapter 5.4"
+ title: "5.6 · Charge Before You Ship: The Paid Pilot Contract"
+ module: "Chapter 5.6"
goal: "Sign a Design Partner Agreement with a refundable Stripe deposit before writing new code."
- slug: outbound-without-sales-team
- title: "5.5 · Going Outbound Without a Sales Team"
- module: "Chapter 5.5"
+ title: "5.7 · Going Outbound Without a Sales Team"
+ module: "Chapter 5.7"
goal: "Send 30 filtered cold messages and book 1-2 paid pilots after the warm-network pass."
diff --git a/docs/projects/2605-tech-for-non-technical-founders/40-49-review/40.16-m4-m5-release-gate-2026-07-10.md b/docs/projects/2605-tech-for-non-technical-founders/40-49-review/40.16-m4-m5-release-gate-2026-07-10.md
new file mode 100644
index 000000000..d0faf91ee
--- /dev/null
+++ b/docs/projects/2605-tech-for-non-technical-founders/40-49-review/40.16-m4-m5-release-gate-2026-07-10.md
@@ -0,0 +1,44 @@
+# 40.16 - Modules 4+5 Release Gate (2026-07-10)
+
+**Branch**: `modules-4-5-v2` · **Sprint shape**: renumber → 6-agent conversion swarm → walkthroughs → 2 cold-eyes review rounds (8 reviewers, different lenses each) → visual scroll gate → gates.
+
+## What shipped
+
+1. **Flat renumber**: 4.3a/4.3b → 4.3/4.4, ceiling → 4.5; 5.3a/b/c → 5.3/5.4/5.5, paid pilot → 5.6, outbound → 5.7. Slugs stable, ~120 cross-references swept, cascade collisions (4.3-4.5, 5.3-5.7 ranges) caught and fixed.
+2. **All 12 M4/M5 lessons on the v2 template** (6 parallel converter agents, disjoint file ownership, zero collisions): Progress chains, TL;DRs, 4-slot footers, optional routing (4.5/5.2/5.7), Artifact #5/#6 indexes retired, 11 case blocks removed, glosses throughout.
+3. **Module 4 + Module 5 Mia walkthroughs** + See-it-in-action wiring in all 12 lessons (same commit).
+4. **Old-spine archaeology**: chapter 7.x/8/9 ghosts in pivot-or-persevere + churn-triage; "Part 2 of 2" framing in 2.4 AND 4.3/4.4; stale "manage-your-team" banners (from #352's review) - all gone.
+5. **Visual scroll gate**: 6 M4/M5 mermaids verified; 4.1 (1897px) and 4.2 (1608px) compressed to ~1050px; zero overflow both viewports; walkthroughs verified mobile.
+
+## Review rounds (all findings fixed unless noted)
+
+| Round | Lens | Verdict / count |
+|---|---|---|
+| R1 | ICP read-back | 6 findings (Part-framing, deposit, optional-5.2 tally...) |
+| R1 | Template + consistency | 11 (deposit floor, Q-routing, trio cover frontmatter...) |
+| R1 | Voice + AI-tells | 13 (4 ban-dodges, walkthrough aphorism stacks...) |
+| R1 | Boundary + Mia canon | 5 (deposit blocker, build-pace calibration...) |
+| R2 | End-to-end spine walk | 4 (5K/10K ceiling contradiction, 8→6 artifacts, Founder OS folder origin, Stripe fee) + explicit clean-list |
+| R2 | Unbriefed stranger | 12 trust-breaks (persona whiplash in 5.1 opener, no-coding tension, gate double-definition...) + 3 keep-list items |
+| R2 | Claims + citations | 15 (Karpathy coined vibe coding, Ellis misattribution, ICANN 14-day myth, funnel math, WorthBuild removed...) |
+| R2 | Diff regression | 4 (orphaned 5.3→b→c, rate contradiction between two fresh edits, ratchet scoping) |
+
+Three reviewers independently converged on the same blocker (Mia's $400 deposit below the course's own $500 floor) - fixed to $600 with the ACV math shown.
+
+## Triage decisions worth recording
+
+- **OpenHunts stats KEPT**: r2-claims flagged them unverifiable, but the primary source was verified via web search in the M3 sprint (openhunts.com/blog/tech-product-launch-statistics-insights) and is cited directly. Reviewer lacked web access.
+- **$80-$120/hr fractional band KEPT**: repo-canonical (hire-track cites Bolster/Toptal); r2-claims' higher market prior noted but unsourced. Revisit if a citable 2026 source lands.
+- **First-party anecdotes KEPT** ($1,800×5 pre-sale in 4.1): policy-compliant "we know a founder" framing.
+- **5.1 hedging-stack + $50K/$30K/$10K scary-number drift**: recorded as P3 polish, not blocking (stranger findings 4, 9).
+- **4.4 callout wall**: partially relieved (one demoted to prose); full re-rhythm is a P3.
+- **Series-A off-ramp box in 4.1**: kept - deliberate boundary-setting.
+
+## Gates at close
+
+8/8 validators (ratchet now 100+ signatures; caught out-of-scope live instances 4 separate times this sprint); test:critical 46 runs / 84 screenshots clean ×3 runs; production link sweep 0 missing ×3; visual scroll gate per docs/workflows/visual-scroll-gate.md.
+
+## Carry-forwards
+
+- P3: 5.1 sample-size callout consolidation; scary-number unification (landing $50K / 4.1 $30K / quickstart $10K+); 4.4 callout-wall full re-rhythm; cover sticky-note "Ship by Friday week 4" vs body's part-time calibration (regen covers if facts drift further).
+- Course COMPLETE on the v2 template after this merges - all 5 modules + 5 walkthroughs. Next stream: Phase 3 cross-cutting polish (30.03 §8) or distribution prep, user's call.
diff --git a/docs/projects/2605-tech-for-non-technical-founders/PROJECT-INDEX.md b/docs/projects/2605-tech-for-non-technical-founders/PROJECT-INDEX.md
index 4a8d5c8a1..e880a1b2c 100644
--- a/docs/projects/2605-tech-for-non-technical-founders/PROJECT-INDEX.md
+++ b/docs/projects/2605-tech-for-non-technical-founders/PROJECT-INDEX.md
@@ -1,7 +1,7 @@
# Project 2605 - Master Index
**Project**: Tech for Non-Technical Founders 2026
-**Status**: 🟢 Course LIVE (PR #345) · 🟢 M2 v2 COMPLETE on PR #351 (awaiting merge) · 🔲 M3 next
+**Status**: 🟢 Course LIVE (PR #345) · 🟢 M1-M3 live (PRs #345/#351/#352) · 🟢 M4+M5 v2 complete on branch modules-4-5-v2 (PR pending) · course fully on v2 template
**Last Updated**: 2026-07-10 (M2 done: flattened 2.1-2.6 with Synthesis as 2.5, walkthrough, all review rounds closed, regression ratchet validator live - see 40.12/40.13/40.14)
**Parent**: `../2510-seo-content-strategy/`
diff --git a/docs/projects/2605-tech-for-non-technical-founders/TASK-TRACKER.md b/docs/projects/2605-tech-for-non-technical-founders/TASK-TRACKER.md
index 25e6d057a..b9516bff9 100644
--- a/docs/projects/2605-tech-for-non-technical-founders/TASK-TRACKER.md
+++ b/docs/projects/2605-tech-for-non-technical-founders/TASK-TRACKER.md
@@ -1,8 +1,8 @@
# Task Tracker - 2605 Tech for Non-Technical Founders
-**Last Updated**: 2026-07-10 (M2 v2 migration COMPLETE on PR #351 - awaiting merge. All review rounds closed, 65-finding fan-out fixed, regression ratchet live.)
+**Last Updated**: 2026-07-10 (M4+M5 v2 COMPLETE on branch modules-4-5-v2 - the whole course is now on the v2 template. Gate report: 40.16.)
-## Active Phase: M2 release (PR #351 ready) → next: M3 migration
+## Active Phase: M4+M5 release (PR pending) → next: Phase 3 cross-cutting polish or distribution prep
**🚀 What shipped 2026-07-09..10: Module 2 v2 complete (PR #351, 20 commits)**
- ✅ All chapters on the M1 v2 template; numbering FLATTENED to 2.1-2.6 (letters retired; Synthesis is Lesson 2.5, in yaml prev/next). Chapter count derives 25 via course-stat.