Feature Cut List
Score each feature by impact and effort and get a clear keep-or-cut list, plus estimated days saved.
Estimated time saved by cutting: 0 day(s)
Recommend Cut 0
No cut candidates — effort doesn't outweigh impact for anything listed.
Keep 0
Nothing clearly worth keeping yet.
Add a name to at least one feature before building your cut list.
How it works
-
List your candidate features
Add every feature currently in scope, even the ones you are unsure about.
-
Rate impact, effort and build days
Score each 1-5 on user impact and build effort, and add a rough day estimate if you have one.
-
We calculate a cut score
Cut score = effort − impact. A positive score means the feature costs more than it currently delivers.
-
Get a keep-or-cut verdict
Features are split into Recommend Cut and Keep, with the total estimated days saved by cutting.
Cutting scope is one lever — see 10 Ways to Speed Up Your MVP Development Timeline for more, or explore our MVP development packages.
Frequently Asked Questions
How is the cut score different from a priority score?
Cut score = effort − impact, a simple signal for "does this cost more than it delivers?" It is deliberately simpler than a full MoSCoW breakdown, built for a fast keep-or-cut pass.
What if a feature has high impact and high effort?
A high-impact, high-effort feature can still score as "Keep" if impact outweighs effort — the cut score only flags features where effort is greater than impact.
Is the days-saved number accurate?
It is only as accurate as the day estimates you enter. Treat it as a rough total, not a committed schedule impact — useful for a quick "is this worth cutting" conversation.
What's the difference between this and the MVP Scope Builder?
The MVP Scope Builder sorts a full feature list into four MVP-scope tiers (Must/Should/Could/Won't). This tool gives a simpler binary keep-or-cut call plus a time-saved estimate.
Should I actually delete cut features from my plan?
No — park them in a backlog. "Cut for now" usually means "not in this MVP," not "never build."
How We Compare
| Feature | MVPHub Feature Cut List | Google Sheets | Trello |
|---|---|---|---|
| Automatic keep-or-cut verdict per feature | Included | Limited | Not included |
| Estimated days saved by cutting | Included | Limited | Not included |
| Transparent, fixed cut-score formula | Included | Limited | Not included |
| No spreadsheet formulas or board setup required | Included | Not included | Not included |
Google Sheets and Trello can track a feature list, but you still have to build and maintain the cut-decision formula yourself. MVPHub applies one fixed formula automatically.