The Universal Problem Trap
You've found it: a problem so obvious, so widespread, that millions face it daily. Your metrics dazzle. India has 60 million small businesses. Untap, unchained market. Then you pitch it, and investors lean back.
Here's what you're not seeing: a problem everyone has is a problem already half-solved. Free tools exist. Workarounds exist. Apathy exists.
Paul Graham wrote that the best startup ideas "seem like bad ideas at first." Universal problems feel like good ideas immediately. That's the warning sign.
Why Specificity Wins
Consider two pitches:
Pitch A: "We solve email overload for all professionals." (Gmail, Outlook, 15 other tools already do this.)
Pitch B: "We reduce email response time for logistics dispatch coordinators in cold-chain supply." (A real, $2B vertical in India with specific pain.)
Pitch B founder will close faster, at higher margins, with fewer competitors. Why? Because the cold-chain problem is specific enough that the founder has likely spoken to 30 customers who all nod vigorously. They've been waiting for this.
YC's thesis: narrow customer group + acute problem = willingness-to-pay. Broad customer group + diffuse problem = price resistance.
The math is simple. A SaaS selling to "all SMBs" at ₹5,000/month faces 1% conversion rates. The same SaaS, repositioned for "pharma distributors" at ₹15,000/month, hits 15% conversion. Specificity is a 15x ARR multiplier.
The India Distortion
Indian founders have an additional blindness. We see a problem in Bangalore or Mumbai and assume it's universal because Tier 1 solutions haven't penetrated beyond metros. A founder in Gurgaon sees no HR SaaS in the market and builds for "all Indian businesses."
What's actually happened: the problem is niche, geographically, and price-sensitive. A ₹10,000 Workday license is a luxury for a 50-person firm in Pune. But a ₹2,000/month payroll tool for garment manufacturers? That's cash flow positive from day one.
The specificity isn't a compromise. It's your actual TAM.
How to Test Specificity
Scott Belsky's framework from The Messy Middle applies here: momentum comes from repeated small validations, not theoretical scale.
Ask yourself:
1. Can you name 10 customer companies without searching? If you can't, you haven't validated a specific segment. You have a general category.
2. Do 7 out of 10 acknowledge the problem unprompted? If you're explaining the problem, you don't have acute pain. You have a nice-to-have.
3. Would they pay today if you had it? Not "might consider." Today. If not, you're 18 months early or solving the wrong problem.
4. Can you describe their current workaround in detail? If you can't, you don't understand the problem deeply. You understand a symptom.
Indian founders often stop at (1). They find 10 CXOs who nod. Then they build for "the market" instead of those 10.
The Competitive Advantage Shelf Life
Universal problems have flat competitive returns. Enter a broad market with a broad solution, and you compete on price, distribution, brand. You race to the bottom.
Narrow problems have moat-building potential. Become the payroll expert for garment manufacturers. Your data, your industry knowledge, your integrations—they compound. A competitor entering later faces network effects you've built.
This is why YC companies with narrow positioning raise more, faster. Less competitive noise. Clearer unit economics. Faster to $1M ARR.
The Honest Reframe
When you pitch "everyone has this problem," investors hear: "I haven't validated with enough depth." It's not mean; it's pattern recognition. Founders who've talked to 50 customers in one vertical can articulate the problem in three sentences. They know the workflow, the price point, the buying cycle.
Founders who claim universality usually haven't yet.
So reframe your work. Stop asking "Who else has this problem?" Start asking "Which specific group has this problem so acutely they'll pay immediately?" The answer is never everyone. It's always someone.
Actionable Next Step
Take your current problem statement. Narrow your customer definition by 10x. A vertical, a company size, a geography, a workflow. Then talk to 15 people in that narrow segment. How many acknowledge the problem? How many would pre-pay?
If fewer than 10 say yes, you've either picked the wrong segment or misidentified the problem. Either way, you've saved months of building toward nobody.
The narrower path feels riskier. It isn't. It's the only path with paying customers waiting on the other side.