Field note for founders

Keep a launch evidence log from your first prototype

A one-page log that records what you shipped, how you checked it, and what you decided next — so every prototype makes the next launch faster.

2026-10-06 · field notes for founders

Fifty launches. Every useful lesson. That line only works if you wrote things down.

Zero to Public is a 187-page field manual and online library built from fifty real internet properties. It documents what was launched, what each product cost, what happened after release, what earned revenue, what failed, and which operating decisions made the next launch faster and less fragile. Figures in the public roster are publication snapshots rather than live status claims.

You can use the same habit on your first prototype. Not a dashboard. Not a post-mortem. A launch evidence log: one page per shipped change, kept while you build.

From Zero to Public field manual cover with a stack of pages spilling onto a blue sheet — The owned From Zero to Public field manual—the context for the habit, not a substitute for keeping your own record.

What to record — five fields only

Hypothesis: Who is this for, and what useful outcome do you expect?
Shipped change: What exactly did you release, and what did you deliberately leave out?
Verification: How did you check delivery and real use? Name the page, test, and date.
Actual outcome: What happened, including weak or zero results?
Next decision: Improve, stop, or keep as infrastructure for the next product?

If it does not fit on one page, the scope is too large. Cut the build, not the log.

Launch cycle log worksheet with fields for expected observation, actual observations, and the next-cycle decision — An actual Launch & Distribution worksheet from the collection, page 18: a useful prompt for recording observations, limits, and the next cycle.

Illustrative hypothetical example — not a portfolio result, not a customer story

Hypothesis

Solo organizers will pay for a one-page event checklist that prints cleanly on mobile.

Shipped change

Oct 12 — single HTML page, 12 checkboxes, print CSS, checkout link. No accounts, no email reminders.

Verification

Loaded on phone and desktop, printed to PDF, completed test purchase path without submitting payment, asked 5 organizers to try the checklist on a real event.

Actual outcome

No result is supplied here because this is a teaching example. In your own log, record the visits, completions, revenue, or zero sales you actually observed, along with the date.

Next decision

If 2 of 5 complete setup without help, narrow to one organizer type and add save-to-PDF. If 0 complete, stop and archive the log.

One-page product promise worksheet with prompts for the useful output, delivery limits, and an acceptance example — An actual Build the MVP worksheet from the collection, page 13: use it when the shipped change needs a precise promise and a realistic acceptance example.

Copy this template

Use this for every prototype:

Date / version:Write the release date and version you can identify later.

Hypothesis (audience + measurable signal):State who it is for and what you expect to observe.

Shipped (URL + what changed + explicit exclusions):Describe the smallest useful workflow and what stayed out.

Verification (manual test + date + who checked):Name the device, path, test, date, and checker.

Costs / time spent:Keep the resource cost beside the result.

Actual outcome (traffic, use, revenue, lessons — including nothing):Record weak outcomes instead of editing them away.

Evidence links (screenshots, receipts, notes):Keep the source material that lets you revisit the decision.

Next decision:[improve / stop / reuse] + reason + date for re-check.

Checklist before you call it launched

One workflow works end-to-end on mobile and desktop
Price, delivery, and access are stated in plain language
You kept the receipt: cost, time, traffic, revenue, lesson
Weak outcomes are recorded, not deleted
Next step has an owner and a date

How this connects to the books

This log is the working habit behind the manual. How to pressure-test an idea before committing to a full build, how to scope an MVP around one useful workflow and a measurable signal, how one server, AI agents and a checkout-first bias support repeated launches, how to record costs, traffic, revenue and lessons without hiding weak outcomes, and how to turn each launch into reusable infrastructure are covered in full in From Zero to Public.

If you want the complete system, get the complete manual for $19 — one-time purchase includes the complete PDF and access to the 58-chapter online library. Or choose your books: $19 each or $59 for all four, including Idea Validation, Build the MVP, and Launch & Distribution, each with eight printable worksheets.

Then browse all fifty property case files, including FoodPhoto, LogoAhora, BunBandit, and Zero to Public; read the five operating-system notes on infrastructure, agents, checkout, traffic, and portfolio decisions; and explore eight cross-property portfolio patterns. For scope and refunds, read the terms and refund scope and review the privacy policy. You can also explore the online library and see the launch directory statistics.

Start today: open one page, write your hypothesis, ship the smallest useful workflow, verify it by hand, record the actual outcome, and decide what happens next.

Keep the evidence close to the work.

Use the complete manual for $19, choose your books, or open the online library when you need the next practical decision.

Get the complete manual for $19

Choose your books · Explore the online library · Browse all fifty property case files