I launched my project about three weeks ago! I have ten paying customers and one huge government website that needs private statistics! I found clients through personal communication, but I know I need to go online and give more people a benefit!
There were a lot of bad messages, a lot of bot traffic to my website (which showed incorrect statistics) — and this is very important to me, because we are growing and I need to be sure that everything is working well and correctly!
But even with this, we are getting through it (every day) — we have created a feature for all clients, even for the free plan, called “Exclude regular bot tracking.”
We don't do anything bad to anyone, only good – we solve problems related to private and confidential analytics!
P.S. – Let's be kinder this year and help each other, and even if you don't like or have any grievances about the new project, don't do anything bad and certainly don't let the project fail!
Congratulations on the launch Serghei! It's tough dealing with bots and negative messages, but it's clear you found solutions and are handling it well.
Thanks for understanding!
Launching a SaaS always attracts noise along with users especially bots. It’s good to see you addressing this early with bot-exclusion at all plan levels, particularly given the sensitivity of private and government analytics. Staying focused on data accuracy, security, and transparency is the right approach as you scale. Keep building and iterating this is part of the process.
Thanks for your comment!
The combination of initial traction with bot noise is a source of stress that I know personally. ~
Through personal experience, I learned that the spikes of bad traffic often occur at the same time you are starting to gain some traction. It can be frustrating, but it also represents a form of momentum.
How are you currently differentiating between “real weird users” and actual bots?
Totally agree. Coming from a cybersecurity/audit background, I often see Indie Hackers treating security as an "afterthought" or something to fix later. But "later" is often too late when user data is involved.
Good on you for highlighting the risk. Digital hygiene is foundational, even for MVPs.
Thanks for the answer!