I can see website visits and signups. But what happened in between?
Hey Indie Hackers 👋
I’ve been building a small analytics tool called Pulse (Pulsytics).
The idea came from a question I kept running into while working on my own products:
Getting traffic is one thing. Understanding what those visitors actually do before converting is another.
Someone discovers your SaaS through Google, reads a blog post, visits your pricing page, and eventually signs up.
But which part of that journey actually matters? And what happens to visitors who never reach that final step?
I wanted a simpler way to connect those dots without jumping between multiple analytics reports.
So I built Pulse.
It brings together visitor journeys, conversion goals, traffic attribution, live website activity, and optional Jev-assisted analysis. You can also connect GA4 to bring in historical analytics data.
It’s currently in beta, and I’m looking for a few SaaS founders who have a real website with some existing traffic.
I’d love to work with 3–5 founders, help them get set up, and see whether Pulse actually helps them understand something they couldn’t see before.
No need to give me a list of feature requests. I’m more interested in what you expected to learn, whether you found it, and what got in your way.
If you’re interested, you can check it out here:
And I’m curious: What analytics tool are you currently using, and what’s one question it still doesn’t answer for you?
Interesting take. Would you still recommend this approach to someone starting today?
Yes, but I’d start simple. Track your key conversions first, then look at the journeys behind them. You don’t need massive traffic to learn from a few real users, but you do need to turn those insights into decisions.
The tension worth resolving early is that journey analytics needs volume to be legible, and the founders yo
Fair point. Even with low traffic, understanding a few real visitor journeys can reveal useful patterns, but finding where it becomes genuinely valuable is exactly what I’m hoping to validate in bet
For the beta founders, what would count as meaningful validation: discovering an unseen conversion bottleneck, changing a decision, or repeatedly returning to answer questions existing analytics can't?
All three matter, but I’d consider repeated usage the strongest signal. If founders discover something they couldn’t see before, act on it, and come back to Pulse for their next question, that’s meaningful validation for me. I’m more interested in that than signups or dashboard visits alone.
This is the kind of thing worth digging into a bit more. Could take it over email sometime — mine’s hello@beryxa.com.