Feature ideas arrive in support chats, replies and passing comments. By the time you sort them, half the context is gone. I would rather give every idea one place to land, with the problem written down next to it.
Who it is for
Small product teams, solo founders and shop owners who hear ideas from customers every week and want to compare them fairly.
What each question is for
- Idea in one line and the task behind it: the idea is a guess. The task is the real need.
- Product area and how often: shows whether it helps everyday use or a rare edge case.
- How much it would help: a rating from 1 to 5 that you can sort by.
- Workaround and example link: how people cope now, and what good looks like to them.
- Early tester tick: a ready list of people to ask.
What a user's AI would ask
"What are you trying to get done?" Then "What do you do today instead?" Then "How often would you use it?" It lists the answers and waits for a yes. Learn more about agent-fillable forms.
Before you use it
Set close_at before a planning week, then read one fixed batch. Add a waitlist for ideas you have not built yet, and send dealers with their own wishes to your reseller application. After a release, check the result with a customer satisfaction survey. More ideas are in forms for SaaS and startups and forms for online shops.
Questions
How do I rank the requests I receive?
Download the CSV, group rows by product area, then sort by the help rating and how often people would use it. Read the task text for the top ones.
Can I freeze requests while I plan a release?
Yes. Set close_at to a date so you work from one fixed batch. Reopen the form when you are ready for the next round of ideas.
Should I make the email required?
I would keep it optional. People share more freely without it. Ask for the email only to follow up, and say so in the form description.