In my experience, running a cross-border business in can bring unique challenges, especially around local compliance and payments. The real issue isn't just meeting expat needs — it's ensuring your backend supports multi-currency transactions and aligns with ever-changing local healthcare regulations. Consider building redundancy in your payment processing to avoid unexpected freezes. $5 saved on fees today could cost $500 in lost clients if you miss a regulatory update.
This is a textbook example of concentration risk — your entity formation, payment processing, and customer relationship all running through a single provider. When Stripe Atlas handles your LLC and your payments, a compliance flag in one system can cascade across your entire business.
Two structural things worth separating going forward: (1) your legal entity from your payment processor — so a payment shutdown doesn't threaten your corporate standing, and (2) your payment stack itself — having a warm backup processor (not just "integrated" but actively processing some volume) means you can switch in hours, not days.
The eSIM space isn't uniquely risky, but any business where Stripe's fraud model doesn't have great training data for your vertical is exposed to this.
Nice execution. The local-first approach is a smart call for this kind of data — most people won't trust a cloud service with their exact location history across countries.
One nuance I've run into working in this space: the 183-day rule gets treated as universal, but the reality is messier. Some countries count partial days, others don't. Some have "center of vital interests" tie-breakers that override day counts entirely. And for US citizens, the day count is almost irrelevant — worldwide taxation applies regardless of where you sleep.
The Schengen rolling window is genuinely confusing for people and a strong feature to nail. Curious how you handle the edge cases where someone holds a residence permit in one Schengen country but travels freely across others — the 90/180 rule doesn't apply the same way in that scenario.