A feature request is when a customer tells you something they wish your product could do. It might come through a support chat, a survey, a public feedback board, a sales call, or a random email. The format doesn't matter. What matters is that someone took the time to ask.
Feature requests are one of the most direct signals you have about what customers actually need, not what you think they need.
Why tracking them matters
Most teams get feature requests constantly. Without a system, those requests pile up in Slack threads, inboxes, and spreadsheets, then get lost. Six months later, nobody can remember what customers actually asked for.
Tracking gives you:
- Volume signal. If 40 customers asked for the same thing, that's different from one customer asking once.
- Context. Who asked, when, what they were trying to do. This makes prioritization defensible.
- A loop to close. When you build it, you know exactly who to tell.
How feature requests feed into roadmaps
Not every request becomes a roadmap item. But the pattern of requests tells you where the pain is. When you're deciding what to build next, a well-organized backlog of requests is one of the most useful inputs you have.
Collect, organize, and prioritize feature requests from your customers using FeatureOS Boards.