Table of Contents

The most common misconception in indie development is "if you build something good, it'll get used." What actually happens is the opposite: the moment you press the publish button, a dead silence awaits. The analytics show rows of zeros; you paste it on social media and the "likes" are a handful from friends. This is where many people jump to the conclusion "my product was a dud" and flee into the next build. But often the problem isn't the quality of the product. It's simply that no one knows about it.

The real bottleneck in indie development isn't code—it's distribution (marketing). Thanks to AI, the cost of "building" has dropped dramatically. Anyone can ship an app over a weekend. And precisely because of that, the value of "being able to build" has fallen, and the value of "being able to reach people" has risen. This article is a down-to-earth manual for gathering your first 100 users/customers from zero. Not chasing a flashy viral hit, but growing your audience one person at a time out of dead silence—that's the realistic method we'll lay out. If you haven't decided what to build yet, it's worth glancing at the whole roadmap for indie development with AI first, then coming back.

The bottom line in 30 seconds

A prescription for "I built it but no one uses it"

Marketing starts before you build
Promoting after it's finished is too late. Share the building process and have "people who were waiting" ready on launch day.
Don't scale at first
Go get the first 10 by hand, directly, one at a time. Automation and ads are still too early.
Contribute, don't sell
Be useful where users already are. Hard selling gets you disliked; contributing builds trust.

* "100" is a waypoint. Once you have a template for carefully gathering one person, the rest is just repeating the same thing.

📚 If you want to work hands-on, step by step, from building to marketing to monetization, the free course is the way. With the intro course "Indie Development with AI", you can practice the flow of idea → MVP → launch → marketing end to end. Keep this article beside you as your "marketing textbook" and you won't lose your way.

1. Why no one uses it: start marketing before you build

The biggest cause of "I built it but no one uses it" is thinking of marketing as the final step. You spend weeks developing, and start promoting from the "day" it's finished. But there's no one in the world waiting for your product. Grabbing attention out of nowhere from a zero state is harder than winning the lottery. Reverse the order—market while you build is the winning path for indie development.

With "Build in Public," create an audience for launch day

Build in Public is the approach of proceeding while openly sharing the very process of building the product. "Built this feature today." "Got stuck here." "A user said this."—you share the work in progress, not the finished product. People are cold to finished promos, but they're drawn into someone building something. They want to root for you, and they follow because they're curious about the progress. On launch day, those people become your first audience.

① Share the process in small doses

Screenshots, what you got stuck on, decisions made. Two or three times a week is fine. "Keeping it up" beats perfect prose. X (formerly Twitter) and Indie Hackers are the standard places to post.

② Build a "waitlist"

Put up a simple landing page + email signup before it's finished. Just "we'll let you know when it's ready" becomes a list of prospects. On launch day, announce to that list all at once.

③ Find allies through the problem

Sharing "what's troubling you" gathers people with the same problem. That's your prospect list right there. Even before building, you can see the faces of "who you're building for."

💡 A common mistake: "I'll share it after it's finished." This leaves you with zero audience on launch day, and dead silence again. Conversely, just saying "I'm thinking of building this" while you have nothing yet gathers reactions and even fuels your motivation to build. Dead silence hurts far more than embarrassment.

First, confirm it's even "something people want"

Before any marketing technique, something no one wants won't get used no matter how much you promote it. Before building, ask your target users not "would you use this if it existed?" but "how are you solving this problem right now?" The former gets a polite Yes; the latter draws out the truth. The more an existing workaround exists (manual work, a spreadsheet, just putting up with it), the more real the demand. How to run this "pre-build validation" with a minimal product is covered in detail in the guide to building an MVP solo.

2. The first 10: go get them by hand, directly, one at a time

Once you launch, don't aim for 100 right away. First, 10. And these 10 come not from automated posts or ads, but from you moving your hands and bringing them in one at a time. There's a famous principle in the startup world—"Do Things That Don't Scale." It's an idea Y Combinator co-founder Paul Graham laid out in an essay of the same name: early on, it's right to throw out efficiency and acquire people one by one, by hand (source: Paul Graham, "Do Things That Don't Scale").

🤝 Reach out directly

Ask acquaintances who seem troubled by that problem, or people you've connected with on social media, individually: "I built this, I'd love you to try it." A one-to-one message works far better than a broadcast post.

👀 Watch them use it beside you

If possible, have them use it right in front of you (screen sharing works). You instantly see where they get stuck and what they misunderstand. Watch 10 people and improvements pile up.

🛎️ Support them to a fault

Support early users almost excessively. Respond to requests instantly, thank them, remember their names. This "delight" becomes the seed of word of mouth. Think about efficiency later.

Why do something this inefficient? There are two reasons. One is that early users' voices are the only material for steering the product in the right direction. If 10 people get stuck in the same place, fix that place. The other is that early users treated with care become fervent supporters and bring people in on their own. Rather than gathering 100 through ads, delighting 10 so each refers one person is, in the end, faster and stronger.

