Let your users vote on what goes on the product roadmap
Make a product roadmap voting form. Users rank shortlisted features, rate each one and add one idea, then you read the results at a link.
Which idea should we do first?
Rank the shortlist, then rate how valuable each idea is.
This is a real form: answer it the way a visitor would. Nothing is saved.
Use this template Describe yours in chatOpen full screenMore to start from: all form, quiz and course templates. Nothing is published until you press Publish, and every answer lands in your account with charts and a CSV.
Roadmaps built only from the team's guesses often miss what customers actually pay for, and long surveys get abandoned halfway. This page builds a short vote: a ranking of the shortlisted features, a rating for each one, and room for one new idea. The live sample above is a general one; the chat adapts it to your product and your list of features.
What you get
Ranking and rating in one vote
The ranking block puts the shortlist in order, and the rate-items block gives each feature its own score. A feature that a few users rate as urgent shows up in the results chart even if it does not win the most first-place votes, so you can see intensity as well as preference.
Logic and pages
Show a follow-up only when it applies, split a long form into pages, or show one question per screen.
Results you can read
A chart for every question, averages and NPS for scales, the order of a ranking, a table of every answer and a CSV.
How it works
- Step 1
Try the sample above, then press Use this template, or describe your own form to the chat.
- Step 2
Change any question by hand or ask the assistant ("add a question about price", "translate it to Spanish"), with a live preview.
- Step 3
Publish, share the link or QR code, and read the answers as they arrive. You get an email for each one.
Who uses it
Founder of a small software company
Choosing between five or six planned features before the next quarter, when every option looks reasonable and you want your own guesses checked against paying users.
Product manager at a tool for agencies
Asking existing clients which integration to build first. A logic rule can show the team-size question only to customers on the Team plan, so the answers stay comparable.
Maintainer of an open-source project
Collecting feature requests from contributors and users, then setting a response limit so the vote closes once enough answers are in and the roadmap can be updated.
Questions
How many features should be on the list?
Five to eight is a good range. Ranking more than that takes long enough that people start dropping answers, and the top choices get lost among the rest. If you have more ideas, group them and vote on the groups first.
Can someone vote more than once?
The form does not check who is answering, so the same person can submit again. A response limit caps the total, and the email sent for each response lets you spot repeats. For a roadmap vote, that is usually enough, but it is not identity verification.
Should I ask for email addresses?
Only if you plan to reply, for example to tell people when a feature ships. Make it optional and say what it is for. Ask only for what you will use; collecting more personal data than you need is your responsibility as the owner.
Will people see the results?
You read the results on your own results page, with charts and a CSV you can download. The live sample above shows a version where everyone sees the running result after voting, and the chat can set your form up that way too.
How do people find the vote?
Every published form gets a link and a QR code. Put the link in your product newsletter, in-app message or support emails, and use the QR code on printed material at events or in your office.