Startup Validation6 min readUpdated July 21, 2026

How to Validate a Startup Idea Before You Build

Most startups fail because nobody wants the product. Here is how to prove demand before you write a line of code.

Validation means proving people already spend time or money on the problem. Not asking friends if your idea is good.

Building before validating is expensive. You commit months of code, design, and marketing to an unproven guess. Validation replaces guesses with evidence. It is cheaper to learn nobody cares from a landing page than from a launched product.

Why validation comes first

Building before validating is expensive. You commit months of code, design, and marketing to an unproven guess. Validation replaces guesses with evidence. It is cheaper to learn nobody cares from a landing page than from a launched product.
Building before validating is expensive. You commit months of code, design, and marketing to an unproven guess. Validation replaces guesses with evidence. It is cheaper to learn nobody cares from a landing page than from a launched product.

Where to find honest signal

People lie in surveys and interviews. They are honest when they complain online. Reddit, Facebook groups, App Store reviews, and G2 reviews are goldmines of unprompted pain. Look for phrases like "I have tried everything" or "nothing works" or "I wasted $X on this."
People lie in surveys and interviews. They are honest when they complain online. Reddit, Facebook groups, App Store reviews, and G2 reviews are goldmines of unprompted pain. Look for phrases like "I have tried everything" or "nothing works" or "I wasted $X on this."

What counts as validation

Real validation is behavioral. A waitlist email is weak. A pre-order is strong. A complaint about a competitor combined with a price point is strongest. You want evidence that people act, not just agree.
Real validation is behavioral. A waitlist email is weak. A pre-order is strong. A complaint about a competitor combined with a price point is strongest. You want evidence that people act, not just agree.

5 Tips to Get Started

1

Talk to people who have the problem. Not people who might have it. Find them in Reddit threads, Facebook groups, or App Store reviews.

2

Ask about past behavior. "What did you try last time?" beats "Would you use this?" every time.

3

Run a smoke test. Build a landing page with a price and a button. If nobody clicks, the idea needs work.

4

Count frequency, not intensity. A problem that happens weekly is a business. A problem that happened once is a story.

5

Look for existing spend. If people already pay for a bad solution, they will pay for a better one.

Ready to Stop Worrying About Infra?

Knowledge is the first step. Get a free 1-hour diagnostic and see where your infrastructure leaks time, money, and focus.

r

roqy.io research team — Market validation specialists

Content reviewed by the roqy.io team. Our guides are based on publicly available data.

Disclaimer: This content is for informational and educational purposes only. It does not constitute professional advice or a guarantee of specific results. Infrastructure needs vary by team, stack, and stage. Consult a qualified engineer for advice tailored to your situation.

Frequently Asked Questions

How many customer conversations do I need?

Five good conversations show you the shape of the problem. Twenty let you see patterns. Fifty give you confidence. Start with five this week.

What is a smoke test?

A smoke test is a fake-it-till-you-make-it experiment. You describe the product, show a price, and measure how many people try to buy or sign up. No product needed.

Should I ask people what they want?

No. People are bad at imagining solutions. Ask what they did, what failed, and what they paid for. You design the solution.

Get the DevOps Ecosystem Behind You

One accountable engineer. Full platform behind him. Month-to-month, no lock-in.