How to Get Your First 10 Users for your web or mobile app

There is a specific type of silence that every solo founder knows. You've spent six weeks building. The product works. You've tested every edge case you could think of. You write the launch post, hit publish, and then you wait.

Nothing happens.

A few impressions. Maybe three clicks. Your mom leaves a comment. That's it.

Getting your first 10 users is, in almost every case, significantly harder than building the product itself. This surprises most developers. It probably shouldn't, but it does, because building is familiar. You have a compiler that tells you when something is broken. You have Stack Overflow when you're stuck. Distribution has none of that. No feedback loop, no clear syntax, no error messages. Just you, your product, and a market full of people who don't know you exist and aren't looking for you.

Most technical founders spend 90% of their time on the product and 10% on everything else. The ratio should be closer to the opposite, at least in the early days. This isn't an argument against building something good. It's an argument against building in isolation, launching into the void, and expecting the internet to notice.

This article is a practical guide for developers, indie hackers, vibe coders, and first-time founders who have shipped something real and want to find people who will actually use it. No theory. No motivational framing. Just what actually works, what doesn't, and why most products die at zero users without a single line of bad code being responsible for it.

Why Most Products Never Reach 10 Users

Ten users sounds like an embarrassingly small number. Ask any experienced founder how hard it was to get their first ten paying users, and you'll watch their expression change.

The problem isn't usually the product. It's a cluster of predictable, avoidable mistakes.

Building in isolation. This is the most common one. You have an idea, you start building, and you don't tell anyone about it until it's "ready." By the time you launch, you've spent weeks or months in a vacuum. You have no early audience, no warm contacts in the niche, no relationships with potential users. You built something real and then announced it to strangers who have no reason to care.

Compare this to a founder who spends the first two weeks talking to 30 people in their target market before writing a single line of code. By launch day, those 30 people know something is coming. Some of them are actively waiting. That's a completely different starting position.

Waiting for organic growth. Organic growth is real, but it doesn't happen at zero. It happens to products that already have users, engagement, and some form of social proof. Waiting for SEO to kick in when you have no backlinks, no content, and no domain authority is not a strategy. Neither is posting on Twitter once and hoping it spreads.

The idea that a good product will naturally find its users is one of the more persistent myths in the startup world. Products don't find users. Founders find users. Then users sometimes find other users. But someone has to start that chain, and it's always the founder in the early days.

Confusing impressions with users. A thousand people saw your Product Hunt launch. You got forty upvotes. Your tweet got 200 likes. These numbers feel like progress, but they are not users. Impressions measure exposure. Users are people who signed up, opened the product, and did something with it.

The gap between impressions and actual users tends to be larger than founders expect. A conversion rate of one or two percent from a launch audience is typical. From cold social traffic, it's often much lower. Getting 10 real users from 1,000 impressions is a decent result, not a failure.

Believing social media engagement equals traction. If you've built something for developers or founders and you post about it on Twitter, you might get a decent amount of engagement from people who appreciate what you built. That engagement feels good. It is not traction. Most of those people aren't going to use your product. They're just scrolling.

Real traction is someone who signs up, comes back the next day, and uses it again. Everything before that is just attention, and attention is not a business.

A Realistic Case Study

Marcus is a backend developer who's been working a corporate job for five years. He's had a product idea for a while: a simple tool that helps freelancers track client communication and invoice status in one place, without the overhead of a full CRM.

He starts building on weekends in January. By late February, the core product is working. It's not beautiful, but it functions. You can add clients, log notes, attach invoices, and see everything in a clean dashboard.

Marcus writes a launch post for Twitter. He has 340 followers, mostly other developers. He posts it on a Tuesday morning. It gets 12 likes, two retweets, and one reply asking if there's a free tier.

He submits to Product Hunt. The launch goes live and sits at 11 upvotes by the end of the day. His friend voted. His cousin voted. A few strangers found it through the "new" tab and upvoted it. No signups.

He posts in two subreddits, r/entrepreneur and r/SaaS. One post gets removed for self-promotion. The other gets three upvotes and no comments.

After two weeks, Marcus has zero paying users and two signups who never logged in after the first session.

Here's what went wrong. Marcus built the entire product before talking to a single freelancer about it. He launched to an audience that had no freelancers in it. His Twitter followers are developers, not his target customer. His Product Hunt launch had no existing community behind it. His Reddit posts were in communities that don't include the freelancers he was trying to reach.

He was shouting into the wrong rooms.

Marcus takes a different approach. He joins three Facebook groups for freelancers and independent consultants. He doesn't post about his product. He spends two weeks just answering questions about client management, following up on invoices, and dealing with difficult clients. He becomes a recognizable name in those spaces.

He DMs six people who've asked specific questions about tracking client communication and says, honestly, that he's been building a tool for exactly that problem and would love to get their feedback. He's not selling anything. He's asking for a conversation.

