I'm Talha, a solo developer from Pakistan. Four months ago I got tired of every "free" online tool site being covered in ads, popups, and forced signups just to compress an image or merge a PDF. So I built my own.
This is the real story, what worked, what didn't, and where things stand right now, numbers included.
DukoTools 104 free tools across PDF, image, developer utilities, finance, text, and a few niches nobody else covers: a Zakat calculator, Pakistani electricity bill (WAPDA) calculator, CNIC validator, cricket run-rate calculator, and construction estimating tools.
No ads. No signup. Most tools run entirely client-side in your browser, nothing gets uploaded to a server unless the tool genuinely needs backend processing (PDF conversion, video downloading, a couple of image tools).
Stack: Next.js frontend on Vercel, FastAPI backend on Railway, 5 languages (English, Spanish, Arabic, French, Urdu).
This is the part most build-in-public posts gloss over, so I'll just say it plainly:
Reddit banned my account. I posted twice, promotionally, from a 2-year-old account that had zero karma. Didn't matter that the account was old, zero karma plus a promotional link reads exactly like a bought/hacked account to Reddit's spam detection, and it got flagged.
Then I made almost the identical mistake on Quora. New account, and I spent a day answering a bunch of genuinely helpful questions, PDF conversion, OCR, Zakat calculations, mentioning my site naturally where it was relevant. Every individual answer was solid. But answering too many similar-topic questions in one day, each pointing at the same domain, read as a spam pattern to their automated detection anyway. Banned. Same root cause as Reddit, different platform: volume and repetition trigger these systems regardless of how genuinely useful the content is.
I killed a tool because of cost, and it cost me more than I saved. My background remover was burning through backend compute faster than expected, so I pulled it from the frontend without setting up a redirect. What I didn't realize until users started dropping: that tool was specifically called out in my Product Hunt launch post as a differentiator. Anyone landing on that old URL just hit a 404 and bounced.
The pattern across both banned accounts is the same lesson, twice: trust has to be built before promotion, not alongside it, regardless of how good the individual content is.
No polished conclusion here, I'm genuinely still learning as I go. If anyone's navigated the "genuinely helpful content still gets flagged as spam" problem on Reddit or Quora specifically, or has thoughts on when it's actually worth turning on AdSense versus waiting for more traffic, I'd like to hear it.
Site's here if you want to poke around: dukotools.com
@talharamzan That's the right move on the measurement gap. Session count sounds like an answer but it isn't one. Return rate per tool, time-to-second-session, same-tool repeat visits — those are what tell you whether you built something useful or just something findable. One thing: don't wait for perfect GA4 before narrowing the subreddit strategy. Set up the measurement and narrow them in parallel. The breadth problem has a faster feedback loop than the tool engagement problem.
Good push, and you're right that I was treating these as sequential when they don't need to be. GA4 setup and narrowing Reddit have completely different feedback loops, one takes weeks to accumulate meaningful data, the other I could act on this week just by picking 2-3 subreddits and stopping the breadth experiment.
No real reason I was waiting on one to inform the other, honestly. I think I was mentally bundling "fix the measurement" and "fix the strategy" into one project because they came from the same realization, but they don't share a dependency at all.
Starting the subreddit narrowing now instead of after GA4 lands.
Incredible output building 104 tools solo!
The lesson about generic vs. niche utility tools is so true. Generic tools like PDF converters drive one-off search traffic, but specialized calculators (like your local ones or a freelance vs. salary rate calculator) solve high-intent, recurring problems that actually bring users back.
Since client-side execution keeps costs low, are you planning to double down on building more financial/calculator tools, or strictly focusing on optimizing the top performers you already have?
Appreciate that, and the generic-vs-niche distinction is exactly the thing I don't have hard data on yet, just a hunch based on which tools got called out specifically in earlier launch posts (Zakat calculator, CNIC validator) versus the ones that got zero individual mentions despite probably having more raw traffic (PDF/image converters).
Honest answer: I'm leaning toward optimizing what exists rather than building more calculators blind, at least for the next few weeks. I just realized my metadata setup serves the same English title/description across all 5 language versions of every tool page — meaning the localized pages probably aren't actually discoverable in Spanish/Arabic/French/Urdu search the way they should be. Fixing that for the niche tools specifically (Zakat, WAPDA, CNIC, the ones with an actual non-English audience) feels like higher leverage than adding tool #105 right now.
If that data ends up confirming the returning-user pattern you're describing, more financial/regional calculators is the obvious next move. Just want the evidence before committing engineering time to guessing.
Thanks for a great post. Sometimes I think building the tool is the easiest part of the whole thing. Building that trust, making mistakes, trying to discern what's real vs what's just hype reaction, etc., is where the real lessons are learned about what it takes to market and sell digital products. You're definitely not alone in making those mistakes; every single one you listed, I've done in some form or another. One of the downsides of working as a boostrapping founder is the question of "is it just me having all these problems? Am I just a moron for not having seen this in advance? Or does everyone go through learning curve challenges, growing pains, and morning-after regrets like I have?" It's posts like these that give us mere mortals the courage to pick up the pieces and keep trying, because yup, everyone experiences stuff like this. Thanks for the transparency.
104 tools in 4 months is seriously impressive. 👏
What stood out to me most was the lesson about promotion vs. trust. I’ve been experimenting with different communities for my own SaaS, and I’m realizing that simply putting a product in front of people is very different from actually becoming part of the community first.
The 76 to 26 drop isn't failure, it's the actual baseline coming through after launch noise. 76 was a spike. 26 is closer to your real starting number. The question is what those 26 are actually doing on the site.
On Reddit: your instinct to go link-free for 3-4 weeks is right, but I'd add one thing. Pick two or three subreddits where your niche tools specifically belong (r/islam for the Zakat calc, r/Cricket, r/pakistan) and participate genuinely there before you ever touch broader subreddits. The spam filters aren't just counting links, they're detecting off-topic breadth. A focused new account in one community looks completely different from a "promotional tour" hitting 10 subreddits. Which of the niche tools is driving the most organic return visits so far?
That reframe on subreddit breadth is a good catch, and honestly the opposite of what I'd been doing, I joined a mix of general (AskReddit, TIL) plus niche ones, thinking "real activity across varied topics" would look more natural. Your point about breadth itself being a signal, not just link count, makes me want to narrow that back down.
Answering your last question is actually where I have to be honest: I don't know yet, because I haven't set up GA4 key events to distinguish "visited a tool page" from "actually used it and would come back." Right now I only have raw session counts, not per-tool return behavior. That gap is exactly why I can't confidently answer which niche tool is pulling its weight versus which one just sounds good in a pitch.
So: fixing that measurement gap moved up my list after this comment. Once it's in, I'll actually have an answer instead of a guess.
The background-remover incident suggests you may need a deletion checklist as much as a build roadmap now that you have 104 tools.
Before removing any public tool, I’d capture four things:
traffic landing directly on that URL, external referrers/backlinks, successful uses versus compute cost, and whether there is a reasonable replacement.
Then I’d avoid deleting the route immediately.
For a tool that is too expensive but still receives traffic, you could first mark it deprecated, keep the URL alive with a short explanation and the closest alternative, and measure how much real demand still arrives for 30 days.
That separates “this feature costs too much” from “nobody values this feature.”
It also gives you better evidence for pruning the other 103 tools. Some may deserve deletion, some may deserve a cheaper implementation, and some may be surprisingly important acquisition pages even if direct usage is low.
With a catalog this large, I suspect disciplined removal will eventually save you as much time as disciplined building.
This is the framework I needed before I pulled background-remover, not after. The four things you listed, direct traffic, backlinks, usage-vs-cost, and replacement availability, would've told me in five minutes that it was mentioned in a launch post before I killed it, instead of finding out after users started dropping and traced back to a 404.
The deprecate-instead-of-delete approach is the piece I'm actually going to implement now. A "this tool is paused, here's the closest alternative" page costs nothing to serve and gives me real signal instead of a guess. I set up a plain redirect after the fact, but a deprecation notice with a 30-day observation window is a better version of that, it tells me something instead of just quietly rerouting traffic away.
"Disciplined removal will eventually save as much time as disciplined building" is a good line to sit with at 104 tools. I've been thinking about this entirely as an addition problem, which tool to build next, and never once as a maintenance/pruning problem, even though the backend cost issue that started this whole thread was exactly that.
Glad the framework helped.
I think the biggest shift is exactly what you described: once the catalog gets large enough, removal becomes its own operating discipline rather than an occasional cleanup task.
A deprecation window gives you a much safer way to prune — keep the acquisition surface alive, observe real demand, then remove, replace, or rebuild based on evidence instead of instinct.
Good luck turning that into a repeatable process across the rest of the catalog.
The 104-tool count may actually be hiding the bigger positioning problem: a visitor has to decide whether DukoTools is an “everything utility site” or a collection of highly specific tools for particular recurring problems. Those are very different reasons to remember a brand. The niche tools have a much clearer “this is exactly for me” signal, while the generic tools risk making the whole product feel interchangeable. I’d be curious whether the homepage is currently asking visitors to understand the breadth first—or helping them immediately recognize the one problem they came to solve.
The "trust before promotion" lesson landing the same way on two different platforms is the tell that it's real, not bad luck. What stands out most is the background remover mistake, that's such a common trap: you cut something for cost reasons without checking what it's actually load-bearing for (a PH listing, an SEO ranking, whatever), and the damage shows up weeks later when you've forgotten you even made the change. That's the kind of thing that's easy to miss when you're solo and juggling 100+ tools. On the GA4 key events point, that's the right call, deciding what to build next off vibes versus actual usage data is the difference between spending a weekend on the right tool and the wrong one. Good luck with the Reddit rebuild, that's a slow, disciplined grind.
Creating 104 tools in just four months is quite a feat, but what really caught my attention was what we learned from the things that didn't work out. ~
You see, after our initial launch, we had a surge of 76 active users, but then it dropped back down to around 26.
This was a good wake-up call, reminding us that getting a lot of users at first and keeping them engaged over time are two very different challenges.
The Reddit and Quora experiences are useful too. It’s easy to think that if the content is genuinely helpful, the platform will treat it that way. In practice, account history, posting patterns, and context matter just as much.
I also like the lesson around infrastructure costs. A small technical decision can become surprisingly expensive once real traffic shows up.
What's really standing out is the traction we're getting on Dev.to - it's looking more promising than the other channels we're using. This makes sense, given that technical content tends to resonate more when it's targeted and specific, rather than trying to push a whole suite of tools all at once. By focusing on the nitty-gritty details, we're likely to see better engagement and interest from our audience.
Talha, this is one of the most honest build-in-public posts I've read on IH. The Reddit and Quora spam detection lesson hits hard I made a similar mistake of posting too much too fast on a new account and got flagged immediately.
Building 104 tools solo in 4 months is genuinely impressive. The niche tools angle is smart Zakat calculator and CNIC validator have almost zero competition, which means easier ranking.
On your AdSense question most makers I've seen recommend waiting until 10K monthly sessions minimum before turning it on. Below that, the revenue is negligible but the UX damage to new visitors is real, especially when you're still trying to build word-of-mouth.
Your Dev to insight about technical deep-dives outperforming promotional posts is something I'm applying to my own tool site right now. Engineering problem posts build genuine trust that 'check out my tool' posts never will.
What's your current average session duration? That might reveal which tools are actually keeping users engaged versus which ones they bounce from immediately.
Good to hear the Reddit/Quora lesson resonated, it's oddly reassuring that this isn't just a "solo dev learning things the hard way" problem, it's apparently common enough that you hit the same wall.
The 10K sessions benchmark is genuinely useful, I had no real number in mind before, just "wait until it feels like enough traffic," which isn't a number at all. Having an actual threshold to work toward changes AdSense from a vague someday into an actual milestone I can track progress against.
Honest answer on session duration: I don't have that data cleanly broken out by tool yet, same gap as the usage-tracking issue a few comments up. Once GA4 key events are in, that's exactly the kind of thing I want to look at, since a tool with high traffic but a 10-second average session is probably just a bounce, not real usage, regardless of how good the raw visit count looks.
Appreciate you finding the Dev.to point useful for your own site too, that one took me two "meta" posts to figure out before the technical deep-dive angle actually worked.
A helpful answer and a product link can still look like a campaign if the same domain keeps showing up. I'd spend a few weeks answering in your target communities without linking at all. Keep DukoTools in your profile, and only mention a specific tool when someone asks for one. Also, slow down and stick to one or two communities so people start to know your name. The boring trust-building route is slower, but it is much less likely to send you back to zero with another ban.
The distribution problem you're hitting isn't really a distribution problem. Reddit bans and Quora flags are the symptom, not the disease.
You built 104 one-off utility tools. A user needs to compress a PDF, finds your site, uses it, leaves, never comes back. Perfect distribution strategy for that is irrelevant - Reddit and Quora can tell you're promoting because you ARE promoting something that only matters on first visit.
The Zakat calculator, WAPDA bill calculator, CNIC validator? Those are different animals. Someone bookmarks those because they need them every month or every quarter. They return to that URL because it solved a real recurring problem. That's why those tools don't trigger spam detection - they're genuinely useful in the context of "people search for this specific thing regularly."
The 76-to-26 drop you're seeing isn't a conversion funnel. It's measurement lag. You don't actually know yet if those 26 are returning to the same tool twice, or if they're 26 different people, each visiting one tool once. GA4 will answer that, but here's the bet I'd make: your niche tools have a 3-week return window around their use case (Ramadan for Zakat, bill-payment time for WAPDA). Your generic tools don't.
Forget distribution strategy. Find which of your 104 tools has people returning within 30 days. That's your moat. Build the next 20 tools in that category instead of trying to make PDFs and image converters the winner.
That reframe is the sharpest thing anyone's said about this whole thread, and it's slightly uncomfortable because it's obviously right in hindsight. I've been treating "why isn't Reddit working" as a platform-mechanics problem when it's actually asking a question about the product itself, a one-off utility has no honest reason to be promoted repeatedly, because nothing about it justifies a second mention any more than it justifies a second visit.
The Ramadan/bill-cycle observation is a genuinely testable hypothesis rather than a vague "niche tools are better" claim, I can actually check whether Zakat calculator traffic clusters around Ramadan and pre-Ramadan weeks specifically, versus WAPDA traffic clustering around bill due dates. If that pattern holds, it's not just "recurring need" in the abstract, it's a predictable calendar I could market against instead of reacting to.
One pushback, though not a disagreement with the core point: I don't think the generic tools become worthless even if they're not the retention moat. A PDF merger with no return visits can still be a legitimate acquisition surface, someone converts a PDF, has a decent experience, and that's what makes them trust clicking into the Zakat calculator on a future unrelated visit. The mistake would be treating PDF tools as the thing to grow, not as the thing to keep functional and quietly supporting the tools that actually deserve investment.
Once GA4 is in, "which of the 104 tools has 30-day returners" is now the single number I'm building toward before deciding anything else. That's a much better first query than anything I had in mind before this thread.
The sheer volume of 104 tools in four months is impressive, but the real play here seems to be your focus on local-specific utilities like the Zakat and WAPDA calculators. Most developers chase generic global tools, but by solving highly specific regional pain points, you've built a defensible moat that a generic PDF converter can't easily replicate. Since you are running these client-side, have you tracked if users are returning to specific pages as recurring utility hubs? It might be worth looking at your logs to see which of those niche tools acts as your primary 'anchor' to bring in organic search traffic versus which ones get one-off usage. Focusing your maintenance and future build efforts on those high-intent categories rather than expanding the total count might offer better long-term compounding.
Same core insight the earlier commenter landed on independently, regional/niche tools as the moat, generic ones as one-off traffic, which makes me trust the pattern more, not less, since two people reading the same post arrived at the identical conclusion without seeing each other's comments.
"Anchor" is a good word for what I'm actually trying to find once GA4 key events are in. Right now I genuinely can't answer this from logs, I have session counts, not per-tool return behaviour, so it's on the list to check rather than something I can report back on yet. Once it's in, the plan is exactly what you're describing: stop counting total tools as progress, and instead find the 2-3 that people treat as a recurring utility versus the ones that get used once and forgotten.
I think your biggest takeaway is bigger than Reddit or Quora. You built 104 tools, but your niche tools are the ones people actually remember. I'd double down on those instead of trying to compete as another "everything tools" site. Distribution matters, but a clear reason to exist matters even more.
The GA4 point stood out — especially after four months of learning mostly from traffic and channel-level signals.
Once you can see actual tool usage, what decision are you most hoping that evidence will let you make with confidence?
The 76 → 26 drop isn't a failure, it's the actual signal. 76 was the launch spike, 26 is the number of people who had a reason to come back. A spike tells you distribution worked; the floor tells you whether a tool earns a repeat visit. Before turning AdSense on, I'd track one number: % of users who return within 7 days to a tool that isn't part of the launch push. One returning loop beats 104 one-off tools.
That reframe is exactly right, and it's uncomfortable in a useful way, I've been treating the drop as a problem to explain rather than a number to actually act on.
The 7-day return metric is the one I don't have right now, and reading your comment made me realize why: I've been tracking raw active-user counts in GA4 but haven't set up key events yet, so I genuinely can't answer "which tools bring people back" versus "which tools got a one-time visitor from a launch post." That's the actual gap, not the drop itself.
Going to set that up before touching AdSense at all. If the honest number is "3 tools have a real returning loop and 103 are one-off utility visits," that changes what I build next far more than the total user count ever would.