Lizzard Solutions

MVP Feature Prioritization: Decide What to Build First

· Lizzard Solutions
MVPProduct ManagementStartupsCustom SoftwarePrioritization

By Nemanja Vukmirović, Lizzard Solutions. Last updated 18 November 2026.

Your feature list has 40 items, the budget covers maybe ten, and every item feels important. So the MVP grows, the launch slips by months, and when real users finally arrive they use three of the features you built.

This guide shows how to do MVP feature prioritization in practice: two proven frameworks, a simple scoring sheet you can copy, a worked example for a booking app, and the mistakes that quietly double MVP budgets.

TL;DR

  • Start from one core user flow, not from a feature list. Anything outside that flow needs a strong reason to be in version one.
  • Use MoSCoW to agree on scope with stakeholders and a value-to-effort score (or RICE) to rank what is left.
  • Write down every "Won't have now" item. A visible parking lot makes it much easier to say no without losing ideas.

What is MVP feature prioritization?

MVP feature prioritization is the process of deciding which features go into the first usable version of a product, by ranking each idea on how much it helps users complete the core task against how much it costs to build, and deliberately postponing everything else.

The goal is not the smallest product, but the smallest product that still delivers real value and lets you learn. Atlassian's MVP guide describes the same idea: enough features to attract early users and validate the product. For the full process from idea to launch, read our MVP development guide for startups.


Step 1: define the one core flow

Before you score anything, write a single sentence: "A [user] can [complete task] so that [result]." Then list the minimum steps a user takes to get there.

Example

For a beauty salon booking app: "A client can book a free time slot with a chosen staff member so that the salon does not have to answer calls." Steps: choose service, choose staff, choose time, confirm with name and phone, get a confirmation.

Every feature now gets one question: does the core flow break without it? If not, it competes for a place later.

Action for today: write your core flow sentence and keep it at the top of your feature document.


Framework 1: MoSCoW for agreeing on scope

MoSCoW sorts features into four groups. It comes from the DSDM agile method, and ProductPlan's MoSCoW overview explains it well:

GroupMeaningRule of thumb
Must haveThe core flow fails without itIf you can launch without it, it is not a Must
Should haveImportant, but a workaround existsPlan it right after launch
Could haveNice to have, small impactOnly if time and budget remain
Won't have (this time)Agreed to be out of this versionWrite it down so nobody re-adds it silently

Key takeaway: MoSCoW is a conversation tool. It works best when founders, developers and the client agree on the Musts in one meeting.


Framework 2: value vs effort scoring (and RICE)

MoSCoW tells you what is in. A score tells you the order. The simplest version: rate each feature 1 to 5 for user value and 1 to 5 for effort, then divide value by effort. Higher is better.

If you have usage data, use RICE instead: Reach × Impact × Confidence ÷ Effort. Intercom, who created RICE, explains each factor and the scales they use. RICE is more precise, but for a product that has no users yet, reach and confidence are often guesses, so the simple score is usually enough.


Worked example: a booking app MVP

Here is the salon booking app scored with the simple method. The scores are our example estimates for illustration, not measured data:

FeatureValue (1-5)Effort (1-5)Value ÷ effortMoSCoW
SMS or email reminders422.00Must
Online booking with time slots531.67Must
Staff calendar sync331.00Should
Online card payment340.75Should
Client accounts with login230.67Could
Loyalty points240.50Won't (now)
Admin reports dashboard240.50Won't (now)

Result: booking and reminders go into version one. Staff calendar sync and card payment follow right after launch. Client accounts, loyalty points and reports wait until real users ask for them, because guests can book with a name and phone number.

Watch out

Effort scores depend on the technology and the team. Ask your developer to score effort, and score value yourself from customer conversations. Mixing the two roles is how optimistic estimates get in.

Action for today: copy the table, replace the features with yours, and score value before you ask anyone about effort.


How to run a 60-minute prioritization session

  1. 10 minutes: read the core flow sentence aloud and agree on it. If people disagree here, stop and fix this first.
  2. 15 minutes: put every feature on a card or sticky note and sort them into Must, Should, Could and Won't.
  3. 15 minutes: the founder scores value for each Must and Should, the developer scores effort, separately.
  4. 10 minutes: calculate value divided by effort, sort, and challenge any Must with a low score.
  5. 10 minutes: write the final list, the parking lot and the date of the next review into one shared document.

Action for today: book this session with everyone who has a say in the product, and send the core flow sentence in advance.


Common prioritization mistakes

  • Everything is a Must. If more than about half the list is Must, the core flow is not defined yet.
  • Building admin tools first. Internal dashboards rarely decide whether users come back. A spreadsheet export often covers the first months.
  • Copying competitors' feature lists. Mature products show where they ended up, not where they started.
  • Ignoring hidden effort. Login, payments and integrations bring security, testing and maintenance work. Our article on custom software cost factors explains why.
  • Never revisiting the list. Re-score after every round of user feedback. Shortcuts taken for speed also build up as technical debt, so plan time to clean up.

Turn the list into a brief

Once priorities are agreed, put the core flow, the Must and Should list and the parking lot into one document. Our software project brief template gives you the structure, so any development partner can estimate the same scope.


Frequently asked questions

How many features should an MVP have?

There is no fixed number. An MVP should have the features needed for one complete core flow that delivers value, plus basic login, data handling and analytics if the flow needs them. For many products that is a handful of features, not dozens.

What is the difference between MoSCoW and RICE?

MoSCoW sorts features into Must, Should, Could and Won't groups and is mainly used to agree on scope. RICE gives each feature a numeric score from reach, impact, confidence and effort, which is useful for ranking when you have data about users.

Who should prioritize MVP features?

The founder or product owner decides, based on customer conversations. Developers estimate effort, and the people who will use the product help judge value. The final list should be agreed in writing before development starts.

When should I re-prioritize?

After every release or round of user feedback. Real usage data usually shows that some Should items matter more than expected and some Musts are barely used.

Planning a product? See our custom software and MVP development services.

Scope your MVP with us

Send us your feature list. We will help you define the core flow, score effort honestly and agree on a version one you can launch. Book a free consultation.

Book a free consultation