🎯 The goal of the 10-person phase is "conviction," not "numbers." Out of 10, how many say "I'd be lost without this"? Expand to 100 or 1,000 while this is thin, and people leak out like water from a hole in a bucket. Finding the template that genuinely satisfies one person first is the job of this stage.

3. The first 100: find them by where they are, and contribute instead of hard-selling

Once you've gotten traction with 10, next is 100. From here, "acquaintances" alone aren't enough—you need to reach strangers. The principle is simple: go to the places where users already gather. Instead of tweeting on your own feed and waiting, step into the communities, forums, and social spaces your target users look at every day.

Pinpoint "where they are" first

Where on the internet do your product's users spend their time? Are they designers, engineers, people with a particular hobby? The best place differs completely depending on that. First, write out three to five "hangouts."

💬 Topic-based communities

Relevant subreddits on Reddit, Discord servers, Slack communities. People gather densely by problem.

🛠️ Places where builders gather

Indie Hackers, Hacker News. Fellow indie developers are both peers and early users.

🚀 Launch platforms

Product Hunt is one of the rare places with "people who come to discover new products." Time your launch to it.

📱 The relevant social circle

The creators and hashtags for that theme on X or LinkedIn. Join the conversation in that circle.

Enter through "contribution," not "hard selling"

This is where 90% of people go wrong. They join a community and immediately paste a link saying "I built this, please use it." This gets you disliked instantly and, in the worst case, banned. A community isn't a place for advertising. The right move is the opposite: become a contributor first.

❌ The disliked way to enter
  • Post your product link on day one
  • Wedge your promo into unrelated topics
  • Blast a sales pitch via DM (treated as spam)
  • Ignore questions and only talk about yourself
✅ The trusted way to enter
  • First, answer others' questions carefully
  • Share useful knowledge in that field for free
  • Naturally mention "actually, I built this" for someone's problem
  • Put a link in your profile and answer when asked

The trick is to "become a useful person in that field without talking about your own product." Once you're recognized as useful, interest naturally turns to what you've built, too. It takes time, but this brings in the least-disliked and highest-retention users. Follow the order: build trust in one community before moving to the next. Contributing deeply in one beats dabbling thinly across five at once.

🧭 If you use Product Hunt, prepare. Rather than dropping it out of nowhere on the day, tidy up your profile in advance and tell your followers and the email list mentioned earlier, "I'm launching on X—I'd love your support." On launch platforms, early momentum (the reaction right after going live) shapes the trajectory. Here too, "priming before you build" pays off.

4. Get found: build a steady stream from search and AI search

Manual acquisition and community activity are powerful, but they have a weakness: they stop the moment you stop moving. So in parallel, set up a funnel where "people find you while you sleep"—traffic from search engines and AI search. It takes time to kick in, but once it starts turning, it becomes an "asset" that keeps bringing traffic even when you stop working. Plant the seeds early, in parallel with the 10- and 100-person phases.

Search (SEO): catch people who search by their problem

People are searching for the problem your product solves. "How to X," "X tool," "X not working"—prepare useful articles around these problem keywords and naturally introduce your product within them. Your product landing page alone won't get caught by search. "How-to, comparison, and problem-solving" content becomes the entrance.

AI search (AEO / LLMO): appear in ChatGPT and AI answers

As of 2026, users increasingly ask not just Google but ChatGPT, Perplexity, and Google's AI Overviews directly: "what do you recommend?" Whether you get named here is the new dividing line in marketing. This "optimization to be cited and recommended by AI" is called AEO (Answer Engine Optimization) / LLMO (Large Language Model Optimization).

🔎 SEO: build the entrance with problem articles

For the full picture of how, see SEO/AEO strategy for the AI era. The standard is to enter through articles that answer searchers' "troubles."

🤖 What AEO is

In What is AEO (Answer Engine Optimization)?, grasp the basics of writing that AI finds easy to cite as an "answer."

🧠 What LLMO is

In What is LLMO (Large Language Model Optimization)?, learn the thinking for getting recommended by AI, systematically.

📝 The point: The content that works for AEO/LLMO and the knowledge that's useful in communities are the same thing. "Writing that carefully answers troubles in that field" is valued by both humans and AI. The marketing channels aren't separate—one piece of quality content works multiple times over in search, AI, and community. It's well worth writing.

5. Use AI to prep your marketing: drafting posts, assets, and analysis

For an indie developer, the pain of marketing is doing "build" and "sell" all by yourself. Writing the copy, making the images, reading the numbers—all you. Using AI here as your "marketing-team prep hand" lightens the load at once. The trick isn't to dump it all and have AI produce a finished piece, but to have AI make 70% of the groundwork and finish the last 30% in your own words.

✍️ Drafting posts

Build-in-Public posts, launch announcements, intro copy for communities. Ask for "three versions of this feature, for this reader," pick the good one, and rework it into your own voice. It's many times faster than writing from scratch.

🎨 Making assets

