2
3 Comments

Built a small tool to deal with bot traffic across my sites

Bots and I kept seeing a lot of them hitting my sites, so I put together a quick script to deal with it. That slowly turned into a small SaaS.

I set it up on BlockABot.com.

It’s a lightweight script you add to your site. It watches behavior and flags or blocks things that don’t look human.

Nothing fancy on the surface, but the results have been pretty interesting so far, especially across multiple sites.

If anyone has dealt with similar issues and wants to check it out, I’d really appreciate the feedback.

I’ll probably offer a discounted plan for early users once billing is fully set up.

If you’ve run into scraping or odd traffic patterns, I’d be curious what’s worked for you.

https://blockabot.com

posted to Icon for group Building in Public
Building in Public
on March 28, 2026
  1. 1

    You've got a real problem solved (bot traffic across multiple sites). That part is solid.
    But your pitch is working against you, not for you.
    Look at what you said: "Nothing fancy on the surface." "Lightweight script." "Small tool." "I'd really appreciate feedback."
    You just talked yourself out of a sale before anyone even clicked.
    Here's what you don't realize: A prospect who lands on BlockABot is already aware they have a bot problem. They don't need you to convince them the problem exists. They need you to convince them you've solved it and it's worth their time to implement.
    Instead, you're apologizing for your product. You're downplaying it. You're using language that says "this isn't a serious solution."
    The people who should be your customers (site owners losing traffic and revenue to bot scraping) are reading this and thinking "this doesn't sound robust enough." But it's not because your product isn't robust. It's because you're not positioning it like it is.
    You mentioned results have been "pretty interesting" across multiple sites. That's the entire story. But you buried it and wrapped it in apologies.
    Here's the uncomfortable part: You're probably filtering out exactly the kinds of customers who would pay because your messaging makes it sound like a side project, not a solution.
    Site owners dealing with real scraping losses aren't looking for "lightweight" and "nothing fancy." They're looking for "stops the bleeding." They're looking for certainty. They're looking for proof it works.
    You have proof (results across multiple sites). You're just not saying it like you believe in it.
    The founders who are winning right now? They're not apologizing for what they built. They're saying exactly what changes when someone uses them—and they sound like they mean it.
    That shift in positioning changes everything. But you have to see the gap first.

    1. 1

      Appreciate the honest feedback. That actually helped I see what you mean about how I’m positioning it.

Trending on Indie Hackers
Never hire an SEO Agency for your Saas Startup User Avatar 100 comments I shipped a productivity SaaS in 30 days as a solo dev — here's what AI actually changed (and what it didn't) User Avatar 76 comments A simple way to keep AI automations from making bad decisions User Avatar 67 comments “This contract looked normal - but could cost millions” User Avatar 54 comments 👉 The most expensive contract mistakes don’t feel risky User Avatar 41 comments Are indie makers actually bad customers? User Avatar 36 comments