App development · 2027 breakdown

MVP development cost:
how lean is too lean?

An MVP costs anywhere from almost nothing to about ₹15 lakh in India, depending on what you are testing. A landing page, video or manual 'concierge' test costs mostly your time; a no-code MVP ₹50,000–3 lakh; a real cross-platform app with one core flow ₹3–15 lakh. It is too lean when it no longer solves the problem well enough to produce honest evidence.

By , FounderUpdated 6 min read

Share

Quick answer: How much does MVP development cost for a startup?

  1. Demand test (landing page, video, pre-orders) — ₹0–50,000.
  2. No-code MVP — ₹50,000–3 lakh, 2–6 weeks.
  3. Software MVP (one core flow, cross-platform, light backend) — ₹3–15 lakh, 6–12 weeks.
  4. Too lean = users cannot get the core job done. Too fat = more than 12 weeks before anyone uses it.

Key takeaways

  • Price the MVP by the question it must answer, not by a feature list.
  • The core flow must be good. Cut everything around it — settings, edge cases, admin polish — before you cut the core.
  • Spend a slice of the MVP budget on research and analytics; without them you build cheaply and learn nothing.
  • No-code is often the right first build; plan the rebuild if it works.
  • An MVP heading past three months or ₹15 lakh has usually stopped being minimal.

The word "minimum" does a lot of damage. Founders hear it and cut the wrong things — the core experience — while keeping the features they are attached to. Agencies hear it and sell a ₹2 lakh "MVP package" that no user would choose over a WhatsApp group. The right question is not "what is the cheapest app I can build?" It is "what is the cheapest way to get an honest answer?"

How much does MVP development cost for a startup? At a glance: Demand test; No-code MVP; Software MVP; Too lean.
At a glance: How much does MVP development cost for a startup?

The short answer: what an MVP costs

MVP development cost in India by approach (Science of Apps estimates, before GST)
MVP approachWhat you buildCost (India, 2027)Time
Demand testLanding page, explainer video, waitlist or paid pre-orders₹0–50,0001–2 weeks
Concierge or manual MVPYou deliver the service by hand to 5–20 customersMostly your time2–6 weeks
No-code MVPThe core flow in no-code tools with real users₹50,000–3 lakh2–6 weeks
Software MVPOne core flow, cross-platform, login, light backend, analytics₹3–15 lakh6–12 weeks
"MVP" with two or more user rolesMarketplace or multi-sided product, scoped tightly₹12–30 lakh10–16 weeks
Bar chart: MVP development cost in India by approach (Science of Apps estimates, before GST) — Demand test: 1–2 weeks; Concierge or manual MVP: 2–6 weeks; No-code MVP: 2–6 weeks; Software MVP: 6–12 weeks; "MVP" with two or more user roles: 10–16 weeks.
MVP development cost in India by approach (Science of Apps estimates, before GST)

Agency rates behind these estimates follow the bands Indian teams publish on Clutch, where the typical app development company charges $25–49 an hour2. Freelancers usually charge less; premium studios more.

Price the question, not the feature list

Eric Ries's definition of an MVP is about learning — the most validated learning for the least effort1. So start the budget from the question:

Matching the MVP to the question
The question you need answeredThe cheapest honest test
Do people want this at all?Landing page with a clear offer and a sign-up or pre-order
Is the outcome valuable enough to pay for?Concierge: deliver it manually and charge
Will people use it repeatedly on their own?No-code or software MVP with analytics
Will they pay for it as software?Software MVP with a real paywall
Can both sides of a marketplace work together?Manual matching first, then a two-sided MVP

What to keep and what to cut

Comparison — Keep (do not cut): The core job, done well enough that a real user would choose it; The minimum trust signals: clear pricing, a privacy notice, working payments if you charge; Analytics on the core funnel, so you can measure the result; A way to reach users: in-app feedback, WhatsApp, e
Keep (do not cut) vs Cut (until it is proven)

Keep (do not cut)

  • The core job, done well enough that a real user would choose it
  • The minimum trust signals: clear pricing, a privacy notice, working payments if you charge
  • Analytics on the core funnel, so you can measure the result
  • A way to reach users: in-app feedback, WhatsApp, email

Cut (until it is proven)

  • Settings, profiles beyond the basics and multiple user roles
  • Admin dashboards (use a spreadsheet or the database console)
  • Edge cases that affect a tiny share of users
  • Onboarding animation, theming and dark mode
  • Native apps on both platforms if one or a web app will do

How lean is too lean?

An MVP is too lean when it stops measuring demand and starts measuring your shortcuts.

