How to find users for your project without paid ads
You shipped something. It works. Nobody's using it yet.
This is the part they don't talk about at hackathons. Building the thing is the fun part. Finding the people who actually need it — that's where most vibe-coded projects quietly die.
Paid ads feel like the obvious answer, but they don't work until you already know who your user is, what message converts them, and whether your landing page holds up. Running ads before you know any of that is just paying to learn things you could learn for free.
This guide is about the free version. Specifically, the channels that work when you have zero budget, zero audience, and a product that's ready but unknown. Some of these take more time than money. A few take neither — just showing up in the right place.
Why organic works better at the start anyway
Paid ads optimize for clicks. Organic channels optimize for fit.
When your first users come from a Reddit thread, a Hacker News comment, or a direct message — they come with context. They know what problem you solve because you explained it to them directly. That makes them better users. They're more likely to stick around, more likely to tell you what's broken, more likely to refer someone else.
The founders who skip organic and go straight to ads usually end up with a list of signups who don't really understand what they signed up for. Churn is high, feedback is sparse, and you're no closer to knowing if the product works.
Organic is slower. But the users you get are worth more.
Channel 1: Reddit — where people ask for exactly what you built
Reddit is the most underrated acquisition channel for early products. Not because it's hidden, but because most founders use it wrong.
The wrong way: post "Hey I built X, check it out" in r/SideProject and wait.
The right way: find threads where people are already asking about the problem you solve, and reply like a human.
The search that unlocks this: site:reddit.com [the problem your product solves]
Run that in Google. You'll find threads from the last two or three years of people complaining about exactly your problem. Some are still active. Some have dozens of comments and no real answer. Those are your posts.
What a good reply looks like: acknowledge the specific situation, share what you know, mention your product only if it's a direct fit. Not as a pitch — as part of the story.
The hard part is doing this consistently. Manually checking ten subreddits every day takes an hour and most founders can't sustain it. This is the specific problem VibeUsers was built for — instead of the daily scroll, you get an email with posts already filtered by your keywords. You open it, see what's worth replying to, go.
Around 20 genuine replies is enough to get a first result, if the pain you're solving is real and people actually talk about it. If you send 20 replies and nothing moves, that's information about the product, not the channel.
Channel 2: Hacker News — Show HN and the comment threads
Hacker News has two separate opportunities.
The first is Show HN — a dedicated thread format for sharing projects. The rules are simple: say what you built, what it does, and why you built it. No marketing speak. The HN audience is technical and allergic to hype, so plain language works better than anything polished. A Show HN that does well can bring hundreds of signups in a day. Most don't do well — but even a quiet one gets you indexed by Google and gives you a URL to share elsewhere.
The second is the comment threads. HN runs daily discussion threads on topics across tech, business, and culture. When a thread is relevant to your product — "Ask HN: how do you find early users for your side project?" — a thoughtful comment that mentions your tool in context is legitimate and often appreciated.
The pattern is the same as Reddit: help first, product second, only if it's genuinely relevant.
Channel 3: Your own network, used properly
Most founders underuse their network because they feel awkward asking for help. So they post once on LinkedIn, get 40 likes from colleagues, and call it done.
That's not using your network. That's performing for an audience that isn't your user.
What actually works: direct messages to specific people who fit the profile. Not "hey check out my thing" — "I built something for people who deal with X, and I think you might know someone who does. Would you be open to a 15-minute call?"
You're not asking them to be a user. You're asking if they know someone. That's a much easier yes. And often, they turn out to be the user themselves.
Ten targeted DMs will outperform a LinkedIn post to 500 connections every time.
Channel 4: Communities your users already hang out in
Every niche has a Slack group, a Discord server, a Facebook group, a forum. These communities have the same dynamic as Reddit: people ask questions, share problems, look for recommendations.
The rules are identical. Join first. Read for a week before you post anything. Understand what kind of content is welcome and what gets you kicked. Then contribute genuinely — answer questions, share what you know — before you ever mention your product.
Communities worth finding for vibe-coded projects:
- Indie Hackers forum and community
- The Lenny's Newsletter Slack (product and growth people)
- Relevant Discord servers for your specific niche
- Makerlog, WIP.co for accountability-style communities
Some communities explicitly welcome "what are you building" posts. Those are your opening.
Channel 5: Content that earns search traffic over time
This one doesn't work immediately. But it compounds.
A blog post that ranks for a keyword your users search for keeps bringing people in for months or years without any ongoing effort. The article you're reading right now is an example of that strategy.
What to write: not "what we built" — that's a press release nobody reads. Write about the problem. "How to find users for your vibe-coded project without paid ads" is a question real people type into Google. Answer it better than anyone else, and the traffic comes to you.
One solid article per week for three months builds a foundation that paid ads can't replicate. Slower start, but the results don't stop when you stop paying.
FAQ
How long does organic user acquisition take? Reddit and community channels can work within days if you find the right thread at the right moment. SEO takes 3-6 months before it compounds meaningfully. Your network is the fastest — direct outreach to ten specific people can get you your first call this week.
Is it worth doing all of these at once? No. Pick one channel, do it consistently for four weeks, measure what happens. Most early founders spread across five channels and do none of them well enough to see results. Reddit is the best starting point for most vibe-coded products because the feedback loop is fast.
What if nobody's talking about my problem online? That's a signal worth taking seriously. If you can't find Reddit threads, HN discussions, or community posts about the problem your product solves, the problem might not be painful enough for people to seek out solutions. It doesn't mean give up — it means do more talking to people before optimizing the acquisition channel.
How do I know if a channel is working? Track where signups come from. UTM links on every URL you share. A basic spreadsheet is fine. After 20-30 signups, a pattern will emerge. Double down on whatever's working, drop the rest.
Can I automate any of this? The finding part of Reddit monitoring — yes. Tools like VibeUsers surface relevant posts automatically so you're not searching manually. Everything else should stay manual until you have product-market fit. Automating outreach before you know what message works just scales the wrong thing.
Start with the channel that requires the least setup
You don't need a content strategy, a Substack, or a presence on every platform. You need one channel that puts you in front of people who have the problem you solve, and enough consistency to actually learn from it.
For most vibe-coded projects, that's Reddit. The conversations are already happening. You just need to show up in them.