Feature Requests
Gather structured product feedback linked to your roadmap.
Browse Feature Requests TemplatesWhy use Forge for feature requests?
Feature request forms are most valuable when they capture not just the request but the underlying problem. Forge feature request forms use multi-step flows to first capture the problem statement, then the proposed solution, then the user's role and company size — giving your product team the context to prioritize effectively.
Use the Forge API to sync every approved feature request directly into a public Notion database that your users can view, turning the form into a transparent roadmap input channel. Users can see their request status updated in real-time. This loop increases user engagement and gives your team a clearer signal on what to build next.
Problem-first flow
Multi-step form: problem statement first, then proposed solution. Forces users to articulate the 'why' not just the 'what'.
Notion/Airtable Sync
Every request syncs to a public Notion database your users can browse. Closes the feedback loop automatically.
Vote aggregation
Use the Forge API to aggregate duplicate requests by topic. Surface the most requested problems for sprint planning.
Performance Data
Teams with public feature request boards see 2.4× higher survey completion rates across all product forms
Feature requests with problem statements attached have 73% higher implementation rate on roadmaps
How to set it up
Create a problem-first form
Step 1: what problem are you trying to solve? Step 2: what's your proposed solution? Step 3: role + company.
Add conditional routing
Route enterprise requests (company 200+) to a dedicated Slack channel for priority review by the product team.
Sync to Notion
Use the Forge webhook with Notion API to create database entries. Set status field to 'Under Review' on creation.
Build a public roadmap view
Embed a filtered Notion view publicly so users can see their requests and current status.
Start from a Template
Or use the Headless API to build from scratch.