Kjerr is a feature request tool for product teams: users post ideas on a public board, vote on each other's requests, and get an email when the status changes. One inbox for the team, a RICE roadmap the team keeps to itself, no per-seat bill.
Feature request management is four jobs: collect requests in one place, let demand rank them, decide, and tell people what you decided. Kjerr does those four and stops.
Your board lives at yourname.kjerr.io. A short title, optional details and up to 5 screenshots or files. Reading and searching need no account. The form is the short version of our feature request template, and you can rename its fields and add your own.
Similar ideas appear as someone types a title, each with a vote button. If a duplicate is posted anyway, merge it: votes de-duplicate, comments move and the old link redirects. AI merge finds the ones nobody noticed and leaves the decision to a teammate.
A status change or an admin reply emails the author and every voter, under your workspace name, with one-click unsubscribe. Votes alone never send email. This is how you close the feedback loop.
Feature voting turns a pile of requests into a ranked list without a meeting. In Kjerr each person has one vote per idea, and the board sorts by top, new or trending.
Feature request tracking means knowing, for every request, what state it is in and who is waiting. The admin inbox is one screen built for that.
Kjerr is feature request software for teams that prioritize by votes, by who is asking and by a RICE score the team keeps to itself. These are deliberately not in the product:
Product teams at SaaS companies of any size, from startups to enterprise, that want a public feedback board, a team-only roadmap scored with RICE, and reliable follow-up emails without a help-desk suite or a per-seat bill. If you need an issue-tracker sync or a feature hierarchy, a heavier tool is the better fit; the customer feedback tools comparison says which.
A feature request tool is one public place where users post what they want from a product, vote on each other's requests and see what the team decided. It replaces requests scattered across email, chat and support tickets with a single ranked list, and it tells the people who asked when something changes.
One click, one vote per person. Votes rank the list, and people can sort ideas by top, new or trending. When two ideas are merged the votes de-duplicate, so nobody counts twice.
Every request carries a status, a vote count, comments, topics and private admin tags. The admin inbox lists requests unread first, Reports counts the ones still awaiting a response, and every chart links to the exact ideas behind it.
Reading and searching need no account. The first post, vote or comment confirms an email address once. If your product signs users in with single sign-on, they arrive on the board already identified.
Yes. A teammate with the Idea Submitter role or above can post an idea and a vote on behalf of a customer who asked by email or on a call. That customer is then notified like any other voter.
It helps you score them, and you decide. The team-only internal roadmap scores each request with RICE (Reach × Impact × Confidence ÷ Effort) or factors and weights you define, with the votes, the companies and the MRR behind the request beside the score. AI can propose a score with a one-line reason; nothing is set until a teammate applies it. Customers never see a score.
Kjerr is free during early access, with every feature included and no credit card. When paid plans arrive they will be priced per workspace, never per admin seat and never per tracked user, so the number of people who post, vote or comment never changes the bill.
Kjerr