Customer interviews are the cheapest and most reliable validation tool a founder has, and yet they remain the most skipped step in the entire startup playbook. Building for six months feels like progress, while talking to ten strangers feels awkward, so thousands of products launch every year to an audience that was never asked whether it wanted them. The graveyard of failed micro startups is not full of bad code. It is full of good code solving problems nobody was willing to pay to fix.
The good news is that great interviewing is a learnable skill with a small set of rules and a handful of questions that do most of the heavy lifting. This article explains why conversations beat surveys and landing pages, how to set interviews up so people tell the truth, and then walks through nine specific questions that separate polite encouragement from real buying intent. By the end, the phrase people said they loved it should never again appear in your validation notes without a number attached.
Why customer interviews beat every other form of validation?
Surveys, waitlists, and social media polls all share the same fatal flaw. They measure what people say in a context where saying yes costs nothing. A thousand waitlist signups can evaporate at the first invoice, and a survey full of enthusiastic ratings tells you only that clicking a star is easy. Live conversations are different because they let you probe, follow up, and watch for the hesitations and workarounds that written answers hide. The gold is rarely in the first answer. It is in the story behind it.
There is also a compounding benefit that founders discover only after their first ten conversations. Interviews do not just validate an idea, they rewrite it. Early customers describe the problem in their own vocabulary, reveal which adjacent pains hurt more than the one you targeted, and hand you the exact phrases that will later become your landing page. Founders who interview consistently report that their positioning, pricing, and roadmap all trace back to sentences a customer said out loud. Product-market fit, in that sense, is less invented than transcribed.
The math seals the argument. Ten solid conversations cost perhaps ten hours and zero euros, while building the wrong feature costs months. Every experienced founder has a story about the quarter they lost to an assumption that one phone call would have destroyed. Interviewing is not a detour from building. It is the fastest route to building the right thing, which is the only kind of speed that counts.
How to set up interviews so people tell you the truth?
The first rule sounds harsh but saves everything downstream. Do not pitch. The moment an interview turns into a demo, the other person switches into politeness mode and starts protecting your feelings, and polite feedback is worthless. Frame the conversation as research about their work and their problems, keep your product out of the first half entirely, and resist every urge to explain what you are building. You are there to learn how they live today, not to audition for their approval.
The second rule concerns the past tense. Ask about what people have actually done, never about what they would hypothetically do, because humans are wildly inaccurate at predicting their own behavior and remarkably accurate at describing it. A question about last month’s real workaround produces facts. A question about future intentions produces fiction delivered with a confident smile. Structure the whole conversation around specific recent events and the truth largely takes care of itself.
The practical setup is simpler than most guides suggest. Aim for fifteen to thirty people in a narrowly defined segment, since five interviews with the same profile teach more than twenty scattered ones. Recruit where your audience already gathers, in trade groups, forums, and communities, offering nothing more than genuine curiosity and perhaps a small thank you. Record with permission, take notes on exact phrases rather than summaries, and always end by asking who else you should talk to. Referrals from one good interview routinely fill the next three slots.
9 questions that reveal what people will actually pay for
Each question below has a specific job. Together they form a rough arc, from understanding the problem to testing real commitment.
1) Tell me about the last time you dealt with this problem
Opening with a story request instead of an opinion request sets the factual tone for everything that follows. Stories contain the context that opinions strip away, including when the problem struck, who was involved, and what was at stake. Listen for emotional language, because the words frustrating, embarrassing, and finally signal pain worth money. If the person struggles to recall a single concrete instance, that silence is itself a finding, and an important one.
2) What are you doing about it today
The current solution is your true competitor, and it is rarely another product. Most of the time you are competing against a spreadsheet, an intern, a group chat, or the time-honored strategy of ignoring the problem entirely. Understanding the existing workaround tells you the bar you must clear and the switching costs you must overcome. A messy, hated workaround is a wonderful sign. A comfortable one is a warning.
3) What have you already tried, and what happened
Past attempts at solving the problem are the strongest evidence of real pain, because searching, trialing, and buying all cost effort. Someone who tested three tools and abandoned each for specific reasons is handing you a requirements document. Someone who never looked for a solution is telling you, gently, that the problem does not hurt enough. This single question filters more false positives than any other on the list.
4) How much time or money does this cost you
Pain becomes purchasable only when it is quantified, so help the person do the math out loud. Hours per week, errors per month, deals lost per quarter, whatever the unit, get to a number and write it down. That figure later anchors your pricing, since a tool that saves a business five hundred euros monthly can comfortably charge fifty. When customers calculate their own cost of the problem, they are simultaneously building your business case for you.
5) Who else is involved when you decide on something like this
Micro startup founders routinely discover, too late, that their enthusiastic contact cannot actually approve a purchase. This question maps the real buying process, including the boss who signs, the colleague who vetoes, and the finance person who asks about invoices. In consumer contexts it surfaces partners and family members who influence spending. Knowing the cast of characters early shapes everything from pricing tiers to the content of your sales page.
6) What would need to be true for you to switch from your current approach
This question surfaces the hidden requirements that never appear in feature wish lists, such as data migration fears, contract lock-ins, training time, and plain old inertia. The answers often reveal that adoption barriers, not missing features, are the real enemy. Listen especially for the phrase it would have to, because whatever follows is a condition you must design for. Switching costs kill more sales than pricing ever does.
7) If a solution removed this problem completely, what would that change for you
Here you finally explore the upside, and the answer reveals how the person frames value. Some will talk about saved hours, others about reduced stress, career wins, or growth they could unlock. The framing they choose tells you which benefit belongs in your headline. Vague answers at this stage suggest the problem is an annoyance rather than a priority, which is exactly the distinction that decides whether anyone pays.
8) What almost stopped you from taking this call, or from trying solutions before
Objections gathered before you sell are worth ten times the ones discovered after launch. This question uncovers skepticism about new tools, past disappointments, security worries, and the quiet belief that nothing will really help. Each answer is a future FAQ entry, an onboarding fix, or a guarantee you should offer. Founders who collect objections early write sales pages that seem to read the customer’s mind, because in a literal sense they do.
9) Would you pay this amount, starting this month
The final question converts conversation into evidence, and it must include a real number and a real timeframe. Reactions split into three useful categories. Immediate agreement suggests you priced too low, negotiation signals genuine intent, and compliments without commitment mean no. Whenever possible, push past words toward action, such as a pre-order, a deposit, a signed letter of intent, or a scheduled onboarding date. People vote with calendars and cards, never with adjectives.
Turning interview notes into product decisions
Raw notes become useful only through synthesis, so block an hour after every batch of five conversations and look for patterns rather than anecdotes. Count how many people described the same pain unprompted, tally the workarounds, and collect the exact phrases that recurred. A problem mentioned spontaneously by seven of ten people in the same segment is a foundation. A problem mentioned by two, after prompting, is a distraction dressed as an opportunity. Discipline at this stage protects you from building for the loudest voice instead of the largest pattern.
Then translate patterns into three concrete artifacts. First, a one-sentence problem statement written in the customers’ own vocabulary, which becomes your positioning. Second, a shortlist of adoption barriers ranked by how often they appeared, which becomes your onboarding and objection-handling plan. Third, a pricing hypothesis anchored to the quantified cost of the problem, which becomes your first offer. When those three documents exist, building can start with a confidence that no amount of solitary brainstorming ever produces. And when a feature debate breaks out later, the notes settle it faster than any opinion.
The founders who win at this are rarely the best talkers. They are the best listeners, the ones who treat customer interviews as an ongoing habit rather than a launch-phase chore, scheduling a few conversations every month long after the first version ships. Markets shift, workarounds evolve, and yesterday’s validated pain quietly fades, so the interviewing muscle never really retires. Ten honest conversations still cost less than one wrong month of building. That trade will remain the best deal in the startup world for as long as startups exist.