Idea Validation Checklist: 10 Steps Before You Build

---

You have an idea. It feels like a good one. Your friends think it’s clever. You’ve already sketched the feature list.

Stop. You’re about to make the most common mistake in product development: building before validating.

According to CB Insights, 35% of startups fail because there’s no market need — not because the technology didn’t work. The fix isn’t better code. It’s better research. This checklist is the research.

The 10-Step Validation Checklist

Step 1: Define the Problem in One Sentence

Write a single sentence: “I’m solving [specific problem] for [specific person] who currently [current workaround].”

If you can’t fill in all three blanks, you don’t have a product idea yet. You have a solution looking for a problem. This is where most founders stumble — they describe features instead of pain points. Customer research fixes this.

Pass criteria: You can state the problem without mentioning your product.

Step 2: Identify Your Target Customer

Not “everyone.” Not “small businesses.” Name a specific person with a specific role, budget, and urgency.

A good customer profile includes: job title, company size, the moment when the problem becomes urgent (the “trigger event”), and how much they’d pay to make the problem disappear.

Pass criteria: You can describe your customer in enough detail that you could find 10 of them on LinkedIn in 15 minutes.

Step 3: Find 15 People Who Have the Problem

Not 15 people who might have the problem. Not friends. Not fellow founders. Find 15 real humans who are actively dealing with the pain you want to solve.

Where to find them: LinkedIn (search by job title + industry), relevant Slack communities, Reddit threads about the problem, industry forums, conference attendee lists.

Pass criteria: You have a list of 15+ names with contact information.

Step 4: Conduct Customer Discovery Interviews

Talk to at least 10 of those 15 people. Not a pitch — a conversation. Your goal is to understand their world, not sell your idea.

Key questions:

• “How do you currently handle [problem]?”
• “What’s the most frustrating part of your current approach?”
• “How much time or money does this cost you?”
• “What have you already tried to fix it?”

If you want a structured approach, use the Jobs-to-Be-Done framework to uncover what progress they’re trying to make.

Pass criteria: At least 7 out of 10 interviews confirm the problem exists and matters enough to pay to solve.

Step 5: Map Existing Solutions and Workarounds

Your competition isn’t just other products — it’s spreadsheets, manual processes, email chains, and “we just live with it.” Map every way your target customers currently deal with the problem.

This tells you two things: how much pain the problem actually causes (the more elaborate the workaround, the more pain) and what you need to be significantly better than.

Pass criteria: You can list 3+ current workarounds and explain why each one falls short.

Step 6: Define Your Unfair Advantage

Why will your solution win? “Better UX” is not an answer. “AI-powered” is not an answer. What specific insight do you have — from your interviews — that competitors have missed?

The best unfair advantages come from customer research. You’ve talked to the people. You understand a nuance that the market leader has overlooked. That’s your edge.

Pass criteria: You can articulate one specific insight from your research that competitors don’t have.

Step 7: Test Willingness to Pay

This is where most founders get uncomfortable — and where the most valuable signal lives. Before building anything, test whether people will pay.

Methods:

• Pre-sales: “If I built this, would you pay $X/month? Can I send you the first invoice when it’s ready?” Track who says yes.
• Landing page test: A simple page describing the product with a “Join waitlist” or “Pre-order” button. Drive traffic with $200–$500 in ads. Measure conversion rate.
• Concierge MVP: Deliver the result manually to 3–5 customers. Charge them. If they pay for the manual version, they’ll pay for the automated one.

Pass criteria: At least 3 people have committed money (pre-paid, signed a LOI, or paid for the manual service).

Step 8: Build a Clickable Prototype

Not code. A visual mockup in Figma, Framer, or similar tools that demonstrates the core workflow. This costs $2,000–$5,000 versus $15,000+ for a functional build.

Put it in front of 5–8 target users. Watch them use it. Don’t explain anything — let them navigate and narrate. The gaps between what you expected and what they do are your most valuable data.

Pass criteria: Users can complete the core workflow without assistance, and at least 4 out of 5 say they’d use this.

Step 9: Define Your Minimum Testable Product

Not a minimum viable product. A minimum testable product — the smallest thing you can build that tests your riskiest assumption.

Your interviews and prototype tests have revealed what matters most. Build only that. If your idea has 8 features, your first build should have 2.

Pass criteria: You can describe the build in one sentence and estimate its cost within a narrow range.

Step 10: Set Kill Criteria

Before you spend a dollar on development, define what failure looks like. What results — after launch — would tell you to pivot or stop?

Examples: “If fewer than 50 people sign up in the first 30 days, we pivot.” “If our 30-day retention is below 20%, we rethink the core value proposition.” “If zero customers convert from free to paid in 60 days, we kill it.”

Without kill criteria, you’ll spend months optimizing something that should have been abandoned. This is how the $200K mistake happens — founders who never defined what “not working” looks like.

Pass criteria: You have 2–3 specific, measurable conditions that would trigger a pivot or stop.

The Scoring Reality Check

Count your passes:

• 9–10 passes: You’ve done the work. Build with confidence.
• 7–8 passes: Close, but the gaps are where risk lives. Shore them up before committing budget.
• 5–6 passes: Significant validation gaps. Go back to interviews before building.
• Below 5: You have a hypothesis, not a validated idea. That’s fine — but don’t spend $15,000 proving it wrong.

Key Takeaways

• Validation isn’t a phase you skip to move faster — it’s how you avoid building something nobody wants
• Talk to at least 10 real potential customers before writing a line of code
• Test willingness to pay before building — pre-sales and landing page tests cost almost nothing
• Define kill criteria upfront so you know when to pivot, not just when to keep going
• A $3,000 validation sprint costs 90% less than discovering “no market need” after launch

What To Do Next

If you scored below 7, start with Step 4 — customer discovery interviews are the highest-ROI activity for any founder at the idea stage. If you’ve validated demand and you’re ready to scope a prototype, our team runs research-driven prototype sprints that start with validation and end with a working product — see what a typical engagement looks like.

---

---