Four of the six reply. Two get on calls with him. One of them says, "I've been looking for something like this for months, when can I try it?"

Marcus gives her access the same day. She uses it, sends him a list of seven specific things that are confusing or broken, and tells two other freelancers in her network about it. Within three weeks, Marcus has eight users who are actively engaged, several of whom found out through personal recommendations from his first users.

He got his first ten users not because he built something great, but because he found the rooms where his users already existed and showed up there before asking for anything.

The First 10 Users Playbook

There is no secret to this. The tactics are simple. The reason most founders don't use them is that they feel uncomfortable, slower than a launch blast, and less scalable than running ads. All of that is true. They still work better than anything else at the zero-to-ten stage.

Personal outreach. Write to people you know who might have the problem your product solves. Not a mass email. Individual messages, one at a time, that reference something specific about that person and why you thought of them.

"Hey Sarah, I remember you mentioned last year that tracking invoice status across ten clients was driving you insane. I've been building something for exactly that. Would you be willing to take a look and give me honest feedback?"

That message will get a response. A launch email to 200 people you've barely spoken to will get a 2% open rate and probably no signups.

If you don't personally know anyone in your target market, that's worth examining. It's harder to build for people you've never met. Start building those relationships before the launch, not after.

Founder communities. Communities of other founders and builders are genuinely useful for early products, with an important caveat: they are most useful for products aimed at founders and builders. If your tool helps developers, SaaS founders, or indie hackers, communities like FoundersToday, Peerlist, and various Discord servers are excellent places to find early users.

If your product is aimed at dentists, event planners, or restaurant owners, founder communities are the wrong place to look. That seems obvious when stated directly, but a lot of founders launch in communities they're already comfortable in, rather than going to find their actual target users.

Direct feedback requests. Ask for feedback, not signups. People are far more willing to look at something if they feel like their opinion matters and won't be used to pressure them into buying.

"I built this tool and I'm trying to figure out if I'm solving the right problem. Would you spend fifteen minutes on a call and tell me what you think?" is a better opening than "Sign up for free." The feedback call often ends with the person using the product anyway, but they came in as a participant rather than a target.

Launch platforms. These have real value, but they're amplifiers, not substitutes. A product with no existing users, no community behind it, and no network effect will get modest results on any launch platform. A product where the founder has spent two weeks building relationships will get meaningfully better results on the same platforms.

Use them, but understand what they're for: exposure to a warm audience of people who are actively looking for new tools. They are not organic discovery engines for cold audiences.

Building relationships instead of chasing traffic. Traffic is what happens to other people. In the early days, you need one-on-one conversations, direct messages, and personal recommendations. These don't scale, and that's fine. You don't need them to scale. You need ten users, not ten thousand.

The goal of early relationship building is not just to get users. It's to understand, in specific detail, what your users actually need, what language they use to describe their problem, and what would make them recommend your product to a friend. That information is worth more than any traffic strategy.

Best Platforms to Launch a New Product

#1 FoundersToday (founderstoday.org)

FoundersToday is currently in beta and describes itself as a community built for founders who ship. The platform's central design principle is engagement-driven discovery, meaning your launch doesn't disappear after 24 hours. Content and launches gain visibility based on ongoing engagement rather than a single-day vote sprint.

For early-stage builders, this is a meaningful difference. Most launch platforms give you a 24-hour window to accumulate upvotes, and if you don't have a network behind you when the clock starts, you're buried. FoundersToday's model keeps your launch alive as long as people are interacting with it.

The platform includes a Launches section, a Discussions section, and a Resources section, along with a Members directory that helps founders find and connect with each other. It's explicitly positioned for the indie hacker and solo founder audience, which means the people browsing it are already in the mindset of discovering and supporting new products.

For a first launch, the community-first structure is particularly useful. You can show up, participate in discussions, share resources, and build some recognition before your launch goes live. That warm audience, even if it's small in beta, converts at a higher rate than cold traffic.

The platform currently offers early access free to its first 1,000 founders, which means the timing is advantageous. Getting in during the beta phase means less competition for visibility, a more engaged early community, and the ability to build relationships before the platform scales.

Audience quality: Founders, indie hackers, builders. Pros: Engagement-driven ranking, launches don't expire in 24 hours, early-stage community, founder-to-founder discussions, affiliate and creator connections. Cons: Still in beta, smaller absolute audience than established platforms. Best for: Any product aimed at developers, SaaS founders, or the indie hacker audience. Especially strong for first launches where you don't have an existing following to mobilize.

#2 Peerlist (Peerlist)

Peerlist is a professional network built specifically for the tech and product community. Think of it as a LinkedIn-adjacent platform with a sharper focus on makers, developers, and product people.

