Direct answer (how to talk to your first customers)
To talk to your first 10 customers without sounding salesy, don’t pitch your idea. Ask about their workflow and recent problems, then listen for specific stories, workarounds, and spending. Your goal in the first 10 conversations is not “validation” — it’s learning what hurts, how they solve it today, and what would make them switch.
If you can’t walk away from each call with (1) a clear problem statement, (2) the words they used to describe it, and (3) one next experiment, you’re doing it wrong.
What “talking to customers” actually means
A first-customer conversation is a problem interview:
- You’re trying to understand a repeated pain.
- You’re mapping how they currently solve it (including tools, people, and workarounds).
- You’re testing whether this is costly enough (time, money, stress, risk) that they’d change behavior.
It is not a demo. It is not “Would you use this?” It is not “How much would you pay?” in minute 3.
The 10-customer rule (what you’re trying to learn)
In your first 10 customer interviews, you’re looking for “rhymes”:
- The same problem shows up repeatedly.
- The same moment triggers it.
- The same workaround shows up.
- The same consequence (lost time, lost money, lost sleep) shows up.
- The same budget owner or decision shape shows up.
When answers rhyme, you have something. When every conversation is a snowflake, your segment is too broad (or you’re interviewing the wrong people).
Framework 1: The “No-Pitch” customer interview script (20–30 minutes)
Use this as a default structure. Keep it conversational. Your only “pitch” is the reason for the call.
1) Opener (60 seconds)
- “Thanks for taking the time. I’m exploring a problem space and I’m trying to learn how people handle [X] today.”
- “I’m not going to pitch you anything — I just want to understand your workflow.”
- “Is it okay if I take notes (or record) so I don’t miss anything?”
2) Context: who are you and what does a normal week look like? (3–5 minutes)
- “What’s your role and what are you responsible for?”
- “Walk me through a normal week. What are the ‘must-not-fail’ tasks?”
- “What tools do you live in all day?”
3) Story time: the last time the problem happened (10–15 minutes)
This is the heart of the interview. Stay in the past, not the hypothetical.
- “Tell me about the last time you had to [do the thing]. What triggered it?”
- “What did you do first?”
- “What did you try next?”
- “Where did it get annoying or slow?”
- “What did you do instead (workaround)?”
- “What did it cost you (time, money, stress, risk)?”
- “Who else got involved?”
- “How did you know it was ‘done’?”
4) Existing solutions (5 minutes)
- “Have you tried anything else? What did you like/hate?”
- “What made you stop using it?”
- “If you could wave a magic wand, what would change?”
5) Priority + willingness to change (3–5 minutes)
You’re not asking for permission to build. You’re asking where this sits in their stack of pain.
- “Where does this rank compared to the other problems you’re dealing with?”
- “What happens if you do nothing for the next 3 months?”
- “What would make this urgent?”
6) Close: ask for the next step, not approval (60 seconds)
- “This was super helpful. If I come back with a simple prototype or a clearer approach, would you be open to a 15-minute follow-up?”
- “Is there one other person like you I should talk to next?”
Framework 2: The “3 levels of evidence” ladder (so you don’t fool yourself)
Most founders get stuck at “people were nice to me.” Use this ladder instead:
- Words (weak): “That’s interesting.” “Yeah, I’d use that.”
- Stories (medium): specific recent examples, clear pain, clear workaround
- Actions (strong): introductions, calendar follow-up, sharing docs/screens, offering to pilot, paying, committing time
Your job is to climb from words → stories → actions. If you only get words, you don’t have demand yet.
Framework 3: The question list (what to ask, what to avoid)
Questions that work
- “Tell me about the last time…”
- “What did you try before?”
- “What did you do instead?”
- “What did it cost you?”
- “Who else cares about this?”
- “What would you have done if [constraint] didn’t exist?”
- “What would make you switch from your current solution?”
Questions that waste your time
- “Would you use an app that…?”
- “Do you like this idea?”
- “How much would you pay?” (before you understand the problem)
- “What features do you want?” (feature requests are downstream of pain)
- “Would you buy this?” (they’ll say yes to be polite)
How to not sound salesy (without being awkward)
Salesy happens when you’re trying to win approval instead of learn.
Here’s what “not salesy” looks like in practice:
- You talk less than 30% of the time.
- You stay in specifics. “Tell me about the last time…” beats “How do you generally…”
- You don’t correct them. Even when they’re “wrong,” you’re learning their mental model.
- You don’t argue about your solution. You’re not there yet.
- You summarize back. “So it sounds like the painful part is [X], and the workaround is [Y]. Did I get that right?”
If you feel the urge to pitch, write down the pitch… and don’t say it. You can test it later.
What to do immediately after each call (the part founders skip)
Right after the call, capture:
- Problem statement (1 sentence): “[_] struggles with [_] because [_].”
- Exact phrases they used: 3–5 quotes in their words
- Current workaround: tools + manual steps
- Cost: time / money / risk / stress
- Next experiment: one action you will take in the next 48 hours
If you’re using iDO!, create one entry per interview and tag it with:
- Customer type
- Problem
- Evidence level (words / story / action)
- Next step
This turns “random conversations” into an actual validation track.
FAQ
How do I find my first 10 customers to talk to?
Start with people who already feel the pain and are easy to reach: friends-of-friends in the role, niche communities, local meetups, LinkedIn, and alumni networks. Your filter is simple: can you name 10 people you can contact this week?
How long should a first customer interview be?
20–30 minutes is enough. Longer interviews often drift into theory. Short, focused calls force specifics.
What if people say they’d use it but never follow up?
Treat that as a signal: polite interest is not evidence. Go back to past behavior (“What did you do the last time this happened?”) and look for action-based next steps (intro, follow-up call, pilot).
Should I show a prototype in the first call?
Not if you’re still unclear on the problem. Do 5–10 problem interviews first. If you do show something, do it at the end and keep it short — you’re testing reaction, not running a demo.
How many customer interviews do I need?
You don’t need “a number.” You need patterns. For most early founders, 10 is enough to tell whether the problem and customer segment rhyme. If they don’t, tighten your segment and do another 10.
If you want a simple system that keeps your interviews, quotes, assumptions, and next steps in one place, save your first idea free in iDO! — then turn each conversation into a concrete experiment instead of a vague “we should talk to more people.”