market entry strategy
The goal is not to enter new markets. The goal is to win in them. Most companies confuse the two and end up losing in both the old market and the new one.
Your CEO walks into the quarterly review and says: “We have dominated Bangalore. Time to go pan-India.” Or maybe it is: “Enterprise is working. Let us go after SMBs.” Or the classic: “Our competitor just launched in Southeast Asia. Should we follow?”
Each of these is a market entry decision. And each one, handled poorly, will drain your engineering capacity, dilute your positioning, and produce a product that is mediocre everywhere instead of dominant somewhere.
Market entry is not a growth tactic. It is a strategic bet. The PM’s job is not to say yes or no — it is to build the framework that makes the go/no-go decision defensible.
The four types of market entry
Not all market entry looks the same. Before you build a plan, you need to know which type of entry you are dealing with, because each carries a different risk profile and demands different product work.
1. Geographic expansion. Same product, new region. This sounds simple — “just launch in Chennai” — but geography in India is not just a pin on a map. It is language, payment behavior, logistics infrastructure, regulatory nuance, and cultural expectation. Swiggy launching in a new city is not a deployment. It is a supply-side cold start problem: restaurants, delivery partners, demand density — all from zero.
2. New segment entry. Same geography, different customer type. You built for startups, now you want mid-market. You built for consumers, now you want businesses. Segment shifts are often harder than geographic expansion because they require product changes, not just distribution changes. An SMB invoicing tool going enterprise needs SSO, audit trails, role-based access, and a six-month sales cycle your team has never run.
3. Competitive entry. Entering a market where an incumbent already dominates. You are not creating demand — you are stealing it. This requires a clear wedge: a segment the incumbent ignores, a price point they cannot match, or a product experience they are too bloated to deliver. Without a wedge, you are just burning money on awareness.
4. Adjacent market entry. Your core product serves one job-to-be-done, and you are expanding to a related one. PhonePe started with UPI payments, then moved into insurance, mutual funds, and lending. Each adjacent market uses existing distribution but demands new domain expertise, new compliance requirements, and often new teams.
Growth planning meeting. Head of Product and CEO debate the next move.
CEO: “Meesho is expanding to tier-3 cities. We should too. We are losing ground.”
Head of Product: “What problem do tier-3 users have that our product solves today? Without changing anything?”
CEO: “Same problem. They want affordable fashion.”
Head of Product: “The problem is the same. The context is not. Payment preferences are different — COD is 80% there. Return logistics barely exist. Our app is 45MB and most users are on 2GB RAM phones. 'Just launching' means launching a broken experience.”
CEO: “So what do you propose?”
Head of Product: “A scoped pilot. Two cities. Lite app. COD-first checkout. Measure retention at 30 days before we commit to pan-India.”
Geographic expansion without contextual adaptation is not expansion. It is tourism.
Entering a new market is not deploying your product. It is rebuilding the assumptions your product was designed around.
The go/no-go framework
Every market entry decision should pass through a structured evaluation before a single line of code is written. Here is the framework I use — five lenses, each with a kill criterion.
Market attractiveness. Is the market worth entering? Size matters, but growth rate matters more. A $500M market growing at 40% annually is more interesting than a $2B market growing at 3%. Check: TAM, growth rate, and whether the market is consolidating or fragmenting. Kill criterion: if the addressable market is smaller than your current market and growing slower, stop here.
Right to win. Why would you win in this market? Not “why is the market attractive” — why would your team, your product, your distribution win specifically? Zerodha had a right to win in retail trading because they understood Indian retail investors, had built trust through transparency, and had a cost structure incumbents could not match. They would not have had a right to win in institutional trading. Kill criterion: if you cannot name a structural advantage you bring to this market, stop here.
Product gap analysis. What must change in your product to serve this market? This is where most teams lie to themselves. “Our product works as-is” is almost never true for a genuinely new market. Map every assumption your current product makes — about user behavior, infrastructure, language, compliance, payment — and check which ones break in the new market. Kill criterion: if the product gap requires more than 30% of your engineering capacity for more than two quarters, you are not entering a market — you are building a new product.
Distribution feasibility. Can you reach these customers? Having a good product for a market you cannot reach is the same as not having a product. In India, this question is especially sharp. B2B SaaS in metros runs on inbound marketing and inside sales. B2B SaaS in tier-2 cities often requires field sales and channel partners. Consumer apps in tier-1 run on digital acquisition. Consumer apps in tier-3 run on referral loops and offline activation. Kill criterion: if your existing distribution channels do not work and you have no plan to build new ones, stop here.
Economic viability. Will the unit economics work? A market can be large, growing, and well-suited to your product — and still be a bad bet if the cost to serve is higher than the revenue per customer. Ola launching in a small city where average ride value is Rs 80 but driver acquisition costs Rs 15,000 is a different economic equation than Bangalore where ride values are Rs 300. Kill criterion: if projected CAC payback exceeds 18 months in the new market, you need a very good reason to proceed.
The beachhead principle
The single biggest mistake in market entry is going broad. “We are launching in India” is not a market entry strategy. “We are launching for independent pharmacies in Pune and Nagpur that currently manage inventory on paper” — that is a market entry strategy.
The beachhead principle is borrowed from military strategy: capture a small, defensible position first, then expand from strength. In product terms, this means picking the narrowest possible segment in the new market where you can win decisively, then using that win as a platform for expansion.
Why narrow? Three reasons.
Feedback density. Twenty customers in one segment give you better signal than two hundred customers across ten segments. You can see patterns. You can build relationships. You can iterate fast. When Freshworks entered the US market, they did not try to compete with Zendesk across all segments. They focused on small businesses that found Zendesk too expensive and too complex. That narrow focus gave them dense feedback and a product that nailed the use case.
Resource concentration. Your team is finite. Spreading across multiple segments in a new market means doing everything poorly. Concentrating on one segment means doing one thing well. A startup with ten engineers cannot build for SMBs and enterprises simultaneously in a new geography. Pick one.
Credibility compounding. Your first ten customers in a new market become your social proof for the next hundred. But only if they are in the same segment. Ten happy pharmacy owners in Pune is a story. Ten random customers across five industries in five cities is noise.
The expansion sequence matters too. Once your beachhead is secure — you have product-market fit in the narrow segment, retention is healthy, unit economics work — you expand to the adjacent segment. Not a distant one. Adjacent. Pharmacies in Pune to pharmacies in Mumbai. Then to clinics in Pune. Then to clinics in Mumbai. Concentric circles, not random jumps.
Pick a market entry scenario relevant to your product (or use this one: an expense management SaaS currently serving startups in Bangalore wants to expand to tier-2 cities).
- Define the narrowest possible beachhead segment. Who specifically? Where specifically? What use case specifically?
- List three assumptions your current product makes that might break for this segment.
- Define the “beachhead secured” criteria — what metrics would prove you have won this segment? (Hint: retention and NPS matter more than acquisition numbers.)
- Map the first three expansion moves after the beachhead. Are they adjacent or random?
If your expansion moves require completely different product work from each other, your beachhead is too broad.
India-specific market entry patterns
Market entry in India has patterns that do not exist elsewhere. If you are building for the Indian market — or expanding within it — these are the dynamics you need to internalize.
Tier-2 and tier-3 are not “smaller versions of tier-1.” This is the most dangerous assumption in Indian product strategy. Users in Jalandhar and Ludhiana have different payment preferences (COD dominance), different device constraints (lower RAM, smaller screens, intermittent connectivity), different language expectations (Hindi-first or regional language-first), and different trust models (word-of-mouth over digital reviews). The companies that cracked tier-2 and tier-3 — Meesho, ShareChat, Josh — built fundamentally different experiences, not just translated ones.
The WhatsApp distribution layer. In India, WhatsApp is not a messaging app. It is infrastructure. Any consumer product expanding to new segments needs a WhatsApp strategy — for onboarding, for support, for viral loops, for commerce. MyGate uses WhatsApp for resident communication. Meesho’s entire reseller model runs on WhatsApp sharing. If your market entry plan does not account for WhatsApp as a channel, you are missing the largest distribution surface in the country.
Regulatory geography. India is not one regulatory market. It is a patchwork. GST compliance differs by state for certain categories. Food delivery has different rules in different states. Fintech products face state-level lending regulations. Healthcare products face different telemedicine rules. Your market entry analysis must include a regulatory map — not just “is it legal?” but “what operational changes does compliance require in each state?”
The trust deficit in new markets. Indian consumers — especially in newer digital segments — have a trust problem with unfamiliar brands. This is rational: they have been burned by fly-by-night apps, fraudulent sellers, and poor support. Your market entry needs a trust-building phase that metro-first products often skip. This might mean COD options you would rather not offer, return policies that hurt your margins, or local language support that adds operational cost. The companies that skip this phase see acquisition numbers and celebrate, then watch 60-day retention collapse.
Offline-to-online bridges. Many Indian market segments are not “offline” because they reject technology. They are offline because no one built the bridge. Khatabook did not convince shopkeepers that digital ledgers are better than paper. They built a digital version of the paper ledger — same mental model, better functionality. Your market entry in India often requires building the bridge between how users currently work and how your product works, rather than asking users to change their workflow.
Product review. PM presents the tier-2 expansion plan.
PM: “For the tier-2 launch, I want to lead with a lite version — under 10MB, works on 2G, Hindi-first interface. We drop the features that assume broadband and focus on the core transaction flow.”
Engineering Lead: “That is basically a different app. Can we not just compress the existing APK?”
PM: “We tried. Our current app assumes persistent connectivity for real-time sync. Tier-2 users drop connection mid-transaction. We need offline-first architecture for the core flow. It is a different app — and that is the point. The market is different.”
Engineering Lead: “How much engineering time?”
PM: “Twelve weeks for the core flow. But we test in two cities first. If 30-day retention is below 25%, we stop and reassess before scaling.”
The PM scoped the investment, set a kill metric, and made the bet reversible. That is how you enter a market you do not fully understand yet.
The best market entry plans are designed to be killed. If your plan has no exit criteria, it is not a plan — it is a hope.
When to not enter a market
The hardest part of market entry is saying no. Here are the signals that a market entry is a bad idea, even when the opportunity looks attractive on a spreadsheet.
Your core market is not yet won. If you have not achieved dominance — or at least defensible market position — in your current market, entering a new one splits your focus. Ola tried international expansion before consolidating India, and it cost them. Uber tried to fight in China while still losing money in the US. The pattern is consistent: premature expansion weakens both positions.
You are chasing a competitor, not a customer. “They launched there, so we should too” is reactive strategy. It assumes your competitor made a good decision. They might not have. Let them spend money validating (or invalidating) the market, then enter with better intelligence.
The entry requires capabilities you do not have and cannot build. If entering the healthcare segment requires regulatory expertise, clinical validation, and doctor relationships — and you are a consumer fintech — the distance between where you are and where you need to be is not a product gap. It is a company gap. No amount of engineering will close it.
The economics only work at scale you cannot reach. Some markets are only viable if you capture 30%+ market share. If the incumbent has 70% share and strong network effects, the math does not work unless you can dislodge them. Be honest about whether you can.
Test yourself
You are the PM for a B2B invoicing SaaS based in Bangalore. You have 800 paying customers, almost all in India. Your CEO returns from a conference in Singapore and says: 'Every Indian SaaS company is expanding to SEA. We need to be there by Q3.' You have 14 engineers and no one on the team has worked in Southeast Asian markets before.
The CEO wants SEA expansion by Q3. That is four months away. What do you do first?
your path
Zoho is considering entering the Indian HR tech market with a payroll and compliance product, competing with Darwinbox and Keka. Zoho has 75,000 SME customers on CRM. The HR market is dominated by mid-market players with deep customer success teams.
The call: Does Zoho's SME CRM base give them a structural advantage in HR tech, or is it a distraction?
Zoho is considering entering the Indian HR tech market with a payroll and compliance product, competing with Darwinbox and Keka. Zoho has 75,000 SME customers on CRM. The HR market is dominated by mid-market players with deep customer success teams.
The call: Does Zoho's SME CRM base give them a structural advantage in HR tech, or is it a distraction?
Where to go next
- Build the strategy that precedes market entry: Product Vision & Strategy
- Prioritize what to build for the new market: Prioritization
- Understand competitive dynamics before entering: Market Research & Competitive Analysis
- Define metrics for your beachhead: Metrics & KPIs