The API, and every endpoint it has
Twenty one endpoints, three of them open, the rest behind a key.
Read itA changelog that emails the people who asked for it
Most release note tools broadcast to a subscriber list.
Read itComments, replies, and the one response that is not a comment
Threaded replies, likes, and a developer response that sits apart from the thread.
Read itExport every feature request to CSV
Twelve columns, Weighted Votes among them, on Lite and Pro.
Read itA custom domain for the board and roadmap
feedback.yourapp.com for the roadmap, the voting board and one named board. Pro.
Read itDemand, effort and priority, and the arithmetic that ranks a feature request
Every request carries a demand score, an effort estimate and a priority made of the two.
Read itA feature request board that needs no account to vote
Visitors vote, comment and suggest without signing up.
Read itImport customer revenue onto your board
Three ways to get what each customer pays onto your board, what each one keeps in sync, and why importing revenue does not change a single vote on its own.
Read itSingle sign on with a JWT
Your logged in customers vote under their own name, from a token your server signs. Pro.
Read itThe Most Wanted list
The ten open requests with the most votes, on a page and in a widget.
Read itA public roadmap your visitors can use without an account
Five columns, your own colours and fonts, and a declined column that is visible by default.
Read itWeight feature requests by what the customer pays
A vote from a customer on your top tier can count for more than a vote from a free account.
Read itCustomer feedback, and the voter list behind every count
Every vote has a person behind it.
Read itA feature request tool has eleven moving parts here, and the useful question about each one is not whether it exists but what it costs you and what it refuses to do. This page is one paragraph per part, with the page that goes into it.
Two plans exist. Nine dollars a month buys one project, and thirty nine buys more projects, a team, a custom domain, the API and single sign on. Every paragraph below says which side of that line its part sits on.
What collects the feedback?
Three parts, and the first of them is the reason the other two have anything to work with.
The feature request board. The board itself, where a visitor posts a request and votes on somebody else's without making an account. Asking for a password before an idea is the fastest way to collect fewer of them, and the board is built so nobody has to.
Comments and replies. A vote says somebody agrees and a comment says why, and the why is the half that changes what you build rather than only what order you build it in. The page also names the one response that is not a comment.
The voter list. Every vote has a person behind it, and the list is what turns forty votes into forty people you can put in a tier and tell when something ships. Customer feedback segmentation on this board means that tier and the revenue beside it, and the page says so rather than dressing it up.
All three are on the nine dollar plan.
What decides the order?
Two parts, and they are the ones the category argues about.
Revenue weighted voting. The requests with the most votes are the ones the most people wanted, and the people who pay you are almost never the most people. This is the arithmetic that lets a vote from a paying tier count for more, with the plain headcount still visible beside it.
Demand, effort and priority. Three numbers on every request. Demand is computed from what people did, effort is the one figure you type, and priority is demand divided by effort. The page prints the formula rather than describing it.
Both are on the nine dollar plan. Weighted voting is not a Pro feature here, which is unusual in this category and is the reason it is worth saying twice.
What gets the revenue in?
Import MRR from Stripe, Paddle or a CSV. Weighting a vote by what somebody pays needs you to know what they pay first. Three ways in, and none of them changes anything on your board by itself until you set the tiers.
On the nine dollar plan, imports included.
What goes back out to the customer?
Two parts, and they are the half of VoteFirst most teams underuse.
The public roadmap. A public roadmap is a promise you have to keep, which is why so many quietly stop being updated: half of 621 public boards measured on 3 October 2026 had gone 90 days without a new request. This one is updated by the same action as running the board, which is the only version that survives.
The changelog. Publishing what shipped is easy and making it pointless is easier. The thing that decides whether a changelog does anything is who finds out, so this one emails the people who asked for the thing.
Both on the nine dollar plan.
What lets you build on it?
The API. Every endpoint listed rather than described. A list is the only thing that answers what somebody with an API in mind is asking, which is whether the thing they want to build is possible.
Twenty one board routes, two of which read your voters and your per feature revenue and need a secret key that never leaves your server.
A custom domain. Your public roadmap, your voting board and one named board at an address like feedback.yourapp.com, with the certificate issued on its own. The changelog and the most wanted list stay on the votefirst.app address.
Single sign on with a JWT. Your server signs a token for a customer who is already logged in, and their votes land under their own name instead of a second account. One shared secret, JWT only, no SAML.
The API, the custom domain and single sign on are on Pro. The widgets are a separate thing that needs no API key, which is why all seven of them work on the nine dollar plan.
14 days, a card at signup, then $9 or $39 a month.
What is not here?
The list is shorter to read than the one above and more useful before you commit.
There are no outgoing webhooks. There is no Slack app and no Zapier listing. There is nothing that writes an issue into your tracker. The integrations page is the whole of what connects to what, and it leads with the absences for the same reason this section does.
There is also no artificial intelligence anywhere in VoteFirst, and that is a decision rather than a gap.
If what you need today is a file rather than a board, eleven free tools and templates are printed in full on their own pages with no form in front of any of them.
Which of these parts you need depends on what you are collecting and from whom, and the four cases people arrive with is the page that sorts that out. Where a word on this page is doing more work than it looks like, the glossary defines it.
Where do I put all this?
On your own site, with one script tag. The seven widgets are the board, the roadmap, the changelog and four smaller pieces, each embeddable on a page you already own, and none of them is behind the higher plan.