Most founders delay talking to customers because they feel underprepared. They want a prototype, a landing page, something to show. That instinct will cost you months of building in the wrong direction. The most valuable conversations happen before you have anything, because people will tell you what they actually need rather than what they think of what you made.
You Are Not Pitching, You Are Listening
The single most important mindset shift is this: early customer conversations are research, not sales. You are not trying to convince anyone of anything. You are trying to understand a problem well enough to know whether your instinct about it is right.
This matters because the moment you start pitching, people start being polite. Politeness is the enemy of useful data. When someone says "that sounds interesting," they are almost never telling you they would pay for it. They are telling you they do not want to hurt your feelings.
Go into every conversation with one goal: understand how this person currently lives with the problem you think you are solving.
Who to Talk to First
Do not aim for a representative sample at this stage. Aim for people who feel the problem most acutely. These are sometimes called "extreme users," and they give you signal faster than average users do.
If you think you are building a tool for operations managers at mid-size companies, find operations managers who have already tried to solve this problem themselves, with spreadsheets, with duct-taped software, or by hiring someone specifically to handle it. Those people have already proven the problem is real enough to spend time and money on. Talk to them first.
Fifteen to twenty conversations with the right people will teach you more than a hundred surveys sent to a broad list.
The Questions That Actually Work
Avoid hypothetical questions. "Would you use a tool that did X?" is almost always useless because people are optimistic about hypothetical futures. Instead, anchor every question in the past.
Ask about behavior, not intention:
- "Tell me about the last time you dealt with this problem."
- "What did you do when that happened?"
- "How long did that take you?"
- "What did that cost you, in time or money?"
- "What have you already tried to fix it?"
That last question is especially powerful. If someone has never tried to fix the problem, it may not be painful enough to pay for a solution. If they have tried three different approaches and none worked, you have found a real gap.
Also ask: "Who else deals with this?" Early customers are your best recruiting channel for more early customers.
How to Get the Meetings
Cold outreach works if you make it specific. A message that says "I am building a tool for ops teams and would love your feedback" will get ignored. A message that says "I saw you scaled your ops team from 3 to 20 people in 18 months at [Company]. I am trying to understand how teams like yours handle [specific workflow]. Would you spend 20 minutes with me?" will get replies.
The three things your outreach needs:
- A specific signal that you did your homework on them
- A clear, narrow topic (not "feedback on my idea")
- A low time commitment (20 minutes is the ceiling)
Do not offer to pay people for their time in early discovery. It changes the dynamic and attracts people who want the payment, not people who care about the problem. Instead, offer to share what you learn across conversations. People find that genuinely useful.
What to Do During the Conversation
Keep it to 25 minutes. Start by asking for their permission to take notes. Explain in one sentence that you are exploring a problem space and are not selling anything.
Then spend the first 20 minutes entirely on their world. Do not mention your idea. Ask about their current process, their frustrations, what they have tried. Only in the final five minutes, if it feels natural, can you briefly describe the problem you are working on and ask whether it resonates.
After the call, write up your notes immediately. Within an hour if possible. The details fade fast, and the details are everything. Look for the specific words people use to describe their pain. Those words will become your copy.
Reading the Signal Correctly
After ten to fifteen conversations, you will start to see patterns. Pay attention to three things: how often the same problem comes up unprompted, how much people have already spent (in time or money) trying to solve it, and whether people ask you to let them know when you have something to try.
That last signal, when someone volunteers to be a beta user or asks how they can follow what you are building, is one of the strongest early indicators you have found something worth pursuing.
Skepticism in a conversation is not a bad sign. Polite disinterest is. If someone pushes back and says "the real problem is actually this other thing," that is useful. If they nod along and say "sure, that makes sense," move on and find a sharper pain.
The One Thing to Do After Reading This
Block two hours this week and identify ten people who might feel the problem you are working on. Write a specific, short outreach message for each one. Send all ten today. You do not need a product to do this. You just need a hypothesis and the willingness to find out if you are right.