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 6030e1e21..32beb7a07 100644 --- a/content/course/tech-for-non-technical-founders-2026/_index.md +++ b/content/course/tech-for-non-technical-founders-2026/_index.md @@ -39,7 +39,7 @@ hero_secondary_url: "/course/tech-for-non-technical-founders-2026/quickstart/" hero_secondary_text: "3-minute Quickstart" --- -Five modules take you from that idea to a signed paid pilot: test demand with strangers, interview the people who respond, turn their words into a one-page brief, build the MVP yourself with no-code tools, and charge your first customer before you ship. The first checkpoint comes fast: two to three weeks in, at an evenings-and-weekends pace, you get a go/iterate/kill verdict on your **Founding Hypothesis** (the one-sentence version of your idea: who the customer is, what problem you solve, why they'd pick you) from real demand data instead of polite nods from friends. +The first checkpoint comes fast: two to three weeks in, at an evenings-and-weekends pace, you get a go/iterate/kill verdict on your **Founding Hypothesis** (the one-sentence version of your idea: who the customer is, what problem you solve, why they'd pick you) from real demand data instead of polite nods from friends. Two ways in: [Start Lesson 1.1 →](/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/) or [see the full syllabus ↓](#module-map). *Prefer a map first? [How This Course Works](/course/tech-for-non-technical-founders-2026/how-this-course-works/) (10 minutes) and the [FAQ](/course/tech-for-non-technical-founders-2026/faq/) cover the route and the most common blockers.* @@ -66,11 +66,11 @@ Why free? A founder who validates before building makes a better future client t The five mistakes below sink more first products than bad code does - we have watched each one play out. The course heads each one off:
The course assumes zero coding ability - Lovable + Supabase + Stripe handle the technical side.
+Covered as a build-path decision in Lesson 4.1, not as org design; early-stage management lives in the Friday Demo Rule + Weekly Dev Report.
+The course produces the artifacts investors want to see. It does not teach pitch decks or fundraising mechanics.
+Module 5 covers your first customers; SEO, content marketing, and paid acquisition at scale are a separate discipline.
+Also out of scope: mobile-only and marketplace-only specifics (they have their own playbooks), and legal incorporation, taxes, and IP filings - use a lawyer or a service like Stripe Atlas, Clerky, or Firstbase. If you need something on this list, the course won't help with it.
Output: a one-sentence Founding Hypothesis + a live smoke-test page (a landing page describing your unbuilt product, to see whether strangers sign up) with a Stripe price button.
-Start here if you don't have a one-sentence Founding Hypothesis yet, or you have one but never tested demand with a landing page.
- -You leave with: a Founding Hypothesis, demand data from cold strangers, and a price test - before you've built anything.
-See it in action: Mia builds TutorMatch - a full Module 1 walkthrough
+Deliverable: a one-sentence Founding Hypothesis + a live smoke-test page (a landing page describing your unbuilt product, to see whether strangers sign up) with a Stripe price button.
+Chapters
+See it in action: Mia builds TutorMatch
+Output: 10 Mom Test interviews (customer conversations run under rules that stop people from politely lying to you - ask about past behavior, never pitch) + a prototype built with Lovable (an AI app builder that turns text prompts into working screens), shown to 5 of them.
-Start here if you've never talked to 10+ potential customers about the problem you want to solve.
-Templates: Interview Script, Interview Scorecard, Validated Problem Statement, Outreach Sequence
-You leave with: 10 scored interview transcripts, a written build/pivot/kill decision, and a prototype 5 real customers have clicked through.
-See it in action: Mia interviews ten parents - a full Module 2 walkthrough
+Deliverable: 10 Mom Test interviews (customer conversations run under rules that stop people from politely lying to you - ask about past behavior, never pitch) + a prototype built with Lovable (an AI app builder that turns text prompts into working screens), shown to 5 of them.
+Chapters
+See it in action: Mia interviews ten parents
+Output: one-page Product Brief drafted from interview transcripts.
-Start here if you've validated the problem but don't have a one-page Product Brief.
- -Template: Vibe PRD
-Glossary: Five Tech Words to Stop Nodding At (reference, not in the linear path)
-You leave with: a one-page Product Brief where every feature traces back to something a customer actually said.
-See it in action: Mia writes the one-page brief
+Deliverable: one-page Product Brief drafted from interview transcripts.
+Chapters
+ +See it in action: Mia writes the one-page brief
+Output: a live MVP at a real URL, built on Lovable + Supabase (a hosted database with user login built in) + Stripe, ownership locked Day 1.
-Start here if you have a Product Brief and need to build the MVP.
-Templates: Build Path Decision Worksheet, Ownership Checklist, Self-Serve Stack Walkthrough, Pre-Launch Checklist
-You leave with: a live MVP at a real URL that you built and you own - every account in your name from Day 1.
-See it in action: Mia ships TutorMatch
+Deliverable: a live MVP at a real URL, built on Lovable + Supabase (a hosted database with user login built in) + Stripe, ownership locked Day 1.
+Chapters
+See it in action: Mia ships TutorMatch
+Output: one paying customer through a deliberately chosen channel.
-Start here if your MVP is live but you don't have a paying customer with a signed pilot.
-Template: First Paying Customer Operating Kit
-You leave with: a signed paid pilot and your first dollar from a customer, not a favor.
-See it in action: Mia gets paid
+Deliverable: one paying customer through a deliberately chosen channel.
+Chapters
+See it in action: Mia gets paid
+ .module-card__leave;
+ this bundle loads after it, so neutralize that inherited pseudo — the ruby
+ ✓ below sits on the sentence, the label owns the top of the panel. */
+.blog .module-card__leave::before {
+ content: none;
+}
+.blog .module-card__leave p:last-child {
+ margin: 0;
+ font-size: 15px;
+ line-height: 1.55;
+ color: #3a3f4a;
+}
+.blog .module-card__leave p:last-child::before {
+ content: "✓ ";
+ color: var(--color-ruby);
+ font-weight: 700;
+}
+@media (min-width: 780px) {
+ .blog .module-card__head {
+ grid-template-columns: minmax(0, 290px) minmax(0, 1fr);
+ align-items: start;
+ }
+ .blog .module-card__body {
+ grid-template-columns: minmax(0, 1fr) minmax(0, 300px);
+ }
}
/* V1.3 Dark closing endcap band — obsidian island with a soft ruby
@@ -194,31 +296,49 @@
}
}
-/* L5-condense (40.26) — NOT-cover exclusions as a tight two-col list;
- the why-excluded explanations sit in one