The data was everywhere. The insight wasn’t.
Hey, I’m John.
Software engineer building Metricsjar
I’ve worked as a software engineer on Insight Timer and Clove—apps used by millions of people every month. Every team ran into the same problem: the data was there, but the insight was hard to reach.
Product events lived in one tool, revenue in another, and store data somewhere else. The few people who knew how to pull it together became a queue for everyone else. By the time a teammate got an answer, the product decision had often already been made.
I built Metricsjar to change that. Anyone on the team should be able to find the insight they need to improve the app.
This isn’t just my problem.
Product and analytics teams describe the same gap again and again: plenty of tracking, plenty of dashboards, and no easy path from a question to a decision.
“You have all the data in the world but zero actionable insights.”
Month six: “Can someone pull the numbers on X?” in Slack because nobody trusts the dashboards anymore.
“Today, most business users don’t actually want another dashboard. They want an answer.”
I built it for myself first.
The stack behind Metricsjar is what I used to grow glp3.wiki to more than 10,000 monthly active users.
It helped me see where people were getting stuck, where the bottleneck had moved, and what was worth improving next. I didn’t need more charts. I needed the right evidence while I was making the decision.
Metricsjar turns that working setup into something other teams can use without rebuilding the plumbing themselves.
Small dashboard. Clear answers.
Connect it once
Create a private dashboard, connect each source from Data health, and let hosted schedules keep it current.
One dashboard for the numbers that matter
Rankings, traffic, downloads, revenue, retention, and product events land in one private view you can check from your phone.
Know where every number comes from
Setup checks and source calculations should be readable, inspectable, and easy to question.
The dashboard stays small
Keep the stable numbers worth glancing at, with their source and freshness visible beside them.
If this sounds familiar, I’d like to hear from you.
Tell me where your team gets stuck, or connect a project and see what your own agent can surface.