HomeRevenue-Weighted Feedback
Revenue-weighted feedback
Prioritize feature requests by revenue, not vote count.
A request from three customers paying $2,000 a month combined carries different weight than one from thirty free-tier users, even though the second has more votes. Here's how to build a backlog that reflects that.
No credit card required · No SDK to install
The problem with vote-count prioritization
Votes measure enthusiasm, not value
A raw vote count treats every voice the same. Thirty free-tier users clicking upvote can outrank three of your highest-paying accounts asking for the same thing. It's not that vote counts are useless; it's that they're missing a dimension.
Loud isn't the same as valuable
The most active voters on a public board are often free users or early adopters with time on their hands, not your highest-value accounts.
You can't see it in a spreadsheet
Even teams that try to correct for this manually end up cross-referencing a voting export against a billing export by hand, which doesn't scale past a handful of requests.
Gut-feel overrides get inconsistent fast
Without a real mechanism, revenue-aware prioritization becomes a judgment call made case by case, which means it's applied inconsistently, if at all.
What revenue-weighted prioritization is
Attach revenue context to every request and vote
Revenue-weighted prioritization means sorting a feedback backlog by the combined revenue of the customers asking for something, not by the number of people who asked. It requires one thing most feedback tools don't have natively: a live link between a submission and the requester's actual account value, so the backlog can reflect who's asking, not just how many.
How Reqio does it
A signed identity token, no SDK required
Reqio ties every vote and submission to a real user via a signed identity token: a short-lived JWT (HS256, 5-minute expiry) your own server mints and passes to the widget on page load. Your auth stack stays yours.
- Works in Node.js, Next.js, Python, PHP, Ruby, and Go, using each language's standard JWT library (jose, PyJWT, firebase/php-jwt, the jwt gem, golang-jwt/jwt)
- Anonymous by default. Identity is opt-in, and you choose exactly what to pass: email, plan tier, MRR value
- Every vote, submission, and conversation carries the identity context you provide, visible in the dashboard backlog
- The dashboard generates the exact server-side snippet for your project, so there's no wire format to reverse-engineer
How it works
From your auth system to a revenue-weighted backlog
Generate a signing secret
Create a per-project signing secret from Project > Settings > Identity. Reqio stores it encrypted at rest.
Mint a token on your server
Using your existing auth system and a standard JWT library, sign a short-lived token carrying the user's ID, plan tier, and MRR, whatever you choose to include.
Pass it to the widget
Embed the widget with `data-identity-token` set to the token you minted. Reqio verifies the signature server-side on every request.
Sort the backlog by revenue
Every vote and submission now carries that context. The dashboard backlog can surface who's asking, not just how many, so you build for the accounts that drive revenue first.
Questions
Questions about revenue-weighted feedback
What is revenue-weighted feedback prioritization?
It means sorting a feedback backlog by the combined revenue of the customers asking for something, not by raw vote count. A request from three customers paying $2,000 a month combined carries different weight than one from thirty free-tier users, even though the second has more votes.
How do I prioritize feature requests by revenue instead of vote count?
Attach each user's plan or MRR tier to their identity before they submit or vote. Reqio does this with a signed identity token: your server mints a short-lived JWT using a standard library, no vendor SDK required, in Node.js, Python, PHP, Ruby, or Go, and passes it to the widget. Every submission and vote then carries that revenue context, so a request with ten votes from your highest-paying accounts can outrank one with fifty votes from free users.
Do I need a CRM integration to weight feedback by revenue?
No. Reqio's approach doesn't depend on syncing a CRM. You pass MRR or plan data directly in the signed token from your own database, so it works even if you don't run Salesforce or HubSpot.
Is identity required to use Reqio?
No. Anonymous submissions and votes work by default. Identity, and the revenue-weighting it enables, is entirely opt-in, and you control exactly what data you attach.
Do I need to install an SDK to pass identity data?
No. Reqio's identity system uses your language's standard JWT library, not a Reqio-published package. The dashboard generates the exact code snippet to mint a token for your project, in Node.js, Next.js, Python, PHP, Ruby, or Go.
Start building for the accounts that pay you.
Get started for freeNo credit card required · No SDK to install