Enter your planned design scope
Count the screens, unique custom components, custom animations/transitions, and custom (non-standard) interactions in your current design plan.
MVP DESIGN COMPLEXITY SCORE
Design Cut
Enter the screens, components, animations, and custom interactions planned for your MVP and get a design-complexity score plus which categories to cut first.
- 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
We compare each category to an MVP norm
Each count is measured against a reasonable MVP ceiling for that category, then averaged into a single complexity score out of 100.
Get the categories to cut first
Categories furthest over their norm are ranked first, so you cut the highest-effort, lowest-validation-value design work before development starts.
Continue learning: How much design does an MVP actually need? · Choosing your MVP features for a first release
Frequently asked questions
Does Design Cut analyze my actual designs or Figma file?
No. Design Cut computes a complexity score entirely from the counts you enter — it does not connect to Figma, parse design files, or run any AI/LLM analysis. It is a scoping calculator, not a design auditor.
Where do the MVP norms come from?
The norms (roughly 12 screens, 15 custom components, 4 custom animations, 3 custom interactions) reflect typical scope for a validation-focused first release, not a hard limit. Treat them as a sanity check, not a rule.
What counts as a "custom" component or interaction?
Anything that isn't a standard pattern from your UI library or OS — a bespoke swipe gesture, a custom chart, a non-standard input control. Standard buttons, forms, and lists don't need to be counted.
My score is low — does that mean my product idea is bad?
No. A low score means the design scope is heavier than an MVP needs to validate the idea, not that the idea itself is flawed. Cutting scope now speeds up your first release without changing what you are trying to learn.
Should I cut the same categories every time?
No — re-run this after every design review. Scope typically creeps back into animations and custom interactions first since they are added incrementally and easy to miss in a screen count.
How We Compare
| Feature | MVPHub | Figma | FigJam |
|---|---|---|---|
| Numeric design-complexity score from your own counts | Included | Not included | Not included |
| Ranked list of categories to cut first | Included | Not included | Not included |
| Actually design and prototype the screens | Not included | Included | Limited |
| Team whiteboarding and scope brainstorming | Not included | Limited | Included |
Figma is where the screens actually get designed, and FigJam is where a team brainstorms and maps scope together. Design Cut runs earlier — a quick scope check before either of those tools to see if your design plan is already heavier than an MVP needs.
Related tools
Embed this tool
Add this tool to your site with the canonical iframe below. It remains hosted and maintained by MVPHub.