From a212bffbbe13238661a17f88adf7002629ad87bf Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 00:55:23 +0200 Subject: [PATCH 01/12] feat(course-w5): 1.4 long-wait bridge Co-Authored-By: Claude Fable 5 --- .../smoke-test-landing-page-7-day-demand-test/index.md | 8 ++++++++ 1 file changed, 8 insertions(+) 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 28c99ef9be..33b6faf797 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 @@ -78,6 +78,14 @@ You will not have to figure out the ad on your own: the launch checklist below l **Success check:** you have a conversion rate from ≥300 cold visits AND a go/iterate/kill decision written down. +## While the 5-7 days pass + +The ads run for 5-7 days before 300 visits land. Camping on the dashboard won't speed it up, and the number means nothing until the traffic is in. Use the wait to get a head start on Module 2. + +In [Lesson 2.3](/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/) you'll need a list of 30 people who have posted about the problem your page names - that list is what makes the interview outreach work. Start it now: open a spreadsheet and, in one sitting, write down 10-15 names you have seen complain about this problem - in a subreddit, a Slack group, wherever your customer hangs out - and paste the exact post next to each name. Module 2 opens with the slowest part already moving. + +**Come back when your campaign dashboard shows 300 landing-page views.** That is the wait over: read your conversion rate against the meter above, then start the price test. + ## If the number looks wrong **If this fails: conversion is below 3%.** From 2158aad6f2f17122fbd20b033ba3d6a977179daa Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 00:55:23 +0200 Subject: [PATCH 02/12] feat(course-w5): 1.5 long-wait bridge Co-Authored-By: Claude Fable 5 --- .../price-hypothesis-on-smoke-test-page/index.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/course/tech-for-non-technical-founders-2026/price-hypothesis-on-smoke-test-page/index.md b/content/course/tech-for-non-technical-founders-2026/price-hypothesis-on-smoke-test-page/index.md index 51861635aa..f8ee82658c 100644 --- a/content/course/tech-for-non-technical-founders-2026/price-hypothesis-on-smoke-test-page/index.md +++ b/content/course/tech-for-non-technical-founders-2026/price-hypothesis-on-smoke-test-page/index.md @@ -71,6 +71,14 @@ Pick one pattern. Do not A/B test - 150 visits each on a $300 budget can't disti > 5. Paste the Payment Link URL on your CTA button. Below it, smaller text: "Not ready? Join the waitlist instead." > 6. **Success check:** your Stripe dashboard shows live-mode (not test-mode) and the button opens a real checkout page. +## While Stripe verifies + +Verification takes 1-3 business days, and live payments won't work until it clears. You don't have to sit idle - build the whole button in test mode now, so the day Stripe clears you paste one link and launch. + +Stripe's test mode is on the moment you sign up. Create the Payment Link (step 2), wire the after-payment redirect (step 3), and run a test checkout on yourself with Stripe's test card `4242 4242 4242 4242` - it walks the full flow without charging anything. Add the refund line to your footer while you're in there, and everything but the live link is done. + +**Come back when your Stripe dashboard shows the account verified - the live-mode toggle stops being greyed out.** Flip the link to live mode, paste the live URL on your button, and re-run one checkout to confirm it charges for real. + ## If Stripe or checkout stalls **If this fails: Stripe verification takes more than 3 days.** From 63e4d0e5a5c219dd95c7ae5e340c00af1ced88e3 Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 00:55:23 +0200 Subject: [PATCH 03/12] feat(course-w5): 2.4 long-wait bridge Co-Authored-By: Claude Fable 5 --- .../find-10-people-with-problem-outreach-2026/index.md | 8 ++++++++ 1 file changed, 8 insertions(+) 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 34e2a31df1..3459afa987 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 @@ -94,6 +94,14 @@ Cold outreach is the main track. Two others run alongside it when they fit: Both tracks, the parallel-run logic, and the part-time founder's batch-send variant are in the [full reference](/course/tech-for-non-technical-founders-2026/reference/find-10-people-full/). +## While the replies trickle in + +Booking 10 calls takes 2-4 weeks - messages go out, a few replies land, you send the next batch, more land. The calendar sits half-full for days at a stretch, and that is where momentum usually dies. Two things keep it moving. + +Don't wait for all 10 before you start. The day a third call is booked, start running interviews with the [Lesson 2.1 script](/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/) - early calls tell you fast whether your questions are landing, and you can fix them before the later ones. While the replies come in, set up the kit in one sitting: open the 2.1 five-question script, make a blank one-page notes doc you'll copy for each person, and put your 20-minute slots into your [NeetoCal](https://www.neeto.com/neetocal) link so booking is one click for them. + +**Come back when 3 calls are booked - and run them, don't hold for 10.** Keep the outreach batches going in the background until the calendar hits 10; the Done below still fires at 10. + > **Done:** 10 interview calls are booked on your calendar and you have sent the first batch of outreach messages. > > **You have now:** question list (2.1-2.2) + 30-name list (2.3) + 10 booked interviews (2.4). The problem itself is still unvalidated - the interviews you run next test it. From e1841e07aea8ab60d87b8447c7434839c23c5747 Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 01:03:05 +0200 Subject: [PATCH 04/12] fix(course-w5): bridge cold-eyes fixes - Stripe activation trigger (correctness), voice banned-patterns, 1.4 path-honesty clause + checklist, 2.3 head-start seam 3-persona panel (voice/Sam/LX): Stripe trigger named a non-existent UI signal (Sam); '## momentum usually dies' + 'Two things keep it moving' banned patterns (voice); 1.4 list built before the 300-visit signal (LX path) - added under-3% re-aim clause; 2.3 now acknowledges the 1.4-wait head-start; subreddit glossed; redundant 'Done fires at 10' trimmed; part-timer note added. Co-Authored-By: Claude Fable 5 --- .../find-10-people-where-to-look/index.md | 2 +- .../find-10-people-with-problem-outreach-2026/index.md | 4 ++-- .../price-hypothesis-on-smoke-test-page/index.md | 2 +- .../smoke-test-landing-page-7-day-demand-test/index.md | 8 +++++++- 4 files changed, 11 insertions(+), 5 deletions(-) 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 4f6840ead8..0067271b24 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 @@ -53,7 +53,7 @@ One time-box: if you catch yourself on day three still polishing the list instea ## Before you start: write three sentences -These are not new homework - they are your 1.1 Founding Hypothesis blanks, unpacked for people-hunting. Open your `Founding Hypothesis` doc, copy the sentence in, and expand two of its blanks into full sentences (the third - Business - is the one genuinely new line). Without them, every interview answer sounds encouraging and you can't tell confirm from kill: +Started a few rows during the Lesson 1.4 wait? Pick up from those. These are not new homework - they are your 1.1 Founding Hypothesis blanks, unpacked for people-hunting. Open your `Founding Hypothesis` doc, copy the sentence in, and expand two of its blanks into full sentences (the third - Business - is the one genuinely new line). Without them, every interview answer sounds encouraging and you can't tell confirm from kill: | Profile | What to write | Bad vs Good | |---------|---------------|------------| 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 3459afa987..5fca97852c 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 @@ -96,11 +96,11 @@ Both tracks, the parallel-run logic, and the part-time founder's batch-send vari ## While the replies trickle in -Booking 10 calls takes 2-4 weeks - messages go out, a few replies land, you send the next batch, more land. The calendar sits half-full for days at a stretch, and that is where momentum usually dies. Two things keep it moving. +Booking 10 calls takes 2-4 weeks - messages go out, a few replies land, and you send the next batch. The calendar sits half-full for days at a stretch, and it's easy to stop pushing new messages out. Don't wait for all 10 before you start. The day a third call is booked, start running interviews with the [Lesson 2.1 script](/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/) - early calls tell you fast whether your questions are landing, and you can fix them before the later ones. While the replies come in, set up the kit in one sitting: open the 2.1 five-question script, make a blank one-page notes doc you'll copy for each person, and put your 20-minute slots into your [NeetoCal](https://www.neeto.com/neetocal) link so booking is one click for them. -**Come back when 3 calls are booked - and run them, don't hold for 10.** Keep the outreach batches going in the background until the calendar hits 10; the Done below still fires at 10. +**Come back when 3 calls are booked - and run them, don't hold for 10.** Keep the outreach batches going in the background until the calendar hits 10. Evening-only, with a couple of hours a week? Run the calls first and resume outreach the week after. > **Done:** 10 interview calls are booked on your calendar and you have sent the first batch of outreach messages. > diff --git a/content/course/tech-for-non-technical-founders-2026/price-hypothesis-on-smoke-test-page/index.md b/content/course/tech-for-non-technical-founders-2026/price-hypothesis-on-smoke-test-page/index.md index f8ee82658c..93ddce8a28 100644 --- a/content/course/tech-for-non-technical-founders-2026/price-hypothesis-on-smoke-test-page/index.md +++ b/content/course/tech-for-non-technical-founders-2026/price-hypothesis-on-smoke-test-page/index.md @@ -77,7 +77,7 @@ Verification takes 1-3 business days, and live payments won't work until it clea Stripe's test mode is on the moment you sign up. Create the Payment Link (step 2), wire the after-payment redirect (step 3), and run a test checkout on yourself with Stripe's test card `4242 4242 4242 4242` - it walks the full flow without charging anything. Add the refund line to your footer while you're in there, and everything but the live link is done. -**Come back when your Stripe dashboard shows the account verified - the live-mode toggle stops being greyed out.** Flip the link to live mode, paste the live URL on your button, and re-run one checkout to confirm it charges for real. +**Come back when Stripe emails you that your account is activated - the dashboard's "activate your account" prompt disappears.** Switch the link to live mode, paste the live URL on your button, and re-run one checkout to confirm it charges for real. ## If Stripe or checkout stalls 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 33b6faf797..635daebb81 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 @@ -82,7 +82,13 @@ You will not have to figure out the ad on your own: the launch checklist below l The ads run for 5-7 days before 300 visits land. Camping on the dashboard won't speed it up, and the number means nothing until the traffic is in. Use the wait to get a head start on Module 2. -In [Lesson 2.3](/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/) you'll need a list of 30 people who have posted about the problem your page names - that list is what makes the interview outreach work. Start it now: open a spreadsheet and, in one sitting, write down 10-15 names you have seen complain about this problem - in a subreddit, a Slack group, wherever your customer hangs out - and paste the exact post next to each name. Module 2 opens with the slowest part already moving. +In [Lesson 2.3](/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/) you'll need a list of 30 people who have posted about the problem your page names - that list is what makes the interview outreach work. Start it now, in one sitting: + +- Open a spreadsheet. +- Write down 10-15 names you have seen complain about this problem - in a subreddit (a Reddit topic forum), a Slack group, wherever your customer hangs out. +- Paste the exact post next to each name. + +If your conversion comes back under 3%, you'll re-aim this list at the tightened hypothesis - the names still cost little. Above that, it's ready as-is, and Module 2 opens with its first task already half-done. **Come back when your campaign dashboard shows 300 landing-page views.** That is the wait over: read your conversion rate against the meter above, then start the price test. From 201779f3d99be4ea5fa41bf56c74c23635b73fc0 Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 01:07:01 +0200 Subject: [PATCH 05/12] =?UTF-8?q?fix(course-w5):=202.1=20Next=20core=20rou?= =?UTF-8?q?te=20=E2=86=92=202.3=20(path-finder=20drift)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The in-body Next funneled solely to the optional 2.2, but 2.1's branch in data/course_sequence.yaml marks 2.3 as the Core path and 2.2 as skippable. Rewrite the Next so the core route names 2.3, with 2.2 offered as optional - mirroring the 5.1-around-5.2 pattern and matching the yaml branch labels. Co-Authored-By: Claude Fable 5 --- .../mom-test-ask-about-past-not-future/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/index.md b/content/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/index.md index 98d60a79d9..503279325e 100644 --- a/content/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/index.md +++ b/content/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/index.md @@ -107,7 +107,7 @@ Read your draft list aloud. Which question would let a polite stranger agree wit > > **You have now:** all Module 1 artifacts + a draft Mom Test question list (2.1). Sharpening and recruiting come next - the problem itself isn't validated until you run the 10 real interviews. > -> **Next:** [2.2 · Sharpen Your Question List with AI Personas](/course/tech-for-non-technical-founders-2026/ai-persona-pre-validation-mom-test-prep/) - takes the draft list you just wrote and stress-tests each question against a simulated ICP before you spend a real interview slot on it. +> **Next:** the core path continues at [2.3 · Find 10 People: Where to Look](/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/) - it turns your draft question list into a 30-name list of real people to interview. If your list still reads hypothetical or generic, run the optional [2.2 · Sharpen Your Question List with AI Personas](/course/tech-for-non-technical-founders-2026/ai-persona-pre-validation-mom-test-prep/) first - it stress-tests each question against a simulated ICP before you spend a real interview slot. > > **If blocked:** open the [Mom Test Interview Script](/course/tech-for-non-technical-founders-2026/mom-test-interview-script/) - it has the 5 questions verbatim with follow-ups. > From d4e3689ac8785eb5a6c838b1f65338d5a63e9d06 Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 01:07:01 +0200 Subject: [PATCH 06/12] feat(devx): O7c bin/check-course-paths path-integrity gate Build-time check modeled on bin/check-svg-floor (report-only by default, COURSE_PATH_BLOCK=1 to block). Per course lesson: (1) every in-body Next link resolves to a real lesson page; (2) for lessons with a yaml Core-path branch, the Next's core route (first link) names that same slug - the 2.1 drift class. Includes --self-test asserting the drift predicate + a clean live tree. Co-Authored-By: Claude Fable 5 --- bin/check-course-paths | 68 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100755 bin/check-course-paths diff --git a/bin/check-course-paths b/bin/check-course-paths new file mode 100755 index 0000000000..577bc65e52 --- /dev/null +++ b/bin/check-course-paths @@ -0,0 +1,68 @@ +#!/usr/bin/env ruby +# frozen_string_literal: true +# +# devx O7c: catch course path drift at build time. Two checks per lesson under +# content/course/tech-for-non-technical-founders-2026/: +# 1. every in-body `Next:` link resolves to a real lesson page (no dead slug) +# 2. for a lesson whose data/course_sequence.yaml branch marks a "Core path →" +# target, the in-body Next's core route (its FIRST link) names that same +# slug - the exact 2.1 drift where the prose Next funneled through the +# optional 2.2 while yaml routed the core path to 2.3. +# +# Report-only by default (exit 0 + list). COURSE_PATH_BLOCK=1 makes it exit 1. +# Usage: bin/check-course-paths [--self-test] + +require "yaml" + +COURSE = "content/course/tech-for-non-technical-founders-2026" +SEQ = "data/course_sequence.yaml" +REPORT_ONLY = ENV.fetch("COURSE_PATH_BLOCK", "") != "1" + +# lesson slugs (first-link order) named on a page's `Next:` line +def next_links(path) + line = File.readlines(path).find { |l| l.include?("**Next:**") } + line ? line.scan(%r{/course/[^/]+/([^/)]+)/?\)}).flatten : [] +end + +# slug => yaml "Core path" target slug, for lessons that declare one +def core_targets(seq_file = SEQ) + YAML.load_file(seq_file)["sequence"].each_with_object({}) do |e, h| + b = (e["branches"] || []).find { |x| x["direction"].to_s.start_with?("Core path") } + h[e["slug"]] = b["slug"] if b + end +end + +def check(course = COURSE, seq_file = SEQ) + core = core_targets(seq_file) + fails = [] + Dir.glob(File.join(course, "*", "index.md")).sort.each do |path| + slug = File.basename(File.dirname(path)) + links = next_links(path) + links.each { |s| fails << [slug, "dead Next link -> #{s}"] unless Dir.exist?(File.join(course, s)) } + if core[slug] && links.first != core[slug] + fails << [slug, "core route #{links.first.inspect} != yaml Core path #{core[slug].inspect}"] + end + end + fails +end + +if ARGV.include?("--self-test") + line = "> **Next:** core continues at [2.3](/course/x/real-core/) - or optional [2.2](/course/x/optional/)." + links = line.scan(%r{/course/[^/]+/([^/)]+)/?\)}).flatten + raise "extract" unless links == %w[real-core optional] + raise "drift predicate" unless links.first != "optional" # yaml core=optional => flagged + raise "clean predicate" if links.first != "real-core" # yaml core=real-core => clean + live = check + raise "live tree drifted: #{live.inspect}" unless live.empty? + puts "self-test: ok (live tree clean)" + exit 0 +end + +fails = check +if fails.empty? + puts "course-paths: all lessons resolve and match their yaml Core path" + exit 0 +end +puts "course-paths: #{fails.size} drift(s):" +fails.each { |slug, msg| puts " #{slug}: #{msg}" } +exit(REPORT_ONLY ? 0 : 1) From 3613e995fcd23496b65984a9663156370e9a896b Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 01:17:03 +0200 Subject: [PATCH 07/12] =?UTF-8?q?feat(course-w5):=204.1=20+=205.6=20forks?= =?UTF-8?q?=20-=20add=20diagnose=E2=86=92route=20layer=20(yaml=20branches?= =?UTF-8?q?=20+=20branch-aware=20Next)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Fable 5 --- .../paid-pilot-charge-before-ship/index.md | 2 +- .../index.md | 2 +- data/course_sequence.yaml | 24 +++++++++++++++++++ 3 files changed, 26 insertions(+), 2 deletions(-) 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 b357fb8139..315f64000b 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 @@ -169,7 +169,7 @@ Send the DPA to your warmest lead first. Asking someone you know for a deposit i > > **You have now:** a signed Design Partner Agreement + a cleared deposit (5.6), sitting alongside your validated problem statement, Product Brief, and live MVP in the `Founder OS` folder. That completes the folder - the artifact investors fund. Converting this pilot into a year-one contract is the next test, 6-8 weeks out. > -> **Next:** that is the core course complete - from a one-sentence hypothesis to a stranger's money in your account. Keep going with the optional [5.7 · Going Outbound Without a Sales Team](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) when your warm list runs dry, or the [Going further chapters](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/#going-further-triggers) once your pilot converts. The [First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/) keeps the build honest through the pilot. +> **Next:** the fork here is persevere or pivot. If a **deposit cleared**, that is the core course complete - from a one-sentence hypothesis to a stranger's money in your account. Keep selling: [5.7 · Going Outbound Without a Sales Team](/course/tech-for-non-technical-founders-2026/outbound-without-sales-team/) when your warm list runs dry, or the [Going further chapters](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/#going-further-triggers) once your pilot converts. The [First-Paying-Customer Operating Kit](/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/) keeps the build honest through the pilot. If **no one will put money down** after the warm list and the 5.7 outbound pass, the signal is the segment, not the pitch - work [Pivot or Persevere: The Decision Framework](/course/tech-for-non-technical-founders-2026/pivot-or-persevere-decision-framework/) before you build more. > > **If blocked:** see "If this fails" above. If you do not have warm demos yet, your work is still in [Lesson 5.3](/course/tech-for-non-technical-founders-2026/first-ten-customers-network-list/) - the DPA is the wrong sprint for an empty pipeline. > 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 01373d1689..e90ba9df2a 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 @@ -130,7 +130,7 @@ Which of the five answers are you least sure of? That one is where your build de > > **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. The default is self-serve; the build itself is the next test. > -> **Next:** [4.2 · Who Owns Your GitHub, AWS, and Database?](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/) - locks ownership of the accounts before anything gets built on the path you just chose. +> **Next:** every path locks ownership first - [4.2 · Who Owns Your GitHub, AWS, and Database?](/course/tech-for-non-technical-founders-2026/github-aws-database-ownership-checklist/), before a line of code or a signed contract. Then the path you wrote at the top of the worksheet routes you: if you are **staying self-serve** (the default), keep building at [4.3 · The Self-Serve MVP Stack](/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-lovable-supabase-stripe-2026/) through 4.4 - the **fractional-CTO bridge** is the same self-serve build with a bought architecture review from the [Fractional CTO SOW reference](/course/tech-for-non-technical-founders-2026/fractional-cto-sow-reference/). If you are **hiring a team** (backend-heavy, or 12+ months of runway), start with the [hire-track reference](/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/) and read its SOW before anyone builds. If Q1 came back **No**, step back and validate without code - re-run the [1.4 demand test](/course/tech-for-non-technical-founders-2026/smoke-test-landing-page-7-day-demand-test/) as an Airbnb test before you spend runway. > > **If blocked:** see "If this fails" above. > diff --git a/data/course_sequence.yaml b/data/course_sequence.yaml index 8168b3405e..cb4e5954d0 100644 --- a/data/course_sequence.yaml +++ b/data/course_sequence.yaml @@ -130,6 +130,20 @@ sequence: title: "4.1 · Should You Hire? The 2026 Decision Tree" module: "Lesson 4.1" goal: "Decide between self-serve, fractional CTO, or hired team via a 5-question matrix." + # Branch-aware strip (W5): the decision tree routes 4 ways but the linear + # Next funneled everyone to 4.2 with no fork surfaced. Ownership (4.2) is + # the shared first step; then the path you scored diverges - self-serve + # build vs the hire track. Mirrors the 2.5 build/pivot/kill routing. + branches: + - slug: github-aws-database-ownership-checklist + direction: "Every path - lock ownership first →" + title: "4.2 · Who Owns Your GitHub, AWS, and Database?" + - slug: self-serve-mvp-stack-lovable-supabase-stripe-2026 + direction: "Then self-serve (the default) →" + title: "4.3 · The Self-Serve MVP Stack" + - slug: hire-track-supplementary-reference + direction: "Then hiring a team →" + title: "Hire-track reference - read the SOW first" - slug: github-aws-database-ownership-checklist title: "4.2 · Who Owns Your GitHub, AWS, and Database?" @@ -189,6 +203,16 @@ sequence: title: "5.6 · Charge Before You Ship: The Paid Pilot Contract" module: "Lesson 5.6" goal: "Sign a Design Partner Agreement with a refundable Stripe deposit before writing new code." + # Branch-aware strip (W5): a signed deposit means persevere (continue M5); + # nobody signing after the warm list AND the 5.7 outbound pass means pivot. + # The linear Next only offered the persevere route. Mirrors the 2.5 pattern. + branches: + - slug: outbound-without-sales-team + direction: "Deposit cleared - keep selling →" + title: "5.7 · Going Outbound Without a Sales Team" + - slug: pivot-or-persevere-decision-framework + direction: "No one will sign after warm + outbound - pivot →" + title: "Pivot or Persevere: the decision framework" - slug: outbound-without-sales-team title: "5.7 · Going Outbound Without a Sales Team" From 82bf0b4fc70a796ae243726b57271e7d8679cb10 Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 01:36:09 +0200 Subject: [PATCH 08/12] refactor(course-w5): compress pivot-or-persevere-decision-framework toward band 3206 -> 2894 words. Cut table-restatement prose, loop-theme restatements, and case-anecdote bloat; fixed banned 'Founders who' / negative-parallelism tells. Six pivot types, trigger table, ledger, and cross-links unchanged. Co-Authored-By: Claude Fable 5 --- .../index.md | 59 +++++++++---------- 1 file changed, 28 insertions(+), 31 deletions(-) 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 0a39dc44e9..7f52750adf 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 @@ -49,21 +49,21 @@ A fintech founder I worked with last quarter - call him D. - hit the cold-outbou *Illustrative composite based on patterns from real founder builds, not a single client story.* -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 - product-led growth, where users find and buy the product self-serve). 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. +The right move was backwards. His 0.6% conversion was telling him the messaging he 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 picked. Three things could be wrong: the customer (segment), the need (problem), or the channel (outbound vs PLG - product-led growth, where users find and buy the product self-serve). Pushing into rebuild mode would have made him a better operator of a misaligned hypothesis; going back with a pivot decision made him a better founder. -The course you have been reading was structured as a numbered sequence because that is the cleanest way to learn the moves. But the actual job is a loop. A founder writes a hypothesis, smoke-tests it, talks to customers, builds an MVP, lands paying customers, and at any point can hit a signal that sends them back to [Form Your Founding Hypothesis](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/) with a new hypothesis. The courses that pretend the journey is one-way escalator produce founders who think pivoting is failure. It is not. Pivoting is the discovery loop working correctly. +The course reads as a numbered sequence because that is the cleanest way to learn the moves. But the actual job is a loop. A founder writes a hypothesis, smoke-tests it, talks to customers, builds an MVP, lands paying customers, and at any point can hit a signal that sends them back to [Form Your Founding Hypothesis](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/) with a new hypothesis. The courses that pretend the journey is one-way escalator produce founders who think pivoting is failure. It is not. Pivoting is the discovery loop working correctly. -This chapter teaches you when to go back vs when to push forward. It is the chapter that turns the rest of the course from a checklist into a system. +This chapter teaches you when to go back vs when to push forward - the move that turns the rest of the course from a checklist into a system. ## The Six Pivot Types -Eric Ries catalogued ten pivot types in *The Lean Startup*; Steve Blank built on them with the customer-development variants. Six of those ten cover 90% of what a non-technical founder will face in 2026. The other four are scope and platform pivots that show up later, when you are managing a product team. Below are the six in plain English, with one trigger sentence and one example each. +Eric Ries catalogued ten pivot types in *The Lean Startup*; Steve Blank added customer-development variants. Six cover 90% of what a non-technical founder faces in 2026; the other four are scope and platform pivots that show up later, when you manage a product team. Here are the six in plain English, one trigger and one example each. ![The 6-pivot wheel - center hypothesis with 6 spokes labeled by pivot type and trigger](pivot-wheel.svg) ### 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 (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. +*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. 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 @@ -75,21 +75,21 @@ Eric Ries catalogued ten pivot types in *The Lean Startup*; Steve Blank built on ### 4. Technology pivot -*Right solution, wrong tech stack.* The shape of the solution is right but the platform you built it on cannot reach the price or performance the customer needs. Less common for non-technical founders because most ship on Lovable, Bubble, or with a hired team and the tech is opaque. Becomes relevant when you outgrow a no-code ceiling. Example: a B2C founder hit 4,000 MAU (monthly active users) on Bubble and discovered the per-row pricing model would cost $11K/month at 20K MAU; the rebuild on a native stack made the unit economics work. +*Right solution, wrong tech stack.* The shape of the solution is right but the platform you built it on cannot reach the price or performance the customer needs. Less common for non-technical founders - most ship on Lovable, Bubble, or with a hired team, so the tech is opaque until you outgrow a no-code ceiling. Example: a B2C founder hit 4,000 MAU (monthly active users) on Bubble and discovered the per-row pricing model would cost $11K/month at 20K MAU; the rebuild on a native stack made the unit economics work. ### 5. Channel pivot -*Right product, wrong distribution.* The product is right, the audience is right, but the way you reach them does not work. The signal usually comes from cold-outbound under 1% conversion or paid ads producing zero qualified pilots. Example: the fintech founder D. above. The product was right (CFO-grade close-the-books tool), the segment was right (50-200-person companies), but cold email could not break through to a CFO's inbox. Channel pivot was to a partner-led motion through fractional CFO networks; conversion went to 4.2% in 30 days. +*Right product, wrong distribution.* The product is right, the audience is right, but the way you reach them does not work. The signal usually comes from cold-outbound under 1% conversion or paid ads producing zero qualified pilots. Example: D. above - product right (CFO-grade close-the-books tool), segment right (50-200-person companies), but cold email could not break through to a CFO's inbox. The channel pivot to a partner-led motion through fractional CFO networks took conversion to 4.2% in 30 days. ### 6. Revenue Model pivot *Right product, wrong pricing.* The product works and the audience pays, but the pricing shape (per seat, per event, flat tier, freemium) does not match how customers value or budget for the product. The signal comes from active customers churning at the renewal date with feedback that points at price, not the product. Example: a B2B SaaS priced at $200/seat/month for 10-seat teams; customers loved it but balked at the renewal because they only needed 3 power users. Pivot was to $400/month flat for unlimited seats with feature gates by usage tier. ARPU (average revenue per user) dropped 20% per customer; net revenue retention (the revenue you keep plus expansion from existing customers) jumped to 118%. -The skill is not memorizing the six types. The skill is asking which of the five Mad Libs blanks (customer, problem, approach, competition, differentiation) is wrong, and matching it to the pivot type that addresses that blank. +The skill is not memorizing the six types but asking which of the five Mad Libs blanks (customer, problem, approach, competition, differentiation) is wrong, then matching it to the pivot type that addresses that blank. ## Trigger Conditions: What Tells You to Pivot -The common pattern is not pivoting too early. It's pivoting too late - watching the cohort numbers, the conversion rates, the ad spend, and the CAC numbers all degrade for two quarters before admitting the signal is real. The trigger conditions below are the numerical thresholds that should override the "let me try one more thing" instinct. +The common failure is not pivoting too early - it's pivoting too late, watching cohort numbers, conversion rates, ad spend, and CAC all degrade for two quarters before admitting the signal is real. The trigger conditions below are the thresholds that override the "let me try one more thing" instinct. Work the five checks in order - the first row whose trigger matches names your pivot type; if none match, you persevere: @@ -103,49 +103,46 @@ Work the five checks in order - the first row whose trigger matches names your p | 5. Tech ceiling | Stack cost or performance ceiling hit | Technology pivot | | All five clear | - | **Persevere - you have signal** | -**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. +Each trigger has a flail response that feels productive and buys the wrong hypothesis another quarter: -**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. - -**Outbound conversion under 1% after 60 personal messages** triggers a Channel pivot. Founders typically react by writing better email copy. After 60 messages with thoughtful copy, the channel itself is the bottleneck. Most B2B products that fail outbound do well via partnerships, communities, or content; most B2C products that fail Meta Ads do well via influencers or organic social. - -**Tech-stack cost or performance ceiling** triggers a Technology pivot. Founders typically react by ignoring the ceiling for too long because rebuilding feels expensive. The cost of a 6-week rebuild is almost always less than the cost of running on a stack that triples every quarter at scale. +- **Sean Ellis under 25% everywhere** (Solution or Customer Need pivot): the flail is more features and polish; the real question is whether the solution shape or the target job is wrong. A churn-triage Decision 3 (no segment retains) points the same way - solution shape, not audience. +- **CAC over 3x LTV with customers who love the product** (Revenue Model pivot): the flail is cheaper ads; when the converters love it, the problem is the pricing model, not acquisition cost. +- **Outbound under 1% after 60 personal messages** (Channel pivot): the flail is better email copy; after 60 thoughtful messages the channel itself is the bottleneck. Most B2B products that die on outbound do well via partnerships or communities; most B2C products that die on Meta Ads do well via influencers or organic social. +- **Tech-stack cost or performance ceiling** (Technology pivot): the flail is ignoring it because rebuilding feels expensive; a 6-week rebuild almost always costs less than a stack that triples every quarter at scale. The right rule is simple: when two consecutive months show the same trigger condition, the next decision is a pivot type, not a "try harder." The flail response is to try harder for two more quarters; the pivot response is to ship a new hypothesis test in two weeks. ## What You Keep When You Pivot -A pivot is not a restart. The founders who treat pivots as restarts are the ones who burn the most runway because they throw away the evidence they already paid to collect. The discipline that distinguishes a real pivot from a flailing reboot is the pivot ledger - a written list of every artifact you have built so far and whether it survives the pivot. +A pivot is not a restart. Treat it as one and you burn the most runway, because you throw away the evidence you already paid to collect. The discipline that distinguishes a real pivot from a flailing reboot is the pivot ledger - a written list of every artifact you have built so far and whether it survives the pivot. ![The pivot ledger - a 4-column table showing what you keep and what you replace](pivot-ledger.svg) -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. +The ledger above is the template. Print it before you declare the pivot and walk every row. The evidence you keep: 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 (your most valuable B2B asset at this stage), the cohort retention numbers from the churn triage, and your domain expertise. The hypothesis sentence, landing page copy, and ad creative get rewritten. The MVP code depends - auth and billing 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. +A second founder we rode shotgun with - Anika, running a vertical SaaS for clinical-trial coordinators - ran the ledger move on a Customer Need pivot (segment still right). She kept her 287-person coordinator contact list, her Stripe integration and auth flow from the Lovable build, her pricing model ($240/month per seat), and 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 scheduling. She rewrote the hypothesis sentence and the landing page headline around consent-form reconciliation. Two weeks later she had a smoke-test 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. -The trade-off worth naming: keeping too much makes a pivot feel like a renaming. The discipline is to be honest about which artifacts genuinely transfer and which ones are sunk cost. If your ledger says everything survives, you have not actually pivoted - you have rebranded. A real pivot rewrites at least the hypothesis sentence, the landing page, and the messaging across all customer touchpoints. If those three are the same after the "pivot," the trigger condition will fire again in 60 days and you will be back here. +The trade-off: keep too much and the pivot is just a renaming. Be honest about which artifacts genuinely transfer and which are sunk cost. If your ledger says everything survives, you have not pivoted - you have rebranded. A real pivot rewrites at least the hypothesis sentence, the landing page, and the messaging; if those are the same after the "pivot," the trigger fires again in 60 days and you are back here. -The ledger also serves a second purpose. When you go back to investors, advisors, or your fractional CTO with the pivot decision, the ledger is the artifact that proves you are pivoting on evidence and not on whim. Investors fund founders who can show their work. The pivot ledger is the work. +The ledger serves a second purpose: when you take the pivot decision to investors, advisors, or your fractional CTO, it proves you are pivoting on evidence, not whim. Investors fund founders who can show their work - the pivot ledger is the work. ## When to PERSEVERE -Not every dip is a pivot signal. The harder skill in 2026 is knowing when to push through a slow signal rather than chase a new hypothesis. Most pivots that fail were premature; the founder mistook a bad month for a bad hypothesis and reset the discovery loop just as the original one was starting to work. +Not every dip is a pivot signal. The harder skill is knowing when to push through a slow signal rather than chase a new hypothesis. Most failed pivots were premature - the founder mistook a bad month for a bad hypothesis and reset the loop just as the original was starting to work. -The persevere signals are quieter than the pivot signals because they are about trajectory, not about absolute numbers. The three signals to look for are: cohort 3-month retention is climbing (even slowly - 12% to 14% to 17% across three monthly cohorts is a persevere signal even if the absolute number is low), one segment is producing referrals without you asking for them (referrals mean the product is creating word-of-mouth value, which is the strongest possible PMF signal), and your own founder energy is genuinely renewing as you ship (not stubbornly continuing despite exhaustion - the difference matters). +The persevere signals are quieter than the pivot signals because they are about trajectory, not absolute numbers. The three to look for: cohort 3-month retention climbing, even slowly (12% to 14% to 17% across three cohorts counts, even at a low absolute number); one segment producing referrals without you asking - the strongest possible PMF signal; and your own founder energy genuinely renewing as you ship, not stubbornly continuing despite exhaustion. -The Eric Ries persistence threshold is 6-12 months of consistent signal in the same direction. Most consumer products that became hits hit their first usable PMF signal in months 7-9; most B2B products in months 9-14. Pivoting at month 4 because the signal was not loud enough is the most common pre-PMF mistake. The right move at month 4 is usually to run a tighter experiment within the current hypothesis - sharpen the segment, refine the messaging, ship one more workflow improvement - and re-measure at month 6. +The Eric Ries persistence threshold is 6-12 months of consistent signal in the same direction. Consumer hits usually see their first usable PMF signal in months 7-9; B2B in months 9-14. Pivoting at month 4 because the signal was not loud enough is the most common pre-PMF mistake. The right move at month 4 is usually to run a tighter experiment within the current hypothesis - sharpen the segment, refine the messaging, ship one more workflow improvement - and re-measure at month 6. -Tomás, a B2B procurement-tools founder, came back to me eleven weeks after his Channel pivot with a different question. The new hypothesis was working: 4.2% outbound conversion, 3 paid pilots signed, MRR around $2,400. He was wondering whether to pivot again because growth had stalled at $2,400 for three weeks. The cohort numbers were good (78% week-4 retention on the 3 pilots), the segment was right, the new pivots from the trigger conditions were not firing. The persevere call was obvious. He had run his pivot 11 weeks earlier; the signal was new, the trajectory was up, and three weeks of flat MRR after a 0-to-$2,400 ramp is noise, not pattern. He stayed put. By week 16 MRR was at $4,100 with no new pivots. +Tomás, a B2B procurement-tools founder, came back eleven weeks after his Channel pivot wondering whether to pivot again because growth had stalled at $2,400 MRR for three weeks. But the new hypothesis was working: 4.2% outbound conversion, 3 paid pilots, 78% week-4 retention, and none of the trigger conditions firing. The persevere call was obvious - the signal was new, the trajectory was up, and three weeks of flat MRR after a 0-to-$2,400 ramp is noise, not pattern. He stayed put. By week 16 MRR was at $4,100 with no new pivots. -The honest trade-off: persevere is the harder discipline because it looks like inaction from outside. Investors ask why you are not pivoting; advisors offer new hypotheses; the [Twitter timeline](https://twitter.com) keeps surfacing founders who pivoted into a unicorn. Persevere works only when you have a written list of trigger conditions and the latest measurements show none of them firing. Without that list, persevere collapses into "stubborn." With the list, persevere is a deliberate operational choice backed by evidence. +The honest trade-off: persevere is the harder discipline because it looks like inaction from outside. Investors ask why you are not pivoting; advisors offer new hypotheses; the [Twitter timeline](https://twitter.com) keeps surfacing founders who pivoted into a unicorn. Persevere works only when you have a written list of trigger conditions and the latest measurements show none firing. Without that list, persevere collapses into "stubborn"; with it, persevere is a deliberate choice backed by evidence. -The KISS rule for the pivot/persevere call: write the trigger conditions down. Re-measure monthly. Pivot when two consecutive months hit a trigger; persevere when none do. Do not pivot every quarter; do not push through every signal. The framework runs on a steady cadence, not on emotion. +The KISS rule for the pivot/persevere call: write the trigger conditions down. Re-measure monthly. Pivot when two consecutive months hit a trigger; persevere when none do. The framework runs on a steady cadence, not on emotion. ## Hand This to the Next Loop -You walk out of this chapter holding a pivot decision (one of six types, or persevere) and a pivot ledger that names what you keep and what you change. The next chapter for you depends on the pivot type. +You walk out holding a pivot decision (one of six types, or persevere) and a pivot ledger naming what you keep and what you change. Your next chapter depends on the pivot type. A Customer Segment pivot or Customer Need pivot routes you back to [Form Your Founding Hypothesis](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/) - rewrite the customer or problem blanks, keep the rest of the sentence template. Then [Find 10 People With the Problem](/course/tech-for-non-technical-founders-2026/find-10-people-with-problem-outreach-2026/) to validate the new hypothesis with the new segment. @@ -157,9 +154,9 @@ A Technology pivot routes you to the [Fractional CTO bridge reference](/course/t 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 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. +The course was always a loop; it reads as a numbered sequence because the discovery moves work the same whether you run them for the first time or the fifth. The founders who graduate holding all six Founder OS artifacts got there by running the loop three or four times and getting better at each pass, not by avoiding pivots. -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. +D. is on his third pivot now: the original hypothesis (audit prep), then month-end close (Customer Need), then 7 weeks later outbound to partnerships (Channel). The two pivots cost 5 weeks of build time combined and saved him at least two quarters of running each wrong hypothesis to its conclusion - each loop a deliberate decision instead of a flail. ## Further reading From 934adc4ae9ac8426badc5d969b87c3a8be7c0275 Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 01:36:09 +0200 Subject: [PATCH 09/12] refactor(course-w5): compress validation-tools-field-guide toward band 3150 -> 2896 words. Merged the four-point 'what none can do' closer, dropped two 'vague input' mistake bullets that duplicated the prepare sections, de-duped viability-score explanation, tightened workflow steps. All three tool sections, tables, prompts, and cross-links unchanged. Co-Authored-By: Claude Fable 5 --- .../validation-tools-field-guide/index.md | 80 +++++++++---------- 1 file changed, 38 insertions(+), 42 deletions(-) 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 3f1b9c7eff..b5a795c0d8 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 @@ -32,9 +32,9 @@ related_posts: false > **Course reference** · [From Idea to First Paying Customer](/course/tech-for-non-technical-founders-2026/) course. > Companion to [Lesson 1.1: Form Your Founding Hypothesis](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/). Read this when you are filling in the five blanks of the Mad Libs sentence and want a structured second opinion before you book the first interview. -You are about to write a one-sentence hypothesis that names your customer, problem, approach, competition, and differentiation. The sentence will anchor every interview, every landing-page headline, and every build decision for the next three months. Before you commit it to your `Founding Hypothesis` Google Doc, push it through one or two validation tools. +You are about to write a one-sentence hypothesis naming your customer, problem, approach, competition, and differentiation - the sentence that anchors every interview, landing-page headline, and build decision for the next three months. Before you commit it to your `Founding Hypothesis` Google Doc, push it through one or two validation tools. -This guide covers three tools - VenturusAI, DimeADozen, and Preuve AI - with enough detail to use each one productively in under ten minutes. All three are pre-interview research aids. They do not replace Lesson 2.1's ten Mom Test interviews. +This guide covers three tools - VenturusAI, DimeADozen, and Preuve AI - in enough detail to use each productively in under ten minutes. All three are pre-interview research aids; they do not replace Lesson 2.1's ten Mom Test interviews. --- @@ -75,7 +75,7 @@ The tools catch different things: | Your problem is real but the market is too small to support a business | DimeADozen (market-sizing section) | | Your `[DIFFERENTIATION]` is "easier to use" - the vaguest claim in SaaS | VenturusAI (SWOT strengths section flags it) | -None of these tools costs more than a month of Perplexity Pro. Two are free. Run at least one before you fill the five blanks. +Two are free; none costs more than a month of Perplexity Pro. Run at least one before you fill the five blanks. --- @@ -95,11 +95,11 @@ None of these tools costs more than a month of Perplexity Pro. Two are free. Run VenturusAI runs your business idea through three classic strategic frameworks - SWOT (Strengths, Weaknesses, Opportunities, Threats), PESTEL (Political, Economic, Social, Technological, Environmental, Legal forces), and Porter's Five Forces (Buyer Power, Supplier Power, Threat of Substitution, Competitive Rivalry, Threat of New Entrants). It also produces sections on target audience, marketing strategy, and financial estimates. -Think of it as a free MBA student who reads your one-paragraph description and produces a structured critique in 30 seconds. The frameworks are academic, but the output is surprisingly practical when your input is specific. +Think of it as a free MBA student who reads your one-paragraph description and produces a structured critique in 30 seconds. The frameworks are academic; the output is practical when your input is. ### What to prepare before you open it -Write a 2-4 sentence paragraph covering four things. Do not open the tool until this paragraph is written: +Write a 2-4 sentence paragraph covering four things before you open the tool: 1. **What you are building** - one sentence, plain English. "A mobile app for solo chiropractors that reduces insurance-claim resubmission time." 2. **Who it is for** - the specific person, not a category. "Solo chiropractors with 1-3 staff who handle their own billing." @@ -120,24 +120,23 @@ Every blank in the Mad Libs sentence is a blank in your VenturusAI input. Specif The report has 7-8 sections. You do not need to read all of them. Focus on three: -**Porter's Five Forces - Competitive Rivalry section.** If it names a competitor you had not thought of, add that competitor to the Competition column in the [full hypothesis sprint](/course/tech-for-non-technical-founders-2026/reference/hypothesis-sprint-full/). If it names one you already knew about but describes their advantage in a way you had not considered, rewrite your `[DIFFERENTIATION]` blank. +**Porter's Five Forces - Competitive Rivalry section.** If it names a competitor you had not thought of, add it to the Competition column in the [full hypothesis sprint](/course/tech-for-non-technical-founders-2026/reference/hypothesis-sprint-full/). If it names one you knew about but describes their advantage in a way you had not considered, rewrite your `[DIFFERENTIATION]` blank. -**SWOT - Weaknesses.** This is the section that hurts. If the AI flags a weakness you already knew about (e.g., "founder has no engineering background"), that is expected. If it flags one you had not considered (e.g., "customer acquisition depends on insurance-industry partnerships that take 6-12 months to close"), pay attention. That is a structural blank in your hypothesis. +**SWOT - Weaknesses.** The section that hurts. A weakness you already knew about (e.g., "founder has no engineering background") is expected. One you had not considered (e.g., "customer acquisition depends on insurance-industry partnerships that take 6-12 months to close") is a structural blank in your hypothesis - pay attention. **PESTEL - Legal/Regulatory.** Many founders skip this. If your product touches healthcare, finance, education, or anything involving personal data, read this section carefully. A regulatory blocker you discover now costs zero dollars. One you discover after building costs your runway. -The Marketing Strategy and Financial Estimates sections are AI-generated first drafts. Skim them for ideas; do not treat the numbers as real. +The Marketing Strategy and Financial Estimates sections are AI-generated first drafts - skim for ideas, do not treat the numbers as real. ### Common mistakes -- **Vague input.** "An app for food delivery" produces generic SWOT that is useless. Write the four-part paragraph above. -- **Trusting it blindly.** The AI generates insights from general logic, not from your specific market. It cannot access your local competitors or proprietary market data. -- **Stopping at one report.** If the first report is too generic, take the most interesting section, expand on it, and re-feed it as a new input. Iterate. +- **Trusting it blindly.** The AI generates insights from general logic, not from your specific market - it cannot access your local competitors or proprietary data. +- **Stopping at one report.** If the first report is too generic, take the most interesting section, expand on it, and re-feed it as new input. ### Pro tips -- Use the export-to-Google-Docs feature. Keep the AI-generated framework and manually update it as you gather real interview data. By Module 2, you will have a side-by-side comparison of what the AI predicted vs. what real humans said. -- Ask the tool explicitly about failure modes. Refine your input to include: "What could cause this to fail?" The Weaknesses and Threats sections will be sharper. +- Export to Google Docs. Keep the AI-generated framework and update it as you gather real interview data - by Module 2 you will have a side-by-side of what the AI predicted vs. what real humans said. +- Ask explicitly about failure modes - add "What could cause this to fail?" to your input and the Weaknesses and Threats sections sharpen. - The free tier has a ~1,000 character limit. If your input exceeds it, cut adjectives before you cut specifics. "Very innovative" costs characters and adds zero signal. --- @@ -146,23 +145,21 @@ The Marketing Strategy and Financial Estimates sections are AI-generated first d ### What it does -DimeADozen produces a multi-section validation report: Executive Summary, Market Sizing, Competitive Landscape, Customer Profiling, Risk Assessment (kill risks), Unit Economics, and Go-To-Market Strategy. The Starter report ($9) is 5-7 pages. The Entrepreneur report ($129) is 40+ pages with sourced data and full metrics. - -The tool was bootstrapped by a solo founder who sold it - it is designed for exactly the person reading this guide: someone who wants a brutal second opinion before committing time and money. +DimeADozen produces a multi-section validation report: Executive Summary, Market Sizing, Competitive Landscape, Customer Profiling, Risk Assessment (kill risks), Unit Economics, and Go-To-Market Strategy. The Starter report ($9) is 5-7 pages; the Entrepreneur report ($129) is 40+ pages with sourced data and full metrics. It is built for exactly the person reading this guide: someone who wants a brutal second opinion before committing time and money. ### What to prepare before you open it -Same 2-4 sentence paragraph as VenturusAI. Plus: name 1-2 competitors you are aware of. The tool uses competitor names to calibrate its market-sizing and competitive-landscape sections. If you name zero competitors, it assumes the market is empty - which makes the report less useful. +Same 2-4 sentence paragraph as VenturusAI, plus 1-2 competitors you are aware of - the tool uses them to calibrate its market-sizing and competitive-landscape sections. Name zero competitors and it assumes the market is empty, which makes the report less useful. ### How to read the report -The Starter report is 5-7 pages. You only need to read two sections on the first pass: +You only need to read two sections on the first pass: **Kill Risks.** This is the section that justifies the $9. It flags existential threats: market saturation (too many entrenched players), low barriers to entry (competitors can clone you in a weekend), CAC-to-LTV problems (acquiring a customer costs more than they will ever pay you), and regulatory hurdles. If any kill risk is specific - names a competitor, a regulation, or a cost number - take it seriously. If it is generic ("the market is competitive"), treat it as a yellow flag, not a red one. **Retention-Curve / Unit Economics.** This section estimates whether the numbers work. If it says your target market is too small at your price point, revisit the `[CUSTOMER]` blank in Lesson 1.1. If it says your CAC is too high relative to LTV, revisit your channel assumption. -Skip the Executive Summary and Go-To-Market sections on first read. They are AI-generated strategy and rarely say anything you could not have guessed. Come back to them after you have real interview data. +Skip the Executive Summary and Go-To-Market sections on first read. They are AI-generated strategy that rarely says anything new; read them after you have real interview data. ### Starter ($9) vs. Entrepreneur ($129) @@ -174,18 +171,18 @@ Skip the Executive Summary and Go-To-Market sections on first read. They are AI- | Unit economics | Rough ranges | Detailed modeling | | When to use | Pre-interview sanity check | Due diligence before committing capital | -At the pre-interview stage, the $9 Starter is enough. You are looking for red flags, not investment-grade due diligence. If the Starter report flags a kill risk, you decide whether to investigate further or pivot. If it comes back clean, you proceed to interviews. +At the pre-interview stage, the $9 Starter is enough - you are looking for red flags, not investment-grade due diligence. If it flags a kill risk, decide whether to investigate or pivot; if it comes back clean, proceed to interviews. ### 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 Lesson 1.2-1.4's smoke test and Lesson 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 the idea is not obviously broken, not that customers will pay - that needs Lesson 1.2-1.4's smoke test and Lesson 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 - Run the report, read the kill risks, adjust your hypothesis, and run it again. Two $9 reports on different versions of your hypothesis are cheaper than one week of building the wrong thing. -- If the report flags a competitor you have never heard of, spend 20 minutes on their website before you dismiss them. Read their pricing page, their testimonials, and their most recent blog post. You will learn more from a live competitor's marketing than from a generic competitive-landscape summary. +- If the report flags a competitor you have never heard of, spend 20 minutes on their website - pricing page, testimonials, most recent blog post. A live competitor's marketing teaches more than a generic competitive-landscape summary. --- @@ -193,13 +190,13 @@ At the pre-interview stage, the $9 Starter is enough. You are looking for red fl ### What it does -Preuve AI scans 50+ live data sources - Crunchbase, Google Trends, Reddit, G2, Capterra, Product Hunt, news aggregators, and industry publications - and produces an evidence-based viability score (0-100). Every claim in the report links to its underlying source. Unlike general-purpose LLMs that hallucinate market facts, Preuve shows you where the data came from. +Preuve AI scans 50+ live data sources - Crunchbase, Google Trends, Reddit, G2, Product Hunt, and industry publications - and produces an evidence-based viability score (0-100). Every claim in the report links to its underlying source. Unlike general-purpose LLMs that hallucinate market facts, Preuve shows you where the data came from. -The key product is the **Founder Report** ($29 one-time): a 13-section analysis with competitor mapping (up to 15 competitors with pricing and weak spots), TAM/SAM/SOM estimates, customer persona identification, and AI Coach pivot suggestions. +The key product is the **Founder Report** ($29 one-time): a 13-section analysis with competitor mapping, TAM/SAM/SOM estimates, customer personas, and AI Coach pivot suggestions. ### What to prepare before you open it -One sentence, as specific as possible. The narrower your niche segment, the more relevant the market signals Preuve finds. +One sentence, as specific as possible. The narrower the niche, the more relevant the signals Preuve finds. Bad: "Helping small businesses." @@ -207,19 +204,19 @@ Good: "Accounts-payable teams at 50-200 person companies." Better: "Solo-practice chiropractors who file their own insurance claims and spend Mondays on resubmissions." -The tool matches your description against live data sources. A broad description matches everything and tells you nothing. A narrow description matches specific signals. +The tool matches your description against live data sources. Broad matches everything and tells you nothing. ### How to read the report -**Start with the Viability Score (0-100).** A score above 70 means the tool found positive market signals. A score below 40 means it found more problems than opportunities. A score between 40-70 means the data is mixed - drill into the specific sections that pulled the score down. +**Start with the Viability Score (0-100).** Above 70 means positive market signals; below 40 means more problems than opportunities; 40-70 means mixed - drill into the sections that pulled the score down. -**Competitor Mapping.** Preuve identifies up to 15 competitors with pricing and "weak spots." The weak spots are the most actionable part of the report - they tell you where existing solutions fall short. If three competitors share the same weak spot, your `[DIFFERENTIATION]` blank should target it. +**Competitor Mapping.** Preuve identifies up to 15 competitors with pricing and "weak spots" - the most actionable part of the report, telling you where existing solutions fall short. If three competitors share the same weak spot, your `[DIFFERENTIATION]` blank should target it. -**Source links.** Every claim is linked to its source. If a score looks off - too high or too low - drill into the cited source before dismissing it. Sometimes the AI misinterprets a data point (e.g., a Reddit post from 2018 gets weighted too heavily). You are the human in the loop. +**Source links.** Every claim links to its source. If a score looks off, drill into the cited source before dismissing it - sometimes the AI misinterprets a data point (e.g., a Reddit post from 2018 gets weighted too heavily). You are the human in the loop. ### The AI Coach -After your first report, the AI Coach suggests pivots based on what the data actually shows. It compares your idea against competitor weaknesses and market demand signals and identifies blind spots. Common pivot suggestions: +After your first report, the AI Coach suggests pivots based on what the data shows - comparing your idea against competitor weaknesses and demand signals to identify blind spots. Common suggestions: - Target a micro-niche where existing solutions are too broad - Change the business model (e.g., B2C → B2B) @@ -236,48 +233,47 @@ Treat the pivot suggestions as hypotheses to test in Lesson 2.1 interviews, not | Radar | $9/mo | Ongoing market monitoring | | Investor-Ready | $499 | Manual review, custom pitch deck, 18-month financial model, 4-page investment memo | -For pre-interview validation, the Free Scan + Founder Report is the sweet spot. Skip the Investor-Ready package until you have a signed paid pilot and a deck to raise on. +For pre-interview validation, the Free Scan + Founder Report is the sweet spot. Skip Investor-Ready until you have a signed paid pilot and a deck to raise on. ### Common mistakes -- **Vague input.** As with VenturusAI, "an app for fitness" produces a generic report. Use the specific-niche format above. -- **Treating the viability score as binary.** A score of 55 does not mean "kill the idea." It means "the data is mixed - investigate the low-scoring sections before proceeding." +- **Treating the viability score as binary.** A 55 does not mean "kill the idea" - it means the data is mixed; investigate the low-scoring sections first. - **Ignoring the pivot suggestions.** Run the report, read the pivots, adjust your description, and scan again. Watch how the score changes. The delta between scans tells you which blank in your hypothesis is weakest. ### Pro tips -- Run the free scan first. If the viability score is above 50 and the competitor mapping names companies you recognize, the $29 Founder Report is worth it. If the free scan comes back below 30 with vague competitors, save your $29 and revisit your hypothesis first. -- Preuve scans Reddit and niche forums. If real people are discussing the problem you want to solve, Preuve will find those discussions and link to them. Read the threads. The verbatim language from real users is worth more than any AI-generated summary. +- Run the free scan first. If the score is above 50 and the competitor mapping names companies you recognize, the $29 Founder Report is worth it. If it comes back below 30 with vague competitors, save your $29 and revisit your hypothesis. +- Preuve scans Reddit and niche forums. If real people are discussing your problem, it links to those threads. Read them - verbatim language from real users beats any AI-generated summary. --- ## Recommended workflow -The three tools work best in sequence, not all at once. Here is the order that produces the most signal for the least time: +The three tools work best in sequence. Here is the order that produces the most signal for the least time: ![The three validation tools in recommended order: VenturusAI first (free, ~30s) catches missed competitors and weak differentiation, Preuve AI free scan second (free, ~60s) reads market signal and flags a too-broad customer, DimeADozen Starter third (optional, $9, ~2min) catches kill risks and unit economics - none validates the hypothesis, only 10 Mom Test interviews do](tools-in-sequence.svg) ### 1. VenturusAI (first - free) -Run your hypothesis paragraph through VenturusAI. Read the Porter's Five Forces Competitive Rivalry section and the SWOT Weaknesses section. If it flags a competitor you missed or a structural weakness you had not considered, fix those blanks in your hypothesis before moving to the next tool. +Run your hypothesis paragraph through VenturusAI and read the Competitive Rivalry and SWOT Weaknesses sections. If it flags a competitor you missed or a structural weakness, fix those blanks before the next tool. **Time:** 10 minutes (5 to write input, 5 to read key sections). ### 2. Preuve AI free scan (second - free) -Run your refined hypothesis through Preuve's free scan. Check if the viability score is above 50 and whether the competitor mapping names companies in your space. If the score is low, revisit your `[CUSTOMER]` or `[PROBLEM]` blank. If the score is solid, you have a data-backed signal that the market exists. +Run your refined hypothesis through Preuve's free scan. If the viability score is low, revisit your `[CUSTOMER]` or `[PROBLEM]` blank; if it is solid and the competitor mapping names companies in your space, you have a data-backed signal the market exists. **Time:** 5 minutes. ### 3. DimeADozen Starter (third - $9, optional) -If VenturusAI and Preuve both gave green or yellow signals, spend $9 on a DimeADozen Starter report. Read only the Kill Risks and Retention-Curve sections. If the report flags specific kill risks, address them before booking interviews. If it comes back clean, you have three independent tools saying your hypothesis is structurally sound. +If VenturusAI and Preuve both gave green or yellow signals, spend $9 on a DimeADozen Starter report and read only the Kill Risks and Retention-Curve sections. Address any specific kill risks before booking interviews; a clean report means three independent tools say your hypothesis is structurally sound. **Time:** 10 minutes + $9. ### After the tools: Lesson 2.1 interviews -No tool validates your hypothesis. Only ten strangers describing the problem in their own words can do that. The tools tell you whether the sentence is well-constructed. The interviews tell you whether the sentence describes something real. +No tool validates your hypothesis - only ten strangers describing the problem in their own words can. The tools tell you the sentence is well-constructed; the interviews tell you it describes something real. --- @@ -287,11 +283,11 @@ 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 Lesson 1.2-1.4's smoke-test landing page and Lesson 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 Lesson 2.1 surface what specific named humans actually did last Friday - a signal no AI tool can produce. +**They cannot tell you whether the problem is real.** AI tools summarize what people have already said online; they cannot surface a problem nobody has articulated publicly. The Mom Test interviews in Lesson 2.1 surface what specific named humans actually did last Friday. **They cannot substitute for the Pragmatic-lens gut-check.** VenturusAI can flag that you have no engineering background, but only you know whether you can ship the thing with Lovable on evenings and weekends. The Pragmatic lens in Lesson 1.1 is still yours to score. -**They do not replace talking to humans.** If you spend three hours across these tools and zero hours on interviews, you have three AI reports and zero validation. The tools exist to sharpen the sentence you test in interviews. Skip the interviews and you have sharpened a sentence that might describe nothing. +Spend three hours across these tools and zero hours on interviews and you have three AI reports and zero validation. The tools sharpen the sentence; the interviews test whether it describes anything real. --- From 8563805ce5cc2cd830b9a8261f29cca203348650 Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 01:38:24 +0200 Subject: [PATCH 10/12] refactor(course-w5): compress customers-leaving-churn-triage-not-acquisition toward band 2870 -> 2860 words. Light pass: removed a restated 'messy middle' line and a doubled 'wrong segment never converts' sentence. All teaching, tables, cohort data, mermaid, and the refund-email prompt unchanged. Soft-over; no deeper fat without cutting teaching. Co-Authored-By: Claude Fable 5 --- .../customers-leaving-churn-triage-not-acquisition/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 9b96f79180..ba7f1be5ef 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 @@ -65,7 +65,7 @@ The fix was not a better Meta Ads brief. The fix was to stop the ads, run a 90-m Bucket holds **32 paying users at $29 / month**. Stop the ads. Run the 90-minute cohort triage. Decide: fix the product, change the segment, or kill the SKU. -Module 5 (Lessons 5.1-5.7) teaches you how to land your first paying customers. This chapter covers what Module 5 does not - what to do when the customers you already have are leaving faster than the funnel can replace them. It is the chapter for the messy middle - the founder who hit Module 5 once, got customers, and watched them slip away faster than the spreadsheet predicted. +Module 5 (Lessons 5.1-5.7) teaches you how to land your first paying customers. This chapter covers what Module 5 does not - what to do when the customers you already have are leaving faster than the funnel can replace them. It is the chapter for the messy middle: you hit Module 5, got customers, and watched them slip away faster than the spreadsheet predicted. The KISS rule for this chapter: if your churn is above 30% in a 30-day window, every dollar you spend on acquisition is wasted until you triage. Read on. @@ -156,7 +156,7 @@ The most common founder failure mode at this triage step is to refuse to pick. T ## The Refund-the-Wrong-Segment Script -Decision 2 is the hardest to execute because it requires telling 18 of your 30 paying customers, in writing, that you built the wrong product for their situation. The default response is to flinch at this step. They run an "improvement campaign" instead, hoping the wrong segment will start retaining if the product gets a few more features. It will not. The wrong segment never converts to the right segment. +Decision 2 is the hardest to execute because it requires telling 18 of your 30 paying customers, in writing, that you built the wrong product for their situation. The default response is to flinch and run an "improvement campaign" instead, hoping the wrong segment starts retaining with a few more features. It will not - the wrong segment never converts to the right one. Refunds are cheaper than churn. If a wrong-segment user churns at month 2, you have collected $58 and lost $200 in CAC and ~$25 in support time - net negative. If you proactively refund their last 30 days at month 2, you have lost $58 plus the same $200 CAC, but you have gained a goodwill quote, a clean Stripe ledger, and 20 minutes of support time you would otherwise spend explaining why the product feels off. The math on a wrong-segment refund campaign is positive against the alternative of waiting for churn. From 94e4a996777eeb55c2c0ca9dcc432833a3123052 Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 01:38:24 +0200 Subject: [PATCH 11/12] refactor(course-w5): compress five-tech-words-stop-nodding-at toward band 2733 -> 2688 words. Removed one abstract 'learn vocabulary under pressure' paragraph that restated the concrete opener and 'why now' section - also drops a mild fake-authority generalization tell. All five word definitions, BS-question prompts, Rails examples, and both acronym tables unchanged. Co-Authored-By: Claude Fable 5 --- .../five-tech-words-stop-nodding-at/index.md | 2 -- 1 file changed, 2 deletions(-) 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 238d60ab7f..6e2de63b55 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 @@ -34,8 +34,6 @@ related_posts: false One word can hide a year in which nothing shipped. "Refactoring" means changing the structure of code without changing what the user sees, so when an agency uses it to narrate week after week, there is nothing user-visible to check it against, and "we're refactoring the order flow" can cover a stretch where production never moved. That is how the word runs up a bill: **$51K and a year of runway** can pass before a new fractional CTO reads the repo and finds nothing new since month three. The glossary below hands you, for each word, the one question the padded version cannot answer. -Non-technical founders often learn engineering vocabulary under pressure, mid-meeting, with a bill on the table. The agency throws a word, the founder nods, the meeting moves on. By the time the founder figures out what the word actually meant, the next sprint is already approved. - Below is the cheat sheet for the five words that hide the most invoices: refactoring, Docker, tech debt, MVP, architecture. For each you get a plain-English definition, the dishonest version your dev shop probably means when they say it, and one question you can ask in your next standup that the BS-version cannot answer. ![Jargon translator: what your dev shop says vs what it usually means, for refactoring, Docker, tech debt, MVP, and architecture](jargon-translator.svg) From d14ec57682809a6a23ac009d34e820c78d3129d0 Mon Sep 17 00:00:00 2001 From: Paul Keen <125715+pftg@users.noreply.github.com> Date: Sun, 2 Aug 2026 01:45:07 +0200 Subject: [PATCH 12/12] fix(course-w5): validation-tools - complete the elliptical readability line (reviewer P3) Co-Authored-By: Claude Fable 5 --- .../validation-tools-field-guide/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 b5a795c0d8..bb7bbbcf5e 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 @@ -95,7 +95,7 @@ Two are free; none costs more than a month of Perplexity Pro. Run at least one b VenturusAI runs your business idea through three classic strategic frameworks - SWOT (Strengths, Weaknesses, Opportunities, Threats), PESTEL (Political, Economic, Social, Technological, Environmental, Legal forces), and Porter's Five Forces (Buyer Power, Supplier Power, Threat of Substitution, Competitive Rivalry, Threat of New Entrants). It also produces sections on target audience, marketing strategy, and financial estimates. -Think of it as a free MBA student who reads your one-paragraph description and produces a structured critique in 30 seconds. The frameworks are academic; the output is practical when your input is. +Think of it as a free MBA student who reads your one-paragraph description and produces a structured critique in 30 seconds. The frameworks are academic; the output is practical when your input is specific. ### What to prepare before you open it