How to Validate Your MVP Idea Before Writing a Line of Code

Building a product nobody wants is the single biggest waste of startup resources. Here's how to validate before you build.

1. The Landing Page Test

Build a landing page in one day that describes your product *as if it already exists*. Add a waitlist or a "Buy now" button. Drive 200–500 targeted visitors with a small ad budget ($50–$200).

What you're measuring: Email signups or payment intent — not just clicks.

What counts as validation: >5% conversion on a cold audience means the problem resonates.

2. The Concierge MVP

Do the thing manually before automating it. If you're building a bookkeeping tool, offer to do bookkeeping manually for 5 small businesses. If it's a hiring platform, manually match candidates by hand.

Why it works: You learn the exact pain points, edge cases, and what users actually value — before writing any code.

3. The Wizard of Oz Test

Build the front-end UI that *looks* automated but is actually powered by humans behind the scenes. Users interact with what feels like a real product; you deliver manually.

Famous example: Zappos founder photographed shoes from local stores and put them online. When orders came in, he bought the shoes retail and shipped them. Only after validating demand did he build the real system.

4. Pre-Sell Before You Build

If you can get someone to pay for a product that doesn't exist yet, you've validated the idea.

• Offer early adopter pricing (30–50% off)
• Be transparent: "We're building this, you're getting in early"
• Use Stripe payment links or even bank transfers

What counts as validation: At least 3 paying customers before a line of code is written.

5. Problem Interviews (The Right Way)

Most founders do customer interviews wrong — they pitch and look for validation. Instead:

1. Never mention your solution in the first 10 minutes
2. Ask about the past, not the hypothetical ("Tell me about the last time you...")
3. Listen for emotion — frustration, time lost, money wasted
4. Ask "how are you solving this today?" — if they're not solving it at all, the problem may not be urgent

Red flags: People say "that's interesting" or "I'd use that." Green flags: "I need this. When can I get it?"

6. Competitive Analysis

If no one has built this, it's either a massive opportunity — or a sign that others have tried and failed. Research:

• Direct competitors (same problem, same solution)
• Indirect competitors (same problem, different solution)
• Why users switch away from existing tools (Reddit, G2, Trustpilot reviews)

The Validation Stack

For most B2B SaaS ideas, run these in order:

1. Problem interviews (1 week, 10+ people)
2. Landing page test (3 days, $100 in ads)
3. Pre-sales outreach (2 weeks, LinkedIn + email)

If all three show signal → start building your MVP.

When Validation Is Not Enough

Validation tells you if people *want* something. It doesn't tell you if you can *build* it fast enough, if the unit economics work, or if you can acquire customers at scale. Those answers only come from a real product.

The bottom line: Validation should take 2–4 weeks maximum. Any longer and you're procrastinating on building.