Installs in ~2 min· 5 assets · 8 steps

Let customer demand rank your roadmap instead of guessing

Stop guessing what to build next. Let the demand rank itself.

Customers submit feature requests through a form. AI groups the duplicates, scores each idea by how many customers actually asked for it, and hands your product manager a ranked report every week. When a request moves to In Progress or Released, every customer who asked for it hears about it, without anyone drafting an email.

Free · no credit card · you connect your own apps

The blueprint
Trigger
Feature Request Form is submitted
Every run starts from one submission.
Transform
Load Existing Themes
Transform
AI Group & Score
AI reads the input and returns a structured result.
Transform
Increment Votes
Action
Notify Product Team
What gets built

5 things appear in your workspace.

Installing provisions each one, wired together and ready to run.

TableFeature Request Submissions

Each request with the customer's details, submission date, status, its AI-assigned feature group, and that group's priority score.

FormFeature Request Form

Public form for customers to submit requests. Every submission opens a row. Publishing it auto-creates the Feature Requests response sheet, which is the single system of record.

WorkflowGroup & Prioritize Feature Requests

Fires on submission. Clusters the request with related ones and recalculates the group's priority score.

WorkflowWeekly Product Digest

Runs weekly. Emails the PM every requested feature in priority order with demand counts, AI summaries, and a link to the table.

WorkflowNotify Requesters on Status Change

Fires when a request moves to In Progress or Released, and emails every customer in that feature group.

What you connect

The apps this recipe needs.

You connect your own accounts. Swap any app that offers an alternative at install.

Product Notification
Slack *

Posts new and trending feature requests to your product team channel. Swap for Telegram, Discord, or Google Chat.

Outbound Email
Gmail *

Sends the weekly PM digest and the automatic requester notifications when a request moves to In Progress or Released. Swap for Brevo.

How it works

Step by step, once it is running.

  1. 01
    Customers Submit Through One Form

    A form captures every feature request in one place, so asks stop scattering across support tickets, sales calls, and DMs where they quietly die.

  2. 02
    Every Request Is Stored Automatically

    Each submission lands in TinyTables with the customer's details, the submission date, and its current status.

  3. 03
    AI Groups Similar Requests and Scores Demand

    AI reads each request, clusters it with the ones asking for the same or related functionality, and assigns a priority score based on how many customers are behind it. Groups and scores update in TinyTables on their own. This is the step that turns a pile of anecdotes into a roadmap signal.

  4. 04
    New Requests Keep Folding Into Their Group

    Through the week, every incoming request continues to be categorized and consolidated into its matching feature group, so the priority score is current when your PM looks at it, not stale since the last review.

  5. 05
    A Ranked Report Reaches Your PM Every Week

    At the end of each week, AI writes a summary listing every requested feature in priority order, with the customer demand behind it and a short AI-written blurb. It's emailed with a direct link into the TinyTables for review.

  6. 06
    The PM Decides What Happens

    Requests are reviewed in TinyTables and moved to Under Review, In Progress, or Released. A human owns the roadmap, AI only ranks the input.

  7. 07
    In Progress → Every Requester Is Told

    The moment a feature moves to In Progress, an automated email goes to every customer who asked for it, letting them know development has started.

  8. 08
    Released → They Hear Again

    When the status changes to Released, those same customers get a second email announcing it's available, with any relevant release notes or documentation.

What you walk away with
FAQ

Questions about Feature Request Collection & Prioritization.

How does it handle the same request arriving twice?
AI groups similar requests into a theme and recalculates that group's priority score, so twenty people asking for the same thing reads as one heavily-demanded feature. duplicate_threshold controls how aggressively requests are merged.
What does the PM actually receive?
A Weekly Product Digest email listing every requested feature in priority order with demand counts, AI summaries and a link back to the records. It runs on a schedule so prioritization does not depend on someone collating a spreadsheet.
Do customers hear back?
Yes, twice. When a request moves to In Progress every customer in that feature group is emailed, and they hear again when it is Released. That closing loop is the part most feedback processes drop.
What do I need to connect?
Slack and Gmail are both required. Slack notifies your product channel and Gmail sends the digest and the status updates. Telegram, Discord, Google Chat and Brevo are supported swaps.
Why are there two places requests live?
The Feature Request Submissions table holds one row per raw submission, and the form's response sheet holds the grouped themes. The theme links them, which is how the status-change workflow can find every customer who asked for one feature.
More recipes

Install it, then make it yours.

Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.