Guide · Updated October 27, 2026
How to prioritize feature requests by revenue
Add up the money that depends on each request: the open deals it could help win, the expansions it could unlock and the renewals at risk without it. Weight each account by how much it needs the feature, count from the day it ships, and rank by the total.
The formula
Revenue at stake = Σ for each account (open deal value × stage odds × need weight) + (expansion value × stage odds × need weight) + (ARR renewing in the window × need weight)
Divide by effort, in engineering weeks, to rank by revenue per week of work.
Why vote counts point the wrong way
Votes count people, not money. The feature with the most votes is often what many small accounts would like. The feature that decides your biggest renewal might have a single vote, from one customer on a call.
Revenue changes the question from “who asked most?” to “what depends on this?” Your CFO asks the second one, and you can defend your answer.
The method in five steps
- 01
Link every request to an account
A request with no customer attached has no dollar value. Match each call, ticket and vote to the account in your CRM, whether that’s Salesforce or HubSpot.
- 02
Pull the money behind each account
For a prospect, take the open deal’s yearly value times the odds of its stage. For a customer, take any open expansion deal and any ARR renewing in your window.
- 03
Rate how much each account needs it
Mark each account decisive, important or nice to have. A deal that won’t close without the feature counts far more than one that mentioned it in passing.
- 04
Count from the day it ships
Revenue starts when the feature lands, so an idea that ships later has fewer months to earn. Pick a fixed horizon, like 12 months, and use it for every idea.
- 05
Show the sources, then keep it current
Every number should open to the accounts and calls behind it. Re-run the ranking when a deal changes stage or a renewal date moves.
Weights you can start with
These are the defaults Zentrik uses. Each one is the share of the money you credit to the feature. A deal can hinge on one feature at signing, so its shares run higher. A renewal also rests on everything the customer already uses, so its shares run lower. Tune both to your own win and churn history.
| Level | Meaning | Share of an open deal | Share of ARR at renewal |
|---|---|---|---|
| Decisive | They won’t buy or renew without it. | 85% | 30% |
| Important | It weighs on the decision. | 30% | 8% |
| Nice to have | It wouldn’t change the decision. | 5% | 1% |
A worked example
Three requests from a fictional backlog. Each could ship next month, so all three earn for the same one-year window. By votes, CSV export wins easily. By revenue per week of work, it comes last.
| Request | Who asked, and how much they need it | The math | Revenue at stake | Effort | Per week | Rank |
|---|---|---|---|---|---|---|
| Bulk CSV export | 41 customers, nice to have | 41 × $8k ARR × 1% | $3,280 | 1 week | $3,280 | 3rd |
| Salesforce sync | 3 open deals, decisive; 2 customers, important | 3 × $50k × 40% odds × 85% + 2 × $120k × 8% | $70,200 | 6 weeks | $11,700 | 2nd |
| Audit log | 1 customer, decisive at renewal | $300k ARR × 30% | $90,000 | 4 weeks | $22,500 | 1st |
Show the number of accounts beside the money, so one big customer doesn’t hide a pattern across many small ones. If one deal backs several features, split its value across them instead of counting it twice. Also leave room for bets revenue can’t see yet, like a new market.
Using revenue with RICE, WSJF or ICE
You don’t have to drop the framework your team knows. Revenue fills the part each one asks you to guess.
| Framework | How it scores | Where revenue fits |
|---|---|---|
| RICE | Reach × Impact × Confidence ÷ Effort, with Impact picked by the team. | Use the revenue at stake as Impact. Reach becomes the number of accounts. |
| WSJF | Cost of delay ÷ job size, with cost of delay scored by the team. | Revenue at stake over your window is a measured cost of delay. |
| ICE | Impact × Confidence × Ease, all scored by the team. | Swap the Impact score for revenue and keep Ease as effort. |
What to look for in a tool
A spreadsheet works for twenty requests. After that, matching requests to accounts and keeping numbers current takes longer than the ranking. A tool should do these for you:
- Reads calls, tickets and usage on its own, so requests don’t depend on someone logging them.
- Matches every request to the right account in your CRM.
- Shows the deal, expansion and renewal money behind each idea, with the stage odds.
- Lets your team set how much each account needs the idea, and keeps a record of every change.
- Opens every number to the quotes and accounts behind it.
- Hands the top ideas to Jira, Linear and your AI agents with the evidence attached.
How Zentrik does it
Zentrik reads your Gong calls, Zendesk tickets, Salesforce or HubSpot accounts and product usage, then gives every idea a Value, which is the revenue that depends on building it. Open the number to see each account, deal and quote behind it. Your team sets how much each account needs it, and Zentrik keeps the record.
Questions
- How do you prioritize feature requests by revenue?
- Add up the money that depends on each request: the open deals it could help win, the expansions it could unlock and the renewals at risk without it. Weight each account by how much it needs the feature, count from the day it ships, and rank by the total.
- How do you tie feature requests to ARR?
- Match every request to the account that made it, then pull that account’s ARR, open deals and expansions from your CRM. A tool like Zentrik does the matching from calls, tickets and votes, so nobody has to tag requests by hand.
- Is revenue-weighted prioritization better than RICE?
- They work together. RICE scores reach, impact, confidence and effort with numbers your team picks. Use the revenue at stake as Impact and the number of accounts as Reach, so the two biggest guesses come from your CRM.
- Won’t one big customer take over the roadmap?
- A feature with high revenue from one account is a different bet from one with the same revenue across forty accounts. Show the account count beside the money, so your team sees both.
- What data do you need to start?
- Your CRM for accounts, deals and ARR, plus wherever customers ask for things: calls, support tickets, a feedback portal and product usage. Connect them once and the ranking updates as the data changes.