Skip to content

Guide

Feature requests: the complete guide

A feature request is a suggestion from a customer or teammate to add or change something in your product. Here's how to collect, track, prioritize and ship them, and how to tell people when you do.

Updated
On this page
  1. What a feature request is
  2. Collecting feature requests
  3. Tracking and organizing requests
  4. Prioritizing what to build
  5. Saying no to a feature request
  6. Shipping and communicating

Feature requests tell you exactly what customers wish your product could do. They're also noisy. The same need arrives in ten phrasings through five channels, and the loudest voice isn't always the one that matters most.

Teams that handle requests well treat them as a pipeline: capture every request in one place, merge and tag them, score them against your strategy, then tell the people who asked what you decided. Whether you get ten a month or ten thousand, the stages are the same.

What a feature request is

A feature request asks for new functionality, or for a change to something that already exists. It's different from a bug report, which says something that should work doesn't, and from general feedback, which describes an experience without asking for anything in particular.

Customers usually describe a solution: "add a CSV export". Your job is to find the problem behind it: "I need this data in our finance tool every month". The problem is what you prioritize. The solution stays open. A useful request records:

  • The problem, in the customer's own words
  • Who's asking: the person, their company and their plan
  • How they work around it today, which shows how painful it is
  • What it's blocking, such as a renewal, an expansion or a new deal
  • Where it came from, with a link back to the conversation

Collecting feature requests

Requests arrive from support tickets, sales calls, social media, in-app widgets and community forums. Getting requests is rarely the problem. Getting them into one system is.

  • Give customers one place to post. A public feedback board lets customers submit ideas, vote on existing ones and see what's happening. Showing similar ideas while they type cuts duplicates before they start.
  • Collect inside your product. A widget in your app catches requests in context, while the need is fresh.
  • Log requests on customers' behalf. When someone asks on a call or in a ticket, your team should be able to add their vote to the existing request in seconds, so they count even if they never visit the board.
  • Keep internal ideas separate. Ideas from your own team belong on a private board, where they won't drown out customer demand.

Tracking and organizing requests

Once requests are in, give each one the same treatment, wherever it came from:

  1. Merge duplicates into one request, keeping every vote and comment.
  2. Tag it by product area or theme.
  3. Set a status so everyone, inside and outside the team, knows where it stands.
  4. Link it to the work in your issue tracker once it's planned.

A short, public set of statuses works for most teams:

StatusWhat it tells the customer
OpenWe have it, and haven't reviewed it yet
Under reviewWe're considering it
PlannedWe've committed to it, and it's on the roadmap
In progressWe're building it now
CompleteIt shipped
ClosedWe won't build it, and here's why

Plenty of teams start in a spreadsheet. It works until customers need to see votes, statuses and replies. That's usually the moment to move to a dedicated tool.

Prioritizing what to build

You'll always have more requests than capacity. Votes show demand, but they're one signal among several. Weigh each request on:

  • Reach: how many customers have the problem
  • Value: the revenue, retention or expansion tied to it
  • Fit: whether it moves your product strategy forward
  • Effort: what it costs to build and maintain

A framework turns that weighing into something repeatable:

FrameworkBest for
RICEData-driven teams comparing many options
ICEFast scoring of smaller bets and experiments
MoSCoWAgreeing the scope of a release with stakeholders
Kano modelSeparating must-haves from features that delight
Impact and effort matrixA quick visual sort in a planning session

Weight votes by who cast them. Ten requests from customers in your target segment can matter more than a hundred from accounts that will never upgrade.

Saying no to a feature request

Most requests won't get built. That's normal, and customers know it. What frustrates them is silence.

  • Decide in the open. Close the request with a status, rather than letting it go stale.
  • Give the reason. One or two sentences: it doesn't fit the product's direction, the cost outweighs the demand, or there's a better way to solve the problem.
  • Offer a way forward. Suggest a workaround, or point to a related request that's planned.
  • Leave room to revisit. If demand grows, say you'll look again, and mean it.

Shipping and communicating

Building the feature is half the job. The customers who asked need to know it exists.

  1. Move the request to Complete, so the board reflects reality.
  2. Publish a changelog entry that leads with what customers can now do.
  3. Notify everyone who requested it, voted or commented. "You asked, we built it" is the best retention message you'll send.

Teams that close the loop this way get more and better requests, because customers can see that asking works.

Feature requests in Quackback

Collect, rank and ship requests in one place

Customers post and vote on your board, your team merges, tags and decides, and everyone who asked hears when it ships. This is a demo portal: try voting.

Example data. What follows is an interactive demo of a made-up workspace called Acme. Its customers, posts, votes and changelog entries are examples, not Quackback's own.

Acme Corp
PN
Boards
Powered by Quackback
VotingOne vote per customer, plus votes you add for customers who asked elsewhere.
Duplicate mergingSimilar ideas show as customers type, and merges keep every vote.
Issue tracker syncSend requests to Linear, Jira or GitHub. Linear and GitHub update the status; Jira changes come back for you to review.
Public roadmapShow what's planned and in progress.
ChangelogAnnounce what shipped and notify everyone who asked.
MCP serverLet AI assistants search, triage and merge requests.

Common questions

What is a feature request?

A feature request is a suggestion from a customer or stakeholder to add new functionality to your product or change what's there. Requests arrive through support tickets, sales calls, social media, in-app widgets and feedback boards.

How do you manage feature requests?

Bring every request into one system, merge duplicates and tag them, score them with a prioritization framework, and tell the people who asked what you decided. A feedback board gives customers one place to submit, vote and follow progress.

How do you prioritize feature requests?

Weigh demand against value, strategic fit and effort, and use a framework so decisions stay consistent. RICE suits data-driven teams, MoSCoW suits agreeing scope with stakeholders, and the Kano model separates basic expectations from features that delight.

What is the best tool for tracking feature requests?

Look for one that combines submission, voting, duplicate merging, statuses and a way to announce what shipped. Quackback is an open-source option with feedback boards, voting, a public roadmap and a changelog. You can start on the free Cloud plan or self-host it.

How do you say no to a feature request?

Close it with a clear status and a short, honest reason, and suggest a workaround if there is one. Customers accept a no far more readily than a request that goes quiet.

Have another question? Talk to the team.

Start managing feature requests today