nocricketsOpen the tool →Use case
Find your first users
The people who want your product are usually already describing the problem somewhere. The work is finding the thread, not inventing an audience from scratch.
Your first users left a paper trail
Before your first user ever hears about you, they usually leave a trace: a complaint about the problem, a question asking if a tool like yours exists, a GitHub issue requesting the exact feature you built. That trace is a better starting list of who to talk to than a cold list of accounts to follow, because these people have already told you, unprompted, that they have the problem.
How to use NoCrickets for this
Describe the problem your product solves the same way you would to validate an idea. NoCrickets searches Reddit, X, Hacker News, GitHub issues, Stack Overflow, and 21 dev forums live, at query time, and returns the actual threads, dated and linked. Read through them for the people, not just the count: a specific person asking a specific question, recently, is a better lead than a large number with no names attached.
Showing up without being spammy
- Answer the actual question first. If you reply to an old thread, make the reply useful on its own, with or without mentioning your product.
- Read the venue's norms. What's welcome on Indie Hackers or a Show HN thread can read as spam on a Reddit thread that wasn't asking for product recommendations.
- Prioritize recency. A person who posted about the problem last week is more reachable, and more likely to still care, than someone who posted three years ago.