A real product
A working public URL with a usable core loop — not a static concept or design file.
Product Builders Challenge 01
Ship one real thing in 30 days.
Bring one narrow product Bet. Put £30 on the deadline. Build in public, demo the result, and leave with proof that another builder can inspect.
The finish line
Receipts, not vibes.
“I worked on it” is not the outcome. Verification checks five visible artifacts against the commitment you wrote before the clock started.
A way to respond
A live checkout, waitlist, booking flow, or another clear customer action.
A public launch
A dated launch post that explains the customer, problem, and what changed.
A five-minute demo
A short walkthrough showing the product working and the builder explaining the result.
An evidence readout
The metric, threshold, actual result, and an explicit keep, kill, or compound decision.
Operating rhythm
A deadline with a pulse.
Four checkpoints turn a distant launch date into the next smallest move. Progress is visible; scope gets cut before it becomes fatal.
Lock the Bet
Publish the customer, problem, threshold, kill date, and exact finish criteria.
Show the risky core
Demo the smallest working loop and cut anything that does not serve the Bet.
Put it in customer hands
Bring a working URL, the first response signal, and one decision the evidence forced.
Ship and show the outcome
Send the product, demo, launch, evidence readout, and learning memo for verification.
Hardcore terms
The £30 buys consequence, not a badge.Enrollment creates the private workspace first; Stripe payment confirms the cohort place. Miss the published finish criteria and the stake is gone. Payment never proves completion. Product Builders reviews the final links and awards the Ship in 30 seal only when the proof holds up.