How To Get First Users After You Built The Product First

If you built the product first and now have no users, the answer is not a bigger launch. Start manually: define one narrow user, find where that person already talks about the problem, help in public before linking, ask a small number of qualified people to try it, and interview the few who actually use it.

That pattern showed up across recent Ask HN and Reddit threads from technical founders, open-source builders, SaaS makers, and side-project developers. The repeated problem was not that they could not build. It was that they built before finding a reachable group of people with an urgent enough pain.

What Founders Are Really Asking

The posts all sound a little different, but the core question is the same: I shipped something, I have no audience, and I do not know where the first real users should come from.

• A builder made 10+ ideas in a month and saw no usage beyond friends and family.
• An open-source student wanted real users but had no reputation or distribution.
• A SaaS founder spent months building and then realized there was no launch audience.
• A solo app maker had a live product but no marketing skills or social following.
• A B2B founder had free demo users, but no paid customers for a specific compliance workflow.

This is why first-user work has to be narrower than normal marketing. You are not trying to reach a market yet. You are trying to find evidence that one small group has the problem strongly enough to respond.

Find The Starving Crowd First

One of the most useful Ask HN replies framed the problem as finding the starving crowd before building the hamburger. That is the correct order. A cool idea is not the same as a sellable problem. A useful tool is not the same as a tool that a reachable group urgently wants right now.

Before you post a launch thread, write down the smallest audience that could care. Not "creators", "developers", or "founders". Use a sharper description: "YouTube creators who check analytics weekly but do not know which video topics to repeat" or "seed-stage founders who just got enterprise security questions and need SOC 2 guidance before a deal stalls."

Choose One First-User Profile

Do not start with every possible buyer. Pick one first-user profile that you can personally reach. A broad target audience makes every channel look plausible and every message vague.

For a dev tool, that might be maintainers who are already asking how to automate a specific workflow. For a consumer app, it might be one niche community that already shares results or progress. For a B2B SaaS, it might be companies that just hit a trigger event: a new hire, a funding round, a compliance request, a migration, a failed audit, or a public complaint about an existing tool.

• Bad first-user profile: small businesses.
• Better: Shopify stores with 5-20 employees that manually answer the same product questions every day.
• Bad first-user profile: developers.
• Better: solo maintainers of TypeScript libraries who are behind on documentation after adding AI-generated code.
• Bad first-user profile: startups that need compliance.
• Better: seed-stage B2B startups losing enterprise pilots because they cannot answer SOC 2 questions yet.

Where To Look For First Users

The common advice in both Ask HN and Reddit was not "post everywhere." It was to find active conversations where the problem is already visible. Search communities, forums, Discords, Slack groups, GitHub issues, YouTube comments, niche newsletters, competitor reviews, and old comparison threads.

Your goal is to find demand language. Look for phrases people use before they know your product exists: "how do I", "what do you use for", "is there a tool that", "I hate that", "I am stuck with", "alternatives to", and "has anyone solved." Save the exact words. Those words become outreach, landing-page copy, FAQs, and article headings.

• Reddit search inside one relevant subreddit, sorted by recent and relevance.
• Hacker News search for Ask HN and Show HN threads around the workflow.
• GitHub issues and discussions for open-source workflows.
• Competitor support forums and changelogs.
• LinkedIn posts from people who own the job function.
• Niche Slack, Discord, or community forums where practitioners ask for help.

How To Use Reddit Without Spamming

Several Reddit threads in this cluster were not just asking where to find users. They were asking how to use Reddit without getting banned, ignored, or treated like a scammer. That is the right concern.

Reddit is not one channel. It is many communities with different rules. Reddit guidance says repeated or unsolicited mass engagement is spam, and it specifically recommends authentic participation in communities where you have a personal interest. That means your first move is not a link drop. It is useful participation.

• Read the subreddit rules before posting or replying.
• Answer the question in the thread before mentioning your product.
• Share the manual fix, framework, or diagnostic first.
• Mention the product only when it is directly relevant and allowed.
• Do not mass-DM people who did not ask for help.
• Use your profile to explain what you build, but let people choose to inspect it.

Manual Outreach Beats Scalable Marketing Early

For the first 10 users, scalable marketing is usually the wrong standard. You do not yet know which promise converts, which objection blocks action, or which user will retain. Manual outreach is not a failure mode. It is the research instrument.

The best early outreach is specific, permission-based, and useful even if the person never tries the product. Reference the problem they described, offer a useful observation, then ask whether they want to see what you built.

Saw your thread about [specific problem].

The manual workaround I would try is [short useful advice].

I built a small tool for [specific audience] that handles [specific part of the problem].
No pressure, but if you want to try it, I can send a beta link and would value blunt feedback.

That message works better than a cold pitch because it proves you understood the context. It also makes the ask smaller: not "become my customer", but "tell me if this solves the thing you already said hurts."

What To Do With The First Few Users

One Reddit founder had 9 onboarded users, 2 paying users, and only 3 active users. That is not a failed launch. That is enough signal to stop chasing more signups for a moment and learn from the active users.

• Ask what made them try it in the first place.
• Ask what almost stopped them.
• Watch where they hesitate in onboarding.
• Ask what they were using before.
• Ask what would make it worth paying for or recommending.
• Ask which part they would be annoyed to lose tomorrow.

The first users are not only traffic. They are the source material for your next positioning pass. Their words can improve the homepage, onboarding, pricing page, demo script, comparison page, and support docs.

When To Write A Launch Post

A public launch post is useful after you can describe the user and the pain clearly. Launching before that can still create comments, but the feedback will be noisy because readers have to guess who the product is for.

Use launch communities when you have something people can try and a specific feedback request. For Hacker News, that might be a Show HN if the product is personally built and usable. For Reddit, follow this Reddit SaaS launch playbook and use a feedback post in a subreddit that allows it. For Launch Receipts, the strongest submission is a product with a public thread attached because the thread preserves market context, objections, and early reactions.

If your product has a public launch or feedback thread, submit it to Launch Receipts so the product is listed with the discussion that shaped it.

First Users Checklist

1. Pick one narrow user profile you can reach manually.
2. Find 20 active conversations where that user talks about the pain.
3. Write down the exact phrases people use for the problem.
4. Reply helpfully in public without linking first.
5. Ask a small number of qualified people if they want to try the product.
6. Book short calls or async feedback with the people who activate.
7. Fix the main onboarding and positioning objections before chasing volume.
8. Turn repeated questions into homepage copy, docs, FAQs, or a comparison page.
9. Use a focused build loop, like the one in the AI coding agent workflow, so user feedback turns into small, reviewable product changes.

Bottom Line

The first users rarely come from one perfect launch post. They come from finding a small group with a real pain, joining the conversations they already have, helping before pitching, and learning intensely from the few people who actually try the product. Build the distribution loop as deliberately as you built the product.