14
48 Comments

641 downloads, 2 sales, and I still don't know why

Follow-up to the "7 plugins, 328 downloads, $34.98" post from two weeks ago.
Downloads roughly doubled since then — 641 across 7 plugins now. Sales didn't move. Still 2 sales, still $34.98, same two plugins (Reading Inbox and Literature Review) that sold before.
Here's the breakdown by plugin, sorted by downloads:

AI Journal Coach — 153 downloads, 0 sales
Literature Review Synthesizer — 135 downloads, 1 sale
Highlight Inbox Synthesizer — 81 downloads, 0 sales
Meeting Notes Synthesizer — 80 downloads, 0 sales
Reading Inbox Synthesizer — 79 downloads, 1 sale
Watch Later Synthesizer — 75 downloads, 0 sales
Periodic Notes Synthesizer — 38 downloads, 0 sales

The pattern from last time held: the plugin with the most downloads (AI Journal Coach, 153) has zero sales. The two that sold are mid-pack on downloads. A commenter last time called this painkiller vs. vitamin — tools that process a backlog you already feel bad about (unread articles, unwatched videos) vs. tools that process your own output (journal entries, meeting notes). I bought that framing, and I still think it's directionally right. But it doesn't fully explain a 2x download jump with zero sales movement.
Where I'm stuck: I don't know if this is (a) a volume problem — 641 downloads is still too small a sample to expect more than 2 conversions at whatever this category's true rate is, (b) a positioning problem — even the backlog plugins aren't making the "why pay" case clearly enough at the free-tier-exhausted moment, or (c) something about the free tier itself (3 uses, lifetime) that's wrong in a way I can't see from the outside.
Genuinely asking, not fishing for reassurance: if you've shipped something similar — free tier + one-time paid upgrade, no subscription — what actually moved your conversion number? Was it volume, positioning, pricing, or something else entirely?

