YC's Pocket Hits $27M ARR

Y Combinator's Paul Graham advises founders to manually recruit their first users instead of waiting for them to come to you. For Stripe, this meant the Collison brothers would literally install the software on their early users' laptops on the spot. This hands-on approach provides an "insanely great" experience that makes up for an early, buggy product and turns initial users into fanatics. Find your early adopters by focusing on a deliberately narrow market, like Facebook did by initially only serving Harvard students. YC Partner Michael Seibel suggests looking for users who have a burning, urgent problem and are willing to work with an early-stage startup. Charging these first customers, even a small amount, is a critical way to validate how intensely they feel the problem. Your first users are often found in existing online "watering holes" where they already discuss their problems. This includes niche subreddits, Discord servers, and professional forums. The key is to participate authentically and add value by answering questions and sharing insights before ever mentioning your product. A cold outreach email to a potential user should be short, personalized, and focus entirely on their problem, not your solution. YC Group Partner Aaron Epstein recommends finding an "uncommon commonality" through research to build a genuine connection. Your email should clearly state your situation, establish credibility, and end with a single, low-friction call to action. To build a pipeline, start with a simple spreadsheet to track every conversation. Document key details like their primary pain points, goals, what solutions they've tried, and any direct quotes. This creates a centralized log to identify recurring themes and inform your product roadmap. The goal of early conversations is to listen, not to pitch. YC Group Partner Gustaf Alströmer advises against even mentioning your idea until the end of the call, if at all. Ask open-ended questions like, "What is the hardest part about X?" and "Tell me about the last time you had to do Y?" to understand their workflow and motivations deeply. Structure your user feedback by categorizing it into themes like usability issues, bugs, and feature requests. Use a simple framework to prioritize what to build next based on the impact versus the effort required. This creates a continuous feedback loop that turns early user insights into a product people actually need.