Exactly. My process: 1. Ship an extremely simple MVP - Solve one problem, for one use-case, using one configuration - Time box this to a weekend - Price low to match the value of solving a simple problem If it gets no traction, move on. Otherwise: 2. Ship a more complete version - Take feedback from early customers - Improve the product following those feedback - Add more features & support more use cases - Raise prices - Ask for testimonials - Time box this to 1 month 3. Promote it widely - Turn customers feedback into your marketing messages - Turn your conversations with customers into your launch story - Spend most of the time promoting it: Reddit, Hacker News, PH, directories… The key is to balance the development commitment vs traction. The mistake most indie hackers make (me included) is to ignore the signal in step 1 (no/low traction) and keep adding features (step 2).