How long does it take to build an MVP?
A minimum viable product takes six to twelve weeks to build with real users on it. A simple MVP — one core workflow, one user type, no payments — ships in four to six weeks. Anything involving payments, multiple user roles, or third-party integrations lands at ten to twelve weeks. Discovery and design take the first one to two weeks.
Where the weeks actually go
Most founders assume the build is the long part. In practice, on a ten-week MVP roughly two weeks go to deciding what not to build, five to engineering, and three to the unglamorous work that makes it usable by strangers: error states, empty states, onboarding, and the admin screens you need to support your first users.
| Phase | Duration | What comes out of it |
|---|---|---|
| Discovery and scope | 1–2 weeks | One core workflow defined, everything else deferred in writing |
| Design | 1–2 weeks | Screens for the happy path plus the three ways it breaks |
| Core build | 4–5 weeks | Working software, deployed, behind a login |
| Integration and hardening | 1–2 weeks | Payments, auth, error handling, admin tooling |
| Beta and fixes | 1 week | Real users on it, fixes shipped daily |
What makes an MVP take four weeks instead of twelve
One variable dominates: the number of things that must be true at once. A single user type doing a single job is fast. Two user types who see different data, transact with each other, and need notifications is not a slightly bigger project — it is a different one.
- Four to six weeks: one user type, one core workflow, no payments, no external integrations
- Six to ten weeks: two user types, a dashboard, file uploads, email or WhatsApp notifications
- Ten to twelve weeks: payments, role-based permissions, third-party integrations, or regulated data
- Beyond twelve weeks: it is no longer an MVP — split it and ship the first half
What belongs in version one
The test is not 'would a user like this' — users like everything. The test is whether the product is unusable without it. Almost nothing passes that test, which is the point.
Things that reliably do not belong in an MVP: a settings page, a notifications centre, an analytics dashboard for your own team, dark mode, multi-language support, and a mobile app when a responsive web app answers the same question in a third of the time.
Why timelines slip
In our experience the two causes are unavailable decision-makers and unbounded scope, in that order. A build waits on the one person who can approve a flow, or a feature gets 'just one more' added to it four times in a fortnight.
Both are solvable by writing the scope down before starting and treating additions as their own small project with their own price and date, rather than absorbing them silently and slipping.
Common questions
- What is included in MVP development?
- One core workflow built properly, end to end: the screens, the backend, authentication, a database, deployment, and enough admin tooling to support real users. It excludes the second and third feature you want, which is what makes it an MVP rather than a product.
- How much does an MVP cost in India?
- An MVP typically runs ₹3,00,000–₹8,00,000 depending on how many user types and integrations it needs. At DMC Tech that maps to the Catalog & Commerce and Business System tiers, starting at ₹3,00,000 and ₹6,00,000 respectively.
- Can you build an MVP in two weeks?
- Rarely, and usually only when the product is a single form with a workflow behind it, or an internal tool for a team that already agrees on the process. If someone quotes two weeks for anything with payments and accounts, ask what they are leaving out.
- What happens after the MVP launches?
- Fixes for the first 30 days are included. After that most teams either move onto a ₹15,000/month maintenance plan or scope version two based on what the first users actually did, rather than what everybody predicted they would do.
Last updated 2026-08-01