Many startups fail because they build something nobody needs. This practical guide shows six ways to validate your idea, from direct conversations with target users to quick, data-driven tests. It helps you move beyond gut instinct and gather real signals that your idea is worth the time and money it takes to build.
The six methods
- Problem interviews. Dig into real pain points and avoid assumptions.
- Solution interviews. Test whether your concept actually solves the problem for users.
- Pre-sell or pre-commit. Get buy-in before you build, through early pilots and letters of intent.
- Landing page experiments. Use simple, no-code sites to test interest and messaging.
- Community listening. Find where your target users already talk about their needs.
- Using external data. Check your idea against market size, competitor traction and investor trends.
Once you have a signal, size the opportunity with the Market Size Guide.
Running your first problem interviews
Problem interviews are the cheapest, fastest validation method and the easiest to get wrong. These habits keep them honest.
- Talk about their life, not your idea. Ask how they handle the problem today. Once you pitch your solution, people start being polite instead of honest.
- Ask about the past, not the future. "When did this last happen, and what did you do?" is far more reliable than "Would you use something that…?"
- Follow the money and the time. Ask what they have already spent, in cash or hours, to solve the problem. Real pain usually has a cost.
- Listen more than you talk. Aim for the other person to speak most of the time.
- Write it down straight away. Capture exact phrases. Customers' own words are useful later in your messaging and your deck.
- Look for patterns. One strong opinion is an anecdote. The same problem described by many people is a signal.
After a round of interviews, sort what you heard into problems people mentioned often, problems they described as painful and problems they already pay to solve. The overlap is where your opportunity is strongest.
Then move to solution interviews and stronger tests, such as pre-sales or pilots, before you commit significant time and money to building.
Choosing the right method for your stage
- Just an idea? Start with problem interviews and community listening. They cost almost nothing and show whether the problem is real.
- A solution in mind? Use solution interviews and a landing page test to see whether your answer resonates.
- Ready to build? Ask for commitment through pre-sales, pilots or letters of intent before you invest heavily.
- Raising money? Add external data on market size and competitor traction to support your story.
Most founders combine several methods. Each one reduces a different kind of risk, so together they give you far more confidence than any one alone.
Who it's for
- Early-stage founders who want to avoid months building something no one needs
- Startup teams refining their go-to-market strategy before launch
- Anyone with an idea who wants real proof that the problem and solution resonate
- Founders already raising who want data to strengthen their pitch
Validation questions founders ask
How many customer interviews should I do?
Enough to hear the same problems repeated. Many founders aim for a few dozen conversations before drawing firm conclusions.
What is the difference between a problem interview and a solution interview?
A problem interview explores the pain without mentioning your idea. A solution interview tests whether your proposed fix actually helps.
Is a landing page test enough to validate an idea?
It shows interest, not commitment. Pair it with a stronger signal, such as a pre-order, a pilot or a letter of intent.
How do I show validation to investors?
Use evidence, not opinion: interview patterns, sign-ups, pilots and early revenue. Put it in your deck and share it as a tracked Pitchwise link.
What is a minimum viable product?
The simplest version of your product that lets real users get value and gives you real feedback. It should test your riskiest assumption, not every feature.
How do I avoid confirmation bias?
Decide before each test what result would prove you wrong. Then accept the answer, even when it is not the one you hoped for.
When should I stop validating and start building?
When you have consistent evidence that the problem is real, painful and something people will pay to solve. You will keep validating as you build, but at that point the main risk shifts to execution.
Can I validate an idea without building anything?
Yes. Interviews, landing pages and pre-sales all test demand before you write code or build a product.

.png)


