IntentHunter

Your first 100 customers are already asking in public.

Pre-revenue, the job is to find the first real people who would use what you built. IntentHunter scans Reddit and Hacker News for threads where they describe the exact problem you solve, scores each one 0-100 by fit, says in one line why it matched, and drafts a reply.

Run a free scan See how it works

What's actually happening today

Cold outbound at zero customers burns the market

No logos, no case studies, no name they recognize. A cold sequence to your whole list teaches you little and spends down the people you most need to reach. Earning a reply in a thread where someone already asked the question is a warmer first touch.

Launch spikes leave, the question stays

Product Hunt and BetaList send a wave of curious visitors who are gone in a day. The people worth talking to are the ones describing your problem in their own words on Reddit, long after the launch traffic clears.

The bottleneck is finding the right thread, not pitching

Early founders learn from a few focused communities. The hard part is spotting the one "is there a tool that does X" thread that is actually you, buried under a hundred that are not. A scored inbox does that read for you.

What IntentHunter does for you

Scored for a narrow ideal customer

When every conversation counts, fit matters more. The 0-100 score floats the closest-fit threads to the top so a request that matches your exact wedge outranks a loose category mention.

A reply drafted, honest about your stage

The drafted reply gives you a starting point that answers the question without claiming scale or social proof you do not have yet. You post it yourself. IntentHunter never posts or DMs for you.

Save the language before you ship

Pre-launch, save the threads now. You end up with real customer phrasing for your copy and a list of source conversations to revisit the day you have something to show.

Test the channel on the trial first

Use the trial and plan limits to find out whether your category has enough public conversation to bother with, before you spend a dollar more on acquisition.

From setup to your first useful signal

  1. 01

    Describe what you're building

    Even if it is not live yet. The clearer the description, the sharper the 0-100 score.

  2. 02

    Scored threads land as scans run

    Reddit and Hacker News by default, sorted by how likely the poster is to care about what you are building, each with a one-line reason it matched.

  3. 03

    Reply if you're live, save if you're not

    Live: open the source thread and use the drafted reply. Pre-launch: save it. Either way you collect real threads from people describing the problem you solve.

Common questions

I don't have a product yet, can I still use this?
Yes. Save the relevant threads before you ship so you have the language and the source links, then decide whether to follow up once you have something useful to show.
How many of my first 100 can I realistically get this way?
It varies by niche, product, and how active your category is on the sources you turn on. Treat it as a validation and conversation channel, not an acquisition forecast. Your first week of scan history is the honest test.
Does IntentHunter tell me to pitch every thread?
No. It scores conversations and drafts a reply for the ones that fit, but it does not post for you or decide where you should show up. Skip the threads where you are not the answer.

Ready when you are.

Create a project, pick your sources, and see what your market is already asking for.

Run a free scan See other use cases →