I’m at $200k ARR, and I’d still rather have 10 customers tell me what’s broken than 1,000 founders tell me it’s cool. [I will not promote]

Compliments are easy to misread. When another founder notices a detail you stayed up fixing, it feels great, even at $200k ARR as a solo YC founder. But revenue does not make you immune to wanting validation, so separate that feeling from evidence of utility. A founder praising your engineering is appreciation. A customer struggling to finish a task is actionable context. I can build more value from the second conversation. Not every complaint deserves a feature. People get annoyed by problems they will not pay to fix, and ten feature requests can pull a product in ten contradictory directions. So focus on context instead of taking requests at face value: • What were they trying to accomplish? • Where did they get stuck, and what workaround did they use? • Who else was involved? A request for a CSV export button might mean a report for a boss, a check on your data, or preparation to churn. Each needs a different solution. Do not ask whether they would use a proposed feature. People say yes to be polite. Ask them to walk you through the last time the problem happened. Pulling up a workaround takes effort and yields concrete truth. Prioritize issues that repeat independently across customers with similar needs. One vocal user is a conversation; a shared bottleneck is a roadmap priority. After shipping, follow up to confirm the underlying problem was solved, not just that a button was added. I still enjoy hearing that something I built is cool. I just do not let admirers have more influence than users.