Scoping
A working session to identify the assumption the MVP must test, the users it serves first, and the features that can wait.
03.3.1MVP development
MVP development for startups
An MVP isn't a cheaper version of the full product — it's the smallest thing that can prove the idea with real users. We help you cut the feature list to what tests the core assumption, design it properly and build it on a stack that can grow, so version two extends the MVP instead of replacing it.
Who it’s for
- Founders validating a product idea before raising or scaling
- Businesses launching a new digital product alongside their core offer
- Startups with a prototype that now needs to handle real users
- Teams that need a working product to show investors or pilot customers
- Non-technical founders who need a product and engineering partner
What’s included
User flows and UX
The core journeys mapped and designed in Figma, then tested with you before development.
Web application build
Front end in Next.js and React, API in Node.js and Express, data in MongoDB — a stack that suits early products and scales with them.
Accounts and payments
Sign-up, login and, where needed, payments or subscriptions, so early users can actually use and pay for the product.
Admin and analytics
An internal view of users and activity, and product analytics so you can see what people do after launch.
Launch and iteration
Deployment on AWS, launch support, and a plan for the first round of changes based on what users do.
What you get
- Scope
- Fixed feature list agreed before build
- Platform
- Responsive web app (mobile apps optional)
- Infrastructure
- AWS, with staging and production
- Code ownership
- Yours, with repository access
- Handover
- Technical documentation
How it works
- 01Scope
Assumption, users, must-have features and what's out of scope.
- 02Design
User flows and key screens designed and clicked through.
- 03Build
Development in short cycles with a working build you can try each week.
- 04Launch
Deployed to real users with analytics and error monitoring in place.
- 05Learn
Review usage and feedback, then plan the next version.
Tools & tech
FigmaNext.js / ReactNode.js / ExpressMongoDBAWS
Timeline
TODO: typical duration from Dev
Starting from
TODO: ₹ from Dev
Questions we get asked
What should an MVP include?
Only what's needed to test your riskiest assumption with real users — usually one core journey done well, plus sign-up and whatever lets you measure success. Everything else goes on a list for later.
Web app or mobile app for an MVP?
A responsive web app is usually faster and cheaper to launch and update, and works on every device. A mobile app makes sense first when the product depends on phone features like the camera, location or notifications.
Will we have to rebuild after the MVP?
That's what we plan to avoid. We keep the scope small but the foundations real — proper data structure, authentication and deployment — so the next version builds on the MVP.
How much does MVP development cost?
It depends on the number of user roles and journeys, integrations such as payments, and whether design is included. Fixing the scope before build is the best way to control cost. TODO: add a ₹ starting price once Dev confirms it.
Who owns the code?
You do. You get access to the code repository and the hosting accounts. TODO: confirm contract wording with Dev.