Documenting my builder journey
Starting tomorrow, I’ll be documenting my daily journey of building Pravix (https://joinpravix.com/) and working in analytics consulting here.
The idea of sharing publicly has always sounded cool, but I never really followed through on it. Until now.
I’m genuinely excited about what I’ll learn along the way, and the people I might meet.
Maybe I’ll be stuck on something, and someone out there has the answer.
Or maybe someone finds my lessons and struggles relatable.
Either way, it’s going to be a ride. And I think a fun one.
Trending on Indie Hackers
Good timing on this - the analytics consulting + building combo is an interesting angle. Consulting gives you steady cash flow while you ship, and you probably see patterns in client work that inform what to build.
Curious what Pravix actually does? The landing page mentions "decisions" but I didn't quite grok what problem it solves. Is it dashboarding, data pipelines, something else?
Also - are you planning daily posts here or somewhere like Twitter? I find the format matters a lot. Short daily tweets work, but longer weekly IH posts seem to get more engagement from what I've seen.
Thank you so much. I want to put it out there on Twitter and IH. Will be putting the Day 1 here in a bit.
Yea, that's the idea. I've built a good cashflow with consulting. Now, I want to build products, and see how it goes.
Pravix is simply a data alerting tool. One of the most common issues with my clients that I've seen is - an event stops flowing, or there is a spike, or a property stops flowing. And, the team only gets to know weeks later when they look at a dashboard, or doing an analysis.
I built Pravix to solve that, so teams are alerted as soon as something is off.
Love this – building in public is such a powerful way to create both accountability and serendipity.
I’m also working solo on a product (in the mental health space), and I’ve had the same resistance to sharing consistently, so this really resonates.
Following along to see how Pravix and your consulting journey evolve.
Do you have a rough structure in mind for your daily updates (one main thread, short recaps, “what I shipped today”, etc.) or are you going to let the format emerge as you go?
Hey, that's amazing. My first product was in the mental health space 3 years back. It didn't work out - so closed it. Would love to know what you're building.
No format in mind. Just going to share naturally how it comes, and then see.
Do you know about executordelta?
Really great to see this kind of builder journey shared — the messy middle between idea and traction is where the actual learning lives. A lot of founders only talk about launches or outcomes, but the real progress happens when you iterate in public and reflect on what worked (and what didn’t).
One subtle pattern I’ve seen in journeys like this is that the chapter where you start noticing user friction patterns — not just features missing, but why people stumble — is often where the product and the positioning start to come together. The early questions become less about “what to build next” and more about “why people do what they do.”
Curious — as you document your journey, is there a moment so far where you realized a core assumption you had before building turned out to be off once real people used it? That kind of insight tends to be the turning point for many founders.