TL;DR: to validate customer pain before you commit a team to building anything, write a pain hypothesis specific enough to fail, run discovery conversations that score real pain instead of collecting polite encouragement, and set a clear bar for when you have enough signal to start. Most teams skip straight to building and spend the next two quarters discovering, the hard way, that interest was never demand.
Most founders build before they have earned the right to
A head of product at a forty-person logistics software company runs eight demo calls with warehouse operations managers. Seven of them say a route-optimization module would be "really useful." The team builds it. Three months and two engineers later, exactly one of those managers signs, at a discount, after four rounds of negotiation.
Nothing in those eight calls was a lie. "Really useful" is a real reaction. It is just not a purchase, and a product team that cannot tell the difference keeps building things people like and will not pay for. The call here is not whether to talk to customers before building, almost everyone does that now. It is whether those conversations are actually testing anything, or just confirming what the team already wanted to hear.
The notes that matter are the ones that contradict the plan.
Write a pain hypothesis specific enough to kill
A testable hypothesis names the segment, the price, and the number of people who will say yes, not a vague sense that "operations teams struggle with this." Something closer to: forty of the five hundred warehouse managers you can reach by name will commit six hundred dollars a month to this by the end of the quarter. That sentence can be proven wrong in six weeks. "Operations teams struggle with this" cannot be proven wrong at all, which is exactly why it survives so many rounds of flattering conversation.
Once the hypothesis is written down, find the people who tried to solve this before and failed. Call the founders and operators who built something adjacent and shut it down, not a text thread, a real call. Most of them will tell you precisely what killed them. If your plan has no answer for the thing that killed the last three attempts, you are walking into the same failure with better branding.
Ask two questions on every call, and resist asking more
Leading questions produce leading answers. "Would a tool like this help you?" is a request for reassurance, and warehouse managers who like you will give it to you. Two questions do the real work: how important is this problem to you, and how satisfied are you with how you solve it today. You are hunting for high importance paired with low satisfaction. Enthusiasm paired with a decent current workaround is not a market. It is a compliment.
Follow the pain to a dollar figure in as few steps as possible. If a prospect needs five logical hops to connect your product to money made, money saved, or risk avoided, that chain length is itself the answer. Short paths to value close. Long ones get discussed in committee meetings forever.
Treat discovery as the start of your funnel, not a detour from it
Separating discovery from sales costs teams months, because it trains the product and revenue groups to hand off a stranger instead of walking one relationship forward. Every discovery call should end with a scheduled next step, no exceptions. A call that ends with "this was helpful, thanks" produced research. A call that ends with "let's look at a prototype next Tuesday" produced a pipeline.
- Run exploratory interviews with people in the segment, open ended, no pitch, listening for pain described in their own words.
- Narrow to focused interviews with the subset who scored high importance and low satisfaction, and ask what they would need to see to act.
- Show a paper prototype or a mockup, not working software, and watch where they get confused or excited.
- Put a rough MVP in front of the same people and ask what it would take for them to use it daily.
- Ask for a paid pilot, even a small one, because money is the only signal that cannot be given out of politeness.
- Ask every paying customer for one specific introduction, and treat a refusal to refer as a signal worth investigating.
Score segments on pain and reach before you commit to one
A segment that loves you but numbers eleven people worldwide is not a market, it is a hobby. A segment of thousands who are mildly annoyed is not one either. Score every candidate segment on how sharp the pain is and how many of them you can reach by name or existing relationship this quarter. The best segment is rarely the one that gave you the warmest call.
This is where most wasted months happen. A team chases the loudest voice in the room instead of the most representative one. A team builds for the one friendly logo that will say yes to anything, then learns that logo is not like the rest of the market. A team lets a string of pleasant calls stand in for a pilot commitment, because a pleasant call feels like progress and a hard ask does not.
Before you write the first product ticket, sit with these
- Can you write the pain hypothesis as one sentence with a segment, a price, and a number of buyers, not a feeling?
- Has anyone in this segment paid anything yet, even a deposit, or has everyone only said nice things?
- Did you find the company that tried this before and died, and do you know exactly what killed it?
- When you ask the two questions directly, does the pain score high and the current solution score low, or are you rounding up?
- How many logical hops sit between your product and the money it makes, saves, or protects for the customer?
- Could you name forty real people in this segment today, or are you still describing a category?
The pattern underneath
The leaders who get this right treat every conversation as a test that could fail, and they go looking for the failure on purpose. The ones who struggle treat discovery as a formality on the way to a decision they already made. It is the same habit that makes a peer room worth joining and an early pitch deck review worth doing: you go looking for the people who will tell you where the plan breaks. Did the eight warehouse managers want the module, or did the team just want them to?
That question, asked honestly before the first ticket gets written, is worth more than the two engineers it would have saved.
If this is the call your team is in the middle of, that is what VEN is for: small groups and 1:1 conversations with peers at your own level of experience, focused on the call you are carrying. Can we help? →