The short answer
An MVP is the smallest product that lets real users complete the one job your business exists for — and lets you learn whether they will pay for it. For most Indian startups that means one city, one core flow done well, the partner or ops side done just enough, and a launch in about twelve weeks.
Below is how to decide what goes in, what waits, a week-by-week plan, and the mistakes that most often burn a first budget.
What an MVP is — and what it is not
An MVP is not a cheap version of the full product. It is a complete version of a small product. A food delivery MVP that takes orders but cannot reliably get them to the customer is not minimal; it is broken.
- It is real. Real users, real payments, real deliveries or bookings.
- It is narrow. One city, one segment, one core flow.
- It is measurable. You know before launch which two or three numbers will tell you it is working.
- It is built to be changed. Clean code and a design system, so version two is an edit, not a rewrite.
A clickable prototype is not an MVP, but it is often the right step before one. It costs far less and can answer “would people want this?” in two weeks.
Find the one flow you must prove
Write your product as a single sentence about one user: “A family in Pune can order tomorrow's milk by 10 pm and find it at the door by 7 am.” That sentence is your MVP. Everything that does not serve it waits.
Then list every person who touches that flow. For the milk example: the customer, the delivery person, and whoever plans tomorrow's routes. Each needs something — but not the same depth. The customer gets a polished app. The delivery person gets a simple run sheet. The planner might start with a dashboard and an export.
Our concepts show this split in practice: Milvara (dairy subscriptions), Zippora (quick commerce) and Cliniqo (clinic OPD) each give the customer side the polish and keep the operator side lean and fast.
What to cut from version one
| Usually cut | Usually keep |
|---|---|
| Referral codes and wallets | A fast, reliable checkout with UPI |
| Ratings and reviews | Clear order or booking status |
| Multiple cities | One city, one zone, done well |
| iOS, if your users are mostly on Android | Testing on real mid-range Android phones |
| A custom admin for every task | A simple dashboard plus exports for the rest |
| Every language at once | The one or two your first users actually speak |
| Complex recommendation engines | Good search and sensible defaults |
Cut features, never trust. In India, a clear price, a working payment and a visible status update decide whether someone orders a second time.
A 12-week plan, week by week
| Weeks | Phase | What you should see |
|---|---|---|
| 1 | Category deep-dive | Your market mapped, the core flow agreed, a one-page concept and a name shortlist |
| 2–3 | Brand system | Logo, colour, type and voice, coded as design tokens |
| 3–6 | Core flow build | The customer flow working end to end on realistic data |
| 6–9 | Partner and ops sides | Staff or partner app and the dashboard, wired to the same data |
| 9–10 | Payments, notifications, polish | Live UPI and cards, SMS or WhatsApp updates, edge cases |
| 10–12 | Test, launch, hand over | Store listings, a soft launch with real users, code and docs handed over |
You should be able to click through working screens by week three or four. If a team shows you only documents and static designs for the first six weeks, ask why. See how this runs in detail on our process page.
What an MVP costs in India
Ballpark ranges with a small studio, before 18% GST:
- Clickable prototype (concept sprint, about two weeks): a fraction of the build cost, often ₹1.5–5 lakh depending on depth.
- One-sided MVP (customer app plus a basic admin): roughly ₹5–15 lakh.
- Two-sided MVP (customer app, partner app, dashboard): roughly ₹12–30 lakh.
- Marketplace MVP with live maps and payouts: roughly ₹25–50 lakh.
For a fuller breakdown, see how much it costs to build an app in India. Leave 20–30% of your budget for the months after launch — that is when you learn the most and need to change things quickly.
Decide what you will measure before launch
An MVP exists to answer a question. Write the question down, and the numbers that answer it, before the first user signs up. Otherwise every result looks like progress.
- Completion. Of the people who start the core flow, how many finish it? For an order, from cart to paid. For a booking, from slot picked to confirmed.
- Repeat use. How many come back within a week or a month? For most consumer products this matters more than first-week signups.
- Fulfilment. On the operator side: orders delivered on time, bookings kept, partner acceptance rate.
- Cost to serve. What one order, ride or visit costs you once delivery, payment fees and support are counted.
- Qualitative signal. Ten conversations with real users, written up, every two weeks.
Build the tracking for these into the product from the start — a simple event log and a dashboard view is enough. Adding analytics after launch means losing the first, most informative weeks of data.
Mistakes that waste a first budget
- Designing for metro iPhone users only. Test on a mid-range Android phone on 4G. That is closer to most of your users.
- Ignoring cash and COD. In many categories, a share of customers will want to pay on delivery. Decide early how you handle it.
- Skipping the ops side. A beautiful customer app with an operations team running on spreadsheets and phone calls breaks the moment orders grow.
- Launching everywhere at once. One area lets you fix problems before they reach thousands of people.
- Building what investors asked about, not what users need. Investors want proof of demand. Real usage is the proof.
- Not owning your code. If the team disappears, you should be able to hand the repository to someone else the next day.
- Forgetting compliance. Personal data, payments and health information have rules. See the DPDP Act checklist.
Prototype first, then build
If you are raising money or are not sure of the core flow, a two-week concept sprint is often the smartest first spend. You get a name and brand direction, a clickable prototype of the core flow, and pitch-ready screens. Show it to twenty potential users before you write production code.
At The Saral, a concept sprint takes two weeks and a full product build takes eight to twelve weeks. Every project gets a fixed quote within 48 hours of a brief, and all code and designs are handed over in full. Read about our services, see startups we work with across India, or send a brief.
Questions people ask
How much does an MVP cost in India?
With a small studio, a one-sided MVP — a customer app plus a basic admin — typically costs ₹5 lakh to ₹15 lakh. A two-sided MVP with a partner app and dashboard usually runs ₹12 lakh to ₹30 lakh. Marketplaces with live tracking and payouts cost more. A clickable prototype first costs far less and reduces risk.
How long does it take to build an MVP?
A clickable prototype takes about two weeks. A working MVP with real users, payments and an ops side typically takes eight to twelve weeks with a focused team. Products with several sides, live maps or many integrations take longer. Changing scope midway is the most common cause of delay.
Should my MVP be an app or a website?
It depends on how often people will use it and whether you need phone features. Daily or weekly use, notifications, tracking or a staff tool point to an app. Occasional use, discovery through Google, or a tight budget point to a website or installable web app first. Many startups launch the customer side on the web and the partner side as an app.
Do I need a technical co-founder to build an MVP?
Not necessarily. Many founders build their first version with a studio and hire engineers once the product has users. What you do need is someone who understands the product deeply, makes decisions quickly, and owns the code, accounts and documentation, so a future in-house team can take over without a rebuild.
