How Founders Validate Ideas: A Blueprint for Building What People Actually Want

You have an idea for a new product and you think it's really, really good. You're tempted to dive straight into building it. "People are going to LOVE this!"

This is a trap.

Many founders learn this the hard way by spending weeks, months, or even years building something people don't want because they never stopped to validate their idea first . The statistics are sobering: the majority of early-stage startup failures stem from a weak grasp of customer needs, not product quality . The issue isn't that founders lack creativity—it's that they skip the messy, uncomfortable step of talking to real users.

The good news? You don't need code. You don't need a product. You don't even need a developer. What you need is proof .

In this comprehensive guide, we'll explore how successful founders from companies like Linear, Mercury, PostHog, and others validated their ideas before committing significant resources. Whether you're a first-time founder or a seasoned entrepreneur, these validation tactics will help you build with confidence, knowing that demand exists before you write a single line of code.

---

The Scientific Approach to Idea Validation

Treat Ideas as Hypotheses, Not Gospel Truths

What does it mean to "validate" a startup idea? At its core, it's about treating business ideas as hypotheses to be tested, rather than truths to be defended .

Research from INSEAD involving 759 startups across multiple cities found that companies embracing the practice of rigorously formulating and testing hypotheses consistently outperformed their peers. They were more likely to weed out unviable ideas early on, pivot to more promising directions, and generate more revenue .

The scientific approach to entrepreneurship follows four key steps:

1. Start with a theory: Begin with your strongest intuition about a problem and solution

2. State your hypotheses: Clearly articulate specific assumptions about your business idea

3. Validate your hypotheses: Design experiments to test each assumption

4. Refine and retest: Continuously refine your theories based on experimental results

This framework transforms validation from a vague concept into a systematic process. Instead of asking "Is my idea good?" you ask specific questions: "Is this problem painful enough that people would pay for a solution?" or "Will this specific customer segment adopt our product?"

The Power of Pivoting

One of the key findings from the INSEAD study is that scientifically minded entrepreneurs are more likely to pull the plug on dubious projects and redirect their efforts to more promising ventures . They avoid the sunk cost fallacy that plagues many startups.

Take Osense, a sustainability-focused venture that participated in the study. The founders avoided wasting time and resources on their envisioned product—a peer-to-peer rental platform—after collecting data that indicated it would fail. Instead, by rigorously testing their hypothesis, they pivoted quickly to a more promising idea: a platform for tracking indirect carbon emissions. After just 10 interviews with sustainability managers, nine of which were overwhelmingly positive, they knew they were onto something big .

---

Before You Start: Building Your Problem List

One Idea is Good; Many Are Better

Before diving into validation, you need something to validate. PostHog's co-founders, James and Tim, pivoted five times before settling on their successful product analytics platform. James admits "we had a lot of terrible ideas"—and validation was there to tell them just how bad they were .

Your ideas should be framed as problems: jobs-to-be-done by your product for a specific customer. Often, the most promising problems come from personal experience:

• Mercury's founder "was just really frustrated" that banking felt like a static, archaic system

• Deel's founders repeatedly faced problems hiring internationally in past startups

• ElevenLabs' founders thought movies dubbed into their native Polish were flat and monotonous

James started with a three-page Google Doc of ideas based on problems he encountered in his career. More were added as he worked through validating them with his co-founder. Many ideas were bad and never got past the first step of validation. Others got further before being invalidated. Only PostHog—"open-source product analytics built for engineers"—made it to the end .

The irony? They stumbled on the right idea through the process of validating their other ideas. Every time they built something and tried to deploy analytics, they were frustrated by hard-to-implement tools not designed for builders.

---

Step 1: Validate the Problem Is Real

Talk to Potential Users

The first and most critical step is confirming that the problem you want to solve actually exists and matters to people. You do this by talking to potential users .

No one else will do this for you. James from PostHog got at least two meetings a day, five days a week while doing other random tasks. He was constantly asking for intros and doing cold outreach via his network .

How to Get Meetings

Getting people to talk to you is often the hardest part of validation. Here are proven tactics:

• Use your network: Find people who want to respond to you—friends, former teammates, followers, members of communities you're part of

• Ask for intros: Sometimes the people you know can introduce you to other relevant people. Mercury's founder says "some of the most useful people were four intro chains down" 

• Be concise: Two to three sentences, not walls of text. Be clear you want feedback—say it's an interview. Don't try to sell yet

• Be quick: Follow up fast. Startups win on speed

• Do interviews in-person if possible: This helps you better understand context and catch non-verbal cues 

What to Ask in Customer Interviews

The quality of your insights depends entirely on the quality of your questions. Ned Dwyer, co-founder of Great Question, suggests using a structured interview script to prevent asking leading questions .

