We re all builders here, which usually means at some point we looked at something clunky, slow, or frustrating and thought, there has to be a better way. Most products don t start with a grand vision; they start with irritation, curiosity, or firsthand pain.
I d love to learn more about how others here have navigated that journey:
How did you uncover the problem you decided to work on? What signals told you this problem was worth solving? How did you validate (if at all) whether people would actually pay for a solution? Has your product stayed true to the original problem, or did it evolve into something different? What surprised you the most along the way?
I m Badar. I m currently building an early-stage AI coaching / thinking-partner app called Thimin.
Right now it s very raw, the core experience is simply talking to an AI, thinking out loud, and seeing where it genuinely helps (or doesn t). I m spending a lot of time testing, talking to users, and trying to understand what actually creates a wow moment before adding more features.
I m here mainly to learn, share what I m discovering, and get better at building something people truly find valuable. Looking forward to engaging and learning from you all!
I m currently building an early-stage AI voice-based coaching app called Thimin. It s very much a work in progress, and at this stage we re not selling anything, we re purely focused on learning.
The idea is simple: give people a non-judgmental AI thinking partner they can talk to freely about their goals, challenges, and decisions. Over time, those conversations are meant to turn into personalized insights and structured growth plans, based on what the user actually shares , not generic advice.
Right now, the app only supports voice-to-voice conversations with transcripts, and that s intentional. We want to first understand whether the core experience (talking to Themin) feels useful, natural, and worth coming back to.
