Feature Priority Calculator

Score your backlog by impact and effort. Get a ranked list and a quick-wins matrix you can drop into your next planning meeting. Want to factor in how many people each feature reaches? Use the RICE calculator.

Add a feature

How much value does this add?
How much work is this?
Priority score preview:1.00

Score = Impact / Effort. Higher is better.

Ranked features

Add features to see them ranked by priority.

How the scoring works

Two frameworks, one goal: value delivered per unit of work.

Impact Score (1-5)

How much value does this feature add? Consider revenue potential, user satisfaction, strategic importance, and how many users it affects. A feature that solves a critical pain point for most users scores higher than a nice-to-have for a few.

Effort Score (1-5)

How much work does this feature require? Include development time, complexity, dependencies, testing, and maintenance. A simple UI tweak scores low; a major infrastructure change scores high.

Simple mode: Impact / Effort = Priority

Divide impact by effort to get your priority score. Higher scores mean better return on investment. This surfaces your quick wins (high impact, low effort) at the top while pushing time sinks (low impact, high effort) to the bottom. The matrix above plots the same data as four quadrants: quick wins, big bets, fill-ins, and time sinks.

5.00
Quick win
2.50
Worth doing
1.00
Consider later
0.20
Deprioritize

When to use which framework

Impact/effort works well for quick backlog triage: it takes seconds per feature and gets a team aligned fast. RICE adds two more inputs, how many people each feature reaches and how sure you are, which helps when stakeholders disagree about audience size. For the full breakdown with a worked example, see the RICE score calculator.

Best practices for both: score features as a team to reduce individual bias. Revisit scores quarterly as circumstances change. Use scores as input to decisions, not the final word. Strategic features may still win with lower scores.

Every number in these formulas is an estimate. For ongoing prioritization, the strongest signal is actual users telling you what they want. That is what feature voting is for.

Frequently asked questions

Practical answers about agents, voting, embeds, and pricing.

Rate each feature on impact (1 to 5) and effort (1 to 5), then the score is impact divided by effort. Higher scores mean better return on work. The quadrant matrix plots the same data: quick wins sit top left (high impact, low effort), time sinks bottom right.

Use Simple mode for quick gut-check prioritization: two scores per feature and you are done. Use RICE mode when features serve very different audience sizes: it adds how many people each feature reaches and how sure you are about your estimates. Both modes rank the same way: value delivered divided by work required.

Yes, in your browser. Your features are stored in localStorage on your device and never sent to a server. Come back any time on the same browser and your list will still be here. The same list is also available on the RICE calculator page. Clear all removes everything.

Yes, and no email is required. Copy your ranked list as a Markdown table to paste into Notion, GitHub, or any doc, or download it as a CSV for spreadsheets.

Yes. No signup and no account. FeatQ makes a paid feature voting board, and this tool is a companion to it.

Still have questions? Contact us

Scores are guesses. Let your users vote.

Every impact and reach number above is an estimate. FeatQ replaces estimates with real signal: users submit requests, vote on them, and you ship what wins.

Try FeatQ$29/month per board. No per-user fees.