Ten First-Customer Interview Questions: How Solo Founders Find Buying Signals Instead of Compliments

Start here: a good interview is not an idea review

The goal is not to collect praise by asking whether the idea sounds good. Learn when the customer last faced the problem, how they handle it now, and what time or money the workaround consumes. A useful interview ends with one clearer experiment, not a longer feature list.

Choose people with recent behavior, not just interest

Prioritize people who tried to solve the problem in the last month: they used a manual workaround, paid for another tool, or asked a colleague. Their answers are concrete. Keep the first five interviewees similar by role, industry, or task frequency so signals are not blurred across segments.

Ten questions to ask before explaining the idea

1. When did you last do this task?
2. What happened from start to finish?
3. Which step takes longest or fails most often?
4. Which tools or documents do you use now?
5. Why did you choose that method?
6. What alternatives have you tried?
7. What time and cost does one run require?
8. Who is affected when it fails?
9. When does it become urgent?
10. What will you do first the next time it happens?

Questions about real events and money already spent are more reliable than hypothetical willingness to use a feature.

Separate strong signals from weak ones

Strong signals are behavior: money already spent, repeated time cost, impact on deadlines or revenue, and a commitment to the next test. Compliments and vague future interest are weak. Record the customer's exact words, frequency, current cost, and next action instead of your impression.

Use one page to turn interviews into product decisions

Summarize each interview in five fields: situation, problem, current workaround, time or cost, and next action. Build a small solution when the same problem repeats across at least three people, carries a real cost, and someone agrees to a next test. If every segment reports a different, non-urgent issue, narrow the audience and questions instead of adding features.

First-customer interview checklist and FAQ

• Have you chosen five people from one segment?
• Do questions focus on recent behavior?
• Is the idea explanation delayed?
• Are exact words and costs recorded?
• Does every interview end with a next action?

How many interviews are enough? Start with five people in one segment. If answers keep diverging, narrow the segment before adding respondents.

Can I ask about price? Ask what they already pay and what would trigger a switch rather than quoting a hypothetical price.

Should I build immediately? Create the smallest test when a repeated problem, a real cost, and a willing next-test participant appear together.

When turning evidence into operations, see the vibe-coding MVP post-launch checklist. You can also connect interview notes and follow-up messages through the OfficialMail external integration guide.