Why Gaps Are Where Ideas Hide
Y Combinator's advice is counterintuitive: don't build for a market that doesn't exist yet. Find where people are already paying with friction. Spreadsheets, email, WhatsApp. These aren't cute workarounds—they're evidence of market demand at scale.
When founders ask "Is there a market?" they usually mean: "Will VCs fund this?" Wrong question. Ask instead: "How many people are solving this problem wrong right now?"
Take inventory management in Indian small businesses. Lakhs of shopkeepers track stock in WhatsApp notes, Excel sheets, physical notebooks. They're not waiting for innovation. They're bleeding 10-15% in stockouts and overstock. The gap between their current solution and Zoho Inventory is the entire market.
The Three Gap Types
1. The Spreadsheet Gap
Spreadsheets are the default office software because they're flexible. But flexibility means humans are doing the computer's job.
Example: Medical clinics in Tier-2 India manage patient records, billing, and appointment scheduling in Google Sheets. Data corruption is constant. Staff makes errors. Compliance is zero. Yet clinics resist dedicated software because Sheets is free and familiar.
This is a $2B gap in India alone. Healtho, MediBuddy, and Sympto all exist. But regional players miss the monetization: charge based on consultations per month, not per-seat licensing. Sheets has already validated willingness to pay through SMS and service quality.
2. The Email Gap
When email handles what software should handle, you have a gap.
Indian B2B services: recruitment, compliance, accounting. They live in email threads. Recruiters send candidate lists as attachments. Accountants email invoices for approval. Compliance consultants exchange documents through Outlook.
The friction: version control is impossible. Audit trails don't exist. Stakeholders miss deadlines because emails get buried. Switching is easy because nothing owns their data yet.
Hire was built on this observation—recruitment agencies wanted software, but they wanted it to feel like email. That insight made them $1.2B in revenue before IPO.
3. The WhatsApp Gap
When business critical operations run on WhatsApp, gaps are widest.
Indian D2C brands use WhatsApp Business for order tracking, customer support, payment collection. Swiggy, Dunzo, and Meesho scaled to millions of users through WhatsApp before building in-app infrastructure. Why? WhatsApp doesn't discriminate by smartphone quality. It works on low-bandwidth networks. Notifications are reliable.
The gap: WhatsApp isn't designed for business. No CRM features. No analytics. No integration. Founders solving for "WhatsApp-first logistics" or "WhatsApp-native fintech" are actually capturing users before they're ready for "real" software.
Nykaa's initial advantage wasn't beauty tech—it was handling orders through email and Orkut when competitors weren't present yet.
How to Spot and Validate Gaps
Step 1: Find the Proxy Tools
Where do target users manage your problem space today?
Talk to 10 founders or operators in your vertical. Ask: "Walk me through your last transaction/decision/workflow." You'll hear Sheets, email, WhatsApp, Slack. Note the specific pain they mention.
Step 2: Quantify the Time Cost
From Scott Belsky's "The Messy Middle": friction costs are hidden until you make them visible.
If a support team of 5 spends 3 hours daily managing tickets from email, that's 3,750 hours annually. At ₹250/hour blended, that's ₹93 lakhs in annual cost. Now you have a price ceiling for software that solves it.
Step 3: Test Willingness to Pay
Don't build the app yet. Build a Zapier automation or a simple Google Forms workflow that removes 40% of the friction. Charge ₹2,000-5,000/month. If 10 businesses sign up, you have validated demand without shipping product.
This is what Pipefy did in Brazil before expanding globally.
Why Indian Founders Miss These
There's a bias toward "innovation." Indian investors want AI, blockchain, moonshots. Gaps feel boring.
But Paul Graham's rule applies: the best ideas often look trivial initially. Stripe looked like Paypal 2.0. Figma looked like Adobe Light. Both crushed markets because they solved gaps others ignored.
In India specifically: fragmentation creates gaps. No single tool dominates SMB operations like Salesforce dominates US enterprise. Regional language preferences, low smartphone penetration in Tier-2, regulatory fragmentation—all create pockets where gaps persist.
Your Framework
1. Vertical Selection: Pick 3 industries where you have operator credibility.
2. Tool Audit: Document the workflow across Sheets, email, WhatsApp, SMS, voice calls.
3. Friction Quantification: Calculate time wasted and cost to the business.
4. Proxy Validation: Build a minimal workflow that removes 40% friction. Charge for it.
5. Scaling Test: If 5+ customers stay after month 3, you have product-market fit direction.
Doesn't require fundraising. Doesn't require innovation theater. Just requires seeing what people tolerate and removing it faster than they expect.
Non-Obvious Insight
Gaps between products are often less competitive than new categories because they're invisible until you solve them. By the time a gap becomes "obvious," the founder solving it owns the vertical. Freshworks didn't face Zendesk competition in India for 5 years. Razorpay didn't compete with Stripe directly—it competed with email and spreadsheets first.