Pick one question
Do not try to prove the whole business at once. Choose the riskiest question: whether the customer has the problem, will pay the price, can be reached through the channel or can be served at acceptable cost.
- Write the assumption as a testable statement
- Choose a result that would change your decision
- Set a deadline
Reduce scope, not usefulness
A minimum test should still produce the core customer outcome. Remove range, automation and polish before removing the part that solves the problem.
Simple example
A template seller can build one complete template for a narrow role and sell it directly before creating a large bundle or storefront.
Use pre-orders or manual delivery carefully
Pre-orders can test demand when the delivery date, product state and refund terms are clear. Manual delivery can test a software or day-to-day outcome before automation, provided customers understand what they are buying.
- Do not present a concept as a finished product
- Confirm that the manual process tests the same value
- Limit the number of early customers to what you can serve
Spend on the bottleneck
Use money only where it unlocks the test: safe samples, a required tool, a small venue booking or targeted access to customers. Use existing equipment and simple pages where they are sufficient.
- Keep a written budget
- Include payment and delivery costs
- Retain a reserve for corrections
Review without moving the goalposts
Compare the result with the success signal chosen before the test. real paying customers supports another controlled step. Specific objections support a focused improvement. Weak interest after reaching the intended customer may support pausing or changing direction.