A good script follows an inverted pyramid: start broad and gradually narrow down to your hypothesis. Here are questions that work:

• "Tell me about your job and your company. What do you do?"

• "Tell me about a day in your life. What's your biggest problem?"

• "What about that problem is painful?"

• "In the next quarter, how likely are you to solve this problem?"

• "Have you already got a plan to solve that?"

• "Have you got a budget to solve that problem?" 

Always open by setting context: explain you're there in a research capacity, not to sell anything. Stay vague in your product description so as not to cloud judgment. Add something like: "I'm looking for your genuine feedback. Please don't pump me up—I want to hear what your actual problems are" .

What to Listen For

You're looking for evidence that the problem is real and urgent. Key signals include:

• People have tried to solve it themselves (often with spreadsheets or manual workarounds)

• They can describe specific painful experiences related to the problem

• They're excited to talk about it and ask follow-up questions

• They ask when your solution will be available 

If people aren't engaged or the problem doesn't feel urgent, it's probably time to pivot to a new problem.

Common Failure Modes in Problem Validation

• Just asking people if they like your idea: Most people will say "yes" or "it's interesting" to get you to stop talking. This doesn't equal validation 

• Asking the wrong people: Sometimes the problem is right but the audience is wrong. Double-check your assumptions

• Telling people what they need: You're validating, not selling. Let them describe their experience

• Going too slow: Speed matters. As one founder put it, "the quicker you are, the worse you can be at product. If you are bad at product and slow, you are doomed" 

---

Step 2: Validate the Solution

From Problem to Solution

Once you've confirmed the problem is real, it's time to validate that your solution resonates with users. This phase is similar to the first, but now you're testing your proposed fix .

Having co-founders helps here—one can focus on building while the other handles validation. In PostHog's early days, Tim built while James sold.

One of their first products was a complicated sales territory management tool for sales reps. After 15 sales leaders said they would use it, they built it and sent them a link. Only one person clicked the link, and they didn't even log in. This was a clear sign that this wasn't what users wanted .

The Minimum Viable Test (MVT)

Gagan Biyani, repeat founder and CEO of Maven, has developed an alternative to the MVP designed specifically for validating ideas before building: the Minimum Viable Test .

"An MVT is a test of an essential hypothesis—something you must be right about, or else the company won't stand a chance," he says .

The MVT framework has four steps:

1. Pick a clear and specific atomic unit: The smallest possible item you could distill your product down to. For Google, it's a search query. For Amazon, it's ordering a book online 

2. Define your risky assumption and test just one at a time: For Maven, the riskiest assumption was whether people would pay 10x more for a cohort-based course than an asynchronous one 

3. Devise a test for that specific assumption: For Maven, Biyani actually ran one course with a partner who already had an audience. It was a hyper-narrow test that achieved exactly what he needed: the course had a 9/10 rating and made over $150,000 in its first cohort 

4. Don't build everything—focus only on the hypothesis: The goal is learning, not launching

Selling Before Building

Material Security's founders took validation to another level. With four potential ideas, they decided to try selling before building anything .

They created "marketing vignettes"—pitch decks built to look like pared-down sales landing pages, with descriptions of different features. No demo, no landing page, no mockup. Just slides.

Over several months, they pitched each idea to different prospects. A clear winner emerged based on two signals:

• One idea generated 20 meetings while others generated only two

• After pitches, prospects asked real questions: "When will this be ready?" "How much does it cost?" "How long does it take to integrate?" 

Common Solution Validation Problems

Not explaining your solution clearly: Articulating the problem is only half the battle. You need to articulate your solution, too. If you do this well, you might build a waitlist before launching—like Dropbox's famous demo video .

Lack of credibility: If you're struggling to convince users, it may be because you don't have enough "street cred." PostHog addressed this by publishing their handbook publicly and making their product open-source and self-hostable, addressing trust concerns .

---

Step 3: Validate Your Solution Works

The Retention Test

The ultimate validation comes from retaining users. If you can retain users, you are repeatedly solving their problems. This is rare, valuable, and a sign you should start investing more .

At an early stage, retention measurement doesn't need to be complicated. You're looking for a retention curve that flattens out—meaning people keep coming back.

Other useful signals include:

• Qualitative feedback: Ask the product-market fit question: "How would you feel if you could no longer use the product?"

• Session replays: Watching real users use your product reveals what's working and what's confusing

• Activation metrics: Users need to experience value before they'll stick around

• Revenue: Having people pay you (or desperately want to pay you) is clear evidence of validation 

Working in Bets

Ned Dwyer suggests working through validation in "bets"—essentially two-week sprints focused on a single hypothesis .

"When you work in bets, you commit to one hypothesis," he explains. Look at your hypotheses quickly and pick one—the biggest, the gnarliest, the one with mega money-making potential.

