Indie Hacker Product Validation: Testing Ideas Before You Build
Learn proven methods to validate your product ideas before writing a line of code — from landing page tests and smoke tests to pre-sales and concierge validation.
The Cost of Building Before Validating
Every indie hacker has a graveyard of half-finished projects. Months of development time poured into features nobody wanted, marketing efforts that fell flat, and the crushing disappointment of launching to crickets. The root cause is almost always the same: building before validating. When you invest significant time coding a product before confirming demand, you gamble with your most scarce resource.
The validation-first approach flips the equation. Instead of asking can I build this, you ask should I build this. Validation does not need to be expensive or time-consuming. In fact, the most effective validation methods can be completed in a weekend. The goal is to gather real evidence that people will pay for your solution before you commit weeks or months.
The Landing Page Smoke Test
The landing page smoke test remains the gold standard for early-stage validation. Create a single landing page describing your product concept, its key benefits, and a call-to-action button that says something like Get Early Access or Join the Waitlist. Drive targeted traffic through a small ad spend on Facebook or Google, or share in relevant communities.
The metric that matters most is the conversion rate from visitor to signup. A rate above five percent suggests real interest, while anything below two percent indicates weak demand. More importantly, the follow-up email sequence builds a relationship with potential early adopters.
Pre-Selling Before Building
Pre-selling takes validation further by asking people to commit money before you build. This is the ultimate signal — talk is cheap, but credit card charges reveal genuine willingness to pay. Launch a discounted lifetime deal on a platform like Product Hunt or through your own audience. If even ten people pay for something that does not exist yet, you have compelling evidence.
The psychological shift when real money is involved is profound. You now have accountability to deliver, which focuses your development on what actually matters to paying customers. Pre-sales also provide initial revenue that can fund development, and early customers become your most engaged beta testers.
The Concierge Validation Method
Concierge validation means manually delivering your product promised outcome before any automation exists. If you are building a SaaS tool for social media scheduling, manually schedule and post content for a handful of customers for a week. If your idea is an automated report generator, create the reports by hand. This reveals whether customers actually value the result.
The insights from concierge validation are unmatched. You learn exactly which features customers use, which they ignore, where they get confused, and what they are willing to pay. Document every interaction and look for patterns. These patterns become your product requirements with zero guesswork.
Fake Door Testing
Fake door testing places a button or feature link on your existing site that leads to a Coming Soon page. Track how many people click it. If hundreds of visitors click a feature that does not exist yet, you have found a real demand signal. This works especially well when you already have a product or audience.
The ethical concern with fake door testing is real. Mitigate this by being honest on the destination page: say you are exploring this feature and ask for their email to be notified when it launches. The click-through rate combined with email signups provides a double validation signal.
Interview-Driven Validation
Customer interviews remain the most informative validation method when done correctly. The key is asking the right questions. Never ask would you use this or would you pay for this — people want to be helpful and will almost always say yes. Instead, ask about their current behavior: how do you solve this problem today, what do you hate about your current solution, how much time or money does this problem cost you each month.
The answers reveal whether the problem is acute enough to justify a paid solution. A prospect who describes their current workaround in frustrated terms and can quantify the cost is a strong validation signal. Conduct at least fifteen to twenty interviews before making a build decision.