Most founder interviews fail in the same way. The founder describes the idea, the person on the other side is polite, and everyone leaves encouraged. Nothing was learned, but it felt like research.
The fix is structural. Do not describe the idea until the end, and ask about what has already happened rather than what might. Here are twelve questions that reliably produce usable answers, in the order we ask them.
Establish the current behaviour
- Walk me through the last time you dealt with this. What actually happened? A specific instance, with dates. Not a general description of how things usually go.
- What did you use or do to handle it? The incumbent is rarely a competitor. Usually it is a spreadsheet, a person, or nothing.
- Who else was involved in that decision? Surfaces the buying committee, which is almost always larger than assumed.
- How long did it take, start to finish? Converts a vague annoyance into a number you can price against.
Find the cost and the trigger
- What did that cost you, in money or in hours? If they cannot answer, the problem is probably not painful enough to fund a solution.
- What made you deal with it then rather than earlier? The trigger event is the single most useful thing you can learn. It tells you when to appear.
- What did you try that did not work? Reveals the graveyard your product is about to walk into.
- How often does this happen? Frequency separates a business from a favour.
Test the money without asking a hypothetical
- What do you currently pay for anything in this area? An existing budget line is worth more than any stated willingness to pay.
- Who signs off on spending of that size? Establishes whether your interviewee can actually buy.
- If this stopped being available tomorrow, what would you do? Switching cost, revealed rather than claimed.
- Who else should I be speaking to about this? Compounding referrals, and a soft check on whether the conversation was worth their time.
Four rules that matter more than the questions
- Do not pitch until the end. The moment you describe your solution, the person shifts from informant to critic, and politeness takes over.
- Record, with permission. Notes capture what you expected to hear. Recordings capture what was said.
- Chase the specific. Any general statement should be followed with "when was the last time that happened?" If the answer is never, it is an opinion, not a behaviour.
- Talk to at least ten. Below that you are collecting anecdotes. Somewhere around a dozen the same three things start repeating, and those three are your answer.
What you do with it
Pull every verbatim answer to question five and question nine into one document. If the numbers there are small, vague or absent, you have your result, and you got it for the cost of a fortnight rather than a launch. If they are specific and large, you now have both a price anchor and the exact language your buyers use — which is, conveniently, the copy for your landing page.
Testing this properly
We run this as a fixed-price service, including a round of twelve recorded buyer interviews from the ₹35,000 plan. See the four validation plans.
Twelve questions that tell you whether anyone will actually pay