# Feature request tracker kanban template

> Every customer has an idea. The trick is collecting them in one place, spotting the ones that keep coming back, and telling people when you ship.

Source: https://cbse.club/templates/feature-requests · Updated 2026-11-03

## Who this board is for

Product managers, founders and customer success teams at small SaaS companies, and maintainers of apps or open-source projects who get a steady stream of “could you add…”.

## Columns

- **Maybe?**: every new card lands here first, to be triaged.
- **Under review**: Someone is looking into demand, cost and fit.
- **Planned**: Decided yes. Will move to the roadmap or a sprint.
- **Building**: In development.
- **Done**: finished cards, with history kept.
- **Not Now**: cards untouched for the auto-postpone period move here automatically.

## How to run it

1. File every request in Maybe? with the customer’s own words in the description.
2. If a request already exists, add a 👍 reaction and a comment with who asked. Reactions are your vote count.
3. Weekly, move the most-requested ideas to Under review and decide: plan, decline (close with a comment explaining why) or Not Now.
4. When a request ships, close it and use the comments to remember whom to email.

## Suggested tags

- #request: came from outside the team
- #popular: asked for many times
- #integration: connects to another tool
- #security: security or compliance

## Tips

- Decline in public. A closed card with a clear reason saves you answering the same request again.
- Let auto-postpone clear requests that nobody has asked about again in 90 days.
- Add a webhook so new requests post to your product channel.

Use this template free: https://cbse.club/templates/feature-requests/use

## Frequently asked questions

### How should I track feature requests?

Keep them in one place, merge duplicates, count demand (reactions work well), review on a schedule, and tell requesters when you decide or ship. A kanban board makes each request’s status visible.
