You shipped the thing. Tests green, manifest valid, listing live. You refresh the install count.
Twelve. Eleven of them are you on different machines.
This is the part nobody warns you about: building the product is the deterministic step. Distribution is the part with no compiler telling you what's wrong. So you reach for the advice everyone gives — "post on social media," "build an audience," "be where your users are" — do all of it, and the counter still says twelve.
Here's the thing that took me too long to internalize: that advice isn't wrong, it's incomplete. It skips the one step that makes every channel actually work. This post is the version with that step put back in.
TL;DR
- The first 100 users come from direct, targeted effort — not passive posting.
- "Post on Reddit" is not a strategy. "Post this problem-solution to this subreddit on this day" is.
- Cold outreach feels awful and has near-zero downside when done right.
- Niche communities convert far better than broad ones at this stage.
- Early reviews are a compounding growth lever most devs completely ignore.
The 176-day wake-up call
A developer once shared, painfully honestly, that it took them 176 days to get their first 100 users on their app. Not 176 days of waiting — 176 days of grinding through every tactic, hitting walls, adjusting, grinding again.
The part that matters: they now hit 100 users in a fraction of that time, and sit at 28,000+ total. The tactics barely changed. Their understanding of how to apply them did.
That gap — between "I know the advice" and "I know how to execute the advice" — is where most indie launches quietly die. Everything below is about closing it.
Why generic advice fails
You read the same list in every growth article: post on Reddit, submit to Product Hunt, tweet about it. You do those things. Nothing happens.
The channels aren't the problem. The missing layer is targeting.
❌ "Post on Reddit"
✅ "Post a problem-first story in r/projectmanagement, aimed at PMs who
manually do the thing your extension automates, Tuesday 9am–noon."
Every tactic below has a targeting layer. Skip it and you're just generating noise with extra steps.
Tactic 1 — Go narrow before you go wide
Your instinct is to maximize exposure: post everywhere, tell everyone. Wrong order. Go narrow first.
A niche community has higher signal density. Drop a Chrome extension for project managers in r/projectmanagement instead of r/chrome_extensions and you're talking to people who feel that exact pain daily. Their see-post → install rate is dramatically higher.
One dev who built a reading-list extension skipped the tech subs entirely and started in r/books, r/reading, and a couple of book-club Discords. Fifty installs the first week. Unremarkable by VC standards — but 50 real users who used the core feature, which produced the first reviews, which unlocked Chrome Web Store visibility.
How to find your niche community:
- Write the problem your app solves in one sentence — no product name.
- Search that sentence on Reddit. The subreddits that surface are your targets.
- Lurk for a week. Read the top posts before you post anything.
- Note the format and tone that actually gets engagement.
- Lead with the problem, mention your solution near the end.
This phase gets you 20–40 users. Not the goal — the foundation everything else builds on.
Tactic 2 — Cold messaging, done right
This is the tactic everyone knows they should do and avoids because it's uncomfortable.
Grounding thought: the worst realistic outcome is silence. Nobody publicly mocks a genuine DM about a useful tool. Downside negligible, upside real.
The founders of Gas (a compliment-based social app that reportedly sold to Discord for ~$170M) got their first 150 users through targeted DMs — reaching out to people who already followed similar creators. The keyword is targeted. Cold messaging a random list is spam. Cold messaging people who've already shown they care about your problem space is relevance.
A cold message that works (under 100 words):
1. One sentence: why you're messaging THIS specific person.
2. One sentence: the problem you noticed they care about.
3. One sentence: what your app does about it.
4. A direct ask: "try it / give feedback" — not "please download."
No feature lists. No pitch deck. No "I hope this finds you well." The discomfort fades around message four. The results don't.
Tactic 3 — Build in public before you need the audience
Requires patience, which is exactly why most people skip it.
Posting your build journey on X/Twitter before launch creates a warm audience. Not a huge one — a relevant one. People who watched you build convert to installs far better than cold followers who happened to catch a launch post. An invested 400 beats a random 4,000.
The mechanics:
- Post weekly progress, even when it feels tiny.
- Share what you're learning, not just what you're building.
- Ask questions — the answered ones reveal what your audience cares about.
- Show your failures. "Here's what broke and why" almost always outperforms "here's what worked."
- Start 8–10 weeks before launch.
One dev posted screenshots of their tab-manager UI iterations every Sunday for two months. By launch day, 340 people were following along → 89 installs in the first 48 hours → enough ratings to break into organic search. No ads, no cold outreach. Just consistency.
Tactic 4 — Free tools as audience builders
Underused by indie devs, universally used by bootstrapped SaaS founders who've been at it a few years.
The mechanic: build a free tool that solves a smaller slice of your main product's problem. Optimize it for search. Let it do top-of-funnel work while you focus on the core product.
A dev building an extension for content creators shipped a standalone free headline analyzer. It ranked for "headline analyzer" within three months. A slice of that traffic converted to extension installs — and the backlinks lifted the extension's own search visibility.
What makes a good funnel tool:
- Solves a problem in one step (no signup).
- Has a natural "want to automate this?" bridge to your main product.
- Is something people search for specifically — "word count checker," "Chrome permissions explainer" — not "productivity tool."
- Buildable in a day or two, not weeks.
This pattern is exactly why ExtensionBooster ships free utilities like a Screenshot Maker, Tile Cropper, icon generator, and an MV3 converter — free, specific, immediately useful, and contextually connected to the broader product. If you're a dev, the free tools are worth a look just for the listing-asset grunt work alone (no signup needed).
Tactic 5 — Early reviews are a growth engine, not a vanity metric
Most devs treat reviews as a number that makes them feel good. They're actually a compounding loop:
more reviews → better store ranking → more organic installs
↑ │
└──────────── more review opportunities ◄──┘
The loop doesn't start spinning until you have enough initial reviews to break into ranked results. Both the Chrome Web Store and Google Play weight review volume and recency in ranking. An extension with 15 recent reviews consistently outranks one with 3 — even when the 3-review product is technically better.
Getting those first reviews needs a system, not hope:
- Ask at the moment of value delivery — not on first install, not on a timer.
- Keep it frictionless: "Did this work? A quick star rating helps others find it."
- Reply to every early review personally, even a text-less 5-star.
- When you fix a bug from a review, reply noting the fix.
There's also a legitimate cold-start fix for the chicken-and-egg problem. Tools like ExtensionBooster get you early reviews from real users who actually install and evaluate your extension — the legit version of "seeding" social proof. Real people, real usage, real ratings that count toward store rankings without violating platform policy. For an extension stuck at 3 reviews, even 10–15 authentic early ones can be the delta between invisible and rankable for your target keywords.
Tactic 6 — Directories and roundup posts
Tedious, quietly very effective.
Submit to AlternativeTo, Product Hunt, Show HN, AppSumo, and niche directories. Each creates an indexed page pointing to your listing — a potential entry point for searchers — and the backlinks lift your own store search visibility.
Roundup outreach is higher-effort, higher-return. Find posts already ranking page-one for "best extensions for [niche]." Email the author one paragraph: noticed the post, your extension fits, here's why their readers benefit, here's the link. No PDF. Response rate is low; conversion-when-they-respond is high. One inclusion in a "best productivity Chrome extensions" post can drive dozens of installs a month, indefinitely.
What realistic actually looks like
Not the viral-Product-Hunt fantasy. The 60-day grind that actually works:
| Window | What happens | Expect |
|---|---|---|
| Days 1–14 | Network installs — ex-colleagues, Discord friends, build-in-public followers. Comes with first reviews if you ask directly. Feels slow. Is slow. | 10–25 installs |
| Days 15–30 | Niche posts + targeted cold DMs. Watch for the first install from a stranger who found you via search — that's your listing working. | +20–40 installs |
| Days 31–60 | Free-tool traffic, directory submissions, and early reviews start compounding. The "found via search" vs "saw your post" ratio shifts toward search. You hit 100. | → 100 |
Hot take: the devs who spend those 60 days chasing the viral moment instead of executing the sequence are the ones still sitting at 12 installs in month three.
The one metric that actually predicts success
Sit with this: are your first users actually using the product?
An install count of 100 means nothing if 70 of them installed once and never reopened it. The number that predicts whether you reach 1,000 is your weekly-active ÷ total-install ratio in the first 60 days.
- > 40% → healthy.
- < 20% → a product/onboarding problem no amount of marketing fixes.
Before you scale any tactic above, pull that number. If it's low, fix onboarding first, then come back to acquisition. The best growth strategy for an indie app is a product that the people who install it actually use.
FAQ
How long does 100 users with no ad budget realistically take?
60–90 days for most devs running a focused organic strategy. Some take longer (176 days, the first time). Building in public beforehand cuts it significantly.
Is cold messaging worth it?
Yes, when targeted. Messaging people who've shown they care about your problem is relevance, not spam. Worst case: no reply. It's a skill that improves with reps.
Do a Chrome extension's first users have to come from the Web Store?
No. The first 100 usually come from external channels — Reddit, IndieHackers, cold DMs, free-tool traffic. Web Store search becomes dominant after you accumulate enough reviews to rank. External channels are how you earn that store visibility.
What's the single most important thing to get right first?
Your problem-solution framing. If you can't say in one sentence what problem your app solves and for whom, nothing converts. Test the framing in a niche community — the response (or silence) tells you if you nailed it.
Should I wait for a big Product Hunt launch?
No. Product Hunt is a milestone marker, not a source of first users — the apps that do well there usually arrive with 50–100 installs already. Get your first 100 through direct channels, then use PH to amplify.
Building or growing a Chrome extension? ExtensionBooster gives indie devs real early reviews, market analytics, and free dev tools (icon generator, MV3 converter, review exporter, screenshot maker) — the unglamorous stuff that gets you from invisible to rankable. Explore the free tools →
What got your indie app its first 10 users? Drop it in the comments — I read every one.
Top comments (0)