An Indian SaaS Goes to Southeast Asia
Payroll software is a local-rules business. Can it travel?
The Prompt
Your client sells payroll-and-compliance SaaS to 18,000 Indian SMEs at ~₹40,000 average annual contract value (ACV), growing 35% with strong retention. The board wants international expansion and has shortlisted Southeast Asia. Assess the move and recommend a market and an entry route.
Opening exchange
Payroll is unusually localization-heavy — tax tables, labour law, statutory filings differ per country and change yearly. So first: why international at all, when India SME penetration is still low? Is this board ambition or a real ceiling?
Challenging the premise is risky — but payroll's localization burden makes "why leave India?" the single best first question here.
Fair challenge. India remains big, but two US-funded competitors are discounting aggressively at home; the board wants a second engine before the home market commoditizes. Budget is $5M over two years.
A hedge, then — with a hard budget. That argues for one country done deeply, not a regional spray. I'll screen SEA markets on three axes: SME-payroll demand and willingness to pay, regulatory complexity (our moat once built, our cost to build), and competitive whitespace. Then pick build-vs-partner-vs-acquire.
Structure & Hypothesis
Analysis & Data
Screen data: Indonesia — 1.2M target SMEs, low SaaS penetration, complex and fast-changing rules, Bahasa-only, two funded local champions. Philippines — 350K target SMEs, English-friendly, US-style payroll culture, moderate rules, no dominant SME player. Vietnam — 500K SMEs, rules moderate, but payroll deeply informal. Singapore — small, saturated, high ACV.
Indonesia is the biggest prize but the worst fit for $5M: language, regulatory velocity, and funded local champions each multiply cost. Vietnam's informality means we'd be selling formalization, not software — a different, slower business. Singapore is a flag, not a market. The Philippines wins on fit: English lowers product and sales translation cost, no dominant incumbent, and US-influenced payroll culture matches SaaS buying behavior. 350K SMEs at even $800 ACV is a $280M TAM — plenty for a second engine.
Picks with reasons tied to the client's constraint ($5M, 2 years), not to raw market size. Biggest ≠ best.
And the route?
Partner-first, acquire-later. Year 1: white-label a local statutory engine, sell with our front-end to BPO-adjacent SMEs in Manila and Cebu — prove 300–500 paying logos. If the wedge holds, use remaining budget to acquire the partner or a rules-engine asset and internalize the moat. Building from scratch spends the whole budget before validating demand — wrong order.
Recommendation
Recommend to the board
- Go international as a hedge — but one country, done deeply: the Philippines, on fit-to-budget, not Indonesia, on size.
- Partner-first entry: white-label local compliance, own the customer experience, validate 300–500 logos in 12 months.
- Pre-negotiate acquisition rights with the compliance partner — option value for the moat, exercised only on proof.
- Kill criteria up front: <250 logos or <70% gross retention at month 15 → stop, refocus on India.
Key Takeaway
What this case teaches
For B2B software entries, screen countries on cost-to-localize and fit-to-budget, not headline TAM — and sequence entry so the cheapest validation comes first. The biggest market is often the most expensive place to learn you were wrong.