The Real Cost of Choosing Wrong
You have 6 months of runway. Building takes 8 weeks. You need 4 weeks to learn if anyone cares. Choose the wrong MVP format and you're dead.
This isn't theoretical. In 2023, Sequoia analyzed 100+ YC companies by failure mode. 34% built working products with zero traction. 23% built landing pages that generated fake interest (high clicks, zero conversions). The survivors did something precise: they matched their MVP type to their core uncertainty.
Landing Page MVP: When Demand Is Your Question
Use a landing page MVP when your biggest risk is market fit, not product fit.
When this applies:
- Your category exists but is fragmented (e.g., another HR-tech tool)
- You're solving a known problem in a new way
- Positioning and messaging are unproven
- You have no technical moat—copycat risk is high
- You're in India's competitive SaaS segments (CRM, billing, analytics)
What you measure:
- Click-through rates from ads (target: 3%+ for paid channels)
- Email signup conversion (target: 15%+ cold, 30%+ warm)
- Founder-led sales conversations (target: 20+ in week one)
- Pre-orders or commitment signals (target: 5+ genuine interest)
YC's Michael Seibel runs this playbook: "Build a landing page in 48 hours. Spend $500 on ads. If you get 50 emails in week one, you have demand. If not, pivot or die." The India advantage: ad costs are 70% cheaper than US, so you can test more angles faster.
Real example: A Mumbai B2B payments startup tested three positioning angles with landing pages ($200/angle, one week each). Angle A ("Payments API for devs") got 8% CTR. Angle B ("POS for unorganized retail") got 2%. Angle C ("B2B reconciliation tool") got 18%. They built only Angle C. Built the wrong one first, they'd have wasted 12 weeks.
Functional MVP: When Behavior Is Your Question
Use a functional MVP when your biggest risk is that users won't actually use it the way you think.
When this applies:
- The product category is new (AI agents, novel workflows)
- You're changing how people work (requires habit formation)
- Your assumptions about user behavior are unproven
- Network effects matter (multi-sided platforms need real usage)
- You need to prove technical feasibility
What you measure:
- Daily active users (DAU) as % of signups (target: 20%+)
- Time in app per session (target: 5+ minutes for consumer, 15+ for B2B)
- Core action completion rate (if it's an invoice tool, invoices created per user)
- Willingness to pay (not hypothetical—real subscription starts)
- Retention D1, D7, D30 (the brutal truth of habit)
Scott Belsky's "Messy Middle" principle: "Most product assumptions break only when users interact with real workflows. Landing pages don't tell you if your UX is broken or if users will actually adopt your feature sequence."
Real example: A Bangalore AI-for-customer-service startup asked: "Will CSRs use an AI copilot in their existing tools?" Landing page got 400 signups. They built a functional MVP with Slack integration (minimal code, max signal). Only 24 actually tried it. Of those, 6 stayed beyond day 7. The landing page promised demand; the functional MVP revealed friction in the workflow. They pivoted to email-first before investing in chat integration.
The Decision Framework
Use Landing Page MVP if:
1. You're in an existing category (you can validate positioning)
2. Technical risk is low (copycat risk is high)
3. Behavioral uncertainty is secondary
4. You have <$500 to test with
5. India advantage: Ad costs let you test 5 angles, not 1
Use Functional MVP if:
1. The category is new (no comparable products exist)
2. User behavior is your biggest unknown
3. Technical execution directly impacts adoption
4. You need to prove habit formation or workflow integration
5. India advantage: Cheap engineering means <4 weeks to functional v0
Hybrid (Most Intelligent) Approach:
1. Landing page week 1-2: Validate positioning + demand
2. Micro-functional MVP week 3-4: 50-100 beta users with core feature only
3. Measure retention. If DAU % > 15%, keep building. If < 5%, pivot positioning.
This is how Stripe India validated before building—they ran landing pages for three payment scenarios, then built functional MVPs for the top two.
The Non-Obvious Insight
Landing pages measure future interest. Functional MVPs measure current behavior. India's startup ecosystem optimizes for speed, so we over-index on landing pages. But in markets where adoption depends on habit (fintech, B2B SaaS), landing page interest decays 80% by day 30. Functional MVPs give you the signal that actually predicts revenue.
Your Move
Write down your core uncertainty: Is it "Do customers want this?" or "Will they actually use this?" Your MVP type depends on that one answer. Wrong choice = 8 weeks wasted. Right choice = 8 weeks of learning at $0 cost.
Start now. Pick one customer segment. Run the appropriate test this week. Report back in 10 days.