Upvoted: a feature request board your users actually use
Collect feature requests in public, let people vote, and publish the roadmap and changelog that follow from it. The queue stops being a mystery and starts being evidence.
- Boards your users actually use
- Votes, statuses, and a changelog
- A roadmap driven by real demand
Every product accumulates a shadow backlog: the feature someone asked for in a support chat, the idea buried in a reply to a newsletter, the thing three customers mentioned on calls that nobody wrote down. It is real demand, and it is scattered across places where it cannot be counted.
Upvoted gives that demand one address. Users post ideas on a public board, other users vote on them, and what rises to the top is a ranked list of what your customers actually want, not what the most persistent emailer wants. You move items through statuses as you work, and each change is visible to the people who asked.
It is the listening half of the Releasy Suite. Hookfire tells you what your product just did; Upvoted tells you what to build next.
What a board gives you
A feature request board is not a suggestion box. Done properly it is three things at once: a queue, a vote count, and a communication channel back to the people who care most.
Requests in one place
Anyone can post an idea, and duplicates get merged into the original so the vote count stays honest. Instead of the same request arriving five times through five channels, it arrives once with five votes attached.
Votes that mean something
Votes are attached to real accounts, so the ranking reflects distinct people rather than enthusiasm. You can see who voted for what, which turns a shipped feature into a list of customers to tell about it.
Statuses and a public roadmap
Move items to Planned, In Progress or Shipped and the board doubles as a roadmap. Users stop asking when something is coming because the answer is on the page they already read.
A changelog that writes itself
Every item you mark Shipped becomes a changelog entry, and the people who voted for it hear about it. Shipping stops being invisible work.
Built to be used, not just installed
Most feedback boards fail the same way: they get set up, linked from the footer, and then nobody posts. The fixes are unglamorous and they are the difference between a board and an empty room.
Embed it where people already are
Drop the widget into your app so requests are made in the moment of frustration, not remembered later. The board that lives inside the product gets an order of magnitude more posts than the one that lives on a subdomain.
Low friction to post
Posting takes a title and a sentence. Voting takes one click. Every extra required field is a percentage of your users who close the tab instead.
Answer in public
Replying on the item, including saying no with a reason, is the single strongest signal that the board is read. A board with visible owner replies keeps filling; a board without them dies in a month.
How teams use it
The same board serves product, support and marketing, which is most of why it is worth having one rather than a spreadsheet.
Prioritisation with evidence
When two features compete for the same sprint, vote counts and the identity of the voters make the argument concrete. It is much easier to defer something when you can see it has four votes and the alternative has forty.
Support deflection
Half of support tickets that begin “does it do X” end with a link to a board item and a status. That is a conversation that used to take three emails.
A reason to come back
Users who vote get told when their item ships. That is a re-engagement email you did not have to invent a pretext for.
Who Upvoted is for
- SaaS products
- Run the public roadmap your customers keep asking for, and stop maintaining it by hand.
- Open source projects
- Give the feature-request pile a home that is not the issue tracker, and let votes do the triage.
- Internal tools
- A private board for colleagues works exactly the same way, and settles the same arguments.
- Early-stage products
- When you have fifty users, the board is the fastest way to find out which of them want the same thing.
Upvoted comes with two more tools
is one subscription covering all three apps, on one login and one bill. Buy it inside any of them and the other two unlock on the same account.
Upvoted FAQ
What is Upvoted?
Upvoted is a feature request and feedback board. Your users post ideas, vote on each other's, and follow items through statuses like Planned, In Progress and Shipped. It doubles as your public roadmap and changelog.
Can I embed the feature request board in my own app?
Yes. Upvoted provides an embeddable widget so users can post and vote without leaving your product, which is where the large majority of real feedback comes from.
Do users need an account to vote?
Votes are tied to identified users so the ranking counts distinct people rather than clicks. That also means you know who to notify when their request ships.
Can I keep a board private?
Yes. Boards can be public for customers or private for a team, using the same voting, status and changelog mechanics.
How is Upvoted different from Canny or Nolt?
The mechanics are familiar: board, votes, statuses, changelog. The difference is that Upvoted comes with Hookfire and Indie Polls on one login and one bill at $29.90 a month, so feedback, alerts and surveys are not three separate subscriptions.
How much does Upvoted cost?
Upvoted is included in the Releasy Suite at $29.90 a month, alongside Hookfire and Indie Polls, and starts with a 7-day free trial.
Get Upvoted with the whole suite
$29.90 a month for Hookfire, Upvoted and Indie Polls. 7-day free trial, no card, cancel anytime.