80% Launch Rule
Launch a viable product, then improve while competitors copy the old version
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 4
- Confidence
- 97%
The guest's rule is to launch when a product is roughly eighty percent ready instead of treating perfection as the release condition. The mechanism is time asymmetry: getting from an idea to a viable product may take weeks, while polishing the final portion can take many additional months and allow competitors to enter first. Before applying the rule, define what ‘ready’ means in terms of safety, function, compliance, and the customer promise. Those are gates, not optional polish. Once the product clears them, begin production and selling while continuing to develop the next version. A competitor that copies the released product is then copying an older state while the original team works from customer evidence toward a better version. The rule optimises learning speed, not permission to ship known harmful or non-functional goods.
Origin
Extracted from The Foundr Podcast
Core principles
- 01The final polish can consume more time than the usable first version
- 02Delay can cost the market window
- 03Launch and continued development can run in parallel
- 04Continuous improvement keeps the original creator ahead of copies
How to run it
- 1
Define viable readiness
Write the non-negotiable safety, legal, functional, and customer-promise requirements. Separate them from refinements that can wait.
Pro tip Make the threshold observable before perfectionism enters the decision.
Watch out Do not classify compliance or material defects as optional polish.
- 2
Measure opportunity cost
Estimate the additional time required for remaining refinements and what could happen in the market during that delay. Compare that cost with the likely customer value of waiting.
- 3
Release the viable version
Move the product into production and launch once it clears the defined readiness gates. Preserve a list of deferred improvements.
Pro tip Use version labels so customers and the team know which product the feedback concerns.
- 4
Develop ahead of copies
Continue improving while the first version is being produced and sold. Use actual feedback to choose the next changes.
Pro tip Prioritise repeated customer problems over founder-only preferences.
Watch out Continuous iteration requires real follow-through; an unfinished first version is not self-correcting.
In the wild
A founder has a travel accessory that is safe, compliant, functional, and solves the target problem, but keeps delaying for new colours and minor packaging refinements. Under the rule, the founder launches the viable design, records the optional work, and uses early customer feedback to decide which changes belong in version two.
→ The product reaches the market while development continues against real evidence.
Common mistakes
Calling defects the final twenty percent
Safety, compliance, core function, and the promised outcome must clear the release gate.
Polishing without a time trade-off
Optional improvements should be weighed against the cost of missing the market window.
Launching without iteration
The framework depends on improving the released version, not abandoning development at eighty percent.
Is it for you?
Best for
Founders whose safe, functional product is delayed mainly by optional refinements.
Not ideal for
Regulated, safety-critical, or materially defective products where the missing twenty percent includes mandatory performance or compliance.
From the transcript
“I always say like develop until a product is 80% ready.”
“I would launch it when it's 80% ready.”
From the episode
585: The $100K Mistake Most Founders Make with Manufacturers (and How to Avoid It) (Best of Foundr)