While building Ortrace, I spent a lot of time talking with PMs, engineers, and startup teams about how they understand what users are struggling with.
One thing kept coming up: feedback exists everywhere support tickets, Slack threads, community posts, session recordings, emails. Each signal is small, but together they often reveal the real problems users face.
Hi guys,
Really excited to finally share Ortrace with the Product Hunt community.
At my workplace, navigating user feedback is honestly a huge pain. Each customer has multiple internal and external Slack channels, and when a bug or issue comes up it usually goes back and forth between adoption pod members, the customer, PMs, and engineers just to understand what actually happened. Sometimes that alone can take days before a clear ticket even exists.
What I kept noticing is that the problem isn’t a lack of feedback, it’s that the signals are scattered everywhere, Slack, emails, support tickets, session recordings, community posts.
That’s what led us to start building Ortrace. The goal is simple, bring these signals together and turn them into clear, actionable insights so teams can quickly understand what users are struggling with and decide what to fix or build next.
This is still an early version, so I’d genuinely love to hear how others here currently handle user feedback and bug reports. Any feedback would mean a lot 🙏