I ve been a long-time lurker, watching how you all build and launch. I m finally stepping out of the shadows because I ve spent the last year obsessed with a specific, expensive gap in how we work. My background isn't traditional tech, it s HR and Operations. I ve spent my career advising executives on how organizations actually run.
Tomorrow we're launching Naoma an AI demo agent that runs live, personalized product demos on your website, 24/7.
Some of you might remember us. Our previous product a sales analytics platform hit #2 Product of the Day. We're grateful for that. But since then, we pivoted hard.
A buyer lands on your site, hits "Book a Demo," gets a Calendly link for 5 days out. By the time the call happens, they've looked at two competitors and half-forgotten why they filled out the form.
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?
On Product Hunt, I can see many people launching their products using "vibe-coding tools" like @Lovable , @bolt.new , or@Replit
I reckon many people who created something with them are usually developers who didn't have enough time for building a side idea before, but with AI, they could make it happen.
