Earlier quoted context omitted.
In my experience, things aren't that simple. For example, if you start a company in Country A but you are the main decision maker and live in Country B, then Country B may try to claim primary taxation of the company based on the fact that they consider the company being 'effectively run' from inside their borders despite your incorporation. And you aren't going to read about this kind of stuff on forums because it i…
As the post states, the idea is to hire / contract a number of people around the world. I don't think it would be easy to argue that that the company effectively operates from country A if most of the work is done by people in countries B..Z. IANAL, of course.
Ask HN: What is the best jurisdiction for internationally distributed teams?
51–60 of 208 posts
Re: Ask HN: What is the best jurisdiction for internationally distributed teams?
#52Earlier quoted context omitted.
I should clarify that the goal is not tax optimization but rather being able to focus on getting product market fit instead of spending time "managing" the company.
Typically low “managing” overheads is an additional perk of the tax havens.
From doing a lot of research I get that the general recommendation is to avoid tax havens (at least the obvious, shady ones - US, Ireland, Netherlands etc. are of course fine).
Re: Ask HN: What is the best jurisdiction for internationally distributed teams?
#53Earlier quoted context omitted.
As the post states, the idea is to hire / contract a number of people around the world. I don't think it would be easy to argue that that the company effectively operates from country A if most of the work is done by people in countries B..Z. IANAL, of course.
Well, wouldn’t a company like GitLab run into the same issues if most of their employees are not in the US?
Re: Ask HN: What is the best jurisdiction for internationally distributed teams?
#54One thing to note if, as a Dutch person (and possibly even if you're another European), you incorporate in the US: Many Dutch financial institutions hate people who have the "US person" status. If you own a US-incorporated company then I believe you will gain that status. Banks, lenders, stock brokers, etc will either refuse to do business with you, or will give you a lot of paperwork headache and/or charge you more…
I am indeed another European and I do know about the issues with being a "US person". Many banks and brokers will simply immediately close your existing account or not allow you to open one. However, are you sure that simply by owning a US company you become a US person? Because according to my understanding if you don't live in the US (and don't spend more than 4 months / year there) you wouldn't actually be tax res…
But I'm not 100% sure.
Re: Ask HN: What is the best jurisdiction for internationally distributed teams?
#55Earlier quoted context omitted.
We are US incorporated with staff in 14 countries. We use contracts for non-US staff and recently implemented letsdeel. So it looks good. You do not need a legal entity in most countries and in fact there can be significant disadvantages. The accounting management alone is a nightmare if you do it yourself. Ps most people set up their own company and we contract with that. Edit: add ps
Thanks for the feedback. Did you generally encounter any bigger issues with this setup or would you do it again for the next company? Also, where in the US did you incorporate? Delaware?
I would absolutely do the same in future. The contract to individual or individual's company is a standard model for remote companies like us that work on open source software. Some of our staff just have email & github access and that's it.
My email is in my profile. Send me email if you want to discuss. I'm happy to share details directly.
Re: Ask HN: What is the best jurisdiction for internationally distributed teams?
#56Earlier quoted context omitted.
I've heard lots of people talking about Estonia but can you name any international remote-first startup that became successful and raised money with an Estonian entity? I don't and this makes me somewhat suspicious :)
I don't know of remote-first companies, but I know of many Estonian companies that have raised a lot of money and been incredibly successful. To name a few: - Bolt - Wise (TransferWise) - Pipedrive I have a long history with e-Residency and know many e-Residents (e-Resident since 2015, 3 companies, member of EERICA.ee). Happy to chat about it. Email in bio.
Re: Ask HN: What is the best jurisdiction for internationally distributed teams?
#57Earlier quoted context omitted.
I've heard lots of people talking about Estonia but can you name any international remote-first startup that became successful and raised money with an Estonian entity? I don't and this makes me somewhat suspicious :)
I don't know of remote-first companies, but I know of many Estonian companies that have raised a lot of money and been incredibly successful. To name a few: - Bolt - Wise (TransferWise) - Pipedrive I have a long history with e-Residency and know many e-Residents (e-Resident since 2015, 3 companies, member of EERICA.ee). Happy to chat about it. Email in bio.
Re: Ask HN: What is the best jurisdiction for internationally distributed teams?
#58First off: There is no such thing as a "remote friendly" jurisdiction. Estonia is trying to market this, but don't drink the Kool Aid. Someone is going to have to make a trip to the bank or the notary every now and then. They'll have to show their faces. They'll have to affix their signature to things. With ink on paper. You will have to deal with business partners who will think this way: "This guy is based where I am based. He knows that if he tries to defraud me, the police will come knocking. So he's probably not trying to defraud me, so it should be safe to do business with them." Versus "This guy is just someone on the other side of the planet sending e-mails. He knows that if he successfully defrauds me, I won't be able to do anything about it. Therefore I don't want to take the risk."
A lot depends on trust and interpersonal dynamics between founders.
If there is a lot of trust between the founders, I'd pick one of the jurisdictions where a founder is actually based. Say you pick the U.S. for ease of access to capital. This means that the person who is physically in the U.S. would probably end up having to liaise, frequently in person, with banks, accountants, government offices, etc. This puts a huge admin burden on that person, and also requires a lot of trust from the founders in the other jurisdictions that this person won't abuse their privileged position. If that founder drops out and there isn't yet any physical presences in the U.S. except for that founder, the others will be in a difficult position, because their own jurisdictions might not recognize that this is legitimately a U.S.-entity if there is no actual person in the U.S. who is connected with this entity. So that's why it requires a lot of trust.
An alternative might be: Set up 4 sole traderships and a "placeholder entity" in a zero tax jurisdiction that kicks into gear when real money starts getting to the table. So:
* Frank Deutschmann registers with German authorities as a German sole tradership.
* John Smith registers with U.S. authorities as a U.S. sole tradership.
* Aussie Australian registers in Australia as an Australian sole tradership.
* Sing Singapore registers in Singapore as a Singapore sole tradership.
* Startup Inc registers in Bermuda, with each of the four holding a 25% ownership stake.
Startup Inc passes the following resolution, and correspondingly makes a contract with each of the other four entities:
Revenues: We intend to sell an API to clients at $1 per 100 calls. To achieve that, Startup Inc will subcontract Deutschmann to run one server, Smith to run one server, Austrialian to run one server, Singapore to run one server. When a request hits a server, the server should use a random number generator: With a 25% probability it will handle the request itself. With a probability of 25% for each of the other three servers, respectively, it will redirect the client to one of the other three servers. Every partner has to pay the costs for their own server (AWS bills etc). Every partner gets to keep revenue of up to $100k per year for requests their server serves. Revenue in excess of that goes to Startup Inc. Intellectual Property: All IP belongs to Startup Inc.
The thing about the API was just an example, but you can think of analogous ways of e.g. splitting sales of widgets. The load balancing algorithm is obviously stupid, this was just for simplicity of exposition.
The great thing about this arrangement:
* As long as your api makes below $400k, Startup Inc doesn't handle any money. The German authorities only deal with a German sole tradership and tax it on its small profits, and don't care about the rest. The U.S. authorities only deal with a U.S. sole tradership and tax it on its small profits, etc.
* The Bermuda entity is the key to the whole thing and yet no jurisdiction would have a reason to scrutinize it or try to poke holes in it or attach any real significance to their respective citizens holding shares that are legally worthless in a company that is legally not really doing anything.
* No founder enjoys a privileged position that requires almost unlimited trust. If any founder drops out at this stage, the other three continue to operate almost as if nothing had happened.
* While it makes a lot of sense for the four to take advantage of economies of scale by sharing heavily, there is also potential for some autonomy which reduces the potential friction if there's something that founders can't agree on (e.g. every one goes to their favourite bank and hosting provider, picks an accountant they personally trust, etc.)
* If they end up making a loss, everybody gets a loss on their personal income tax which they can each offset against future earnings.
* In this stage the whole thing legally just looks like four people coordinating their efforts on a joint venture of sorts. But the main thing is each of the persons. Which is the actual reality of the thing at this stage.
* For each additional dollar that the API makes beyond the $400k per year, the whole thing starts gradually to look more and more like a corporation, both legally and in terms of the real life circumstance that the legal structure represents. Increasingly, what matters is no longer the four people, but the IP and money held by the Bermuda Inc with every individual being pretty replaceable. And the legal structure actually reflects that, automagically turning from joint venture-like to corporate-like.
Re: Ask HN: What is the best jurisdiction for internationally distributed teams?
#59Delaware company and then all team members get set up as contractors in their country of residence. If they are in the EU they can contract from where they are from but live within the EU - more flexibility. But putting people on payroll has a huge overhead - better compensate employees to pay a local book keeper to invoice and process their payroll. Encourage people who have not contracted to research what contracto…
Re: Ask HN: What is the best jurisdiction for internationally distributed teams?
#60Earlier quoted context omitted.
I am indeed another European and I do know about the issues with being a "US person". Many banks and brokers will simply immediately close your existing account or not allow you to open one. However, are you sure that simply by owning a US company you become a US person? Because according to my understanding if you don't live in the US (and don't spend more than 4 months / year there) you wouldn't actually be tax res…
I recall that some of the questions mention that having US income is problematic, and that even having a US phone number is problematic. But I'm not 100% sure.