Most feedback tools rank requests by upvotes. It feels fair: the most-wanted thing wins. But an upvote count answers the wrong question. It tells you who's loudest, not who's at risk.
The customer quietly renewing a six-figure contract rarely campaigns for votes. The ten free-tier users who will never convert often do. Rank by volume and you optimize for noise.
Tie every request to an account
In Crumb, a piece of feedback isn't a floating idea; it's attached to the account that submitted it, and every account carries its ARR. So your inbox doesn't show "+12 upvotes." It shows Acme · $48k next to the request.
Prioritization went from arguing about gut feel to reading the number off the screen.
When three accounts worth $48k, $34k, and a smaller logo all ask for the same export, you don't debate it. You see $186k of ARR waiting on one feature and you build it.
Volume still matters, as a tiebreaker
This isn't "ignore everyone but your biggest customer." Revenue is the first lens; following counts, recency, and segment are the next ones. The point is that the dollars are visible at the moment you decide, instead of buried in a CRM you'd have to go cross-reference.
Then close the loop
Prioritizing by revenue only pays off if the account hears back. When the export ships, the customers who asked get the "it's live" note automatically, so the prioritization they triggered becomes a relationship moment, not a silent backlog item.
That's the whole loop: capture in context, prioritize by revenue, ship, and tell them. See how it fits together →