How to Validate Your Startup Idea Before You Build

Short answer: validate a startup idea by proving three things before you spend serious money on development: that a specific group of people has the problem, that they care enough to change how they handle it today, and that some of them will commit something real, such as time, an email address, a deposit or a pre-order. Interviews, a landing page and a small paid test can tell you this in a few weeks.

Validation does not guarantee success. It reduces the chance of building something nobody wants, which is the most expensive mistake a founder can make.

Step 1: Write down your riskiest assumptions

Every idea rests on a few beliefs. Write them as testable statements:

• Problem: "Freelance designers lose hours every month chasing late invoices."
• Urgency: "They are actively looking for a better way, not just mildly annoyed."
• Solution: "Automatic reminders tied to the invoice would solve most of it."
• Willingness to pay: "They would pay a monthly fee to stop chasing."
• Reach: "We can find them through specific communities and newsletters."

Rank them by risk. The riskiest one is what you test first.

Step 2: Talk to people who have the problem

Aim for 10 to 20 conversations with people in your exact target group. The goal is to learn about their current behavior, not to pitch.

Good questions

• "Tell me about the last time this happened."
• "How do you handle it today?"
• "What have you tried that didn't work?"
• "What does it cost you, in time or money?"
• "If this were solved tomorrow, what would change for you?"

Questions to avoid

• "Would you use an app that does X?" People say yes to be polite.
• "How much would you pay?" Hypothetical prices are unreliable.

Listen for specifics: dates, tools, workarounds and frustration. Vague answers mean the problem is not painful enough.

Step 3: Look at what people already do

The strongest evidence is existing behavior:

• They have built a spreadsheet or workaround.
• They pay for a partial solution and complain about it.
• They search for solutions, ask in forums, or hire someone to do it manually.

If nobody is doing anything about the problem today, ask why. It may not be a real priority.

Step 4: Run a landing page test

Create a simple page that explains the value in one sentence, shows who it is for, and asks for a specific action: join a waitlist, book a call, or reserve early access. Drive a small amount of targeted traffic to it from the communities where your users spend time.

Measure:

• How many visitors take the action.
• Which message or headline works better (test two).
• Whether sign-ups respond when you email them.

A waitlist alone is weak evidence. Replies, calls booked and people asking "when can I use it?" are much stronger.

Step 5: Ask for a real commitment

The best validation is someone giving up something of value:

• A paid pilot or pre-order.
• A refundable deposit.
• A letter of intent from a business customer.
• Committing time to a structured trial.

Even a few paying early customers tell you more than hundreds of free sign-ups.

Step 6: Try a concierge or manual version

Before building software, deliver the outcome by hand for a few customers. Send the reminders yourself, do the matching in a spreadsheet, or run the service over email. You learn exactly what the product must do, and what it does not need to do, with almost no cost.

When to stop validating and start building

You are ready to build an MVP when:

• You can describe the target user precisely.
• Several of them have shown real commitment.
• You understand their current workaround and why it fails.
• You know the one core flow your product must deliver.
• You have a measurable goal for the first version.

At that point, more research has diminishing returns. The next lesson only comes from real software in real hands. Our guide What is an MVP? explains what to build, and How to write a PRD shows how to turn your findings into a scope.

Common validation mistakes

1. Asking friends and family. They want to support you, not tell you the truth.
2. Counting compliments. "Great idea!" is not evidence.
3. Validating the solution before the problem. Prove the pain first.
4. Endless research. Validation should take weeks, not months.
5. Ignoring negative signals. If interviews keep pointing elsewhere, follow them.

A two-week validation plan

If you want a concrete schedule, this works for many founders:

• Days 1 to 2: write your assumptions and rank them by risk. Draft your interview questions.
• Days 3 to 7: run 10 to 15 interviews with people in your exact target group. Take notes on behavior, not opinions.
• Days 8 to 9: build a one-page landing page with a single clear call to action.
• Days 10 to 13: share it in two or three communities where your users spend time, and follow up personally with everyone who signs up.
• Day 14: review the evidence against the success criteria you set on day one, and decide: build, adjust or drop.

Setting the success criteria before you start is the important part. It stops you from reading weak results as strong ones after the fact.

What strong evidence looks like

Strong evidence is specific and costly for the person giving it: someone describes the problem in detail without prompting, shows you their workaround, asks when they can start, or puts money down. Weak evidence is cheap: likes, compliments and "I would probably use that." Weigh one strong signal more heavily than many weak ones.

Frequently asked questions

How many interviews do I need? Usually 10 to 20 with the right people. Patterns tend to appear by the tenth conversation.

Can I validate with a prototype instead of an MVP? Yes. A clickable prototype can test whether users understand the concept. It cannot test whether they keep using it, which is what an MVP is for. See Prototype vs MVP vs Proof of Concept.

Should I validate before raising money? Yes. Evidence of demand makes conversations with investors much easier. See what pre-seed investors want to see.

Turn validation into a build plan

Once your idea is validated, FounderMate's MVP Spec turns your research into a product requirements document, user flows, a screen list, a tech stack and a fixed build quote in 5 days, for $490. When you are ready, Launch MVP builds your first version in about three weeks for $4,900.