Public roadmap and feedback board
Turn it on and you get a Canny-style board: anyone can submit a request and upvote without an account, you move items across roadmap columns, and you publish a changelog of what shipped. The board is the public-facing part of Usero, separate from the AI that opens your pull requests.
Telling users "we hear you" with no public place to prove it is how a roadmap turns into a black box. They ask twice, get no reply, and assume the request died, because nothing shows them otherwise.
Most teams keep their roadmap in a private tool and a Slack thread, so a user who asks for something has no way to see it was logged, no way to see anyone else wants it, and no way to learn when it ships. So the same request arrives five times, support re-answers it five times, and the user who asked first never finds out it is now live. The polished tools that solve this (Canny is the reference) dropped their free tier years ago and start near 79 dollars a month, which is a lot for a board you mostly want to stop re-answering the same question. What you want is plain: a page users can reach, post on, and vote on, that shows them the request is real, where it sits on the roadmap, and what already shipped.
How it works
Disclosure: I build Usero, so weigh that, and let me be clear about what this is and is not. The board is the standalone, Canny-style part of Usero. You enable it in the project settings, Usero gives you a public board at usero.io/b/<slug>, and on a Pro or Team plan you can point your own domain at it. Anyone can submit a request and upvote it with no account (votes are deduped per browser), comment on a thread, and your team can post an official reply that is marked as the team. You run the board by moving each post through statuses you control: the defaults are Open, Under Review, Planned, In Progress, Complete, and Closed, and the three you flag as roadmap (Planned, In Progress, Complete) render as the public /roadmap columns. A separate changelog at /changelog is where you announce what shipped. One honest limit: the board does not feed the AI-PR pipeline. A voted-up board post is not the thing that becomes a pull request today. The PR side of Usero runs off feedback from the widget, Slack, forms, GitHub issues, and the API, which cluster and can open a PR. The board and the PR engine live in the same product but are not wired together yet. If you want the board, use it as a board.
A visitor reaches usero.io/b/<slug>, posts a request with a title and description, and upvotes anything already there, all without signing up. Votes are deduped per browser, so the count reflects distinct people rather than one person clicking ten times. The lower the bar to vote, the more honest the count, which is the whole reason a public board beats a private list.
You move each post through statuses you define. Flag a status as a roadmap column and it shows up on the public /roadmap view, so the defaults Planned, In Progress, and Complete become the three columns a user reads to see where their request sits. They stop asking "is this happening" because the answer is on the page.
Each post has a comment thread anyone can join, and a reply from your team is marked as official so it stands out from the crowd. That is how you answer "why not" once, in public, instead of re-typing it into five support tickets.
Publish what shipped to a /changelog on the same board. A user who voted for something gets a public record that it is done, which is the payoff that makes them vote next time. The changelog is authored by you, it is not auto-generated from posts you mark complete.
The honest objection
That critique is real and I have written about it. Most users never post on a feedback board, so a board read on its own over-weights the vocal minority and the people angry enough to type. The honest answer is that the board is one input, not your whole signal. Treat the vote count as a tiebreaker among things you already suspect, not as your roadmap, and get the quiet majority from the channels they actually use: the widget mid-task, support, session replays, and reaching out to ten users directly. In Usero the board is deliberately separate from the feedback that clusters and opens PRs, so it is the public face of your roadmap, not the source of truth for what to build. If you want a board purely to stop re-answering the same question and to show users their request is logged, it is a good fit. If you are hoping it tells you what to build, read it with that bias in mind.
FAQ
No. Anyone who reaches usero.io/b/<slug> can submit a request, upvote existing posts, and comment, all without signing up. Votes are deduped per browser so one person cannot inflate a count, and a request can include an optional email if the submitter wants a reply.
You move each post through statuses you control. The defaults are Open, Under Review, Planned, In Progress, Complete, and Closed. The statuses you flag as roadmap (Planned, In Progress, and Complete by default) appear as columns on the public /roadmap view, so users can see where a request sits. You can add, rename, or delete statuses.
Yes, on the Pro and Team plans. By default the board lives at usero.io/b/<slug>; the paid tiers let you point a custom domain at it. The free board uses the usero.io URL. Confirm current plan details on the pricing page, these can change.
No, not today. The board is the standalone public-facing part of Usero and is not wired into the AI-PR pipeline. The PR side runs off feedback from the widget, Slack, forms, GitHub issues, and the API, which cluster and can open a pull request. A board post is not that input yet, so use the board as a board.
You write it. The changelog at /changelog on your board is authored by your team to announce what shipped (a feature, an improvement, a fix, or an announcement). Marking a post Complete does not automatically create a changelog entry; the two are separate so you control exactly what gets announced.
Free tier. No credit card. Two-minute install. The AI opens the PR, you merge it.
Keep reading