Capture feature requests with the problem behind them, so your roadmap is built on needs, not just asks.
Ready to use
What feature would you like?
Short Answer
What problem would this solve for you?
Long Answer
How are you working around it today?
Long Answer
How important is this to you?
Multiple Choice
Your email (so we can tell you if we build it)
A feature request form built on the product-management golden rule: capture the problem, not just the proposed solution. Users describe what they can't do and how they cope today, the two answers that make a roadmap decision possible.
Users are experts on their problems and amateurs on your solution space, so this template makes the problem question required and treats the feature ask as its headline. The workaround question is the underrated one: it measures real pain (elaborate workarounds signal high willingness to pay) and occasionally reveals that the need is already met and undiscovered, which is a documentation fix, not a feature.
The self-reported importance scale (with the honest 'I might leave without it' top option) helps you separate churn risks from wishlist items when the same request comes from ten different people.
A private form avoids the bandwagon effect of public voting and captures the requester's own problem context. Many teams run both: a board for visibility, a form for depth.
Weigh frequency of the underlying problem, the importance answers, and who's asking (plan, tenure, churn risk). The structured fields in this template make that triage a sort, not a séance.
Yes. Embed it in your app's help menu or as a popup, so requests arrive in the moment of need rather than never.
Not an exact fit? Use this template as a starting point and edit anything, or describe what you need and let Formly's AI adapt it for you.
