Why Speed Matters More Than You Think
YC doesn't fund teams who ship slowly. Paul Graham's insight still holds: "Do things that don't scale." But what does that mean operationally?
It means: your first MVP should be something you can build in 2 weeks with 2 people. If you can't, your scope is broken.
Here's the brutal truth: every week you don't ship is a week your assumption isn't being tested. In India's market density and competitive pace, that's death. Zomato shipped their MVP in 3 months (2010). Today's winning Indian founders ship in 3 weeks.
The YC Speed Framework: Hardcode, Fake, Skip
This is the hierarchy of cutting that actually works:
Tier 1: Hardcode Everything
Hardcoding is not a bug—it's your speed advantage. Here's how:
- User data: For your first 20 users, paste their data directly into your code or database schema. Don't build an admin panel. Don't build dashboards. Just show them the information they need.
- Calculations: If your SaaS does pricing optimization, hardcode 5 price-point examples for your first users. Calculate manually if needed. Users don't care how you got the number—they care that it works.
- Personalization: Instead of building a recommendation engine, show each user's top 3 most relevant items by hand. Mark them in your database directly. You'll learn more from 20 manually-curated experiences than 1,000 algorithmic ones.
Why this works: Hardcoding forces you to deeply understand your core loop. You interact with your own product. You find dead ends fast.
Tier 2: Fake Your Backend
When hardcoding breaks—when you need 50+ users or variable data—fake the backend:
- Use Airtable + Zapier: Airtable is your database. Zapier connects it to your frontend. You can build 80% of an early SaaS in Airtable + Zapier + a Webflow frontend in 5 days. Cost: ~$100/month.
- Google Sheets + Apps Script: For India-specific use cases (fintech, logistics), a Google Sheet with custom Apps Script can act as your real-time API. It's not elegant, but it works.
- Manual workflows: Process orders via email initially. Have your co-founder literally handle the first 10 transactions by hand. You'll learn if your pricing works. You'll feel customer pain. You'll adjust.
- Stripe for payments: Don't build custom billing. Use Stripe's hosted checkout. It's 2 hours of integration. That's not optional—it's mandatory.
India-specific note: Many founders here worry about appearing "non-technical" using no-code tools. This is ego. Flipkart's founding MVP was a single landing page with manual order processing. Speed beats perfection.
Tier 3: Skip Features Entirely
Features you can absolutely skip in week 1:
- User authentication (use magic links via email, not OAuth)
- Mobile apps (web-only for now; responsive design only)
- Analytics dashboards (use Mixpanel for free tier; capture events, visualize later)
- Email notifications (batch them; send daily digests via a manual script)
- Search functionality (show all items on one page; use browser Cmd+F)
- Admin panels (don't build one; use database GUIs like pgAdmin)
- Compliance integrations (legal placeholder; ship the core product first)
The cut metric: If a feature takes more than 8 hours to build, and you're not sure 5 users will ask for it, skip it.
Your 2-Week Shipping Checklist
Week 1 (Days 1-7)
- Day 1-2: Define your core loop (what's the one thing your user does?)
- Day 2-3: Design UI (Figma, no custom design; use free templates)
- Day 3-5: Build core feature in no-code (Bubble/FlutterFlow) or hardcoded code
- Day 5-6: Integrate payments (Stripe) if revenue model exists
- Day 6-7: Manual QA with your co-founder; hardcode fixes
Week 2 (Days 8-14)
- Day 8-9: Deploy to live URL (Vercel for code, Bubble's built-in hosting)
- Day 9-10: Recruit 5-10 beta users from your network
- Day 10-12: Watch them use it; capture feedback via Loom or live calls
- Day 12-13: Fix 3-5 critical issues; ignore minor bugs
- Day 14: Ship publicly (ProductHunt, Twitter, relevant India communities)
The Non-Obvious Insight: Scope Cutting is a Skill
Scott Belsky calls this "ruthless prioritization." But here's what founders miss: ruthless prioritization is a muscle. You get better at it.
Your first MVP will feel incomplete. It will feel amateur. Your job is to recognize that feeling as success, not failure. If it feels polished, you cut too little.
The founders who win in India's market aren't the ones with the best technical architecture. They're the ones who can say "no" to 70% of what they want to build.
Regulatory Reality Check for India
If you're in fintech, insurtech, or healthtech: don't let compliance kill your speed. Ship the core product with a legal placeholder: "This product is in beta and not yet RBI-compliant. By using, you acknowledge this is a prototype." You have 3 months to get compliance while you're building the next version.
Regulators want to see traction and a real product. An incomplete compliant product gets you nowhere.
What Successful Indian MVPs Look Like
- Cred's MVP (2018): A single credit card payment page. That's it. Users got cashback. Shipped in weeks.
- Razorpay's MVP: A basic payment gateway for merchants. No dashboard. No analytics. Just processing. Built in 6 weeks.
- Unacademy's MVP: A single educator's courses on YouTube + Stripe. Manually managed. No platform. Shipped in 2 weeks.
All three are now unicorns. None of them shipped "complete" MVPs. They shipped useful ones.
Your Action: The 2-Week Sprint
Pick your core loop. Define it in one sentence. Cut everything else. Ship it. Watch users use it. Iterate.
If you can't ship a working version in 2 weeks, your idea might not be your problem—your scope is.