Before you write a single line of code, there are 15 questions every app idea needs to survive. This checklist condenses months of failed launches and successful validations into a structured process you can complete in a week.
Work through each step honestly. The goal is not to kill your idea — it is to arrive at a version of the idea that has the highest chance of success, or to fail fast if the fundamentals aren't there.
Problem Validation (Steps 1–5)
Step 1: Can you describe the problem in one sentence without mentioning your solution?
If your problem statement includes words like "app," "platform," or "tool," you're describing a solution. A real problem statement sounds like: "Freelance writers lose 4–6 hours per week managing invoices and follow-up emails." Rewrite until the problem stands alone.
Step 2: Do you personally know 5 people who have this problem?
This is the minimum viable sample for problem existence. Not potential users — people you can call right now who would recognize the problem immediately. If you struggle to name five, the problem may be niche to the point of being unviable, or you may not know your target market well enough yet.
Step 3: Are people currently paying for an imperfect solution?
Existing payment behavior is the strongest signal that a problem is real and worth solving. Find the top three alternatives to your idea and confirm they have paying users. Reviews mentioning pricing while continuing to pay are especially strong signals.
Step 4: What is the cost of not solving this problem?
Quantify the pain. Time lost, money lost, stress, or missed opportunities. The higher the cost, the higher the willingness to pay for a better solution. Problems that cost users under $10/month in aggravation rarely support SaaS pricing above $10/month.
Step 5: Is the problem getting worse or better over time?
Problems worsening due to structural trends (regulatory change, market growth, technology shifts) are better bets than problems being slowly resolved. Confirm the trajectory before committing.
Market Validation (Steps 6–9)
Step 6: How many potential customers exist?
You don't need a precise number. You need to confirm the market isn't too small. A rough calculation: if you charged $50/month, how many customers would you need to reach $10K MRR? Is that number plausibly achievable given who you're targeting?
Step 7: How do potential customers currently find solutions to this problem?
If users can't easily find existing solutions, they likely won't easily find you either. The channels your competitors use to acquire users are the channels available to you. If there are no channels, distribution is your first problem, not your product.
Step 8: Is the market growing, stable, or declining?
Check Google Trends for related keywords. Look at how long established competitors have been growing. Read industry reports for your category. Building on a declining trend is an uphill battle that compounds over time.
Step 9: What does the competitive density tell you?
A market with 2–5 direct competitors is typically healthy. Zero competitors suggests the market may not exist. Twenty competitors suggests commoditization. Either extreme requires a clear explanation for why you'd succeed where others haven't.
Competitor Analysis (Steps 10–12)
Step 10: What are the top 3 complaints about each major competitor?
Read at least 50 reviews per major competitor across App Store, Google Play, and Product Hunt. Identify the patterns. If you can't identify three recurring, specific complaints, either the competitors are excellent (bad for you) or you haven't read enough reviews.
Tools like GoShipOrSkip automate this process, analyzing hundreds of reviews across multiple platforms and surfacing the key patterns in minutes.
Step 11: What do customers love about existing solutions?
You need to preserve what's working while fixing what isn't. Five-star reviews reveal what the market values — features you must match or exceed. Ignoring five-star reviews leads to building something that addresses complaints but loses the core value.
Step 12: Can you complete this sentence clearly?
"Unlike [competitor], my product is specifically for [persona] who needs [capability], which [competitor] doesn't provide because [reason]." If you can't complete it without using vague words like "better" or "simpler," you don't have clear differentiation yet.
Demand Validation (Steps 13–15)
Step 13: Have you built a landing page and measured signups?
A landing page with a clear value proposition and email capture is the cheapest validation experiment. Run $50 of targeted ads to your target customer profile. A 15%+ email capture rate suggests strong problem-solution fit messaging. Below 5% signals a messaging or targeting problem.
Step 14: Have you asked for money before building?
Pre-sales or commitments to pay are the gold standard. Even a single paying customer before building is more signal than a hundred "I'd definitely use this" responses. If you've found someone willing to pay for early access, the problem is real and your solution is plausible.
Step 15: What would make you stop building this?
Define your kill criteria in advance. "If I can't get 10 paying customers within 30 days of launching a beta" is a clear, honest exit condition. Founders who define this upfront avoid the trap of rationalized persistence — continuing to build long past the point where the evidence says stop.
Scoring Your Validation
Count how many of the 15 steps you can answer with clear, specific, evidence-backed responses:
- 12–15 clear answers: Strong signal. Proceed to build with confidence.
- 8–11 clear answers: Promising but gaps exist. Address the unclear steps before building.
- Below 8: Significant unknowns remain. More research before committing to development.
Validation is not a one-time exercise. Revisit this checklist after your first 10 customer conversations — your answers will likely change, and that's valuable information.