Weighing requests by revenue without losing the plot
Money behind a request is a real signal. Use it well and you won't turn into a custom shop for your biggest customer.
Nº 20 · HeedPost team · Sep 30, 2026 · 2 min read
At some point a founder looks at the top of the feedback board and asks the uncomfortable question: but who's asking? The most-voted request might come from a hundred free users. The third one down might be what your three largest customers have been waiting on for six months.
Weighing requests by revenue answers that question. Used well, it's one of the best inputs you have. Used badly, it turns your product into a list of favours.
Why it helps
Votes treat every customer the same. That's fair, and it's also not how your business works. Some customers pay a hundred times more than others. Some are about to renew. Some are the reason you can hire. A request that matters to them matters to the company, and pretending otherwise isn't principled, it's just not looking.
Revenue also catches what votes miss: the quiet request. Large customers often post once and never vote, because the person who uses your product isn't the person who'd go vote on things. Sort by votes and their request is on page three. Sort by the money behind it and it's on top.
How it goes wrong
One customer becomes the roadmap. Your biggest account asks for something only they need. It's expensive, it complicates the product, and once built it's yours to maintain for every other customer forever.
You build for who pays today, not who'll pay tomorrow. Revenue is backwards-looking. The customers you want next year may not be paying you yet.
Small customers stop posting. If they sense only big accounts are heard, they leave the board, and you lose your widest view of the product.
Use it as a weight, not a rule
A few habits keep it healthy:
- Look at both columns. A request high on votes and high on revenue is an easy yes. High on one and low on the other is the interesting conversation.
- Count companies, not just dollars. One giant customer and twelve mid-sized ones asking for the same thing are different situations, even at the same total.
- Keep revenue inside the team. Customers should never see what a request is worth. It changes how they post.
Ask whether others would use it
The question that protects you from becoming a custom shop: if we build this for them, how many other customers would use it within a year? If the answer is "basically none", it might be a services engagement, not a feature. That's fine too, but call it what it is.