"Feature request management for a small SaaS: a process that fits one person"

By Hasan · November 5, 2026 · 2 min read

Feature request management means collecting what customers ask for, deciding what to build and telling them what happened. For a small SaaS the process has to fit one person's week. This is a version that does.

What do you need?

One place where requests live, a way for customers to vote, three statuses, and a habit of closing the loop. A spreadsheet works at the start. A board works better once customers submit requests themselves, because votes show which ones many people want.

How does the process work?

  1. Collect. Customers submit ideas on a board, or you add ones you hear in chat and calls. Merge duplicates so votes add up in one place.
  2. Rank. Look at votes and comments, but also at who asked. A request from many small customers and a request from your best customer are different signals.
  3. Decide. Move ideas through three statuses: Planned, In progress and Shipped. Say no to the rest, kindly, in a comment.
  4. Ship and tell. When you mark an idea Shipped, its voters get an email and a changelog draft is created. You edit it and publish it.

Nothing reaches the changelog until you publish it, so you stay in control of what customers read.

How do you keep it from taking over your week?

  • Review the board once a week, at a fixed time.
  • Turn on moderation if you do not want new ideas public until you approve them.
  • Do not promise dates. Statuses are enough.
  • Write the changelog entry in terms of what changed for the user, not the ticket title.

Who should see the board?

You choose an access mode. Public lets anyone read and vote without signing in. Identified needs a visitor you identified before they can write. Private shows the board only to customers you signed in with a verified identity. For B2B products with sensitive plans, Private is the safer start.

Where can the board live?

On your website, embedded in a page, with an in-app What's new panel. On your own subdomain such as roadmap.yourcompany.com. Or on a hosted page, with no code. All three show the same content.

Next steps

Read how to build a public product roadmap and how to write a changelog. If you want a custom domain, see roadmap on a custom domain.

See it working in 2 minutes

Try the live demo

Related