28 October 2026 EN ES
The First Users

How products get their first real users

Finding Them

Find First 100 Users: Skip 93% Noise, Work 1.4% Buying

Read strong-intent posts first, not every thread, and start with a small subreddit watchlist plus funding announcements to reach your first hundred users.

Illustration: Find First 100 Users: Skip 93% Noise, Work 1.4% Buying

Your feed is full of posts that will never become users. In one 60-day window, 420,867 of 451,903 analyzed public posts carried no buying signal, a 93.1% share. Only 6,392 posts, 1.41%, were tagged HOT. The real question is where buyers actually post. The answer is narrower than it looks: a small set of communities where people are already asking for help, complaining about tools, or announcing money.

Use a filter-first reading rule: strong-intent posts first, read second. The rest of the feed is context, not work.

A short watchlist beats a firehose

Build a 13-subreddit watchlist before you read anything else. Pick communities where your buyer already asks for recommendations, complains about current tools, or describes a budget problem. Finish with a saved list you can check in a short daily pass, instead of a feed you scroll all day.

Search for your product category plus words like recommendation, alternative, budget, and hiring. If a subreddit has recent posts with those words, keep it. If it is full of self-promotion, drop it. The test is a list that feels like a buyer conversation, rather than a marketing channel.

Use Reddit as the first channel. Reddit supplied 4,919 of the 6,392 HOT posts, a 77.0% share. The buying conversation is already happening in a place with context. Reddit reported that ads in contextually relevant communities produced up to 16 times higher purchase intent than keyword-based targeting alone. The same logic applies to reading. The output is a daily check that ends in a short list of posts worth answering.

Avoid spending equal time on every channel. LinkedIn's hot-buyer rate was 2.55%, while Hacker News, a tech-news forum, and GitHub, a code-hosting site, each sat at 0.36%. If your buyer is a developer, those channels may still matter, but the buying-intent yield is lower. You know it works when the channel mix matches where your buyer asks for help, not where you want to be seen.

Funding announcements are the highest-yield first signal

Sort the feed by intent before you read by popularity. Funding-intent posts had a 45.1% HOT rate, 123 of 273, the highest among tracked intent categories. A company announcing new capital is usually ready to buy software, services, or help. The result is a short queue of recent announcements, each with a clear next question you can ask.

Create a simple spreadsheet with columns for post, intent, date, and reply status. Put funding announcements at the top. Rank budget and deadline posts next. Leave general complaints last. Make the queue ordered, not random.

Strong-intent posts usually contain one of these markers:

  • A budget or a deadline.
  • A vendor comparison or a request for recommendations.
  • A hiring post that implies a new workflow.
  • A growth plan that needs new tools.

The mistake is treating the watchlist as a lead list. A post is not a buyer until the person replies. If you message a handful of people and get no answer, the problem is usually the filter, not the effort.

Manual outreach is the whole job

Message the poster, not the crowd. Skip the growth tactics that need scale; at this stage, the work is personal. Founder-led outreach works when the reply is specific to the post: what you noticed, what you do, and one low-friction next step. Make the message sound like a person, not a template.

Keep the first message short. Name the post, say why you are relevant, and offer one next step. Do not ask for a call before you have given a reason to reply. Aim for a reply that asks a question, not a polite no.

Keep a simple log: who posted, what they asked, when you replied, and what they said back. If a funding announcement is in the queue, lead with the timing: you saw the announcement, you can help with the next build-out, and you want a short call. If the answer is silence, move to the next post. Use the log to see which posts deserve a second reply.

Follow up once, a few days later, only if the post is still relevant. Send what they asked for: pricing, a demo link, or a case study. If they did not ask for anything, do not send a brochure. Make the follow-up useful, not a new pitch.

The first hundred stay through hand-holding

Onboard the first users by hand. Walk them through setup, ask what almost stopped them, and fix the first blocker yourself. Leave a user who can use the product without a tutorial, and a log note about what to change next.

Do not wait for a support system. The first hundred are small enough that every complaint is a product lesson. If several users hit the same wall, change the product before you change the copy.

Advertisement