MVP development
MVP development: a narrow first product, shipped in 6 to 12 weeks
A good MVP development company helps you cut scope before it writes any code. We pick one user, one painful job and one measurable outcome, then design and build the smallest web or mobile product that tests it, usually in 6 to 12 weeks, on fixed-price milestones. Analytics are in place on launch day, and you own the code and accounts.
- Timeline
- 6–12 weeks
- Start with
- Paid discovery or one milestone
- Platforms
- Web, iOS, Android
- Measured
- Activation, retention, payment
Updated · By the Codebrix team
What an MVP is actually for
An MVP is not a cheaper version of the full product. It is the smallest thing that answers the question your business depends on: will this kind of user come back, or pay, for this job done this way? Everything that does not help answer that question waits.
How we cut scope
- List every feature you have in mind, without judging.
- Mark each one: needed to test the belief, nice later, or never.
- For each 'needed' item, ask whether a person could do it by hand for the first fifty users. If yes, do it by hand.
- Use ready-made services for anything that is not your edge: sign-in, payments, email, maps, file storage.
- Pick one platform first unless the test requires both.
- Agree a list of what is out of scope and attach it to the proposal.
| Feature idea | MVP version | Later |
|---|---|---|
| Smart scheduling | Tutor sets weekly slots; student picks one | Calendar sync, auto-rescheduling |
| Payments | Hosted checkout link per booking | Wallets, packages, refunds in-app |
| Reviews | Founder emails students for feedback | Public ratings |
| Messaging | WhatsApp link on the booking | In-app chat |
Our MVP scope guide walks through this exercise step by step if you want to do it before talking to anyone.
A typical 6 to 12 week plan
| Stage | Weeks | What you get |
|---|---|---|
| Discovery and scope | Week 1 | Written scope, out-of-scope list, success metric, fixed price |
| Design and prototype | 1–3 weeks | Figma screens for the core flow and a clickable prototype to show users |
| Build sprints | 3–7 weeks | A working demo on a staging link every week |
| Private beta | About 1 week | Real users, bug fixes, analytics checked |
| Launch and handover | About 1 week | Live app, accounts in your name, recorded walkthrough |
Design can overlap with the first build sprint, which is how simpler MVPs land near six weeks. A mobile MVP needing store review sits toward twelve.
Web, mobile or both for the first release
Pick the platform where the test happens, not the one that looks impressive in a pitch deck.
- Web first when buyers are businesses, the work happens at a desk, or you want to change things daily without store reviews. See custom web application development.
- Mobile first when the product depends on the camera, location, push reminders or a daily habit. We usually use React Native with Expo so iOS and Android come from one codebase; see React Native app development.
- Both only when the test needs two sides, such as a customer app and a provider dashboard.
What to measure from day one
If the MVP launches without measurement, you will argue about anecdotes. We set up events before the beta and agree the target numbers before launch, so the result cannot be reinterpreted afterwards.
- Activation: the share of sign-ups who complete the core action once.
- Retention: how many come back in week one and week four.
- Task success: how many start the core flow and finish it, and where they drop out.
- Willingness to pay: paid pilots, pre-orders or a price shown before checkout, not survey answers.
- Five to ten user conversations, recorded with permission, to explain the numbers.
What an MVP costs
Indicative ranges from our estimator: a web application is ₹1,50,000–6,00,000 ($5,500–22,000) and a mobile app for iOS and Android is ₹2,50,000–9,00,000 ($9,000–33,000). A tightly cut MVP aims for the lower part of these ranges; the fixed quote comes after a discovery call.
To lower your risk, you can start with paid discovery alone, or with only the design milestone, and decide after seeing the prototype. Comparing us with freelancers? Our agency vs freelancer guide is honest about when a freelancer is the better call.
After the MVP: keep, change or stop
At the agreed review date we look at the numbers with you. If the metric was hit, the next milestone adds what users asked for most. If it was close, we change one thing and rerun. If it missed clearly, stopping is a valid outcome and cheaper now than after a full build.
We do not build throwaway code to hit a date. The MVP uses the same TypeScript, PostgreSQL and test setup as a full product, so version two extends it rather than replacing it. If the product becomes a subscription business, SaaS development covers what comes next.
Frequently asked questions
How long does MVP development take?
Most of our MVPs take 6 to 12 weeks from signed scope to launch. A single-platform web MVP with one core flow sits near the lower end. A mobile MVP on both stores, or one with a customer side and an admin side, sits near the upper end, partly because app store review adds time before launch.
What if we want to add features halfway through?
We write them down, estimate them, and you decide whether they replace something in scope or go into a later milestone. The fixed price covers the agreed scope, so additions are priced separately and visibly. In practice most mid-build ideas turn out to belong after launch, once real users have shown what matters.
Should we build with no-code tools instead?
Sometimes yes. If the test is whether anyone wants the service at all, a no-code prototype, a form and some manual work can answer it in days. A coded MVP makes sense when the product's value is in the software itself, when you need performance or specific integrations, or when you plan to keep building on it.
Do we need designs ready before we contact you?
No. Design is part of the process: Figma screens and a clickable prototype in the first one to three weeks. If you already have designs, we review them against the cut scope, and the design milestone shrinks. Rough sketches, competitor screenshots or a list of flows are a perfectly good starting point.
What do you need from us during the build?
One decision-maker available for a weekly demo and quick answers on the shared channel, access to any accounts the product uses, and the people you want to test with. MVPs slip most often because feedback waits a week, not because of the code, so a responsive founder matters more than a long brief.
Can you help us get the first users?
We can build a landing page with tracking and run paid campaigns to it through our digital marketing service, quoted separately. Finding the right early users through your own network and conversations is still the founder's job, and it usually produces better early feedback than ads do.
Related
Product guide
How to scope an MVP you can build in about eight weeks
How to scope an MVP: pick the one assumption to test, prioritise with MoSCoW, cut the rest, follow a sample 8-week plan and track the right metrics.
Read moreWeb applications
Custom web application development for portals, dashboards and internal tools
Custom web application development for portals, dashboards and internal tools: roles, Postgres, integrations and tests. Fixed price, code in your name.
Read moreSaaS development
SaaS development with multi-tenancy, billing and admin built in from the start
SaaS development company building multi-tenant products with Stripe or Razorpay billing, onboarding, admin and analytics. Milestone pricing, your code.
Read moreReact Native apps
React Native app development: one Expo codebase for iOS and Android
React Native app development company building iOS and Android apps from one TypeScript codebase with Expo, OTA updates and native modules where needed.
Read moreBuying guide
Agency vs freelancer for website development: which should build your site?
Agency vs freelancer for website development: an honest look at cost, risk, speed and ownership, with a comparison table and a checklist before you sign.
Read moreUI/UX design
A UI/UX design agency in India that designs what will be built
UI UX design agency in India: user research, wireframes, Figma screens, a design system and a clickable prototype, designed by the team that builds it.
Read more