I remember the exact moment I knew we were in trouble. We had just hired our first engineer in Germany for RemoteTeam. The guy was a rockstar, a 10x engineer for real, and we were ecstatic. We sent him our standard US employment contract, he signed it, and we thought we were done. Six months later, he quit, and our German legal bill was ten times his salary. Why? Because we were complete rookies in international labor law. That single mistake cost us over $150,000 and a massive headache.
Everyone dreams of taking their startup global. It's a sign you've made it, that you have a product the world wants. But what no one tells you is that the world is a messy, complicated place full of different rules. I’ve been fortunate enough to build and sell two companies, RemoteTeam and MovieLaLa, and I’ve invested in over 200 startups, including some you might have heard of like Anthropic and Scale AI. I’ve seen this movie play out dozens of times. Founders, brilliant product people, and visionary marketers get absolutely wrecked by legal issues that seem boring until they blow up in your face. This is the guide I wish I had when I was starting out. Forget the dense legal jargon; here’s what you actually need to know.
Mistake 1: Thinking Your US Employment Contract Works Everywhere
This was my first big, expensive lesson. We thought hiring was hiring. You find a great person, agree on a salary, sign a contract, and get to work. That’s how it works in Silicon Valley, right? Wrong. So, so wrong.
When we hired that engineer in Germany, we had no idea about the country's powerful worker protections. Our at-will employment clause? Totally unenforceable. The non-compete we thought was ironclad? Laughed out of the room by his lawyer. In Germany, and much of Europe, employees have significant rights regarding termination, notice periods, and severance. You can’t just fire someone because it’s not working out. You need a damn good, documented reason, and even then, you’re likely paying them for months.
It’s not just Germany. I saw a founder try to hire a contractor in Brazil, only to find out after a year that the person was legally considered a full-time employee, and the company owed a fortune in back-pay for benefits, vacation time, and something called the "13th salary." Every country has its own quirks. In some, you have to pay for a mandatory health insurance plan. In others, you have to contribute to a state pension fund.
My advice is simple and non-negotiable: Do not hire a single person outside your home country without consulting a local employment lawyer. I know you’re a startup and you’re trying to save money. But spending $5,000 on a lawyer to get your contracts and hiring process right will save you from a potential $500,000 lawsuit down the road. I’m not exaggerating. I’ve seen it happen. Don’t be the founder who learns this lesson the hard way.
Mistake 2: Getting Your Corporate Structure and Tax Strategy Wrong
This one is less dramatic than the employment horror stories, but it can be even more expensive. You’ve got your Delaware C-Corp, you’re raising money, everything is great. Then you decide to open a small office in Singapore to tackle the Asian market. You create a subsidiary, move some money over, and start hiring. A year later, your accountant tells you that you have a massive tax problem because of something called "transfer pricing."
Transfer pricing is basically the set of rules that governs how you move money, intellectual property, and services between different parts of your company in different countries. If your US parent company owns the IP, and your Singapore subsidiary is selling the product, how much does the Singapore entity "pay" the US entity for the use of that IP? If you get that price wrong—if you set it artificially low to make your Singapore profits look bigger and your US profits look smaller—the tax authorities will come for you. And they are not friendly.
I watched a portfolio company spend two years and over a million dollars in legal and accounting fees to clean up a transfer pricing mess they created in their first year of international expansion. They had set up a subsidiary in Ireland and were essentially selling their own product to themselves for a dollar to book all the profit in a low-tax jurisdiction. It seemed clever at the time, but the IRS and its Irish counterpart did not see the humor.
Here’s the breakdown of what you need to consider:
- Subsidiary vs. Branch: Do you set up a separate legal entity (a subsidiary) in the new country, or do you operate as a branch of your parent company? They have wildly different legal and tax implications.
- IP Ownership: Where does your intellectual property live? Is it in your US parent company, or do you transfer it to a holding company in a tax-friendly location like Switzerland or the Netherlands? This has huge consequences for your long-term tax strategy.
- Cash Management: How do you get money into the foreign entity to pay for salaries and expenses? How do you get profits out? Every transaction has a tax consequence.
This is not stuff you can figure out on a weekend. You need a good international tax advisor. Yes, they are expensive. But they are a lot cheaper than a tax audit from two different countries at the same time.
Mistake 3: Ignoring Privacy and Data Laws (GDPR and Friends)
If you’re a software company, you’re a data company. And if you have users in different parts of the world, you are subject to their data privacy laws. The most famous of these is Europe’s General Data Protection Regulation (GDPR), but there are dozens of others, from California’s CCPA to Brazil’s LGPD.
When GDPR first came out, a lot of US startups just ignored it. They thought, "We’re a small company in San Francisco, what are they going to do?" Then the fines started rolling in. Fines that can be up to 4% of your global annual revenue. For a fast-growing startup, that’s a terrifying number.
I had a front-row seat to this with one of my investments. They were a B2C app with a few hundred thousand users in Europe. They had a privacy policy they copied from another website and thought they were covered. Then they got a letter from the Irish Data Protection Commission. It turned out their entire data collection and storage process was non-compliant. They weren’t getting proper consent, they were storing data for too long, and they couldn’t process a user’s request to delete their data.
The fix was a nightmare. They had to halt product development for three months to re-architect their backend. They spent over $200,000 on lawyers and consultants. And they lost a ton of user trust. All because they didn’t take data privacy seriously from day one.
Here’s what you need to do, right now:
- Map Your Data: Understand what data you are collecting, where you are storing it, and who you are sharing it with.
- Read the Rules: You don’t need to be a lawyer, but you need to understand the basic principles of GDPR. Things like "data minimization" (only collect what you need) and "purpose limitation" (only use it for the reason you collected it).
- Get a Real Privacy Policy: Don’t copy and paste. Use a reputable service or a lawyer to draft a policy that accurately reflects your practices.
- Build for Privacy: Make it easy for users to see their data, correct it, and delete it. This shouldn’t be an afterthought; it should be a core part of your product.
Expanding internationally is one of the most exciting things you can do as a founder. It’s a sign of success, of ambition, of building something that matters. But don’t let your ambition outrun your preparation. These three legal mistakes—employment, tax, and data privacy—are the unsexy, boring things that can kill your dream. I’ve made these mistakes myself, and I’ve seen them cripple dozens of otherwise promising companies. Learn from our scars. Spend the money, do the work, and build your global empire on a solid legal foundation.
Frequently Asked Questions
How has this view evolved over time?
My thinking on most topics has changed significantly over the years. Early in my career, I held many conventional views that experience proved wrong. I try to update my beliefs when the evidence changes.
What's the most common pushback you get on this?
People often push back by citing exceptions or edge cases. And they're usually right that exceptions exist. But building a strategy around exceptions rather than patterns is a losing game for most founders.
What experience informs this perspective?
This perspective comes from over a decade of building companies in Silicon Valley, two successful exits (RemoteTeam to Gusto, MovieLaLa to Gfycat), and investing in 200+ startups including Anthropic, OpenAI, and Scale AI. I write about what I've lived.
How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.