I searched “MVP development cost in India” on 14 October 2026 and read what came back. Page one offered a range from about $15,000 to over $150,000. The India-specific figures clustered between $15,000 and $70,000. Quoted hourly rates ran from $20 to $70. Not one page showed its arithmetic.
That spread is not a market. It is a stack of sales pages. So this one does something else: it hands you the method, tells you what the Indian tax layer actually adds, and declines to print a price for a product nobody has described yet.
The short answer
An MVP costs team shape multiplied by weeks, plus 18% GST if you are an Indian company buying from an Indian company. The rest is a negotiation about scope. “MVP” is not a fixed quantity of work. It is whatever you agreed to build, and the agreement is the price.
If you want one sentence to carry into a vendor call: a focused first version, two or three engineers, eight to twelve weeks. That is the shape most early products actually need. Price that shape at the rate you are quoted and you have a floor. A quote well below it is missing scope you will meet in week four.
What this page will not do is quote you a number. Any figure printed here without seeing your scope would be a sales figure dressed up as information, and the pages ranking above this one have already done that.
Why every published number is different
Four reasons. Understanding them is worth more than any of the figures.
They are pricing different products. A listings app with email login and a payment gateway is not the same build as a health product with audit logs and role-based access. Both get called an MVP.
Some quote the build, some include discovery. Deciding what to make takes weeks. If a quote excludes that phase, the phase does not disappear. You pay for it in your own time, or later in rework.
A low rate is not a low cost. A cheaper hour that needs three times as many hours is more expensive. Compare delivered scope, never the rate card. A blended rate hides the senior-to-junior mix, which is the most useful thing on the page to ask about.
“MVP” has stopped meaning minimum. Most quotes you receive are not for a minimum viable product. They are for the product you described, which is usually version 1.0 of the entire idea.
Work out your own number before you ask anyone
Four steps, half an hour, a notebook.
- Count user types, not features. One user type is one set of screens, one permission model, one onboarding path. Two is closer to double than to plus fifty percent.
- Write the one sentence that must be true for this to be worth continuing. One sentence. If it takes two, you have two products.
- Cross out every feature that sentence does not need. This is the whole exercise. It is the only lever that moves cost by multiples rather than percentages.
- Multiply. Ask for two numbers: the blended day rate and the number of person-days. Multiply them, then add GST. A vendor who will not give you both has made their total impossible to check, which is usually the intention.
Do this before the first call and the conversation changes shape. You stop asking what an MVP costs and start asking why this one is 140 person-days.
The Indian layer nobody puts in the quote
This is where a page about building in India should earn its keep, and most do not.
GST is 18%, and it may not be a cost. Software development services sit under SAC 9983 and attract 18% GST. If your company is GST-registered in India and buying this for your business, that 18% is normally input tax credit rather than money burned, but only if the invoice carries your correct GSTIN and the right SAC code. Confirm the current rate on the CBIC rate finder and confirm the credit position with your CA. Then ask every vendor, in writing, whether the quote is inclusive or exclusive of GST. Two quotes are not comparable until you know.
If you are paying from outside India, the arithmetic differs. Export of services is treated as zero-rated under GST subject to conditions, so an Indian vendor invoicing a foreign entity should not normally be adding 18% to a USD quote. If one is, ask why before you argue about the rate.
TDS changes your cash flow, not your price. An Indian company paying an Indian vendor withholds tax at source. Whether that falls under section 194C or 194J is a question for your accountant, and the answer changes what leaves your bank account this month. Settle it before the first invoice rather than after it.
Startup India recognition is free, and founders skip it. DPIIT recognition is open to a private limited company, a registered partnership firm or an LLP, within ten years of incorporation, with turnover under ₹100 crore in any previous financial year, working on innovation or a scalable business model, and not formed by splitting up or reconstructing an existing business. Recognition is what makes you eligible to then apply for the three-year profit deduction under section 80-IAC, via a separate Inter-Ministerial Board certificate. The criteria and the current application route are on startupindia.gov.in. None of this reduces your build cost. It changes what the build is worth once it works.
Ask where the team actually sits. Rates differ by city and so does attrition, and a quote that averages both without telling you has made a decision on your behalf.
What actually moves the number
In rough order of impact on a quote:
- Number of user types. The most expensive line item nobody prices separately.
- Payments, KYC, anything regulated. The integration is a week. Edge cases, reconciliation and failure states are the rest of the month.
- Real-time anything. Live tracking, chat, collaborative editing. Each one adds infrastructure that somebody has to operate, not merely write.
- Web, mobile, or both. Both is closer to twice the work than to slightly more work.
- Admin tooling. Almost always cut from the quote. Almost always needed by week three of real use. If it is not in there, ask who will be running database queries by hand, and when.
- Multi-tenancy. If you are selling to businesses you are building multi-tenant SaaS, and the data isolation decision you take in week one is expensive to revisit in month six.
- AI features. An assistant answering from your own documents is a different build from a model you train. Ask which one is being quoted. If that is the core of the product rather than a feature on top, our AI development work and the detailed breakdown of AI chatbot development cost in India go through those cost drivers properly.
Three decisions that cost more than the rate card
Scope, settled before any code. The expensive mistakes in an MVP happen in the conversation, not in the editor. Every week spent cutting scope pays itself back several times over. Most of what MVP development for startups consists of is that argument, held early and in writing.
Who owns the repository and the cloud account. You do, from the first commit, in your own organisation. If a vendor holds either, you have not bought software. You have rented a dependency. Insisting on this at the start costs nothing and fixing it later is painful.
What happens on the last day. Ask what you receive at handover: repository access, deployment instructions, environment variables, a runbook, a named person for the first month. A build you cannot deploy without the people who built it is not finished.
What a quote should contain
- A written scope listing what is excluded, not only what is included.
- A milestone schedule where every milestone produces something you can click.
- Named engineers with their time allocation, not “a team of five”.
- A staging environment you can use throughout, not a demo at the end.
- Repository and cloud ownership in your name from day one.
- GST treatment stated explicitly, and a written change process. Scope will change. The only question is whether that is a conversation or an invoice.
Red flags
- A fixed price quoted before any scoping conversation. Nobody can price an unseen scope. They have either padded it or they will come back for more.
- A quote with no exclusions list.
- A blended rate with no senior-to-junior split behind it.
- “Let us start with the design.” Design that precedes a scope decision is work you will redo.
- An estimate that matches your budget exactly, whatever your budget happened to be.
Frequently asked questions
How much does an MVP cost in India in 2026?
Published vendor estimates on page one of that search, read on 14 October 2026, span roughly $15,000 to over $150,000, with the India-specific figures clustering between $15,000 and $70,000. Treat all of them, including anything on this page, as vendor estimates rather than market prices. Scope sets the figure, not geography. The figures are quoted in USD because the sources are; ask for quotes in the currency you will actually pay in, and ask whether tax is included.
How long does it take to build an MVP?
Published estimates for a focused MVP cluster around eight to fourteen weeks. Discovery is usually excluded from that, and web plus mobile is closer to twice the work than to slightly more. The number to hold a vendor to is person-days, not calendar weeks, because calendar weeks are the part they can stretch without telling you.
Is GST charged on MVP development in India?
Software development services fall under SAC 9983 and attract 18% GST. If you are a GST-registered Indian business buying for your own business, that is normally input tax credit rather than a cost, provided the invoice carries your correct GSTIN and SAC. Export of services to a foreign entity is treated as zero-rated subject to conditions, so a USD quote from an Indian vendor should not usually carry 18% on top. Confirm the current rate on the CBIC rate finder and the credit position with your CA.
Is it actually cheaper to build an MVP in India?
Hourly rates quoted by Indian agencies in that search ran from $20 to $70, which is lower than most Western equivalents. Whether the project is cheaper depends on how many hours it takes, and that depends on scope clarity and communication rather than on location. A cheap rate attached to a vague scope is the most expensive combination available.
What should an MVP not include?
Anything the one validating sentence does not need. The usual candidates: a settings page, a second user role before the first one works, a second platform, analytics dashboards, and a redesign of something nobody has used yet.
Should a non-technical founder hire an agency or find a technical co-founder?
They solve different problems. A co-founder is a long-term owner of technical decisions. An agency is a way to test an idea without making that hire first, and a scoped build is a reasonable version of a paid trial. What an agency cannot be is your permanent CTO, and any vendor who implies otherwise is selling you a dependency.
Work with us
We build first versions for founders and we argue about scope before we write code, because that is where the money is. If you want a second opinion on a quote you already have, send it over. If you want to see how we scope an MVP, that page sets out the approach, and you can talk to us whenever the scope conversation is worth having.