Twenty-Percent Paid Validation
Test an unfinished product with paying customers to reach truth faster.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 97%
Identify the commercial assumption most likely to invalidate the idea, then build only enough of the product to test that assumption—Herjavec suggests roughly 20 percent rather than waiting for completion. Present it to a genuine target customer and require a meaningful market signal, ideally payment, rather than relying on compliments from non-paying testers. Acceptance shows that the problem and proposed value may be real; rejection exposes objections while changes remain inexpensive. Use the evidence to modify the offer, run another paid test, or abandon the idea. The goal is not careless speed or shipping a dangerous product. It is to compress the distance between an assumption and credible customer truth so repeated decisions improve the product before resources are exhausted.
Origin
Herjavec presents this as a practical way to develop urgency and fail quickly when creating products. Extracted from BigDeal.
Core principles
- 01Real payment reveals more than polite feedback.
- 02Early failure is useful because it preserves time and capital.
- 03A partial product can test the riskiest assumption.
- 04Fast decisions create more opportunities to learn and adapt.
How to run it
- 1
Find the Critical Assumption
Name the belief about the customer, problem, price, or solution that would make the idea fail if it proved false.
- 2
Build the Testable Twenty Percent
Create only the portion needed to demonstrate the core outcome or sell the proposed result.
- 3
Ask a Real Customer to Pay
Take the incomplete offer to someone who genuinely experiences the problem and request money or another costly commitment.
- 4
Classify the Signal
Separate acceptance, price resistance, trust concerns, missing functionality, and lack of need instead of treating every no identically.
- 5
Iterate or Exit Quickly
Improve the smallest relevant component and retest, or stop when repeated evidence invalidates the core premise.
In the wild
A founder developing scheduling software completes only the workflow needed to demonstrate automated appointment recovery. She offers a paid pilot to three clinics before building reporting, integrations, and administration features. Two clinics decline because they need a specific integration, while one pays for the pilot.
→ The founder validates willingness to pay and learns which integration deserves the next development cycle.
Herjavec advises a product creator to avoid waiting for 100 percent completion and testing with non-paying users. Instead, the creator should finish about 20 percent and call a paying customer.
→ The business reaches acceptance or failure while adaptation is still fast and inexpensive.
Common mistakes
Perfecting Before Contact
Completing the entire product delays the discovery of fundamental demand or positioning problems.
Testing Only With Free Users
People behave differently when a transaction requires them to exchange real money for value.
Mistaking Speed for Sloppiness
The test should minimize unnecessary scope, not abandon safety, honesty, or professional standards.
Is it for you?
Best for
It is best for founders testing a new product, service, feature, or commercial proposition.
Not ideal for
It is not ideal for safety-critical products whose incomplete versions could harm users or violate regulations.
From the transcript
“Find a way to fail quickly.”
“Finish 20% of it, test it with the real customers.”
“Get as fast as you can to acceptance or failure as quickly as you can.”
From the episode
The Mindset Shift That Made Me Millions