Ok. I am in. We only need 27 more then.Actually, we don't even need 40 people to take over the island. We only need 30. Some of the residents, such as their doctor, are temporary residents and have no right to vote.
Ok. I am in. We only need 27 more then.Actually, we don't even need 40 people to take over the island. We only need 30. Some of the residents, such as their doctor, are temporary residents and have no right to vote.
Have you read thisseems like Cyprus is good jurisdiction for what I want. Sure, it's not 0% tax. The 2.5% will require us to do some bookkeeping. But, as long as the company is low income, whenever we don't have time to deal with bookkeeping, we can just pay 2.5% of gross minus salaries, without bothering to record every single small expense, essentially paying more taxes than we will owe in order to save time.
Are we taking about doing node.js code he will write here? I would not worry much about this.For the above three reasons, the IP entity needs to precede the development of the IP.
Have you read this
https://www.soneverse.com/cyprus-audit-requirements-a-comprehensive-guide/
The audit is going to cost you 2000 per year. Minimum.
Are we taking about doing node.js code he will write here? I would not worry much about this.
The above solution will put the IP at risk.
But it will also be of minimal costs if the project ends up to be a total flop. As in it never really gets off the ground.
You want to find a solution for that fit's your revenue and not look at much at what others do. The revenue is still small but if you think you can grow it 2x or even 3x while later on 10x it would make sense to plan already now.Yeah, better not start this business for $10-$100k in revenue (!) if you expect to lose all your customer data...
@EliasIT with all due respect, I agree with you. But in his case, he does not expect it to grow beyond 100k.You want to find a solution for that fit's your revenue and not look at much at what others do. The revenue is still small but if you think you can grow it 2x or even 3x while later on 10x it would make sense to plan already now.
The customers for Goofer SAAS will be in the United States. I expect the gross revenues from Goofer SAAS to be between $10,000 a year and $100,000 a year. That's because it will be serving a very tiny niche market that is already well served by several desktop applications (but, to my knowlege, no SAAS).
You could probably also just set up a US LLC or UK Ltd.
As to the timeline, if everything goes to plan, I am expecting to need the Cyprus LLC is in spring 2026. 15 to 18 months from now. So, it's not too early to think about it. Like I said, I need an entity into which Yacine will assign intellectual property before he starts the development of the initial most likely (but not necessarily) throw away web applicatiion. For three reasons:
1) I need to give Yacine an incentive to work for $1 a year, to do the best job he can and create as little technical debt as possible during the development.
2) I need Yacine to have a strong incentive to run the SAAS business to the best of his abilities, while my remote involvement will be less than 10 hours a week.
3) As a US Citizen, if Yacine assigned the intellectual property to me before its development, and I later assign it to a non US company after it has been developed, I would be inviting the IRS and a whole lot of hurt into my life.
For the above three reasons, the IP entity needs to precede the development of the IP
you do a "code rewrite" (you do not actually do anything) and place the "new" code in a company built for this.
I wouldn’t recommend that he tries to reinvent the wheel and write everything from scratch.Let me give you some advice.
Program Code
I would highly advise you to have your friend programming the software alone. Do not take in external programmers. If he is a guy with capabilities, he will have a much easier task changing anything in 5 to 10 years from now.
I would also advise to limit the number of external libraries to the minimum. Chances are that there will be updates, changes etc. and the library becomes unsupported by the time you go live. Better write your own code that you can maintain.
Intellectual Property
We are not talking about an operating system where 1000 people are working on it for 5 years. You can just write it and one things would eventually kick off, you do a "code rewrite" (you do not actually do anything) and place the "new" code in a company built for this. Nobody is going to track a one-month-project by some seond-year student (aka sophomore in the US).
That all being said, just focus on your work. Things are small enough that there will never be any big discussion about company goodwill, exit tax, etc.