In this article
MVP stands for minimum viable product. It is the smallest version of your product that lets real people do the one main thing it is meant for. It is not a rough demo, and it is not a poor-quality product. It is a small product that works, built to answer one question: will real people use this?
You learn more from real users on a small product than from months of planning. This article explains what to put in a first version, what to leave out, and how to decide.
What an MVP is for
A first version has one job: to teach you what you cannot know in advance. Who really uses the product? What do they do first? Where do they get stuck? Would they pay? A smaller product reaches users sooner, so you start learning sooner, and you spend less before you know whether the idea works.
What to include
One clear problem and one type of user. Write both in a single sentence. If you cannot, the scope is too wide.
The main journey, from start to finish. Example only: for an appointment app, a customer finds a free time, books it and gets a confirmation. Build that one path well.
Sign-in and basic security. People need accounts, and their data must be protected from day one.
Payment, but only if the product needs it to deliver value. Otherwise collect payment by hand at first, for example by invoice.
A simple admin view, so you can see what is happening and fix mistakes without waiting for a developer.
Basic measuring and a way to hear from users. Know how many people sign up and how many finish the main journey, and give users an easy way to send feedback.
Safety basics: backups, error alerts and tests on the main journey. A small product can still break, and a broken first version loses the trust you are trying to earn.
Privacy basics. If your product handles personal data, a data protection law probably applies: the law of each country where your users live, such as the GDPR in the European Union or India's Digital Personal Data Protection (DPDP) Act. The main duties for businesses under the DPDP Act start on 13 May 2027. Put a clear privacy notice and a consent step into the first version, instead of adding them later.
What to leave out
Extra user types and complicated permissions.
Many connections to other tools.
Apps for every device, when one web app can do the job.
Advanced reports and dashboards.
Rare cases. Handle them by hand while there are few users.
Polish beyond what is needed. Screens must be clear and easy to use. They do not need to be fancy.
Features that someone might want one day.
A simple test for every feature
Ask: if we remove this, can a user still complete the main journey? If yes, move it to a 'later' list. Keep three lists: needed now, later, and not planned. Keep cutting until the first version feels a little uncomfortably small. That is usually about right.
How to run the build
Decide the goal before you start, and how you will measure it. Example only: 'Ten customers book an appointment through the app in the first month.'
Ask for a working demo every week, so you can correct course early.
Put the product in front of a few real users before the official launch, and watch where they struggle.
Agree in advance what result means keep going, what means change direction, and what means stop.
After launch
Talk to your users. Watch what they do, not only what they say. Fix whatever blocks the main journey first. Then add the one feature users ask for most, and nothing more until you have learned from it. Your 'later' list is where the other ideas wait.
Common mistakes
Trying to build for everyone at once.
Adding just one more feature before launch, again and again.
Launching with no way to measure or hear from users.
Treating the MVP as a throwaway. It can be small and still be secure and reliable.
What to do next
If you have an idea and want to know what a first version would contain, send us your requirement. We reply with a written proposal showing scope, timeline and quote, at no cost until you agree. While we build, you get a demo and a written update every week, and you own the code, the accounts and the documentation.
Sources: Digital Personal Data Protection Act, 2023, and notification G.S.R. 843(E) of 13 November 2025, Ministry of Electronics and Information Technology (meity.gov.in). Regulation (EU) 2016/679, the General Data Protection Regulation (eur-lex.europa.eu).