The first is firstusers.tech, a place where early-stage startups can get their first users and where early adopters can discover new products before they launch.
The second is usercompass.tech, a lightweight feedback tool that integrates with FirstUsers. It gives you a public feedback board, anonymous submissions, a simple kanban workflow, and a public roadmap. It’s meant for founders who want something minimal but functional to collect and organize feedback.
I’m curious how others handle this:
Where do you collect feedback?
How do you prioritize it?
Do you use public roadmaps or keep everything internal?
Would love to learn how different teams approach this.
links:
https://www.firstusers.tech/
https://www.usercompass.tech/
jjcob•36m ago
Using every possible channel. Feedback button in the app, email, Github issues, ... I make it as easy as possible for people to tell me what they want.
> How do you prioritize it?
When multiple people independently request the same thing I start working on it.
> Do you use public roadmaps or keep everything internal?
I think public roadmaps are stupid because I never know how much effort something is ahead of time. It often happens that I realise after starting a project that it is way harder than I thought. I also often realise after some time has passed that something I thought was useful is actually not necessary and I remove it from the roadmap. I don't want people to buy my product expecting feature X and then I strike it.