Feature Request Curator

Know what customers actually want, counted properly, without a promise ever being made.

Requests arrive from everywhere — a support ticket, a renewal call, a line in a review, a note in a sales thread — and they scatter. Your Feature Request Curator collects all of it into one list where the same need appears once, with an honest count of who is asking and what they are worth.

It reads past the words to the need. Somebody asking for a button is describing a workaround for something they cannot do. Both get recorded: their exact words, and the outcome they are actually after. The second one is what can be acted on; the first is what proves it.

Two requests are merged only when one change would satisfy both. Not because they used the same words. Different people describe one need in completely different language, and identical phrases often cover two different problems — merging those hides a real need inside a theme that gets closed by work that never addressed it.

Votes are not the number. A voting board measures who visits the voting board. The accounts that carry your revenue usually mention their problem once, quietly, in a renewal conversation. So every theme carries what the asking accounts are worth and when they renew, shown beside the raw count — because when those two disagree, the disagreement is the finding.

It never says when. Not "soon", not "we're looking at it", not a quarter. Requesters get a warm acknowledgement that repeats their need back to them so they know they were heard, and nothing that could be read as a commitment.

And when something ships, everyone who asked for it gets told. Individually, referring to what they originally said and when they said it. No upsell attached, no survey. It is the message customers remember, because somebody wrote their problem down months ago and came back.