Running ops across four countries with no playbook
Running operations across four countries taught me that cross-border work fails for regulatory and reconciliation reasons far more often than strategic ones. By the time I was building the India–US operating bridge for an AI/robotics startup, I'd already run hospitality and investment operations in the Maldives and closed angel rounds for two space-tech ventures. None of it came with a manual. Here's what actually held it together.
1. Compliance first, growth second
Compliance comes first because each step blocks the next one, not because it is virtuous. It's tempting to chase the exciting part — the first US customer, the big tourism booking, the investor deck. But ODI filings, entity setup, and work-visa compliance are the load-bearing walls. Get them wrong and everything built on top of them is at risk. I've watched founders want to skip this step to move faster. It never actually saves time.
2. One source of truth for money, in one currency you trust
One currency of record, one system, and the rate recorded at the moment of each transaction — that is the whole discipline. Managing a ~₹1 Cr monthly budget across currencies taught me this the hard way: if your billing and reporting live in five spreadsheets and three currencies, nobody — including the founder — actually knows the real number. Centralizing cross-border billing into one dashboard was the single highest-leverage thing I built in that role.
3. The team doesn't need you to have the answer — they need you to close the loop
Most operational chaos in a distributed team is a follow-up problem, not a knowledge problem. Coordinating a 17-person multinational team in the Maldives, or a 6-person cross-border team for a robotics startup, taught me that people start things and someone has to make sure they finish. Across time zones that guarantee matters more than availability, because nobody can wait eight hours for an answer but everybody can wait for a reliable one.
What I'd tell someone starting this kind of role tomorrow
Get comfortable being the least specialized person in the room and the only person who knows how all the pieces fit together. That's the job.
If you're doing this deliberately rather than by accident, the field guide to cross-border operations sets out the sequence in more detail, and what a founder's office actually is covers why the role boundaries matter before you start.
Common questions
- What is the most common mistake when expanding a startup to a new country?
- Chasing first revenue before the compliance sequence is finished. Entity setup, banking, tax registration and any outbound-investment filing each block the next one, so a signed customer can arrive before there is any legal way to invoice or get paid. Sequencing compliance first is slower for about six weeks and faster after that.
- How should an early-stage company handle multi-currency reporting?
- Choose one currency of record and hold every figure against it, recording the exchange rate at the time of each transaction rather than at month end. Keep it in one system. The damage from spreading it across per-country spreadsheets is not an incorrect number but two people quoting different numbers for the same month, after which the founder stops trusting all reporting.
- What actually causes operational chaos in distributed teams?
- Follow-up, not knowledge. Most stalled work in a cross-border team is not blocked on expertise — it is work someone started and nobody closed. The operator's job is less about having answers than about guaranteeing that anything raised comes back resolved.
Keep reading
Before you hand operations to an AI agent, fix the ledger
AI agents are moving into startup operations, and many projects stall on messy data and unclear ownership. Three tests a founder's office should run first.
What a founder's office actually is (and isn't)
It's not chief-of-staff cosplay. A founder's office is the person a founder hands a half-formed idea to and trusts that it comes back as a working business.
For the full picture of how this played out in practice, see the four ventures I have run a founder’s office for, or how I work with founders.
Enjoyed this? Get the next one.
Occasional notes on founder’s-office work and cross-border ops.
One click to confirm on Substack. No spam, unsubscribe anytime.