And it is too fat when:

  • more than 12 weeks pass before a real user touches it,
  • the budget passes ₹15 lakh for a single core flow,
  • or you cannot name the one assumption it tests.

Budget split for a ₹8 lakh software MVP

How to split a ₹8 lakh MVP budget (Science of Apps estimates)
LineShareWhy it matters
Discovery and user interviews8–10%Points the build at the real problem
UX and UI design, prototype test12–15%Five-user tests catch most usability problems early3
App and backend development55–60%The core flow, done well
Testing on real devices8–10%Bugs distort the result
Analytics, store setup and launch6–8%You need to measure, and to ship
Bar chart: How to split a ₹8 lakh MVP budget (Science of Apps estimates) — Discovery and user interviews: 8–10%; UX and UI design, prototype test: 12–15%; App and backend development: 55–60%; Testing on real devices: 8–10%; Analytics, store setup and launch: 6–8%.
How to split a ₹8 lakh MVP budget (Science of Apps estimates)

Remember the store rules. New Google Play personal developer accounts must run a closed test with 12 testers for 14 days before production access4 — useful for an MVP anyway, but plan it.

No-code first, then code?

No-code tools are often the smartest first build: fast, cheap and good enough to test real usage. Their limits show up later — complex logic, performance, scale, data ownership and vendor lock-in. A sensible path:

Diagram of 3 steps for no-code first, then code?: 1. Test demand with a landing page or concierge service.; 2. Build the core flow in no-code and get real, repeat users.; 3. When usage proves the idea, rebuild the core in code, keeping what….
No-code first, then code?
  1. Test demand with a landing page or concierge service.
  2. Build the core flow in no-code and get real, repeat users.
  3. When usage proves the idea, rebuild the core in code, keeping what users loved and dropping what they ignored.

How we estimated these numbers

These ranges are Science of Apps editorial estimates for MVPs built by Indian agencies or experienced freelancers, consistent with the simple-MVP band (₹3–8 lakh) in our app development cost guide, extended for multi-role products. Rates follow Clutch's published bands2. Figures are before GST and reviewed every six months.

Key terms, defined

MVP — the smallest product that tests your riskiest assumption with real users. Concierge MVP — delivering the service manually before automating it. No-code — building software with visual tools instead of programming. Core flow — the main path a user takes to get the product's value. Pre-order — payment before the product exists, the strongest demand signal.

Frequently asked questions

How much does it cost to build an MVP in India?

A software MVP — one core flow, cross-platform, with login and a light backend — costs about ₹3–15 lakh with an Indian agency or experienced freelancers and takes 6–12 weeks. A no-code MVP costs ₹50,000–3 lakh. Demand tests such as a landing page or video cost mostly your time.

What should an MVP include?

Only what your test needs: the core job done well, sign-up if you must identify users, analytics to measure the result, and a way for users to give feedback. Leave out settings, multiple user roles, advanced search, admin polish and anything that does not affect the answer to your question.

How do I know if my MVP is too lean?

If users cannot complete the core task, cannot trust the product with their data or money, or leave because of bugs rather than because they lack need, your MVP is too lean. The test then measures your build quality, not demand.

Is no-code good enough for an MVP?

Often, yes. No-code tools can test demand and workflows quickly and cheaply. They struggle with complex logic, scale and performance, and some lock you in. If the MVP succeeds, budget to rebuild the core in code once you know what users need.

Should I build an MVP with an agency or a freelancer?

A freelancer suits a small, well-specified MVP you can manage yourself. An agency suits founders who need design, testing and project management included. Either way, insist on code in your repository and a written assignment of intellectual property.

How long does it take to build an MVP?

Demand tests take one to two weeks, no-code MVPs two to six weeks, and software MVPs six to twelve weeks including design and testing. If yours is heading past three months, cut scope until it is minimal again.

Sources

  1. Eric Ries, Startup Lessons Learned — Minimum viable product: a guide (2009)
  2. Clutch — Mobile app development pricing guide
  3. Nielsen Norman Group — Why you only need to test with 5 users
  4. Google Play Console Help — App testing requirements for new personal developer accounts
  5. Checked October 23, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Before you build

Spend your budget on what users want.

A behavioral UX audit of your app or SaaS product: why users hesitate, stall and leave, and a prioritized fix list. Fixed price, 2–4 weeks.

Free certification

Turn what you know into a credential.

Free, test-based UX, UI and product certifications. Answer real product scenarios, graded on our server, and earn a founder-signed certificate anyone can verify and you can add to LinkedIn.

  • Credential ID
  • QR verification
  • LinkedIn-ready
Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 74 pages

Get Laws of UX by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy

Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 90 pages

Get 100+ Paywalls, Decoded by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy