i built a tool i actually use myself
i kept running into the same problem with pullnotifier - users would ask for features in support tickets, emails, random dms, and i had no idea what to actually prioritise.
so i built featuresvote. it gives your users a place to submit ideas and vote on what matters most. you get a public roadmap, and when something ships, voters get notified automatically.
i use it inside pullnotifier and it's genuinely changed how i decide what to build. instead of guessing, i just look at the votes.
over 1,000 businesses are using it now which is still kind of surreal to me.
if you're a founder drowning in feature requests with no system to manage them, check it out - features.vote
happy to answer any questions 👋 :)
Interesting tool. Thanks for sharing.
This is actually a very real problem. A lot of founders end up building based on noise instead of signal. Having structured feedback like this makes decision-making so much clearer.
Hello Gabriel, this sound like a great idea i'll check it out
the "drowning in feature requests" part hit hard. i've been collecting user feedback across support emails, twitter dms, and random app store reviews like some kind of chaotic archaeologist. no system, just vibes and guilt.
the "i built it for myself first" origin story is always the most believable one. you can tell the difference between a tool someone actually needed and one someone thought the market needed.
curious - how do you handle the gap between what users vote for and what you know is actually the right thing to build? sometimes the most-voted feature isn't the highest-leverage one. do you override the votes or does the ranking usually align with your own intuition?
Interesting, looks clean with just the most important features.
If I were you, I'd keep it thin like how it is. IMO too many features make the product onboarding really difficult. Hope I grow to use this product in near future :)