Talking to users before you have anything to show them

Founders often wait for a prototype before talking to potential users. Some of the most useful conversations happen earlier, with nothing to show at all.

Most founders wait until they have a prototype, or at least a clickable mockup, before talking to potential users, reasoning that a conversation without something concrete to react to will not produce useful information. Some of the most valuable early conversations happen before any of that exists, with nothing to show at all.

What a conversation with nothing to show actually reveals

Without a product to react to, a conversation has nowhere to go except toward the problem itself — how someone currently handles the situation a founder hopes to improve, what they have already tried, what specifically frustrates them about the current options. This kind of conversation, uncontaminated by a specific proposed solution, tends to surface the actual shape of a problem more honestly than a conversation anchored around reacting to a mockup, where people tend to react to the mockup’s specific choices rather than the underlying need.

A prototype conversation risks a subtle trap: people are generally polite about mockups, offering surface feedback on colors and layout rather than the harder, more useful answer of whether they would actually use this at all. A conversation with nothing to react to has no surface to be polite about, which pushes it toward the more substantive question underneath.

What this looks like in practice

The most useful version of this conversation asks almost nothing about a proposed solution and almost everything about the current situation — what tools or workarounds are already in use, what specifically about them is disappointing, and how much that disappointment actually costs in time, money, or frustration. A founder who can answer these questions in detail, before writing a line of product copy, has usually done more useful early work than one who jumped straight to building something to show people.

Product-market fit doesn’t arrive as one clean number

Product-market fit doesn’t arrive as one clean number. It shows up as a handful of quieter signals — and only together do they actually mean something.

The feature that ships and changes nothing

A shipped feature with no measurable effect on retention or growth is a common, quiet failure mode that rarely gets discussed as openly as it should.

When a small, loud user base fools a whole team

A handful of vocal, enthusiastic early users can convince a team that fit exists broadly, when the enthusiasm may not extend past that small, unusual group.