Writing

How to Find Your First Users by Messaging People Who Complain About Your Problem

By Scott Wilder · November 6, 2026 · 6 min read · All writing

Find people who are already complaining about the problem your app solves, answer them in public first, then send one short message that quotes what they said. By the end you will have a list of 10 real posts, a script you can paste, and a daily cap that keeps you out of trouble.

Your first users are usually in a community you have not joined yet, talking about a problem you already solve. So you go to them, one person at a time, and you do it by hand.

Look for the post that asks for a fix, not the one that only vents

Not every complaint is a lead. A person who vents wants to be heard. A person who asks for a fix wants a solution, and you are allowed to bring one.

The posts worth your time look like these, per the first-users write-up on Substack:

Here is the rule. When the post asks for a tool or a fix, reply in the thread with a real answer. When the person only vented, answer in public or skip. Do not send a direct message to someone who never said they have the problem.

Search the words people use, not your product's name

Nobody types your product name or your category label. They type the problem, half-annoyed, in plain words.

  1. Write the problem as people say it, in 3 or 4 short phrases. Use the frames above: "is there a tool for...", "I tried X but...", "how do you handle...".
  2. Search those phrases on Reddit, X, Indie Hackers and Hacker News. Sort by newest. A thread from last week is still open. A thread from two years ago is not.
  3. Open each result and read the whole thread before you decide it is a match. Check what they tried and what they ruled out.
  4. Stop at 10 posts. More than that and you will start skimming, and skimming is how messages end up generic.

Keep a 10-post list so every message refers to something real

This is the part you copy. Make a table with one row per post. The last column forces you to quote the person, which is what keeps the message from sounding like a template.

Example: say you built a small tool that turns photographed receipts into a spreadsheet. Your first rows might look like this.

# Link What they said What they tried Reply sent Message sent
1 thread URL "I retype receipts every Sunday" A free scanner app, bad at totals Yes, a manual trick Not yet
2 thread URL "Is there any tool for receipts to CSV?" Nothing yet Yes, two options Waiting on reply
3 thread URL "Accounting software is overkill" Spreadsheets No, only vented Skip

Row 3 is the point of the table. The person complained but never asked for help, so the plan is to skip. You will skip more than you send, and that is fine.

The reason to be this strict: a DEV Community write-up on cold DMs reports that referring to something specific the person said got better response rates than generic outreach, and that messages reading like a template get deleted.

Reply in public first, then send one three-sentence message

The order matters. The same DEV Community write-up reports that giving a real solution or workaround in a reply first, then messaging, works best.

The public reply

Answer the question. Give the workaround, the setting, the trick. Leave your link out. If you built a tool for this, you can say so later, in the message, where you can explain why you are biased.

The message

Keep it to three sentences, say what you are, and make the ask easy to refuse. Paste this and fill the brackets with their exact words:

Hi [name], I saw your post about [exact thing they said]. I'm the person who built [tool], so I'm biased. Happy to share it if it helps, and no worries if not.

The disclosure line is not decoration. Reddit marketing guides list hiding your affiliation as something never to do, and they say the same about unsolicited DMs and multiple accounts.

The follow-up

One follow-up at most. If they say no, or say nothing, stop. A second nudge turns a helpful stranger into a spammer.

Match the rules of each place before you send anything

Each community has its own line between helping and promoting. Read the rules page first. Then use this table.

Place Do Skip Source
Reddit Reply in the thread first. Disclose that you built the tool. Use one account. Unsolicited sales DMs. Several accounts. Redship
Hacker News Post your own work as a "Show HN". Say what you built, link straight to it, be the maker. A plain link to your own product, which is reported to get flagged and removed. Show HN guide, HN posting guide
Indie Hackers Promote with context. Say plainly when a tool you mention is yours. Dropping your product with no explanation. Indie Hackers launch guide
Product Hunt Ask people for feedback on the problem. Asking for or offering anything for votes, which can get a product unfeatured. Product Hunt guidelines

On Hacker News, repeat posting has a price too. The HN posting guide reports that moderators email you directly when they see a pattern of self-promotion.

If you already post on Reddit, the 3-week Reddit plan on this site covers the warm-up. For the subreddit most builders start with, run the r/indiehackers pre-post checklist first.

Cap yourself at 5 to 10 messages a day

Reddit marketing guides report safe daily DM ranges that rise with account age: 5 to 10 a day under 30 days, 15 to 25 from 30 to 90 days, and higher after that. Those are reported guidance, not a Reddit rule, and a first-users hunt does not need them anyway.

You have a list of 10 posts. Send 5 to 10 messages a day, spread out, and you will be done in two days. If your account is brand new, take the low end.

The same guides say the 9:1 rule is community-cited: nine non-promotional contributions for every promotional one. Many communities use a 10 percent norm or stricter local rules. Count it yourself: promo posts divided by all posts, and keep it at or under 10 percent.

Four mistakes that get your message deleted or your account flagged

Do this in the next ten minutes

Write 3 phrases your future user would type when stuck. Search each one on Reddit and Hacker News, sorted by newest. Paste the first 5 matching posts into the table above, with the exact words they used in the third column.

If you want to compare notes on the table, or you have a manual task you would rather automate than chase by hand, I read every message. The week after you ship is its own job, and the first-week checklist covers what comes next.

Email Me

Questions

Is it okay to DM someone on Reddit about my product?

Only if they asked for a tool or said they have the problem. Reddit marketing guides report that unsolicited sales DMs to strangers are reported as spam and are one of the surest routes to a suspension. Reply in the thread first, disclose that you built the tool, and keep the message to three sentences.

How many people should I message?

Start with a list of 10 posts where the person asked for a fix, and send 5 to 10 messages a day. A new account should stay at the low end. Reported guidance says safe daily DM volume rises with account age, but a first-users hunt does not need high volume.

What is the 9:1 rule?

It is a community-cited norm: nine non-promotional contributions for every promotional one. Many communities use a 10 percent self-promotion norm or stricter local rules, so check each community's own rules page.

Do I have to say I built the product?

Yes. Reddit marketing guides list hiding your affiliation as something never to do, and Indie Hackers asks for transparency about tools you are tied to. A line like "I'm the person who built this, so I'm biased" covers it.

Can I just post my product on Hacker News?

Not as a plain link. A plain link to your own product is reported to get flagged and removed. Post it as a Show HN, with a title that says what you built, and link straight to the thing.

Can I ask for upvotes on Product Hunt?

No. Product Hunt does not allow asking for or incentivizing votes, and doing so can get a product unfeatured. Ask people for feedback on the problem instead.