The Founder OS Pack: Your Evidence in One Folder

Companion to the From Idea to First Paying Customer course - the index for the artifacts the modules produce.

Use when you finish a module (file the new artifact) and again after Lesson 5.7 (check the pack is complete).

Every module of this course ends with something you made, not something you read. Those 6 artifacts, filed in one Google Drive folder, are your Founder OS: the written record of what you tested, what the evidence said, and what you decided. Print this page and drop it in the folder as the cover sheet - it lists each artifact, the lesson that produces it, and what someone reading your folder learns from it.

The folder is private. Nothing in this course publishes it anywhere. But the day you talk to an investor, a co-founder, or your first hire, this is the folder you open: not a pitch about what you believe, a record of what you observed.

Prefer paper? Download the PDF - same content, print-ready.


The pack index

Check each artifact off as you file it. If one is missing, the lesson link is the way back.

☐ 1. Founding Hypothesis

  • Built in: Lesson 1.1 - Form Your Founding Hypothesis
  • What it is: your idea as a one-sentence bet - who the customer is, what problem you solve, why they’d pick you - scored ≥14/20 across four lenses.
  • What a reader learns: you can state the bet in one testable sentence, and you scored it before you spent money on it.

☐ 2. Smoke-test demand and price data

  • Built in: Lessons 1.2-1.5, ending with the price test
  • What it is: the conversion numbers from 300 cold visitors on your smoke-test page, plus the click-to-payment rate on a real Stripe price button.
  • What a reader learns: strangers - not friends - responded to the offer at a stated price, before anything was built.

☐ 3. Validated Problem Statement

  • Built in: Lesson 2.5 - Mom Test Synthesis · template
  • What it is: 10 scored interview transcripts distilled into a one-page problem statement, with your written build / pivot / kill decision.
  • What a reader learns: you interviewed 10 real people, scored each call against a rubric, and wrote the decision down - including what the evidence ruled out.

☐ 4. One-page Product Brief

  • Built in: Lesson 3.1 - The One-Page Product Brief · template
  • What it is: the single page that scopes your MVP (minimum viable product - the first working version), with every feature traced to something a customer said.
  • What a reader learns: scope discipline. The build follows customer evidence, not a feature wishlist.

☐ 5. Live MVP and Ownership Checklist

  • Built in: Lesson 4.4 - Build Phases + Lesson 4.2 - Ownership · checklist
  • What it is: the URL of your working product, plus the audited 12-item checklist confirming the code, cloud, domain, and database accounts are in your name.
  • What a reader learns: the product exists, it runs, and no contractor or agency can hold it hostage.

☐ 6. Signed paid pilot agreement

  • Built in: Lesson 5.6 - Charge Before You Ship
  • What it is: a signed DPA (Design Partner Agreement - a one-page co-design pilot contract) with the refundable Stripe deposit cleared in your account.
  • What a reader learns: revenue. A customer paid real money before you shipped - the strongest single line in the folder.

Filing it

  1. Create one Google Drive folder. Name it Founder OS - [your product].
  2. Drop each artifact in as you finish its module - a doc, a spreadsheet export, a screenshot of the live URL, a signed PDF.
  3. Print this page and put it first, so anyone you hand the folder to reads the index before the evidence.

That is the whole system. No tool to install, no account to create - a folder and the work you already did.


Done: the folder exists, this index sits on top, and every artifact you’ve produced so far is filed.

Next: keep filing as you move through the modules. After Lesson 5.7, run down the index once more - a complete pack means the course delivered what it promised.

If blocked: an artifact is missing and you’re not sure why. Its “Built in” link above goes to the lesson that produces it - the lesson’s Done block states exactly what the artifact must contain.


Built by JetThoughts as part of the From Idea to First Paying Customer free curriculum.