Cross-border startup operations
Running operations across countries fails for regulatory and reconciliation reasons far more often than strategic ones. Compliance has to be sequenced before growth, money needs one source of truth in one currency, and distributed teams need written follow-through more than they need answers. Everything below comes from doing this across India, the Maldives, the United States and the United Kingdom.
1. Compliance first, growth second
Compliance comes first because each step blocks the next. You cannot open a bank account without an entity, you cannot legally move capital without the outbound-investment filing, and you cannot invoice without tax registration. The sequence is not interchangeable, and discovering that mid-launch is expensive.
Setting up US operations for an AI/robotics company from India meant entity formation, ODI compliance, US banking, then the vendor and logistics network — in that order — before the first US customer could be closed. Teams that chase revenue first typically reach a signed customer they cannot legally bill.
2. One source of truth for money, in one currency you trust
Pick a reporting currency and hold every figure against it. Record the rate used at the moment of each transaction, not at month end. Keep it in one system rather than per-country spreadsheets that drift.
Across a roughly ₹1 crore monthly budget, centralised cross-border billing and a single metrics dashboard were what made a multi-currency monthly close reconcile. The real risk is not an incorrect figure — it is two people quoting different numbers for the same month, after which the founder stops trusting any reporting at all.
3. Close the loop, don’t have every answer
Distributed teams do not need their operator to know the answer immediately. They need to know that a question raised will come back resolved. Predictable written follow-through beats being constantly available, and it is the only thing that survives an eight-hour time difference.
Automated reporting that removed ten-plus hours a week of manual data retrieval from a founder’s calendar mattered less for the hours saved than for making the reporting boringly reliable.
4. Expect the operational surface to be jagged
Payment rails, hiring norms, invoicing expectations and vendor reliability differ per country in ways no research turns up in advance. Budget explicitly for a discovery period in a new market rather than assuming the second country works like the first.
Work-visa navigation in the Maldives, ODI filings from India, and fully remote operation from India for a London company were three genuinely different problems, sharing only the property that none of them came with a manual.
What I would tell someone starting this tomorrow
Map the regulatory sequence before writing the growth plan, and treat the first ninety days in a new country as instrumentation rather than execution. And read what a founder’s office actually is first — cross-border work is much harder if the role boundaries are not clear before you start.
Common questions
- What is the first thing to get right when expanding to a new country?
- Compliance sequencing, before growth. Entity, banking, tax registration and any outbound-investment filings have to be ordered correctly because each one blocks the next — you cannot open a bank account without an entity, and you cannot move money without the filing. Teams that chase first revenue before this is settled usually end up unable to invoice or receive payment.
- How do you handle multi-currency accounting in an early-stage company?
- Pick one reporting currency and hold every figure against it, with a single source of truth rather than per-country spreadsheets. Record the rate used on each transaction at the time it happens. The failure mode is not a wrong number but two teams quoting different numbers for the same month, which erodes the founder's trust in all reporting.
- What is ODI compliance and when does it apply?
- Overseas Direct Investment (ODI) is the Indian regulatory filing required when an Indian entity or resident invests in a foreign entity — for example, an Indian startup setting up a US subsidiary. It gates the legal movement of capital abroad, so it sits early in any India-to-US expansion sequence rather than being handled after incorporation.
- How do you manage a team across several time zones?
- Close the loop in writing, and reduce the number of decisions that need a live conversation. Teams working across time zones do not need their operator to have every answer immediately; they need to know that a question raised will be resolved and returned to them. Predictable written follow-through beats availability.
- How many countries can one operator realistically cover?
- Two well, three with strain, in my experience — but the limit is regulatory surface area rather than headcount. Two countries with simple structures is easier than one country with a complex entity and licensing position.
Expanding into a new market?
Cross-border market entry is one of the engagements I take on. The longer narrative version of this is in running ops across four countries with no playbook.