An MVP, or minimum viable product, is the smallest version of your product that real users can use to solve one real problem, built so you can learn whether they keep using it and will pay for it. Knowing how to build an MVP for a startup is mostly about deciding what not to build. MVPs rarely fail because of bad code. They fail because they are too big, too slow to reach users, or built around a problem nobody confirmed.
This guide walks through the process step by step: validating the problem, cutting features, choosing between no-code and custom development, picking a tech stack, planning a realistic timeline and budget in rupees, and deciding what to measure after launch. If you would rather have a team build it with you, see our MVP development services.
What an MVP Is, and What It Is Not
An MVP is not a cheap copy of your full product, and it is not a prototype. A clickable prototype tests whether people understand the idea. An MVP tests whether they use it when it costs them time or money.
It also does not have to start as software. Some of the most useful early tests are:
- Landing page test: describe the product, show a price, and measure how many visitors join a waitlist or pay a small deposit.
- Concierge MVP: deliver the service by hand to your first ten customers using WhatsApp, Google Sheets and phone calls, before automating anything.
- Single-workflow software: one core journey built properly, with everything else handled manually behind the scenes.
How to Build an MVP for a Startup in 9 Steps
1. Write down the problem and your riskiest assumption
Write one sentence: who has the problem, what it costs them today, and how they deal with it now. Then list your assumptions and mark the one that would sink the business if it turned out to be wrong. For most startups that is not whether the product can be built, but whether this customer will pay for it, and how often. Your MVP exists to test that assumption first.
2. Validate the problem before writing code
Speak to at least 15 to 20 people who fit your target customer. Ask about their current process, what they have already tried and what they spend on it. Do not pitch; you are collecting facts, not compliments. Strong signals are people who already pay for a workaround, people who ask when they can start, and people willing to pay a deposit or sign a letter of intent. Polite interest is not validation.
3. Cut the feature list with MoSCoW
List every feature you have imagined, then sort each one into Must have, Should have, Could have and Won't have (this time). Only the Must column goes into version one. A Must is a feature without which the core journey cannot be completed at all.
Here is an illustration for a hypothetical appointment and reminder app for small clinics:
| Priority | Features |
|---|---|
| Must have | Patient booking by link, clinic calendar, WhatsApp or SMS reminder, simple admin login |
| Should have | Online payment of the consultation fee, rescheduling by the patient |
| Could have | Dashboards for several doctors, analytics, patient ratings |
| Won't have (this time) | Native mobile apps, medical records, multi-branch chains, AI features |
A useful test: if your team can do something by hand for the first 50 customers, it is not a Must.
4. Decide between no-code and custom development
No-code tools such as Bubble, FlutterFlow, Glide or Softr can put a working product in front of users within days. Custom development takes longer but gives you full control. Neither is right for every startup.
| Factor | No-code or low-code | Custom development |
|---|---|---|
| Time to first version | Days to a few weeks | Usually 6–10 weeks |
| Upfront cost | Lower | Higher |
| Complex logic and integrations | Limited; workarounds get messy | Built to fit |
| Running cost as users grow | Platform fees can rise steeply | Mostly hosting, which grows gradually |
| Ownership | Tied to the platform; moving later often means a rebuild | You control the code and data |
| Investor and enterprise due diligence | Sometimes questioned | Easier to pass |
Choose no-code when you mainly need to test demand and the workflow is simple. Choose custom when the technology is the product (a SaaS platform, marketplace or fintech tool), when you need integrations such as payment gateways, Tally or a CRM, or when you handle sensitive personal data and need control over where it lives.
5. Pick a boring, proven tech stack
Choose your stack for speed of development, availability of developers in India and low running cost, not novelty. A sensible default for most startups:
- Web first. A responsive web app reaches users on every device without app store reviews. Add Flutter or React Native apps once usage proves the need.
- Backend: a mainstream framework such as Laravel, Node.js or Django, with PostgreSQL or MySQL.
- Frontend: React or Vue, or server-rendered pages if the product is mostly forms and dashboards.
- Hosting: a managed cloud setup in an Indian region, with automated backups from day one.
- Buy, do not build: payments through an Indian payment gateway, OTP and WhatsApp messages through an established provider, and email through a transactional email service.
If you are building subscription software, plan multi-tenancy, which keeps each customer's data separate, from the start. Retrofitting it later is expensive. Our SaaS MVP development work is built around this.
6. Plan a realistic timeline
A typical custom MVP takes 6 to 10 weeks from signed scope to first users. A common shape:
| Weeks | Work | Output |
|---|---|---|
| Week 1 | Discovery, user journeys, MoSCoW sign-off, clickable prototype | Approved scope and screens |
| Weeks 2–7 | Build in one-week sprints with a demo every week | Working features on a staging site |
| Week 8 | Testing, security basics, performance checks | Release candidate |
| Weeks 9–10 | Beta launch to a small group, fixes | Live product with real users |
Projects usually slip because of scope changes and slow feedback, not coding. Agree a change process before you start: anything new goes into the backlog for the next version unless something of equal size comes out.
7. Set a budget that includes running costs
The ranges below are indicative for the Indian market. They are not survey figures, and scope moves them a lot.
- No-code MVP built by a freelancer or agency: roughly ₹50,000 to ₹2 lakh, plus monthly platform fees.
- Custom web MVP with one core workflow, an admin panel and payments: roughly ₹1.5 lakh to ₹5 lakh.
- Custom web plus mobile apps, several user roles and integrations: roughly ₹4 lakh to ₹12 lakh or more.
At EthicsComputer, custom software and MVP projects start from ₹45,000 + 18% GST for a tightly scoped build, with the final quote after scoping. You can compare packages on our pricing page.
Budget for life after launch too: hosting, third-party charges for SMS, WhatsApp and payment gateway fees, and ongoing fixes and improvements. A common rule of thumb is to set aside 15 to 20 per cent of the build cost each year for maintenance, and more if you are changing the product quickly.
8. Decide your metrics before launch
Set up analytics before the first user signs up, and pick a few numbers that tell you whether the product is working:
- Activation: the share of sign-ups who complete the core action. For the clinic app, that is a clinic sending its first reminder.
- Retention: how many users active in week one are still active in week four. Retention that holds steady, even at a modest level, is the strongest early signal.
- Willingness to pay: conversion from trial to paid, or deposits collected.
- Time to value: how long a new user takes to get the first useful result.
- Direct feedback: short calls with active users and with those who stopped.
Downloads, page views and total sign-ups feel encouraging but rarely tell you whether to keep going.
9. Launch small, then iterate on evidence
Launch to a small group first, perhaps 20 to 50 users you can speak to directly. Ship improvements weekly or fortnightly. Before launch, write down which results would make you continue, change direction or stop, and review them after six to eight weeks of real use. Deciding this in advance keeps you honest when the numbers come in.
Common Mistakes When Building an MVP
- Building for everyone. An MVP for all small businesses serves none of them well. Start with one customer type and one sector or city.
- Too many user roles. Each role multiplies screens, permissions and testing. Start with the customer and one admin.
- Polishing design before proving use. Clean and usable is enough. Polish comes after retention.
- Skipping security basics. Even an MVP needs proper access control, limits on OTP requests and careful handling of personal data. A short security review before launch costs far less than a leak; our guide on what VAPT is and when you need it explains the options.
- No analytics at launch. Without data you will argue opinions instead of reading results.
- A weak development contract. Make sure it gives you ownership of the source code and IP, access to the code repository from day one, and proper handover documentation.
- Treating the MVP as either final or disposable. Build the core cleanly enough to extend, and accept that some parts will be rewritten.
After the MVP: Planning the Next Stage
Once you see steady retention and paying users, the work shifts from learning to scaling: performance, automated testing, monitoring, more roles and integrations, and a proper product roadmap. Our article on the technology roadmap for startups, from MVP to enterprise covers that stage in detail. If your MVP is a subscription product, our SaaS development team can take it from a validated MVP to a full multi-tenant platform.
FAQs
How long does it take to build an MVP?
Most custom MVPs take 6 to 10 weeks from signed scope to first users: about a week of discovery and prototyping, five to six weeks of building in weekly sprints, then testing and a small beta launch. A no-code MVP can be faster, while mobile apps or complex integrations make it longer.
How much does it cost to build an MVP in India?
It depends on scope. As indicative market ranges, a no-code MVP often costs ₹50,000 to ₹2 lakh, a custom web MVP with one core workflow ₹1.5 lakh to ₹5 lakh, and web plus mobile apps with several user roles ₹4 lakh to ₹12 lakh or more. EthicsComputer's custom software and MVP projects start from ₹45,000 plus 18% GST, with the final quote after scoping.
Should I build my MVP with no-code tools or custom code?
Use no-code when you mainly need to test demand and the workflow is simple. Choose custom development when the technology is the product, when you need integrations such as payment gateways, a CRM or Tally, or when you handle sensitive personal data and need full control over the code and data.
How many features should an MVP have?
Only the features needed to complete one core user journey from start to finish. Sort your feature list with MoSCoW and build only the Must haves. If your team can handle something by hand for the first 50 customers, it can wait.
What should I measure after launching an MVP?
Focus on activation, meaning users who complete the core action, retention from week one to week four, willingness to pay, and time to first value, along with direct feedback from active users and those who stopped. Downloads and total sign-ups alone rarely tell you whether to continue.
If you have validated the problem and want a team to scope and build the first version with you, our MVP development services for startups cover discovery, build, launch and iteration. Contact us to book a scoping call, or WhatsApp us on +91 90532 10052.
