Ilytics is minimal real-time analytics and link tracking built for clarity. It gives you clean, actionable insights without dashboards full of noise or extra complexity. Handle 300,000–500,000 events per month, run everything on your own custom domains, and stay fully GDPR compliant by design. Simple to set up, privacy-focused from the start, and priced at $29/month so you can focus on understanding your traffic and links instead of fighting the tool.
I’ve been building my little B2B SaaS for about 14 months now. Bootstrap, solo founder, nights and weekends until I went full-time six months ago. We’re at ~$4.2k MRR, nothing crazy, but enough that every churned customer stings.
For the longest time I was flying completely blind on why people left.
I’d stare at Stripe, Mixpanel, a messy Google Sheet of “notes from support tickets,” and the occasional angry email. I’d invent stories: “They didn’t get the value.” “Onboarding is too long.” “Price is too high.” Half the time I was just projecting my own insecurities onto the data.
I tried the usual suspects. Built custom dashboards that took days. Paid for tools that felt like they were designed for companies with data teams. Ended up with prettier charts and the same confusion.
Then one random Tuesday I was complaining about it in a Discord and someone casually mentioned they’d been using ilytics.dev for their own product analytics. Not in a “check out my tool” way — more like “this is the only thing that didn’t make me want to throw my laptop.”
I signed up out of pure frustration.
What surprised me was how little setup it needed. I connected the sources I already had, and within a day I could ask plain-English questions about my actual users instead of wrestling with event definitions and funnels that never quite matched reality. Stuff like:
Which features do the people who stay past day 14 actually use in their first session?
What’s different about the accounts that upgrade vs the ones that ghost after the trial?
Where do the “silent churners” (the ones who never open a support ticket) drop off compared to the vocal ones?
It wasn’t magic. It just made the patterns visible without me having to become a part-time data engineer.
One concrete thing that changed: I discovered a specific workflow that almost every retained user completed in the first 48 hours… and almost none of the churned ones did. I’d been burying that step under three other “important” features. We simplified the path, added a gentle nudge, and the 30-day retention for new signups jumped noticeably over the next six weeks. Not overnight hockey-stick stuff, but the first time the numbers moved in a way that felt causal instead of random.
I’m still a small team of one. I still have bad weeks. But I no longer wake up and immediately open five different tabs trying to reverse-engineer why last month’s cohort behaved the way it did. That alone has been worth it.
If you’re in that same fog of “I have data but no clarity,” it might be worth a look. Just sharing what finally helped me stop guessing.
Curious if anyone else has had a similar “wait, the answer was sitting in the data the whole time” moment.