on July 10, 2026
  1. 1

    My guess is people don't buy because they haven't yet experienced enough value before the paywall. If the first few uses don't create an "I can't go back" moment, they'll just move on instead of upgrading.

  2. 1

    my hunch: don't treat downloads as the funnel start, treat first successful use as the start. 641 downloads could still be like 80 people who actually hit the aha moment. i'd instrument: first run completed, second run within 7 days, export/save/share, then paywall shown. if the 2 buyers had repeat/backlog behavior, i'd price around that exact moment instead of tweaking the whole free tier. 3 lifetime uses may also make ppl ration it before they even trust it.

  3. 1

    maybe it's saturation, too mush softwares, apps...

  4. 7

    Some of us are pure beginners so am very lost but got some insight thanks

    1. 1

      Same here, already learnt alot.

    2. 1

      Stay strong were in it together

    3. 1

      Glad it was useful, even in the lost-beginner state — that's honestly the most honest place to read a post like this from.

  5. 1

    The download-to-sale conversion challenge is real. From my experience with AI tools, the gap often comes down to onboarding friction - users download but don't hit that first 'aha moment'. What's your activation rate like? Sometimes optimizing the first 5 minutes of user experience matters more than the product itself.

  6. 1

    The $34 metric is impressive. From building similar tools, I've learned that numbers alone don't tell the full story - user retention and satisfaction often matter more long-term. What's your take on balancing growth vs. quality?The $34 metric is impressive. From building similar tools, I've learned that numbers alone don't tell the full story - user retention and satisfaction often matter more long-term. What's your take on balancing growth vs. quality?

  7. 2

    I think you're focusing on the conversion rate, but the more interesting signal is that 641 people downloaded something from you and almost nobody asked for a refund or complained. That suggests the problem isn't trust or product quality.

    My guess is that most users haven't reached a strong enough pain point yet. A download is curiosity. A purchase is urgency.

    If I were you, I'd spend less time testing pricing and more time understanding the exact moment when someone thinks: "I don't want to do this manually anymore." Then make your paywall and messaging revolve around that moment.

    Also, I'd definitely interview the 2 buyers before changing anything major. Two paying customers may sound insignificant, but they contain 100% of your revenue data. Their reasons for buying are probably worth more than another 500 downloads.

  8. 2

    the volume worry is a bit of a distraction imo. 2 out of 641 doesn't reveal your true rate, but the shape of the data already does: the two that convert are the backlog tools people feel guilty about. that's the signal. you're spreading yourself across 7 when the data is telling you which 2 have any pull.

    i'd bet it's (c) wearing a (b) costume. '3 uses lifetime' drops the paywall at an arbitrary spot instead of the moment the value actually lands. for a backlog tool that moment is when the pile is huge and you just made it vanish, not on use #4. a lifetime cap also quietly frames the thing as a one-time job, and one-time jobs are brutal to charge for, once it's done there's no reason to come back or pay.

    what actually moved my numbers wasn't more traffic, it was gating on outcome instead of a use counter, and picking the one tool with a recurring reason to reopen. a reading inbox refills every week, a journal coach is basically one-and-done for most people. go where there's a natural cadence and put the paywall at peak relief, not peak use count.

  9. 2

    This resonates — just launched my own first side project this week and going through the same "did people actually get it or did they just bounce" feeling. Following this thread, curious what you find out. Did you get any direct feedback from the 2 who converted, or just silence?

    1. 1

      Honestly, silence so far — I haven't reached out yet, which a few people in this thread have fairly called out. Doing it this week. Will post back with whatever I find, good or bad.

  10. 2

    The cleanest part of our 2-buyer dataset wasn't the number, it was WHAT they said when we asked why they paid. Neither trigger was a product feature — both were about the moment: one paid because a live experiment was 9 minutes from failing and he could be the ending, the other because his advice had just been implemented in front of him. No landing page could have contained either sentence. That's what made me stop treating positioning as copy and start treating it as timing: the same product converts when the buyer can see their own action mattering RIGHT NOW.

    If you ever interview your two buyers, I'd genuinely like to know if you find the same shape — a moment, not a feature.

    1. 1

      That's exactly the kind of thing I was hoping talking to buyers would surface, and you already have it: a moment, not a feature. "9 minutes from a live experiment failing" and "advice just got implemented in front of him" are both about the buyer watching their own action have a consequence right then, not about anything on a landing page. I hadn't separated timing from positioning as cleanly as you just did. Reaching out to my two this week — I'll report back whether I find the same shape.

  11. 2

    The volume/revenue gap is brutal. 641 downloads is solid distribution, but 2 sales suggests a messaging or positioning issue more than a product one. Have you tried segmenting your users - like, which countries/device types are downloading vs. which ones are converting? Sometimes the gap isn't about getting more downloads, it's about finding the 10% who actually value what you built.

    1. 1

      I haven't segmented by country or device, no — that's a real gap, I've only been looking at aggregate Gumroad numbers. Will check what's actually available there and see if a pattern shows up. Appreciate the reframe: "more downloads" and "find the 10% who value it" are different problems and I've mostly been treating them as the same one.

  12. 2

    Before touching pricing or positioning, the number I'd want is: of the 641, how many actually reached use #3 and hit the wall? Downloads is the wrong denominator. Your real conversion rate is paid divided by people who exhausted the free tier, and my bet is most of the 641 tried it once and drifted, so the "why pay" moment never even fired. If that's the case, this is an activation problem wearing a conversion problem's clothes.

    The 3-uses-lifetime tier is probably working against you. For backlog tools the value compounds through a habit, and a lifetime cap that small kills the habit before it forms. People hit the wall as curious triers, not as attached users, so they churn instead of paying. Counterintuitively a more generous recurring limit (say N a week) often converts better than a tiny lifetime one, because the limit bites over and over at a moment of real need instead of once, early, before they care.

    On painkiller vs vitamin, I'd sharpen it to recurring guilt vs one-time nicety. Reading Inbox and Literature Review map to a backlog that refills and nags you every week. AI Journal Coach processes your own output, and a lot of people who install it don't have a painful pile yet, so there's nothing to relieve. Most-downloaded just means best title; sales follow felt pain, not curiosity.

    For context, I'm the founder of Automateed (freemium AI tool with a paid upgrade, plus a marketplace), so I've stared at this exact curve. The one change that actually moved our number wasn't price or landing-page copy, it was making the paywall fire after the user had already produced an output they wanted to keep, and making the free tier generous enough to reliably reach that moment. Before that aha, every upgrade button is just noise. At 641 downloads with a lifetime free cap, I'd fix the moment before I'd touch the price.

    1. 1

      This is a genuinely useful reframe — "denominator should be people who hit the wall, not total downloads" is a number I don't have and should. And the recurring-limit point landed: I actually started a small experiment today, before reading this, raising one plugin's free tier from 3 lifetime uses to 10 lifetime — still a lifetime cap, not recurring, mostly because I don't want to build usage tracking (no telemetry is a hard line here). But your point about the paywall firing after the user already has something they want to keep, rather than as an arbitrary count, is the sharper lever and I don't think 10-vs-3 addresses it at all. Noting it as a real candidate for the next iteration if the lifetime-cap bump doesn't move anything.

  13. 2

    I'm having some trouble getting my product out there as well. Currently at a place where I just want people to try it, not even pay for it.

  14. 2

    I honestly think it's still too early to read too much into the numbers. 641 downloads sounds like a lot, but with only 2 sales the sample is still tiny.

    One thing I did notice though is the free tier. If I get 3 lifetime uses, there's a decent chance I never actually hit the limit. I'd try it, think "nice tool," and then not touch it again for weeks. In that case I'm never even given a reason to buy.

    I'd be more interested in seeing how many people came back and used a plugin a second or third time. Feels like that would tell you way more than total downloads.

    Just my 2 cents, but I'd probably focus on getting people to come back before changing the pricing. The pricing might not even be the real issue.

    1. 1

      That's the same shape a couple of others in this thread landed on independently, and I think you're right that it matters more than the download total does. I don't have return-usage data broken out right now — it's on the list to go dig up. Appreciate the steer toward fixing return behavior before touching price; that's probably the correct order and I had it backwards.

  15. 2

    Small dataset from a different corner, but it changed how I read numbers like yours: we sell a dev playbook with a pay-what-you-want tier, and 100% of the revenue came from direct conversations — replies to specific people who were already engaged — while broadcast posts with 10x the impressions produced exactly zero. Downloads/views never predicted anything; the only variable that ever moved money was whether a real exchange happened first.

    So on your (a)/(b)/(c): I'd bet on a fourth option — the 641 downloads aren't a funnel, they're an audience. A 3-use lifetime free tier means people hit the paywall alone at their desk, with no conversation running. Have you tried talking to the 2 buyers instead of the 639 non-buyers? Both of ours told us the exact sentence that made them pay, and it wasn't anything we had written on the landing page.

    1. 1

      That downloads-vs-conversation split matches something I've seen too, just from a different angle: every push channel I've tried (social, forum posts, Product Hunt) has converted at roughly 0%, while the only real signal has come from passive/organic discovery. I hadn't framed it as "broadcast vs. direct exchange" before, but that's a sharper way to say it than "push vs. pull." Appreciate the number — 100% from direct conversation on a pay-what-you-want tier is a much cleaner signal than my 2-sales dataset can give me right now.

  16. 2

    My honest read leans toward (b) over (a). I run a free audit tool as the entry point into my own paid work, and the pattern that took me the longest to see was that people will use a free tool that solves an immediate, nameable problem without ever connecting it to the paid step, because the free tool already made them feel done. Reading Inbox and Literature Review sold because they process a backlog someone already feels guilty about, and hitting the free tier ceiling on that specific guilt is a sharper moment than hitting a usage cap on a journal tool nobody was dreading in the first place.
    I'd push on your free tier itself before touching pricing. Three uses, lifetime, is a hard wall with no visible edge to it while someone's using the tool. The conversion moment that actually works is usually mid task, not after the door's already closed, something closer to a visible counter ticking down so the person feels the wall coming before they hit it. That's a positioning problem wearing a volume problem's clothes.
    I wouldn't rule out volume yet either. Two sales at 641 is thin enough that you genuinely can't separate signal from noise. I'd want to see this at two or three thousand downloads before trusting any conclusion about which framing is right.

    1. 1

      Agreed on all three points, and the third one is the one I keep underweighting — assuming the free-tier ceiling IS the trigger, rather than checking whether it's just when the tool became habitual. I don't have telemetry to tell those apart (won't add tracking here), so the only honest move I have is asking the people who converted directly what was actually happening for them at the time, rather than reverse-engineering it from usage numbers alone.

  17. 2

    This mirrors something I learned the hard way: the obvious answer usually has a non-obvious cost that only shows up six months later. Worth naming it early.

    1. 1

      That's a useful frame, thanks. I don't have a six-month-out cost I'm bracing for yet, but the closest thing might be the free tier itself — if I raise it and it turns out the real issue was never volume, I'll have spent effort optimizing the wrong knob while the actual answer (category, or something about how the paywall moment is framed) sits untouched. Naming it early, per your suggestion: I'll treat a flat conversion rate after the free-tier bump as a signal to stop tuning the number and go talk to the two people who bought instead of guessing further.

  18. 2

    One thing that might help: if you're using Stripe (or something similar) to charge, you likely have the email of those 2 people who paid. Try reaching out directly and just ask what made them decide to buy vs. everyone else who just downloaded. A 5-minute conversation with an actual paying user usually reveals more than any amount of guessing from the data alone.

  19. 2

    This is a great kind of post to see — real numbers and honest uncertainty. Have you looked at where the 2 paying users came from? Sometimes the pattern between who converts vs. who just downloads gives a clue for repositioning.

    1. 1

      Yes on both counts — I do have their emails from the purchase, and no, I haven't reached out yet, which several people here have now (fairly) called out. Doing it this week. Your second point is the one I want the answer to more: whether there's a pattern in what those two were doing before they bought, since that's the thing that would actually tell me something about repositioning rather than just confirming I should talk to people (which, yes, obviously).

  20. 2

    That's an interesting issue you've run into. One thing that is helping me (in a very similar situation) has been tracking usage and seeing falloff there.
    I recently had an issue with DeerDawn where I was getting signups but no payments, and not even any real change in api costs. I added posthog tracking for key things, mcp calls, context shared, and whatnot and found that most people who made an account weren't even completing onboarding.
    This observation allowed me to go through the onboarding process and look at where people were getting stuck, and what was just taking too long. (I was making people open their terminal to complete onboarding, I changed that to pasting a custom mcp connect to claude or chatgpt and completion improved)
    Best of luck!

    1. 2

      You and a couple others below are converging on the same point and I don't have a good excuse for not having done it yet — I haven't talked to the 2 people who actually paid. I've been treating this as a data problem (limit size, category, copy) when the fastest way to actually find out is just asking the two humans who made the decision. Going to reach out to both this week and report back honestly, including if the answer turns out boring or unflattering to my current theories.

      1. 1

        I had the same exact issue when I was working through my onboarding process. All the data in the world is worth less than just hearing what people think. End of the day knowing that and adjusting based off it will get you way further, way faster. Best of luck!

  21. 2

    I wonder if the downloads are telling you one thing and the sales another.
    Someone downloading a plugin is a very low-commitment action. Buying it requires trusting that it will become part of their workflow.
    If I were in your position, I'd spend some time talking to the two customers who did buy. Understanding why they paid might be more valuable than trying to guess why the other 639 didn't.
    Sometimes the buyers reveal your real positioning better than the non-buyers.

    1. 1

      That's a clean way to put the asymmetry — download is basically free to do, purchase requires believing the tool earns a permanent spot in your workflow. I've been reading the download number as if it validated the idea, when it might only validate the pitch. Talking to the two buyers is the next step, agreed — seems to be the one thing everyone in this thread landed on independently, which is probably a signal in itself.

  22. 2

    Great breakdown, Ibrahim. The 'painkiller vs. vitamin' framework is solid, but with a 2x jump in downloads and 0 sales, I highly suspect it's (c) the free tier structure.

    3 lifetime uses might be too restrictive for them to build a real habit or see the compound value of the tool, OR it's the exact opposite: they use it once or twice for a specific urgent task and never need it again.

    Have you considered switching the free tier to a time-based trial (e.g., 7 days with unlimited uses) or a usage limit that resets monthly? This forces a habit loop, and once they are hooked, the conversion to the paid one-time upgrade becomes much more natural when the wall hits.

    1. 1

      Fair challenge. I don't think I'll go time-based — a subscription-shaped trial cuts against the whole reason people pick this over a SaaS tool (no server, no account, no recurring anything). But "3 might just be the wrong number" is a much cheaper thing to test than the model itself, so I'm bumping it to 10 lifetime uses on one plugin and watching what happens. If it's still not converting at 10, that tells me something useful too — it'd point away from "too stingy" and back toward category (I've got other data suggesting backlog-type tools convert very differently from personal-archive tools, independent of the limit).

    2. 1

      This comment was deleted 20 hours ago.

  23. 2

    If that's true, I'd spend less time asking why people aren't converting and more time asking what changes in the moment someone decides, "I can't keep doing this manually." That transition may reveal more than another few hundred downloads ever will.

    1. 2

      Spot on! That’s the real inflection point. It shifts the focus from a cold conversion metric to a psychological trigger. When someone says 'I can't keep doing this manually,' they aren't just looking for a tool anymore they are looking for relief.

      If Ibrahim can figure out exactly when that frustration peaks during those 3 free uses, he can place his pricing wall precisely at that emotional trigger. Downloads bring eyeballs, but solving that specific friction point is what brings the revenue.

      1. 1

        Fair challenge. I don't think I'll go time-based — a subscription-shaped trial cuts against the whole reason people pick this over a SaaS tool (no server, no account, no recurring anything). But "3 might just be the wrong number" is a much cheaper thing to test than the model itself, so I'm bumping it to 10 lifetime uses on one plugin and watching what happens. If it's still not converting at 10, that tells me something useful too — it'd point away from "too stingy" and back toward category (I've got other data suggesting backlog-type tools convert very differently from personal-archive tools, independent of the limit).

        1. 2

          That's the part I was hoping you'd expand on.

          Reading your reply raised a question for me about how you're interpreting those experiments. I'd rather explain why I'm asking with your product as the context than reduce it to a generic discussion.

          What's the best email to reach you on?

          1. 1

            That's a better question than the one I was asking, honestly. I don't have instrumentation on which sync number the frustration actually hits at — right now the wall is just "you've used your 3," not tied to any observed behavior. Don't have a clean way to detect that moment yet without adding tracking I'm not willing to add (no telemetry is a hard line for this project). But it reframes what I should be watching for once the free-tier number changes: not just "did conversion go up" but "did anyone come back and use it heavily right up to the new limit" — that pattern would be the closest proxy I can get to what you're describing without instrumenting anything.

            1. 2

              I think that's a sensible proxy.

              The only thing I'd be careful about is assuming heavy usage always means the limit arrived at the right moment. Sometimes it only means the product became part of someone's workflow before they decided whether it was worth paying for.

              I'd be interested to see whether those two patterns separate as you gather more evidence.

    2. 1

      This comment was deleted 20 hours ago.

  24. 2

    The 0.3% conversion on 641 downloads points most strongly to your option (b) — positioning at the moment of free-tier exhaustion. That moment is your entire sales pitch and most tools blow it with a generic 'upgrade to unlock more' wall. The people who hit the 3-use limit and don't pay aren't saying the product is bad. They're saying the value isn't clear enough at that exact moment to justify spending money. What happens right now when someone hits their limit? Is there a message that articulates specifically what they're losing, or is it just a paywall? Changing that one screen has moved conversion numbers more for me than any other single change.

    1. 1

      This is a sharp read and I think you're right. I went back and looked at what the free-tier-exhausted screen actually says across all 7 plugins, and it's the generic version of exactly what you're describing: "Free limit reached" + a short explanation + a "Get Pro license" button. It never tells the person what they specifically just lost access to.

      Concretely, for a synthesis plugin that means the screen could say something like "3 more articles are waiting to be synthesized" instead of a flat limit notice — the cost of not upgrading becomes a specific, visible thing instead of an abstract wall. I hadn't separated "the limit exists" from "how the limit is communicated" as two different problems until you framed it this way — I'd been treating low conversion as a category problem (backlog vs. own-archive tools) and hadn't isolated the paywall-copy variable at all.

      I'll try rewriting that screen with capsule-specific language and see if it moves anything. Appreciate you laying out the reasoning instead of just dropping a conclusion.

  25. 1

    One thing to watch as you test the new free tier: at 641 downloads and 2 sales, no experiment you run will clear noise for months. The only statistically honest move at this volume is qualitative, so those two buyer interviews matter more than any knob you turn. I see this constantly in early portfolio companies: founders A/B testing at sample sizes where a coin flip explains the result.

Trending on Indie Hackers
5 days post-launch: Top 50 on Product Hunt, zero signups, and why I think that's actually fine User Avatar 135 comments The feature you're most sure about is the one you should question first User Avatar 122 comments I built an AI fitness coach, then realized AI was only solving half my funnel User Avatar 71 comments I let 3 LLMs argue on the famous AI "Car wash: Walk or Drive" problem to prove a point. User Avatar 50 comments I built a macOS app to make mobile E2E testing less awful User Avatar 46 comments