Growth

From 100 to 100,000 Installs: What Changes

by Sunny T.5 min read

Five indie founders. Five different niches. One shared bug in their listing. The composite case study of what changes between an app at 100 installs and an app at 100,000 installs, and the structural moves that close the gap. Composite reporting, no app names that can be reverse-engineered.

Five indie founders. Five different niches. One shared bug in their listing.

The composite case study below is what changes between an app at 100 installs and an app at 100,000 installs. The structural moves that close the gap. The false scaling moves that compound the gap instead.

Composite reporting throughout. Niches anonymised. The point is the pattern, not the leaderboard.

The shared bug

Across the five founders I tracked, the listing bug was the same. Title started with the brand. Subtitle was a tagline. Keyword field was either empty or stuffed with overlap. First screenshot was the home dashboard. Description led with "Welcome to."

None of those five mistakes are unusual. All five appear in most indie listings on launch day. The reason they matter is compounding. An app at 100 installs with the bug is stuck. An app at 100,000 installs without the bug is also stuck, but at a much higher number. Fixing the bug at 100 unlocks the ladder.

Phase 1. 0 to 100 installs (the listing audit)

At under 100 installs, paid acquisition does not work. The cost per install on Apple Search Ads at this scale is dominated by the broken listing. The only move is the listing audit.

Five-check audit:

  1. Anchor keyword in the first 5 characters of the title.
  2. Subtitle = second-best keyword + 4-word outcome.
  3. 100-character keyword field, no overlap, no stop words.
  4. First screenshot = outcome, not the home dashboard.
  5. Description first 170 characters = outcome, not features.

Each of the five founders ran this audit. Each of the five cleared all five checks inside a weekend. Installs in the following 14 days moved from a low double-digit run rate to a triple-digit run rate. The exact lift varied. The direction did not.

Detailed breakdown in App Store Keyword Research in 60 Seconds.

Phase 2. 100 to 1,000 installs (the proof slot)

Past 100 installs, the bottleneck shifts. The listing is no longer broken. The screenshots are no longer leading with the dashboard. What is missing is the proof slot.

The proof slot is screenshot 3. A stat, a number, or a differentiator. "127,432 entries logged." "Works offline. Forever." "Five-star average from 2,200 reviewers." This is the slot most indie devs skip and the one that converts the buyer who stopped scrolling.

All five founders added the proof slot in phase 2. Product-page conversion lifted in every case. The lifts ranged from meaningful to substantial. None lifted by zero.

Phase 2 also introduces the review-prompt framework. Trigger the prompt on the first outcome moment, anchor the before-prompt screen on what the buyer just experienced, write a one-line transition. Reviews start landing with outcome language instead of brand praise. Apple indexes the outcome language. Rankings tick up.

Phase 3. 1,000 to 10,000 installs (localisation)

At 1,000 installs the home storefront is mostly working. The bottleneck is now the other 26 storefronts.

Localising the metadata to the five highest-revenue non-English storefronts (typically DE, FR, JP, KR, BR) is the cheapest sustained ranking lift indie launches can buy at this phase. The work is one weekend the first time and an hour every refresh after. Most indie devs skip this entirely.

Of the five founders I tracked, three did the localisation pass in phase 3. Their install ramp from 1,000 to 10,000 was materially faster than the two who stayed English-only. The gap was the localisation, not the product. Detail in Localization Is ASO Most Devs Miss.

Phase 4. 10,000 to 100,000 installs (the engine)

At 10,000 installs, the listing is doing the work. What changes from here is the engine that compounds.

Three engine moves:

Review-prompt at scale. Reviews are now landing in volume. Reply to every review. Use responses to reinforce keywords the review missed. Read 1-star reviews as keyword input and update the listing proactively. Apple indexes the review text and the responses. The listing improves itself.

Quarterly regeneration cadence. Re-shoot the hero and proof screenshots every 90 days. Re-test the title and subtitle against new competitors entering the category. Localised metadata refresh per locale on the same 90-day cadence. The discipline is calendared, not improvised.

Apple Search Ads as a scaling tool. Now that the listing converts at twenty-five percent or higher, ASA starts paying for itself. Bid on the anchor keyword first, long tail second, cap daily spend at ten percent of expected MRR, pause during any week of product-page edits. Detail in Apple Search Ads or ASO: What Indie Devs Should Do First.

At 100,000 installs the engine is running. The work is no longer launching the app. The work is the talk-to-50, the retention loop, the pricing test, and the next product. Different post.

False scaling moves to avoid

Three moves all five founders tried at different phases and regretted:

Bulk buying installs. Apple downranks apps with low post-install engagement. Bought installs lower engagement. The boost in raw install count was followed by a sustained ranking drop. Two of the five founders did this in phase 2. Both reversed it inside a month.

Redesigning the icon during a working phase. Icon redesigns mid-phase reset whatever brand recognition scrolling buyers had built. Saturating the redesign with new colours during a phase the listing was converting was the single most expensive mistake any of the five made. Save icon work for the start of a new phase.

Adding features to fix discovery. Discovery is a listing problem. New features in the app do not fix the listing. They cost engineering time that should have gone to the localisation pass or the proof slot. All five made this mistake at least once.

Why we built AsoGrove around this

The five phases above map directly to the AsoGrove tool set. Phase 1 uses the keyword research tool and the metadata generator. Phase 2 uses the screenshot studio. Phase 3 uses the localised keyword pass. Phase 4 uses the regeneration cadence built into every tool plus the review-sentiment work that ships post-Cohort-1.

One workflow, four tools, one subscription. The order is the discipline. The 50 founding seats at €49 a month for life are open while Cohort 1 is filling. Same offer as the rest of the blog. Closes at 50 regardless of when you read this.

The five phases, summarised

  1. 0 → 100: listing audit. Five checks, one weekend.
  2. 100 → 1,000: proof slot. Screenshot 3 carries a number, a stat, or a differentiator.
  3. 1,000 → 10,000: localisation. Five locales, one weekend.
  4. 10,000 → 100,000: the engine. Reviews, regeneration cadence, ASA as scaling tool.
  5. 100,000+: different work. Talk-to-50, retention, pricing.

Same shared bug at the start. Same engine at the finish. The only variable is whether you ran the work in this order or not.

50 founding seats at €49/mo for life are open while Cohort 1 is filling. Claim a founding seat 🌱.

From 100 to 100,000 Installs: What Changes — AsoGrove