Zero signups can feel like a verdict on the product. It is better treated as an urgent clue with several possible explanations. Maybe the wrong people arrived. Maybe they did not understand the offer. Maybe the problem is real but not urgent, or the registration path failed. Five conversations will not establish market demand, but they can help a team choose what to investigate next.
Two founders described weak signup outcomes in community discussions: one reported 200-plus visits and one signup, while another described multiple channels and no signups alongside concern that the product was hard to understand (Reddit, Indie Hackers). These stories are anecdotes. They do not tell another team why its launch failed, but they suggest the right first move: talk to people who might use it.
Before recruiting, verify the basics
Test the signup flow yourself on common devices. Check form submission, confirmation, email delivery, spam filtering, and analytics. Reconcile the dashboard with the actual database. If all of those work, segment the visitors by source and confirm that they resemble the intended audience. Five interviews with the wrong audience can reinforce the wrong conclusion.
Recruit people who have the problem, including some who did not sign up. Avoid interviewing only friends, investors, and other founders. Explain that the goal is to understand their current process, not to persuade them to join.
Prepare a short guide and one note-taker if possible. Ask the same core questions in each conversation, while allowing useful follow-ups. Do not introduce the product too early, and avoid rewarding praise with extra attention. Participants should know whether their comments will be quoted, recorded, or associated with their name. A consistent, respectful process makes the small sample easier to compare and more comfortable for participants.
Conversation one: reconstruct the last time the problem occurred
Ask: “Tell me about the last time you had to do this.” Follow the story from trigger to completion. What made the task difficult? How often does it happen? What did they try? What did failure cost in time, money, or risk? Ask for examples rather than general opinions.
This conversation helps determine whether the team is solving a concrete recurring problem or a hypothetical one. A person who says “that sounds useful” may not have faced the problem recently. Someone describing a cumbersome workaround may reveal a real need even if they do not immediately praise the product.
Conversation two: test the explanation without teaching it
Show the landing page briefly, then ask the person to describe what the product does and who it is for. Do not explain the concept first. Record the words they use and where they hesitate. If they misunderstand the category or expected outcome, ask which phrase led them there.
This is a comprehension check. One session can surface a confusing term, but five people do not provide a statistically representative result. Look for repeated patterns and test a revised explanation with another small group.
Conversation three: compare the current workaround
Ask what tool, service, or manual process they use now. What do they like about it? What is frustrating? What would make them switch? What would make switching too risky? This helps distinguish a product that is merely novel from one that offers a meaningful improvement.
Do not lead the participant toward the new product as the obvious answer. If their current method is acceptable, that matters. The business may need a narrower audience with a more acute problem or a different promise.
Conversation four: observe a real task
If a prototype works, ask the participant to complete a realistic task without coaching. Observe where they stop, what they expect, and whether the product produces the intended result. Ask them to explain their choices afterward. Do not ask whether they would “use it someday”; watch whether the product supports the task today.
If the product is not ready, use a paper prototype or a truthful walkthrough and label it. Do not portray a mock-up as a functioning system. Treat feedback as design research, not a commitment to purchase.
Conversation five: clarify the next commitment
Ask what a reasonable next step would be: a second test, a pilot, a paid trial, or no further contact. If they are interested, explain the time, cost, data, and responsibilities involved. Observe what they actually agree to do. Behavioral commitments are more informative than compliments, but a single participant’s decision cannot quantify demand.
Synthesize carefully
After five conversations, write down observations separately from interpretations. “Three participants could not tell whether it works with their current software” is an observation. “The integration promise is unclear” is an interpretation to test. “There is no market” is far beyond what five interviews establish.
Keep dissenting evidence in the summary. If four people misunderstood the offer but one target buyer immediately recognized a high-value use, do not erase that segment. It may point to a narrower audience worth testing. The point is not to find a unanimous verdict; it is to learn which assumptions deserve another experiment and which audience is most likely to benefit.
Choose one next experiment: improve the explanation, recruit a more specific segment, fix the form, or test the core task. Then measure what happens. The point of early conversations is not to collect approval. It is to discover what the launch result does—and does not—mean.