MVP

An MVP (Minimum Viable Product) is the bare-bones version of your product designed to solve one problem for early adopters. It contains only essential features—nothing more. The goal is speed: launch in weeks, not months, and learn directly from users.

In practice, your MVP should take 4–12 weeks to build, cost under ₹20–50 lakhs for a tech startup, and reach 50–100 initial users. It answers a single question: Do people want this? Not: Is it perfect?

Many Indian founders mistake MVP for a feature-limited final product. That's wrong. An MVP is a learning tool. You gather feedback, iterate, and either pivot or scale. The unit economics and user retention data from your MVP inform your Series A pitch far more than polish.

Common MVP approaches: landing page with email signups, manual backend (Wizard of Oz), or a single-feature app. Founders who ship MVPs within 8 weeks report 3–4x faster product-market fit discovery than those who spend 6+ months perfecting before launch.

Indian founders often over-engineer MVPs because they fear judgment or want to compete on feature parity with established players. This kills speed. Successful Indian startups like Swiggy (started with restaurant ordering in one Bangalore area) and Razorpay (payment gateway for 10 merchants first) launched hyper-focused MVPs in 4–6 weeks. They nailed one use case before expanding.

Regulatory note: If your MVP handles payments, PII, or financial data, you must comply with RBI guidelines and NIST compliance from day one—even as an MVP. This adds 2–3 weeks but is non-negotiable. For fintech MVPs, expect ₹5–10 lakh extra for compliance infrastructure.

Indian user behavior differs from Western cohorts. Your MVP must account for: low broadband speeds (optimize for 2G/3G), vernacular language support (if B2C), and offline-first design where applicable. Many successful Indian MVPs are mobile-only, not web-first.