Start with a specific person
An early company rarely has enough data to make its market look obvious. That does not mean every claim has to remain abstract. A founder can describe one person, the job that person is trying to complete, and the moment when the existing approach becomes painful. That level of detail gives a conversation something concrete to test.
A broad category such as ‘productivity for knowledge workers’ leaves too many possibilities open. A description of an analyst checking a report against five source documents tells us where to begin. We want to understand what happens today, what the workaround costs and why the person has not already switched.
Look for learning that changed a decision
Customer conversations matter most when they change what the team does. Ten interviews that confirm a pitch may be less useful than one conversation that exposes a mistaken assumption. Ask what the founder removed from the roadmap, narrowed in the target customer or stopped promising after hearing from users.
The point is not to reward uncertainty for its own sake. It is to see whether a team can turn incomplete information into a better next step. A short record of a hypothesis, an experiment, an observation and a resulting decision can reveal more than a long feature list.
Separate interest from commitment
A compliment is easy to give. A prospective user sharing an existing workflow, arranging a second conversation or trying a rough product with real work is making a more meaningful commitment. None of these signals proves a business, but they help distinguish curiosity from a problem someone wants solved.
Early evidence should be interpreted in context. A paid pilot with one unusually friendly customer can still mislead. We would ask who made the decision, what changed after the trial, and whether a similar customer could reach the same conclusion without a personal relationship.
Make the next risk legible
A useful first conversation does not require a perfect fundraising narrative. It requires a clear view of what the team believes, what it has learned and what could prove it wrong. If the biggest uncertainty is distribution, another polished product demo will not settle it. If it is technical feasibility, a large waitlist will not make the hard part disappear.
The strongest next milestone is an observation that changes a decision. Describe the smallest test that could produce it, what it would cost and what you would do after either result. That is a practical place for a first believer to enter the conversation.
Show the trail from an assumption to a decision. Early conviction has something to stand on when the learning is visible.