Resonly – prioritize feature requests by revenue impact

Hi HN,

I’m building Resonly to help teams prioritize feature requests with more context than just votes.

The idea is simple: not every request is equal. A feature requested by multiple paying customers may matter more than one with 100 upvotes from free users.

I’ve added a way to associate revenue with each customer, so when someone upvotes or submits a feature request, the admin can see three signals:

MRR at risk — how much current MRR is tied to customers asking for it;

MRR lost — how much MRR was lost from customers who churned before it was solved;

Potential MRR — how much MRR could be converted from trial customers requesting it.

I’d love your honest feedback on the idea and positioning.