Founders learn the most about a new idea by talking to people who already have the problem and people who have already built in the space, before a single line gets built.
The Moment Every Founder Dreads
You spend months, sometimes years, building something. You put money into it, convince investors to back it, and tell everyone you know about it. Then you launch, and nobody cares.
The people you hoped to reach never needed it. They were never your customer, and all the planning and confidence did not change that. This happens constantly, and most of the time it is preventable.
Most founders do talk to potential customers before building. The trouble is how they talk to them. They describe the idea and ask, "Would you use this?" People say yes, because saying yes costs nothing when nothing is at stake. Then the founder builds, launches, and blames the market, the timing or luck. The fix is a better kind of conversation, and it starts with knowing the difference between research and validation.
The Difference Between Research and Real Validation
Research means asking people hypothetical questions about a hypothetical product. "If we built something that did X, would you be interested?" "Would you pay for a solution that works like Z?" People answer these politely and seem engaged, and most of those answers predict very little about what they will actually do.
Real validation comes from someone with skin in the game. This person has a problem right now, spends time and money on workarounds, and would benefit immediately from a solution. They talk differently. They get specific about the gap, name the tools they have tried, explain where those tools fail, and tell you what it costs them to live with the problem. That person is your buyer, and that is who you need to hear from before you build anything.
Why Expert Conversations Are Your Cheapest Validation
The people who have already built in your space are your best first reference check. Suppose you have a SaaS idea, a clear market and a sketched product. Have you talked to the 5 people who tried to build in this space and either won big or failed?
One conversation can give you what took them 6 months to learn. They can point out the landmines before you step on them, tell you what customers want versus what customers say they want, and show you what is defensible and where competition arrives immediately. They can also tell you whether your idea is smart or whether you are walking into a wall.
Most of them will talk to you if you are honest about why you are asking: "I'm exploring this space, you have already done this, and I'd love to learn from what you built." People with real experience enjoy talking with someone curious and willing to learn. You are not a competitor yet, and they remember what it felt like to be where you are. An hour with the founder who built a competitor 3 years ago and sold it is worth more than most consulting engagements, because the advice comes from someone with real stakes. If you would rather book that conversation than chase an introduction, our guide to choosing the right expert shows how to pick someone whose experience matches your exact problem.
The Customer Conversation That Matters
Next come your actual customers. You know who you think they are, but have you asked about their workflow? Skip "Would you use a tool that does X?" and ask instead: "Walk me through your week. What takes the most time? What frustrates you? What are you using today, and where does it break? When did you last get frustrated enough to look for something different? What would need to be true for you to switch? Have you ever paid to solve this problem before?"
Listen, ask follow-ups, and resist the urge to defend your idea.
Here is what usually happens. The problem you thought was their main pain turns out to matter less than you assumed. Or it matters, yet it is a problem they will never pay to solve. Or the workflow is more complex than you understood and your idea does not fit into it. Or a constraint appears that changes what you need to build: budget, approval chains, integration requirements or regulation. Sometimes you learn that someone has already built something close, and customers keep using it despite its flaws because switching costs are high. All of that is validation, and it is real, messy and specific.
What Real Validation Looks Like
Real validation rarely sounds like "Yes, I'd definitely use that." It sounds like this:
- "We spend $3,000 a month on workarounds. Something that cut that in half would pay for itself immediately."
- "I tried a competitor, but it does not do the one thing we need. If you built that, I'd be interested."
- "Our team spends about 15 hours a week on this. If you could cut that to 5, I'd test it right away."
- "We have stayed with our current tool because switching is painful. If you could do that one thing, the switch would be worth it."
- "I need this specific feature. Everything else is secondary."
When someone quotes a budget, describes an exact problem or names a competitor, they are thinking about your idea seriously instead of being polite. Those conversations tell you what to build.
The Pre-Build Advantage
Before you have invested heavily, you can still change direction. You can pivot, decide the market differs from what you assumed, or discover that 3 experts independently mention the same problem you missed. After you build, momentum, ego and a team executing your original vision make every change harder.
So have the conversations first. Talk to 5 experts who have done this, 10 customers who have the problem, and 3 people who tried to build it and failed. Then build. You will still face surprises, but you will miss far fewer landmines, and you will know what matters before you spend 6 months and $100k finding out. If you plan to book an expert for this, read 5 questions to ask before you book any expert session first.
How to Have These Conversations
Start by getting specific about who you need to hear from. For experts, ask who has built something similar, who has written about the space, and who speaks at conferences. For customers, ask where they gather, which communities they join, and which thought leaders they follow. For people who tried and failed, find out whether they talk about it publicly.
Next, reach out honestly. A message like this works: "I'm exploring an idea in your space. You've built something in this area, and I'd love to learn from it. Would you have 20 minutes to chat?" Most people say yes, because people like talking about what they have built and like helping someone who is curious.
Then prepare questions without scripting them. What did you build? What worked, and what did not? What surprised you about the market? What would you do differently? Who is the ideal customer? What stopped you from scaling, or what let you scale? Follow up on what they say, and listen for what they mean beyond the words.
With customers, start with problems before solutions: "Tell me about your workflow. What takes the most time? What is frustrating?" When a pain point comes up, dig in: "That happens every week? What does it cost you per month? How have you tried to solve it?" Near the end, ask: "If something made this problem disappear, what would that be worth to you?" You will recognize real interest when you hear it. To get the most from a short call, see how to get maximum value from a 30-minute expert call.
The Real Lesson
Most founders skip these conversations because they feel slow. They want to build fast and "fail fast", which usually means building fast, launching half-baked, and being surprised when nobody wants it. Talking to people is faster. 4 weeks of real conversations with experts, customers and people who tried before you will teach more than 6 months of building in the wrong direction.
After that you build knowing who your first customers are, because you have already spoken with them, and you know what to prioritize. That avoids the hardest part of entrepreneurship: spending time, money and energy on something nobody wants.
So before you build, invest or commit, have the conversations. Talk to people who know, listen to people who would buy, and learn from people who tried. If you want a fast route to someone who has already done it, browse experts on TapTime and book the conversation before you write the first line of code.
Frequently Asked Questions
How many people should I talk to before building? A workable target is 5 experts who have built in your space, 10 customers who have the problem, and 3 people who tried and failed. Keep going until the same problems repeat across conversations.
Why do customers say yes to my idea and still not buy? Saying yes costs nothing when nothing is at stake. Ask about their current workflow, what they spend today and what they have already tried, and weigh those answers above their opinion of your idea.
Will experts really give me their time? Most will, when you explain honestly that you are exploring the space and want to learn from what they built. A specific request for 20 minutes works better than a vague request to pick their brain.
What if the feedback says my idea is weak? That is the best outcome of validating early, because you can pivot before you spend months and money building. A clear no in week 2 costs far less than a quiet failure after launch.