Most advice on getting your first users comes down to a long list of websites where you can submit a new product. Most of those sites are directories: you fill in a form once, and then nothing happens.
Directories are fine, and a few are worth your time. But your first hundred users rarely come from a form. They come from places where a handful of the right people are already talking about your problem, and from you turning up there more than once.
This list is built that way. It has 20 places, a mix of communities, launch sites, directories and newer channels like AI assistants. For each one: what to post, what to avoid, and what it costs in time or money. Rules and prices change often, so we link the source where it matters. Check it before you act.
Before you post anywhere
Three things save you weeks. First, write one sentence that says who the product is for and what it does. Every post below is a version of that sentence. Second, make the first use work without a call, a demo request or a card. Third, put a different ?ref= tag on every link you share. A week later you want to know which place sent the people who stayed, not just the ones who clicked.
1. Hacker News
Show HN is for something you made that other people can try. The title starts with “Show HN”, and the Show HN rules (opens in a new tab) say a landing page or a sign-up form doesn’t count, because people can’t try it. It suits developer tools, open-source projects and anything technical. It is a poor fit for a consumer app with a waitlist.
How to use it: link straight to something that works. Post a first comment yourself saying what it is, why you built it and what is still rough. Then stay in the thread for the rest of the day and answer plainly. Don’t ask for upvotes or get friends to leave praise. Readers notice, and the guidelines discourage it.
2. Reddit
Every subreddit writes its own rules, and the sidebar beats any general advice. A common rule of thumb is that no more than about one post in ten should be your own work, and moderators read your history as well as your post. A new account with a product link as its first post is the quickest way to be removed.
How to use it: pick two or three subreddits where your users ask for help, and spend two weeks answering questions. When you do post, say the product is yours, say what it does, and end with a specific question. r/SideProject is made for showing projects. r/SaaS has been reported to limit promotion to certain threads, so read its rules first.
3. Product Hunt
Guides based on Product Hunt’s own advice say to schedule a launch up to a month ahead for 12:01 a.m. Pacific, and that you don’t need a well-known “hunter” to post for you. Treat the day as awareness, not acquisition. Founders on Indie Hackers describe a sharp one-day spike with few sign-ups that last. What stays is the page that ranks for your name, the badge, and a list of early supporters you can email.
How to use it: launch after ten people have used the product and you’ve fixed what they hit. Prepare a clear tagline, a few screenshots or a short video, and a first comment. Message the people you’ve actually spoken to, one at a time, and be in the comments all day. The Product Hunt (opens in a new tab) help pages have the current rules.
4. Indie Hackers
This is a community of people building and selling small products, so the replies are blunt and often useful. Some of them become users. The posts that do well teach something: a pricing change and what happened, a channel that failed, a revenue number.
How to use it: add your product to your Indie Hackers (opens in a new tab) profile, then write posts that lead to it by being worth reading. New accounts can face posting limits, so comment on other people’s threads first.
5. X
A few short posts a week with a real screenshot or number will do more than one launch thread. The faster route is search. Look up the exact phrase your users type when they complain about the problem, and reply with something useful. Mention your product only when it fits.
How to use it: pin one post that explains the product in a sentence and links to it. Follow the people your users follow, and reply to them before you ask for anything. A list of links gets reposted. A specific story gets replies.
6. LinkedIn
If you sell to businesses, your buyers are here, and the first users often come from messages, not posts. Search for the job title you’re building for, connect, and send a short note: what you’re working on, and a request for ten minutes of feedback. Don’t pitch in the first message.
How to use it: post the problem story, with a screenshot, instead of a product announcement. After a call, ask who else has the same problem. That question is how many founders find their next ten users.
7. Peerlist
Peerlist is a professional network for developers and designers. Its Launchpad runs weekly: you launch on Monday, and staff picks are chosen the next day, according to its help center (opens in a new tab). You need a verified profile to launch.
How to use it: it fits tools for people who build things. Add the project to your profile first, and use the weeks before launch to follow, comment on and support other people’s launches. A cold launch from an empty profile gets little.
8. BetaList
BetaList is for early and pre-launch products, and its readers like trying new things. Older guides describe a free queue. The BetaList support page (opens in a new tab) says every submission is now paid, with the price shown at the end of the form, and that you’re refunded in full if it isn’t selected.
How to use it: it’s worth a try when you have a working beta and a way to collect email. Don’t submit if you can’t answer the messages that follow.
9. Uneed
Uneed is a launch board with a free queue. Reviews of it put the wait anywhere from about a month to several months, and paid options skip the line. Prices vary by source, so read them on Uneed’s own pages.
How to use it: submit early and forget it. The slot arrives while you’re working on other things on this list, so have the page, screenshots and pricing ready before your date. Don’t pay to skip the line until you know the product holds up.
10. DevHunt
DevHunt takes developer tools only: APIs, SDKs, command-line tools, frameworks, testing and DevOps tools, and MCP servers. Third-party guides say a free listing gives you a permanent page, and that entering a specific launch week can cost money. Check the DevHunt (opens in a new tab) site for the current terms.
How to use it: developers will try a tool if they can get it running in a minute. Put the install command or a live demo at the top of your listing, and answer technical questions in the comments the same day.
11. AlternativeTo
People who search for “alternative to” a product have already decided they’re unhappy. That is a warmer audience than most launch sites give you. Per its AlternativeTo FAQ (opens in a new tab), you create a free account and choose “Suggest new application”, then fill in platforms, licence, description and tags.
How to use it: after your listing is approved, go to each competitor’s page and suggest yours as an alternative. Write the description around what the incumbent does badly. Sources disagree on whether the outbound link helps search rankings, so judge the site by the visitors it sends.
12. G2
Software buyers compare products on review sites, and a free vendor profile on G2 is the way in. G2 has agreed to buy Capterra, Software Advice and GetApp from Gartner, so one profile may soon cover several sites. Look at what G2 offers when you claim yours.
How to use it: this is a later step, because an empty profile does nothing. Once you have real users, ask your happiest ten for an honest review a month after they started. Follow the site’s rules on rewards. Best for business software with a budget behind it.
13. The QuickToolz product directory
This is our own site, so weigh it accordingly. Every listing gets its own page with a plain description, features, FAQ and alternatives, and the order of products never depends on payment. Makers can claim a listing with a verified email and edit it.
How to use it: Submit your product, then fill in the alternatives and FAQ. Those fields are what people search for. It’s one place among twenty, so don’t expect it to carry a launch.
14. The official MCP Registry
If your product has an API, a Model Context Protocol server lets AI assistants use it. The official MCP Registry (opens in a new tab) lists servers. You write a server.json file and publish it with the mcp-publisher command-line tool. The registry holds only the listing, so your package must already be on npm, PyPI or a similar index. Guides this year still called it a preview.
How to use it: write the description as the job a person would ask an assistant to do, not as a feature list. Other MCP directories are expected to pull from the registry, so one good listing travels. It suits developer and data products best.
15. The ChatGPT app directory
OpenAI opened app submissions (opens in a new tab) on 17 December 2025. Apps are built with its Apps SDK, which sits on MCP, and go through a review before they appear in a directory inside ChatGPT. It fits jobs that work in conversation: lookups, calculations, bookings and short workflows.
Watch for: the review. A submission includes connection details, test instructions and directory information, and only one version can be under review at a time. We couldn’t find an update on the rules this year, so read OpenAI’s current guidelines before you build anything. Don’t start here unless your product already has a clean API.
16. Discord and Slack communities
Most niches have a chat group, and it’s often where the best early users are. Founders in Indie Hackers threads describe Discord groups as one of the places their first users came from. Find yours by searching for the niche plus “Discord” or “Slack community”, or by asking in the subreddits you already read.
How to use it: join as a member, not a marketer. Introduce yourself in the right channel, answer questions for a couple of weeks, and share your product when someone describes the problem it solves. Say it’s yours. Check the rules on self-promotion first.
17. DEV and Hashnode
Write the tutorial your user is searching for, with your product as the tool in it. “How to do X with Y” brings readers for months, where a launch post is read once. Both DEV (opens in a new tab) and Hashnode (opens in a new tab) let you set a canonical URL, so you can publish on your own site first and keep the search credit.
How to use it: make the article useful if the reader never signs up. Include working code or exact steps, and end with one link to try it. Articles that read like ads get ignored on both.
18. GitHub
A good README is a landing page: one sentence on what it does, a screenshot or short recording, the install command and a link. Add topics so people can find the repo, and send pull requests to “awesome” lists in your area, following each list’s contribution rules.
How to use it: if your product isn’t open source, publish a small open piece that carries the audience, such as a command-line tool, an SDK or a set of templates. Answer issues quickly. It shows people someone is home.
19. Niche newsletters
A small newsletter read by exactly your kind of user can beat a big audience that doesn’t care. Many writers take a “tool of the week” suggestion, and smaller ones sell sponsorships for little money.
How to use it: email the writer directly. Say who you are in one line, explain why their readers would care, and offer free access. If you buy a sponsorship, ask for the average click rate first, and send readers to one page with one action.
20. App marketplaces
The Chrome Web Store, the Shopify App Store, Slack’s directory and Zapier’s app list put you in front of people who are already searching for something that does X inside the tool they use. Pick the platform where your users already spend their day, and build for that one.
Watch for: review times and policy rules. Start the listing before you think you’re ready, because a rejection can take a week to fix. Write the listing around the search phrase, since store search is how most people find you.
What order to do it in
Start with conversations. In the first two weeks, work the places where you talk to people: Reddit, Discord and Slack groups, LinkedIn messages and X replies. Your first ten users almost always come from here. In the same weeks, submit to the queues that take time, such as Uneed, BetaList and AlternativeTo.
Launch once ten people have used it and you’ve fixed what they found. That’s Product Hunt, Hacker News and Peerlist. After that, build the slow channels that keep sending people: tutorials, GitHub, review sites, the MCP Registry and the marketplaces.
Count three things for each place: visits, people who finished setup, and people who came back a week later. If a place sent 40 visits and nobody finished setup, the problem is your first-use experience, not the place. Fix that before you add another channel.
Sources
Rules and prices come from each site’s own pages where we could reach them: Hacker News (opens in a new tab), BetaList (opens in a new tab), Peerlist (opens in a new tab), AlternativeTo (opens in a new tab), the MCP Registry (opens in a new tab) and OpenAI (opens in a new tab). Details for Product Hunt, Reddit, Uneed, DevHunt and G2 come from third-party guides and founder threads, so confirm them on the site before you spend money.