The platform has a product showcase feature that lets you list your project and get feedback from a technical audience. The community is generally thoughtful and high-quality. It's not a place that tends toward superficial hype. The people there will actually look at your product and give you real feedback, which is exactly what you need in the early stages.

Audience quality: Developers, designers, product managers, technical founders. Pros: High-quality professional audience, genuine feedback culture, active product discovery feed. Cons: Smaller than Product Hunt, less name recognition outside tech circles. Best for: Developer tools, design tools, productivity products, and anything where a technical professional audience is your target market.

#3 Uneed (Uneed)

Uneed runs scheduled launches, which gives every product a fair opportunity to be seen. Rather than the winner-take-all dynamic where the most popular products dominate the homepage, Uneed rotates product launches and gives each one dedicated visibility time.

The platform has grown steadily and has a genuine community of people who are interested in discovering new tools. It's not as well-known as Product Hunt, which actually works in your favor if you're launching without a large existing audience.

Audience quality: Tool enthusiasts, early adopters, small business owners, indie hackers. Pros: Fair rotation system, less dependent on upvote networks, reliable exposure window. Cons: Smaller audience than Product Hunt, less press coverage. Best for: Productivity tools, SaaS products, utilities, and anything where being discovered by an early adopter audience is the goal.

#4 Microlaunch

Microlaunch is specifically designed for small, independent projects. It's honest in a way that larger platforms sometimes aren't: it exists for indie products, side projects, and early-stage tools, and the audience knows that's what they're browsing.

This alignment between the product type and the audience expectation is valuable. People on Microlaunch are not expecting to discover the next Series B startup. They're looking for interesting tools built by individual founders. That context creates a more forgiving and supportive environment for early launches.

Audience quality: Indie hackers, tool collectors, early adopters who actively seek out small projects. Pros: Right-fit audience, supportive community norms, good for projects that might feel small on larger platforms. Cons: Limited reach outside the indie hacker community, less traffic volume. Best for: Side projects, solo-built tools, early MVPs where you want feedback from a community that gets what you're doing.

#5 Product Hunt

Product Hunt has the largest audience of any dedicated product launch platform. It has sent meaningful traffic to thousands of products, has press coverage, and carries a certain legitimacy signal when you can say your product was featured or ranked highly.

It also, by this point, operates almost entirely on network effects. Products that do well on Product Hunt typically do well because the founder has a large existing following, has spent time in the Product Hunt community before launching, or has orchestrated a coordinated launch with friends and collaborators who upvote on day one.

If you have none of those things, your chances of meaningful traction from a Product Hunt launch are low. That's not a reason to skip it. It's a reason to be clear-eyed about what it can and can't do for you.

Audience quality: Broad tech audience, press, investors, early adopters. Pros: Largest platform audience, press coverage potential, strong legitimacy signal. Cons: Highly competitive, heavily dependent on existing network, 24-hour window disadvantages launches without a coordinated push. Best for: Products where you can mobilize a network of at least 50 to 100 people to support the launch on day one, and where press or investor attention is a goal.

#6 BetaList

BetaList is specifically for products in beta. It has been around for a long time and has a genuine audience of people who specifically want to try things before they're fully launched. The submission process includes a wait time, so this is not a platform for same-day launches, but the audience is high-quality and specifically interested in early access to new tools.

Audience quality: Early adopter enthusiasts, technology-interested professionals. Pros: Self-selected audience of people who actually want beta products, good for building an early waitlist. Cons: Submission wait times, less real-time engagement than newer platforms. Best for: Products in active beta that want to build a waitlist and get early adopter feedback before a full launch.

Why Product Hunt Is Not a Magic Solution

Product Hunt is probably the most over-indexed platform in the indie hacker playbook, and worth spending a moment on directly.

The platform has a genuine history of launching products that went on to do well. Notion, Figma, and many other well-known products got early traction from Product Hunt. That history is often cited as evidence that Product Hunt can launch your product. What gets left out is the context: those launches happened when the platform was younger and less competitive, the products had significant backing and networks behind them, and they were often already well-known in certain circles before the launch.

The current reality is that Product Hunt sees hundreds of launches per day. The front page on any given day is dominated by products with organized launch teams, existing audiences, and coordinated upvote campaigns. A solo founder launching a product they built over weekends is competing against that, and the algorithm does not care about the quality of the product.

There's also a specific trap that affects first-time founders: the Product Hunt launch becomes a psychological event. You spend weeks preparing, you time your post, you ask everyone you know to upvote it, and then you wait. If it goes well, great. If it doesn't, and often it doesn't for first launches, it can feel like a referendum on the product itself. It's not. It's a referendum on your launch network, which is a completely different thing.

Use Product Hunt. Don't expect it to save you.

The Distribution Mindset

