How to find early adopters before a product
The loudest practical advice is to talk to the people who feel the pain most intensely, and to run brutal feedback loops by cold‑DMing for critique before you build. People also shared ready‑made prompt sets for staging MVP conversations and mapping target users, which founders can reuse to make early outreach more systematic. The emphasis across posts was the same: validate with real prospects first, then iterate on product decisions. (x.com/i/status/2041863120138760443, x.com/NainsiDwiv50980/status/2041858086508650540 )
The advice founders keep repeating in 2026 is blunt: if nobody is angry enough about a problem to answer a cold message today, they probably will not become your first customer after six months of building. Y Combinator’s recent guidance frames first-user search as finding people with a “burning issue,” not persuading the average person to care. (ycombinator.com) That flips the usual order. Instead of building a polished minimum viable product and then hunting for demand, the playbook is to start with a tiny group whose pain is already expensive, frequent, and visible in public. (ycombinator.com) Paul Graham wrote this years earlier in one sentence that still runs through founder circles: early growth usually starts with recruiting users manually. His Stripe example describes Patrick and John Collison setting people up on the spot instead of sending a link and waiting. (paulgraham.com) That is why cold direct messages keep showing up in these conversations. A cold message is not really a sales pitch at this stage; it is a filter for urgency, because the people who reply fastest are often the ones already trying spreadsheets, workarounds, or interns to patch the problem. (ycombinator.com) The target is not “small-business owners” or “marketers” or any other broad label. The target is a much narrower person like “agency owner who sends 40 client updates a week” or “operations manager exporting the same dashboard every Friday,” because specific pain produces specific replies. (ycombinator.com) Y Combinator’s user-interview advice makes the next step concrete: ask about the last time the problem happened, what they did instead, and what it cost them in time or money. Those questions pull out real behavior, while vague questions like “would you use this?” mostly produce polite fiction. (ycombinator.com) That is where reusable prompt sets and interview scripts fit in. They are useful not because prompts are magic, but because they force founders to ask the same hard questions across 10 or 20 conversations and compare answers instead of cherry-picking compliments. (ycombinator.com) The newer Y Combinator framing adds one more twist: build a “minimum evolvable product,” not just a minimum viable product. The first version only has to survive contact with a few real users and change quickly when those users expose the wrong assumptions. (ycombinator.com) That is also why charging early matters. Y Combinator argues that first customers who pay real money, even a small amount, usually give sharper feedback than free users because they are testing whether the product solves a costly problem, not whether the demo looks interesting. (ycombinator.com) So the practical recipe is simple and unglamorous: find the people already feeling the pain, message them before you build too much, run the same interview loop repeatedly, and let their objections shape the product. The founders who do this look less like inventors unveiling a surprise and more like mechanics diagnosing a car with the owner standing beside them. (paulgraham.com, ycombinator.com)