Thumbnail images, OGP, a demo-GIF outline. "Looking the part" is enough. For marketing, quickly preparing one image that gets the point across beats an elaborate design.

📊 Analysis and improvement ideas

Paste in analytics or user feedback and ask for "three causes of drop-off and moves to make." It surfaces perspectives you'd miss alone. You judge; AI drafts.

⚠️ The pitfall of dumping it all on AI: The "mass-produced template copy" AI writes verbatim is seen through by both readers and communities. It moves no one, and can be treated as spam. Always add the "parts only you can write"—experiences, numbers, failure stories—yourself. AI handles the prep; you do the seasoning. Marketing stops working the moment you mass-produce by copy-paste.

If you want to use AI broadly as a partner for building side income, not just marketing, how to start an AI side hustle is a helpful reference too. The templates for posting, analysis, and asset-making are largely the same as for indie-development marketing.

6. A system to keep going: measure and iterate

Marketing isn't about "hitting it big once"—it's about keeping this loop turning: test small, extend what works, drop what doesn't. Indie development has limited time. That's exactly why you need to measure "which marketing actually brought people in" and concentrate on the winning path. Continuing "vaguely, social media" on gut feel easily becomes a waste of time.

📥 Look at sources

Use analytics to grasp "where they came from." Search, social, community, referral—which is working?

🚪 Look at drop-off

Where do arrivals leave? Before signup? On first use? Fix this and, with the same traffic, more people stay.

🔁 Test one move at a time

Don't change everything at once. Test one thing a week, watch the effect, and decide to keep or drop it.

📣 Prompt referrals

Add a line to satisfied users: "If you liked it, tell people around you." Word of mouth is the cheapest, strongest marketing.

Don't pour water into a "leaky bucket"

Before you push hard on marketing, check retention. Gather 100 people with great effort, and if they all leave right away, marketing is pouring water into a sieve. Building the state where arrivals "come back" first is often more cost-effective than increasing new acquisition. Have you captured the "I'd be lost without this" voices in the 10-person phase?—come back here and confirm. Step on the marketing accelerator only after retention is confirmed; that's the order.

💰 Beyond marketing lies monetization. Once 100 people are retained for free, next is the design of "getting them to pay." At what price and how to charge is a separate skill—in the guide to indie-dev monetization & pricing, get a handle on the free/paid line and pricing thinking. Only when marketing and monetization come as a set does it become "indie development you can keep going."

Summary

  • The real bottleneck in indie development is not building but marketing. "Build it and they'll come" is a fantasy.
  • Marketing starts before you build. Share the process with Build in Public and prepare a launch-day audience and a prospect list.
  • Get the first 10 through non-scalable manual acquisition. Reach out one at a time, treat them with care, and earn conviction.
  • Gather 100 by contributing where users are. Hard selling gets disliked; useful people get trusted.
  • In parallel, plant search and AI-search (SEO/AEO/LLMO) assets so people find you while you sleep.
  • AI is the prep hand. Delegate posts, assets, and analysis, and do the parts only you can write yourself.
  • Measure and iterate. Lock in retention first, then step on the marketing accelerator.

"I built it but no one uses it" isn't a problem of talent or product. It's just that you haven't started the separate skill of marketing yet. And that, like code, can be learned and gets better with practice. The first step you can take today is small—share one thing about what you're building. When a reaction comes back, that's your first person. The 100 lie beyond stacking that one person 100 times over. No rush, one at a time. Add the power to reach people to your power to build.

FAQ

Q. I've already launched and it's dead silent. Is it too late to start now?

A. It's not too late. Launch day is just one day of marketing. You can start Build in Public (sharing the improvement process) now and redo it from acquiring the first 10 by hand. If anything, "already having something that works" is a strength. Leave the product as is and simply start marketing anew.

Q. I have zero social followers. Isn't sharing pointless?

A. Everyone starts from zero. Before growing followers, contributing in communities where people already gather is the shortcut. As you answer others' questions and share knowledge, you get recognized, and your own followers grow from there too. Rather than tilling your own field, head first to where it's already lively.

Q. Wouldn't running ads gather people faster?

A. Not recommended early on. Running ads before you know "who resonates with what" tends to just burn money. First find the "resonating message" and "retention system" through the manual 10 and the community 100. Ads after you know the winning pattern are the first ones that actually pay off.

Q. I promoted in a community and got banned.

A. A common mistake. The cause is "selling before contributing." A community isn't a place for advertising. Spend a few weeks providing purely useful answers and knowledge to earn trust first, then mention your product when asked—follow this order and you won't be disliked. Putting a link in your profile field is usually fine.

Q. Marketing eats my time and development doesn't progress.

A. That worry points the right way—indie development runs on two wheels, "build" and "reach," and one alone won't move it forward. Let AI prep your posts, assets, and analysis to cut the marketing load, and put the freed time into development. Also, don't do every marketing channel indiscriminately—narrow to the one or two moves that measurement shows are working to raise your output per hour.