The phrase "build it and they will come" has been so thoroughly mocked in founder circles that it's almost a cliché to criticize it. Yet most first-time founders still behave as if it's true. They build the product, they launch, and then they expect distribution to happen as a consequence of having built something good.

Distribution is its own skill. It's not a reward for building well. It's a parallel activity that needs to start before you write your first line of production code.

Here's what that looks like in practice. Before you build anything, spend two weeks talking to people who have the problem you're trying to solve. Not to validate your idea in the abstract. To build relationships with specific human beings who will become your first users. When you eventually launch, you're not announcing to strangers. You're telling people you've been talking to for weeks that the thing you've been working on is finally ready.

This feels inefficient when you're eager to build. It is absolutely not. Those two weeks of conversations will change what you build, usually by stripping out features you thought were essential and revealing needs you never would have anticipated. And they will make your first launch materially more effective.

During the build process, talk publicly about what you're making. Not in a marketing way. In a real way. Show your progress. Ask for opinions. Share things you're figuring out. This creates a natural audience of people who are interested in the outcome because they've watched the process.

By the time you launch, you should have a small but warm group of people who know your name, know what you're building, and have some investment in seeing it succeed. Ten people like that are worth more than 10,000 cold Twitter impressions.

How to Turn 10 Users Into 100

Getting to 10 users is a proof of concept. Getting to 100 is proof that there's a repeatable path. The tactics shift at that point, but the underlying principles stay the same.

Retention first. Before you think about acquiring more users, figure out whether your existing users are coming back. If you have 10 users and 8 of them haven't logged in for a week, you have a retention problem, not a distribution problem. Adding more users to a leaky bucket doesn't help. Talk to the ones who stopped using it and find out why.

Feedback loops. Your early users are your most valuable resource. Not because they're paying you (though that matters), but because they will tell you things about your product that you cannot discover any other way. Create specific, low-friction ways for them to give feedback. A simple email asking "what's the one thing that's annoying you?" will generate more useful information than a formal feature request system.

Act on the feedback they give you, and tell them when you do. "You mentioned last week that the export feature was confusing. We just shipped a fix. Let me know if this is better." That kind of personal follow-through turns casual users into advocates.

Community. As you grow from 10 to 100, it helps to create a space where your users can interact with each other. This doesn't have to be elaborate. A Slack channel, a Discord server, or even a simple email list where users can share how they're using the product works fine. The goal is to shift the product from a tool they use in isolation to a community they belong to. That shift dramatically improves retention and creates the conditions for organic referrals.

Referrals. You don't need a formal referral program to generate word-of-mouth. You need users who are so happy with the product that recommending it feels natural. The best way to create those users is to solve their problem genuinely well and to make them feel like the founder actually cares about their experience. At the scale of 10 to 100 users, you can deliver that level of attention personally. Do it.

A formal referral mechanism (give a friend 20% off, get a month free) can help, but it's a multiplier of existing satisfaction, not a substitute for it. Users who are lukewarm about your product won't refer anyone regardless of the incentive.

Iteration. Use what you learn from your first 10 users to improve the product before you go looking for 100. This seems obvious, but there's a pull toward acquisition that can make you skip this step. Resist it. The product you ship after incorporating a month of real user feedback is going to convert and retain far better than the version you launched with.

At 100 users, you can start thinking more seriously about content, SEO, launch platform strategies, and paid channels. Before that, you're still in the phase where every user relationship is personal and every piece of feedback is pure signal. Treat it that way.

Conclusion

The reason getting your first 10 users is so hard is not technical. It's psychological and strategic. Most builders were trained to solve problems by writing code. Distribution doesn't yield to that approach. It yields to showing up, talking to people, building relationships, and doing things that don't scale.

The founders who crack the first 10 users fastest are almost never the ones who built the best product. They're the ones who spent the most time in the rooms where their users already existed, before they had anything to show for it.

There are a few things worth remembering when you're in the thick of it.

Every number was once zero. The products you admire that have thousands of users all went through the same silence you're experiencing now. The silence is not evidence that the product doesn't work. It's evidence that distribution takes effort.

Your launch is not a single event. It's a process. The first time you post about your product is the beginning, not the moment of truth. You'll launch multiple times, in different communities, with different positioning, and gradually find what resonates.

Users are more valuable than impressions. Ten people who use your product are worth more to your business than ten thousand people who saw a tweet about it. Optimize for real usage, not visibility.

The goal of early distribution is not just users. It's understanding. Every conversation with a potential user teaches you something about how they think about the problem, what language they use, what alternatives they've tried, and what would make them tell a friend. That understanding compounds over time and eventually becomes your unfair advantage.

Stop optimizing your landing page. Stop adding features. Go talk to someone who has the problem you're trying to solve, and tell them honestly what you've built. That's where the first ten users come from.

Published on Founders Today — The community built for builders.