Feedback2026-09-191 min read

Sort feedback by revenue, not by volume

The loudest request and the most valuable one are rarely the same post. Harkly shows you both.

Pro customers · last 90 days
  • 1Dark mode184$9.1k
  • 2CSV export122$6.3k
  • 3Public API97$24.6k
  • 4Slack notifications63$11.9k
  • 5SAML single sign-on41$38.2k

"Dark mode" has 184 votes. "SAML single sign-on" has 41. On most boards that's the end of the conversation.

Then you look at who voted. The 41 are three enterprise accounts worth $38k a month between them, and one of them told sales it's the reason they haven't renewed yet. The 184 are mostly people on the free plan.

Both lists are true. You need to be able to see both.

Revenue on every vote

When your app identifies a customer, it can say who they are and what they pay:

Harkly.identify(
  { id: user.id, email: user.email, plan: "pro", mrr: 149 },
  { company: { id: account.id, name: account.name, plan: "enterprise", mrr: 12_400 } },
);

Each vote then carries that weight. Sort any board by Revenue and posts rank by the MRR behind them, counting each company once however many of its people voted.

Or let your CRM fill in the rest

Coming soon on Team: connect HubSpot or Salesforce and Harkly syncs every night: companies matched by domain, people by email, with industry, size, revenue and lifecycle stage as attributes on the record. They're there to segment by even if your app only ever sends an email address.

Segments and RICE

Revenue is one lens. Two more ship with it:

  • Segments filter votes to the customers you care about this quarter — "enterprise", "churn risk", "EU" — built from any attribute.
  • RICE scores posts from reach, impact, confidence and effort, when you want to weigh cost as well as demand.

None of these picks for you. They make the trade-off visible, which is the part a raw vote count hides.