Create a testing plan and decide how you'll proceed based on results. Then throw yourself at this plan for two weeks.

Dwyer and his co-founder used this approach at Y Combinator. At one point, they tested whether researchers were their ideal early adopters. Before conducting interviews, they decided: if we get five responses out of 100 messages, we'll add an extra week. If we only get two, we'll stop and change something.

As it turned out, researchers were not their ideal early adopters. They're often risk-averse, have long sales cycles, and don't like being early adopters. Working in bets helped them discover this quickly rather than building on a bad assumption .

---

Advanced Validation Techniques

Zero-Cost Validation

Validating an idea doesn't require money—it requires curiosity. Think of it like testing whether a seed can sprout before farming acres of land around it .

Student founders can run these tests from a hostel room using nothing more than social media, free tools, and curiosity. Simple questions provide clarity:

• Is this problem real, or just relatable among friends?

• Are people currently paying for any workaround?

• Would the user feel relieved if this solution existed?

• Are there active discussions about this problem in communities or forums? 

Platforms like Reddit, LinkedIn, and Quora act as free insight hubs—people openly discuss what bothers them, what they're willing to try, and what they ignore.

Go Undercover at Your Day Job

If your coworkers fit your ideal customer profile, validation can happen before you quit your day job. That's exactly what Linear's Karri Saarinen did .

He and his co-founders hated the project management software they used at fast-growing startups. Over about a year, they ran casual user research with coworkers, asking:

• What do you think is bad about this tool?

• How would you want to improve it?

• What would make you more productive?

Everyone had complaints, but most assumed this wasn't a problem that could be solved. One grievance stood out: how slow the tools were. This insight shaped Linear's focus on speed and performance .

Don't Pitch Your Friends

Ryan Glasgow did the opposite when validating Sprig—he kept his outreach cold to see if prospects were genuinely interested, not just doing him a favor .

"One of the key learnings I had early is to never involve people who you personally know in the customer development process. Folks often reach out to their own audience for customer development, but I think it's often misleading," he says .

See If Other Founders Have Idea FOMO

To narrow down ideas for Crossbeam, Bob Moore pitched his contenders to other founders—but with a different question .

"With founders, I wasn't asking, 'Would you buy this?' But instead, 'Would you start this company? And what are the things that you think you might bump into?'" he says .

This approach broadened his horizons of what the ideas could become, rather than narrowing them to how a specific persona would use them.

Design Matters

"My personal belief now is that design is super important. I don't think you can get away with an ugly-looking product anymore," says Ajay Prakash, founder of EntryLevel .

People make snap decisions based on appearance. You could lose users just because your product looks scammy. In 2025 especially, people come from a perspective of no trust, and you've got to build that trust fast .

---

What Counts as Real Validation?

Not sure what qualifies as proof? Here are the signals successful founders chase :

• Email signups for a waitlist

• User interviews with pain point confirmation

• Heatmap clicks on mockups

• Survey data from ideal users

• Pre-orders or signups for early access

Someone liking your idea at a conference proves nothing—it's a throwaway comment, not meaningful insight .

---

The Toolkit: Tools to Validate Without Code

You don't need to write a single line of code to validate your startup idea. Here are tools founders use in 2025 :

All of these tools are affordable, no-code, and startup-friendly.

---

What's After Validation?

If you clear all three stages—problem validation, solution validation, and retention validation—congratulations: your idea is validated and you're on your way to product-market fit .

But the reality is you never stop validating. You still need to:

• Validate features on your roadmap

• Talk to users and figure out their real problems

• Get people to try what you've built

• Activate and retain them

• Iterate on feedback 

Success in entrepreneurship is less about unwavering belief in a singular vision, and more about the disciplined, systematic testing of ideas .

---

Conclusion

The difference between founders who succeed and those who waste years on the wrong idea often comes down to one thing: validation.

Not fancy pitch decks. Not months of silent coding. Not assumptions dressed as certainty. Just the willingness to get uncomfortable, talk to real humans, and let their feedback guide your path.

The most successful founders share a common mindset: they fall in love with the problem, not their solution . They treat ideas as hypotheses to test, not truths to defend . They collect data like diamonds and let it inform their decisions .

Validation isn't about preventing failure—that's impossible. The goal is to increase your chances of success . Every conversation, every prototype, every failed experiment teaches you something that brings you closer to building something people actually want.

As you start your validation journey, remember that you're not alone. There are countless resources, communities, and tools designed to help founders like you build smarter. For more insights on building and scaling your startup, explore our blog for articles on entrepreneurship, product development, and growth strategies. And when you're ready to start building, check out our curated list of products and tools that can accelerate your journey.

The teams that win consistently understand that technical skills get you into the game, but customer understanding determines who wins. In the end, it's not about what you build—it's about whether anyone needed it in the first place.