By Mantravi Team · May 18, 2026 · 8 min read
Eight to twelve weeks is enough for a focused MVP — if you cut scope deliberately. A practical framework for Indian founders prioritizing learning over feature lists.
In this article
Indian founders often arrive with investor decks listing twelve modules and a twelve-week timeline. Something has to give. The purpose of an MVP is learning — whether users will pay, return, or refer — not proving you can build everything. Eight to twelve weeks is realistic when scope is a single hypothesis, not a miniature of the Series B vision.
Frame the hypothesis in one sentence
Example: "Independent tutors will pay for a tool that collects fees and shares lesson notes with parents." Every feature must serve that sentence. Marketplace discovery, AI lesson plans, and multi-language support are Phase 2 until fee collection works and retains ten paying tutors.
The 8–12 week MVP stack
Weeks 1–2: discovery, flows, technical spike. Weeks 3–8: build core loop with weekly demos. Weeks 9–12: hardening, analytics, onboarding polish, and staged beta. Parallel tracks for design and QA — not a big bang at week eleven.
| Include | Defer |
|---|---|
| Core user journey | Secondary personas |
| Auth + roles | Complex RBAC |
| Admin for ops | Full BI dashboards |
| Analytics events | Advanced ML |
| Payment if revenue-critical | Loyalty / referrals |
Metrics that matter at MVP stage
Activation rate, week-one retention, and conversion to paid or repeat action — not vanity signups. Instrument funnels on day one. Interview ten users who churned; their reasons beat roadmap debates.
Mantravi runs fixed-scope MVP engagements with weekly demos and explicit out-of-scope lists.
Scoping your MVP?
Turn your deck into an 8–12 week build plan
Frequently asked questions
- How much can we build in 8–12 weeks?
- Typically one core loop — signup, primary action, payment or booking if needed, and basic admin — on web or mobile, not both at full depth.
- Should the MVP include AI?
- Only if AI is the hypothesis. Otherwise add AI after you validate demand for the core workflow.
- Web or mobile first in India?
- B2B and SaaS often start web; consumer on-demand or social products may need mobile early. Follow where your user already spends time.
- Do we need a design system?
- Use a lightweight component library. Full design systems can wait until post-PMF when UI velocity matters at scale.
- What about compliance?
- Bake in privacy policy, consent, and payment PCI basics from day one. Heavy compliance features scope separately with legal input.