Rate three factors
Usage rate, maintenance cost, and strategic value are each rated 1-10 for a feature that's already live.
SHIPPED-FEATURE REVIEW
Feature Sunset Candidate Finder
For features you've already shipped: score usage, maintenance cost, and strategic value to see whether it's a keep, a simplify, or a sunset candidate.
- Uses your inputs in a transparent calculation
- Instant result with practical next steps
- No signup required
Planning guidance only. Validate important decisions with customer evidence and your delivery team.
YOUR INPUTS
Build your result
Complete every field. The result updates only when you choose Calculate.
How it works
Get a sunset score
The score combines the three inputs so that high maintenance cost with low usage and low strategic value pushes toward sunset.
Get a keep/simplify/sunset call
The recommendation is threshold-based and explains which factors are driving it.
Continue learning: MVP feature prioritization
Frequently asked questions
How is this different from Feature Cut List?
Feature Cut List scores features that haven't been built yet, based on impact vs. effort, to help you decide what to cut before launch. This tool is for the opposite situation — a feature that's already shipped and live — and scores usage, maintenance cost, and strategic value to decide whether to keep, simplify, or sunset it.
What counts as 'maintenance cost'?
Ongoing burden: recurring bugs, support tickets, code that blocks other changes, or infrastructure it depends on. Rate it high if the team dreads touching that part of the codebase.
Can a heavily-used feature still be a sunset candidate?
It's less likely, since usage reduces the score, but if maintenance cost is extreme and strategic value is low, it can still land in the 'simplify' zone even with moderate usage.
What does 'simplify or monitor' mean in practice?
It means the case for full removal isn't strong yet — consider trimming the feature's scope to reduce maintenance cost while keeping the core value, or revisit the score next quarter.
How is the score calculated?
Sunset score = maintenance cost minus usage rate minus strategic value, normalized from a [-20, 10] range to 0-100. It's transparent arithmetic — no hidden weighting.
Should I use this alone to decide on removal?
No — pair it with real usage analytics and a conversation with support/success teams before removing anything customer-facing.
How We Compare
| Feature | MVPHub | Notion | Airtable |
|---|---|---|---|
| Post-launch sunset scoring | Included | Not included | Not included |
| Keep/simplify/sunset recommendation | Included | Not included | Not included |
| Instant weighted score | Included | Not included | Limited |
| No setup required | Included | Limited | Included |
Notion and Airtable can track feature usage notes in a table, but neither computes a sunset score or a keep/simplify/sunset recommendation automatically.
Related tools
Embed this tool
Add this tool to your site with the canonical iframe below. It remains hosted and maintained by MVPHub.