How to Validate a Startup Idea Before Building Anything
The most common startup failure: building something nobody wants. The problem isn't execution - it's validation. You can validate 90% of assumptions before writing a single line of code.
The Three Assumptions to Validate
Every startup idea rests on three assumptions:
- Problem: This problem exists and people experience it regularly
- Solution: Your specific solution solves it better than alternatives
- Market: Enough people have this problem and will pay to solve it
Most founders validate only #2 ("I built this, do you like it?"). That's backwards. Validate in order: problem → market → solution.
Stage 1: Problem Validation (Week 1-2)
The Problem Interview
Talk to 15-20 potential customers. Goal: understand their current reality, not pitch your idea.
Questions that work:
- "Tell me about the last time you dealt with [problem area]. Walk me through what happened."
- "How do you currently handle [problem]?"
- "What's the most frustrating part of [current solution]?"
- "How much time/money does this cost you monthly?"
Questions that don't work:
- "Would you use an app that [your idea]?" - people lie about hypothetical behavior
- "Do you think this is a problem?" - they'll say yes to be polite
- "How much would you pay for [solution]?" - hypothetical pricing is meaningless
What you're looking for:
- Specific past instances of the problem (not "yeah that happens sometimes")
- Active workarounds (spreadsheets, manual processes) - evidence the problem is real enough to solve
- Emotional language about the problem ("it drives me crazy", "we lose hours every week")
Red flag: If people describe the problem vaguely or say "it's fine, just a bit annoying" - the pain isn't strong enough.
Stage 2: Demand Testing (Before Building)
Once you've confirmed the problem exists, test demand for your specific solution without building it.
Method 1: The Landing Page Test
Build a landing page describing your solution. No product behind it - just the value prop, a pricing page, and a "Sign up for early access" button.
Run $200-500 in Google/social ads to your target audience. Measure:
- Click-through rate: > 2% is promising
- Email signups: > 5% of page visitors is promising
This tests whether people want the solution enough to act, not just agree in conversation.
Method 2: Pre-Sales
"We're building [solution]. It launches in 6 weeks. First 10 customers get 50% off - locked in forever. Want to be one of them?"
If 3+ people pay upfront: you have real demand. If everyone says "sounds great, let me know when it's live" - you have polite interest, not demand.
Method 3: Concierge MVP
Deliver the service manually before automating it. If your idea is an automated accounting tool - do the accounting manually for 5 clients first. Charge them. See if they want to keep paying.
This validates willingness to pay and teaches you what the product actually needs to do.
Stage 3: Solution Validation (Before Full Build)
You have confirmed: problem is real, people will pay. Now test your specific solution.
Prototype Testing
Build a Figma prototype (no code). Get 5 potential customers to use it while you watch.
You're measuring:
- Can they complete the core task without help?
- Where do they get confused?
- What do they try to do that you didn't design?
One session rule: If one person struggles with the same thing - note it. If three people struggle - fix it before building.
The Smoke Test
Launch with a real (tiny) customer base before full development. A Notion doc, Airtable form, or even WhatsApp group delivering value manually. The tooling doesn't matter. Does the customer get value? Do they tell others?
Signals That Say "Build"
✅ You have paying customers or committed pre-orders
✅ 3+ people said "I'd switch to this from [current solution] immediately"
✅ You've identified the specific job-to-be-done people are hiring your solution for
✅ You understand the buying process (who decides, what they compare, what blocks purchase)
✅ You know your CAC and LTV rough numbers even at small scale
Signals That Say "Don't Build Yet"
❌ "People said they liked it" - without paying
❌ "We ran a survey, 78% said they'd use it" - survey responses are not customers
❌ "It's obvious this is a problem" - you're not the target customer
❌ No one can name a competitor - either blue ocean or no market
❌ Target customers can't explain how they'd justify buying it internally
The Validation Timeline
| Week | Activity | Output |
|---|---|---|
| 1-2 | 15 problem interviews | Confirmed problem + customer language |
| 3 | Landing page + $300 ads | Click/signup data |
| 4 | 5 pre-sale conversations | 0-5 paid commitments |
| 5-6 | Concierge MVP for 3 customers | Real usage data, actual payment |
| 7 | Prototype testing | UX assumptions validated |
| 8+ | Start building (if signals are positive) | - |
8 weeks of validation is far cheaper than 6 months of building a product nobody buys.
Get help validating your product idea →
Aunimeda builds software products for businesses - websites, mobile apps, automation systems, and custom platforms.
Contact us to discuss your project. See also: Web Development, Mobile App Development