16
156 Comments

I’m trying to grow a mobile app without relying on paid ads. Here’s my experiment.

I’m an indie mobile developer and for quite long time my main approach to growth was pretty simple: build the app, do ASO and try paid ads.

The problem is that paid acquisition for my resume app became expensive very quickly. And when your app is still making very little revenue, it’s hard to make the numbers work.

So this week I decided to try a different approach.

Instead of putting more money into ads, I’m building a small organic acquisition system around the app.

What I’m testing now:

dedicated website for the app
SEO landing pages for specific resume searches
directories and product listings
Reddit, but without direct promotion
Indie Hackers
social media content
ASO in parallel

Yesterday I submitted the app to SaaSHub and started participating here on Indie Hackers. Today I also added Make Resume to the IH product database.

The website is completely new and not even indexed by Google yet, so right now the numbers are basically zero :)

But that actually makes the experiment more interesting.

I want to track what happens from the beginning: traffic, App Store clicks, installs and eventually purchases.

I’m planning to work on this consistently for the next few weeks and share the actual numbers here, including things that don’t work.

For people who grew a consumer/mobile app organically — which channel gave you the first real users?

SEO? Communities? Directories? Social media? Something else?

on September 24, 2026
  1. 1

    Interesting approach. What was the hardest part to get right?

  2. 1

    Helpful post. How did you get your first bit of traction?

  3. 1

    Interesting approach. What was the hardest part to get right?

  4. 1

    This is the exact stage I'm in right now, just a few weeks ahead. Same frustration with paid acquisition, same shift to trying to build an organic system from scratch.

    One data point that might save you time: Reddit is a trap for new accounts. I tried posting my launch in r/SideProject and it got auto-removed by the spam filter within seconds — new accounts linking to a sales page get flagged automatically. The fix (which I learned the hard way) is to wait, comment genuinely on 10+ posts to build karma, then post again without any link in the body. Link goes in a comment, not the post.

    The channel that actually worked for me was Dev.to. No spam filter, welcomes "how I built this" posts, and the article stays indexed on Google forever. It's a slow burn, not a spike, but it's the only channel so far where my content actually stayed online long enough to be found.

    Two questions:

    1. For the SEO landing pages — are you targeting specific resume queries like "best resume format for software engineers", or broader ones? Curious how niche you're going.
    2. What's your plan for the first real signal? Weekly numbers here, or waiting until you have something more meaningful to report?

    Following along. Post the ugly numbers—those are the useful ones.

  5. 1

    Running a similar no-ads experiment right now, so here's one thing I wish I'd set up on day one: measure time on page and filter bots before trusting any channel. My first "visits" were mostly link-preview crawlers and scanners (0 seconds, no clicks), which made a couple of channels look better than they were.

    Also: give every channel its own short link (?via=name). Otherwise TikTok, typed URLs and in-app browsers all show up as "direct" and you can't tell what worked.

    What are you counting as a "real user" for the experiment, install or first action?

  6. 1

    Looks like my first comment got mangled. What I meant was: for a resume app, I’d split channels by intent. Go first where people are actively stuck with a resume or job search, then use those conversations to choose specific SEO pages. “Resume builder” is probably too broad early; pages around career-change resumes, software engineer bullets, ATS formatting, etc. might teach you more.

  7. 1

    around specific pains like career-change resumes, software engineer bullets, ATS formatting, etc. may teach you more.ware engineer bullets, ATS formatting, etc. m

  8. 1

    Interesting approach. What was the hardest part to get right?

  9. 1

    Interesting approach. What was the hardest part to get right?

  10. 1

    Helpful post. How did you get your first bit of traction?

  11. 1

    Interesting approach. What was the hardest part to get right?

  12. 1

    Helpful post. How did you get your first bit of traction?

  13. 1

    Interesting approach. What was the hardest part to get right?

  14. 1

    am trying similar aproach. i just know i will get more positive results on this

  15. 1

    Our first real users at SocialPost.ai came from founder communities like this one, not SEO or directories, someone actively looking for a solution today converts faster than someone finding you in six months once Google trusts the domain. Directories rarely move the needle before you have social proof. For a resume app specifically, I'd go where people are actively venting about job hunting right now, like r/jobs or LinkedIn comment sections, not app store directories.

  16. 1

    This is an interesting experiment, especially because you’re tracking everything from zero rather than just trying a bunch of channels and guessing what worked.

    I’m doing something related with my AI visibility tool, although from a slightly different angle. It lets you enter a brand and its competitors, generate prompts around them, and analyse the actual AI responses to see which brands are being surfaced, how often, and in what context.

    What’s interesting to me is that organic discovery is no longer just about Google rankings or App Store search. If someone asks ChatGPT or another AI for “the best resume app” or “resume builders for X”, that response is another discovery surface — and brands can be completely invisible there even if their SEO/ASO is doing well.

    Your experiment is basically measuring where users discover you. I’m looking at another piece of that puzzle: whether AI systems are discovering and mentioning you in the first place.

  17. 1

    I'm running a similar zero-budget experiment for a different B2B product. The part I keep having to separate is 'submitted to a directory' from 'listed,' and 'listed' from 'a buyer actually arrived.' Your traffic-to-App-Store-click-to-install sequence is a good way to keep those apart. Are you planning to tag each channel's links separately so you can tell which one produces installs?

    1. 1

      Yeah, I think that distinction is really important — “listed” and “actually discovered” are two very different things.

      That’s actually the problem I’m looking at with my AI visibility tool. A brand can technically be present in the ecosystem, have a website, directory listings, good content, etc., but that doesn’t necessarily mean AI systems will actually mention it when someone asks a relevant question.

      My tool lets you test a brand against its competitors by running prompts through AI and analysing the actual responses — so instead of assuming a brand has visibility because it exists somewhere, you can see whether it’s actually being surfaced in the answers people might see.

      It’s made me think about visibility as a funnel too: listed → discovered → mentioned → actually considered. The interesting part is figuring out where that drop-off happens.

  18. 1

    This is a really interesting experiment, especially because you’re tracking everything from day one. I think building an organic acquisition system alongside ASO makes a lot of sense when paid acquisition isn’t profitable yet.

    1. 1

      Totally agree. What makes your experiment particularly interesting to me is that organic acquisition is increasingly happening outside traditional search as well.

      That’s the problem I’m focused on with my AI visibility tool. You can have a website, do ASO, get listed in directories and publish content, but there’s another discovery layer now: what happens when someone asks an AI for a recommendation?

      My tool lets you enter a brand and its competitors, run relevant prompts through AI, and analyse the actual responses to see which brands get mentioned, how often, and in what context.

      So I think your experiment is measuring one side of organic discovery really well — where people are finding the app — while AI visibility adds another question: when someone asks an AI directly, does your product even make it into the consideration set?

  19. 1

    Organic channels tend to compound, but they can be hard to compare early on. What’s your plan for deciding whether a directory or community is worth the time before installs show up?

  20. 1

    This is a smart experiment. Paid acquisition can get expensive very quickly before product-market fit is clear, so building an organic loop around the product makes a lot of sense.

    I’d be especially interested to see which channel brings the highest-quality users, not just the most traffic. Please share the results once you have enough data.

  21. 1

    I agree with the social and the organic. GEO is also very important and is working well once you have your SEO sorted. What I learned it takes time and investment. Either in money or in a lot of your personal time. The internet isn't what it used to be and the big players are controlling the game in an unfair way. Depending on your business, worth of mouth is also very important. Engaging actively with your first customers may have them recommend it to their friends, family, coworkers, which in turn will give you more customers. Good luck!

  22. 1

    Directory submissions + organic social have been the two channels actually giving us anything so far — no paid spend either, running two SaaS products through the same playbook right now. Directories are slow-burn (a trickle of backlink/domain-authority value, not a flood of signups), but organic social with real consistent posting has been the bigger driver early on. Reddit's tricky like you said — anywhere it works, it's because you're answering a real question, not pitching.

    Honestly the first real signups took longer than expected either way. If it's working at all this early without ads, you're already ahead of where most people are at this stage.

    1. 2

      Directories actually work as a way of bringing in users?

  23. 1

    We're running almost the same list for our app, so two things I wish I'd known earlier. On Reddit, some subreddits silently hide comments from new accounts, and from your own account it all looks normal: check your comments from a logged-out private window now and then, two of the six communities I used were hiding mine. And give the SEO pages time with Bing, it took only a small share of ours into its index even though every technical check passed.

  24. 1

    I am in Organic marketing field for 4 years and currently working on Mindfuse app. So i think in current organic marketing space focusing on communities and SEO will be better choice, Directories are just for telling that "you know we are part of this app category" but in Communities you are answering and solving direct user problems so its more beneficial. Social media marketing is complete different space including influencer promo, UGC etc.

  25. 1

    For a review site of mine, communities beat directories by a wide margin for real first users. Directories mostly bring backlinks and crawler traffic, not people who click through. What worked was answering existing questions on Q&A sites where someone already had the exact problem the app solves, no self-promotion, just a useful answer with the app mentioned where it fit. Slower than ads, but people who arrive that way convert better because they came in with intent.

  26. 1

    For a resume tool, your first real users are usually in intent-rich pockets: niche career and resume subreddits, plus SEO pages targeting hyper-specific queries like resume examples for specific roles. Directories are a lottery ticket — cheap to list, but they rarely move the needle in week one. One thing worth adding to the experiment: answer-first content that AI search can surface, since more people now ask AI assistants instead of Googling. And track each channel to activation rather than clicks, because resume tools live or die on whether someone actually finishes a draft.

  27. 1

    i also tried the same but this works littlr bit slow

  28. 1

    For a resume app specifically, the first real users often come from intent-matched SEO pages rather than directories — but not generic "resume builder" pages. Long-tail pages like "resume format for [specific job] in [country]" have weak competition and match exactly what someone searches the moment before they need your app. Reddit works the same way: people post "roast my resume" threads constantly, and genuinely helping there, with the app mentioned only as the tool you used, tends to convert better than any listing. One caution from watching these experiments: ASO and SEO have compounding curves that look flat for the first 4-6 weeks, so when you share weekly numbers, don't let week two's zeros kill the channels that would have paid off in week eight.

  29. 1

    Navigating growth without paid ads is such a universal challenge for solo founders. Tracking this from day 0 with zero index is going to yield super insightful data for the community!

    I'll be following along closely to see what works best for you, and I’ll be sure to share my own learnings down the road as well. Rooting for you—looking forward to the next update!

  30. 1

    Straight answer: communities, and replies more than posts. Directories and SEO showed up in our referral report long before they showed up in activations - for a while our "top channel" by UTM was one thread that produced a single real conversation. The fix wasn't a new channel, it was tagging every link per post and then reading source -> signup -> first meaningful action, instead of source -> sessions. If all you have so far is installs, pick one channel and instrument it end to end before adding the next one. Which one are you instrumenting first?

  31. 1

    On Reddit we learned the hard way: one soft product link in a helpful comment got the comment removed. Since then we keep Reddit replies DIY-only with no product URL, and treat that channel as conversation, not a listing. Curious which of your UTM sources first produces an install that also creates a resume, not just a store click.

  32. 1

    I too am close to releasing my App posting it on the Google Play Store first. I'm still trying to find my first 50 beta testers. This is a very different world for me. My past jobs have been working for companies that already had sales channels and a force of people who could do more on the ground work. I'm a solo guy trying to get into a world wide market starting ANYWHERE. Sorry to not be able to answer your question directly but any dialog is good dialog.
    Kirk

  33. 1

    Interesting approach. What was the hardest part to get right?

  34. 1

    Interesting approach. What was the hardest part to get right?

  35. 1

    Helpful post. How did you get your first bit of traction?

  36. 1

    Interesting. How are you measuring whether it is working?

  37. 1

    Interesting approach. What was the hardest part to get right?

  38. 1

    Interesting. How are you measuring whether it is working?

  39. 1

    Helpful post. How did you get your first bit of traction?

  40. 1

    Interesting approach. What was the hardest part to get right?

  41. 1

    Good approach. With a new site, I’d separate the signals: track which channel produces a first useful action, not just traffic. The channel that gets people far enough to try the app is probably the one worth leaning into first. Curious to see the comparison.

  42. 1

    Interesting approach. What was the hardest part to get right?

  43. 1

    Interesting approach. What was the hardest part to get right?

  44. 1

    Interesting. How are you measuring whether it is working?

  45. 1

    Helpful post. How did you get your first bit of traction?

  46. 1

    Interesting approach. What was the hardest part to get right?

  47. 1

    Helpful post. How did you get your first bit of traction?

  48. 1

    Interesting. How are you measuring whether it is working?

  49. 1

    Interesting approach. What was the hardest part to get right?

  50. 1

    Helpful post. How did you get your first bit of traction?

  51. 1

    Interesting approach. What was the hardest part to get right?

  52. 1

    Interesting. How are you measuring whether it is working?

  53. 1

    Interesting approach. What was the hardest part to get right?

  54. 1

    Interesting approach. What was the hardest part to get right?

  55. 1

    Interesting. How are you measuring whether it is working?

  56. 1

    Helpful post. How did you get your first bit of traction?

  57. 1

    Interesting approach. What was the hardest part to get right?

  58. 1

    For my stuff, communities beat SEO for the first real users every time. SEO is a slow compounder — great in month six, useless in week two when you need signal. If I were running your experiment I'd pick one community where resume pain actually gets discussed (career subs, not marketing subs), answer questions genuinely for two weeks, and measure landing page to install, not raw traffic. Directories gave me vanity traffic but almost zero installs. The real trap is spreading across six channels at once and learning nothing about any of them.

  59. 1

    Helpful post. How did you get your first bit of traction?

  60. 1

    Interesting approach. What was the hardest part to get right?

  61. 1

    Interesting. How are you measuring whether it is working?

  62. 1

    Interesting approach. What was the hardest part to get right?

  63. 1

    Interesting approach. What was the hardest part to get right?

  64. 1

    Helpful post. How did you get your first bit of traction?

  65. 1

    Interesting. How are you measuring whether it is working?

  66. 1

    Interesting approach. What was the hardest part to get right?

  67. 1

    Interesting approach. What was the hardest part to get right?

  68. 1

    Helpful post. How did you get your first bit of traction?

  69. 1

    Interesting approach. What was the hardest part to get right?

  70. 1

    Interesting. How are you measuring whether it is working?

  71. 1

    Interesting approach. What was the hardest part to get right?

  72. 1

    Interesting approach. What was the hardest part to get right?

  73. 1

    Helpful post. How did you get your first bit of traction?

  74. 1

    Interesting. How are you measuring whether it is working?

  75. 1

    Interesting approach. What was the hardest part to get right?

  76. 1

    Interesting. How are you measuring whether it is working?

  77. 1

    Helpful post. How did you get your first bit of traction?

  78. 1

    Interesting approach. What was the hardest part to get right?

  79. 1

    Interesting approach. What was the hardest part to get right?

  80. 1

    Interesting. How are you measuring whether it is working?

  81. 1

    Helpful post. How did you get your first bit of traction?

  82. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

  83. 1

    Appreciate the honesty here, most people only share the wins.

  84. 1

    Helpful post. How did you get your first bit of traction?

  85. 1

    Interesting. How are you measuring whether it is working?

  86. 1

    Interesting approach. What was the hardest part to get right?

  87. 1

    Interesting approach. What was the hardest part to get right?

  88. 1

    Helpful post. How did you get your first bit of traction?

  89. 1

    Interesting approach. What was the hardest part to get right?

  90. 1

    Interesting approach. What was the hardest part to get right?

  91. 1

    Interesting. How are you measuring whether it is working?

  92. 1

    Interesting approach. What was the hardest part to get right?

  93. 1

    Interesting. How are you measuring whether it is working?

  94. 1

    Interesting approach. What was the hardest part to get right?

  95. 1

    Helpful post. How did you get your first bit of traction?

  96. 1

    Tracking the experiment from zero is a smart way to separate channel anecdotes from actual conversion. I’d keep the landing pages narrowly aligned to the exact resume questions people search, then tag each page through install and first-use so directories and communities are comparable. Since you’re avoiding direct promotion on Reddit, observing which questions generate useful discussions could also reveal the content topics worth turning into SEO pages.

  97. 1

    Helpful post. How did you get your first bit of traction?

  98. 1

    Interesting approach. What was the hardest part to get right?

  99. 1

    Interesting. How are you measuring whether it is working?

  100. 1

    Interesting approach. What was the hardest part to get right?

  101. 1

    What made you pick this stack over the alternatives?

  102. 1

    Really relatable. How much time do you put into this each week?

  103. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  104. 1

    This is useful. How are you finding your first users so far?

  105. 1

    Interesting approach. What was the hardest part to get right?

  106. 1

    Curious how long it took before you saw the first real results?

  107. 1

    Thanks for sharing the numbers, that makes it much easier to follow.

  108. 1

    Helpful post. How did you get your first bit of traction?

  109. 1

    Interesting approach. What was the hardest part to get right?

  110. 1

    Interesting. How are you measuring whether it is working?

  111. 1

    Interesting approach. What was the hardest part to get right?

  112. 1

    Interesting approach. What was the hardest part to get right?

  113. 1

    Interesting. How are you measuring whether it is working?

  114. 1

    Interesting approach. What was the hardest part to get right?

  115. 1

    Helpful post. How did you get your first bit of traction?

  116. 1

    Helpful post. How did you get your first bit of traction?

  117. 1

    Interesting. How are you measuring whether it is working?

  118. 1

    Interesting approach. What was the hardest part to get right?

  119. 1

    Interesting approach. What was the hardest part to get right?

  120. 1

    Went through this exact math a few days ago. Ran the numbers on paid (LinkedIn CAC benchmarks alone were north of $2k) against a $9.99/mo product and it just doesn't work yet, not without a validated conversion rate first. Only just wired up real analytics this week, before that I genuinely had no idea if clicks from IH/X were converting or not, just vibes. Directories, IH, and X replies (not cold posts) have been the only channels that felt worth the time so far. Curious to see your SEO landing page results, that's the one I haven't tried.

  121. 1

    For a new organic system, I’d resist judging channels by traffic first. Give each channel one narrowly defined job, use a different landing-page message or onboarding question for each, and track the first meaningful action through to a retained user. Otherwise directories, search, and community activity all blur into one “zero” and you won’t know which small signal deserves another week of effort.

  122. 1

    Interesting approach. What was the hardest part to get right?

  123. 1

    Interesting approach. What was the hardest part to get right?

  124. 1

    Interesting. How are you measuring whether it is working?

  125. 1

    Helpful post. How did you get your first bit of traction?

  126. 1

    Thanks for writing this up. Bookmarking it for later.

  127. 1

    Appreciate the honesty here, most people only share the wins.

  128. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

  129. 1

    Interesting approach. What was the hardest part to get right?

  130. 1

    Curious how long it took before you saw the first real results?

  131. 1

    Curious how long it took before you saw the first real results?

  132. 1

    Helpful post. How did you get your first bit of traction?

  133. 1

    we're running almost the same experiment right now, and the first surprise was how little the directories did. most of them give you a backlink and zero people. what moved anything for us were places where someone actually reads every entry: monthly "what are you working on" threads, niche newsletters, small communities where the builder answers every reply. for a resume app i'd bet on the weekly threads in career subs over any listing. curious to see your numbers per channel in a few weeks

    1. 2

      That's a really useful point about career subs. I’ve mostly been thinking about Reddit as a place to join relevant conversations, but weekly career threads could be a much better fit for a resume app.

      I’m tracking each source separately with UTMs, so in a few weeks I should have actual numbers for directories vs Reddit vs Indie Hackers vs SEO. I’ll share the results even if they’re terrible 😅

      Would be interesting to compare notes since you’re running a similar experiment.

      1. 1

        deal, let's compare. one thing that bit us: analytics only counts people who accept cookies, and a lot of people type the name instead of clicking, so small channels look even smaller than they are. a one-line "where did you hear about us" question at signup would catch what utm misses. we don't have one yet and kind of regret it

  134. 1

    As the experiment runs, what result would make you shift resources decisively toward organic—lower cost per install, better purchase rates, or stronger retention than paid users?

    1. 1

      Ultimately, purchase rate and revenue per acquired user.

      Cheap installs alone wouldn’t be enough for me to shift resources. I’ve already seen that getting installs is very different from getting users who actually create a resume, reach the paywall and purchase.

      For this experiment I’m tracking the funnel from source → landing page → install → activation → paywall → purchase. If an organic channel brings fewer users but they convert better, I’d rather scale that than chase cheap traffic.

      The goal for me isn’t “grow organic traffic” — it’s to find a repeatable path to revenue without depending entirely on paid ads.

      1. 1

        That source-to-revenue funnel is much more useful than install volume. Could be worth comparing notes on it by email sometime, if you’re open to it.

  135. 1

    Nice to see you treating this as an experiment rather than just adding more channels. I’d give each source its own landing page or deep link and track one funnel consistently: source → landing view → App Store click → install → first useful action → purchase. That makes a directory’s small but high-intent traffic comparable to a social post’s larger, noisier reach. I’d also separate assisted conversions and retention by channel; raw installs can make a channel look good even if the day-7 cohort is weak. SEO probably needs longer than a few weeks, so use indexing/impressions as its leading signal while judging communities and directories on activated users. If bandwidth is limited, test two channels deeply before spreading across all of them.

  136. 1

    Interesting approach. What was the hardest part to get right?

  137. 1

    Interesting approach. What was the hardest part to get right?

  138. 1

    Interesting. How are you measuring whether it is working?

  139. 1

    Helpful post. How did you get your first bit of traction?

  140. 1

    Helpful post. How did you get your first bit of traction?

  141. 1

    Interesting approach. What was the hardest part to get right?

  142. 1

    Interesting approach. What was the hardest part to get right?

  143. 1

    Interesting. How are you measuring whether it is working?

  144. 1

    Interesting approach. What was the hardest part to get right?

  145. 1

    Interesting approach. What was the hardest part to get right?

  146. 1

    Interesting. How are you measuring whether it is working?

  147. 1

    Helpful post. How did you get your first bit of traction?

  148. 1

    Interesting approach. What was the hardest part to get right?

  149. 1

    This is great work — reminds me of some of the calls I've had to make building Xstream4K. What would you do differently if you started over?