4 ms·

I see, thank you so much for your detailed response again davismfwl. It definitely seems like going the international contractor route seems most feasible. I do

I see, thank you so much for your detailed response again davismfwl. It definitely seems like going the international contractor route seems most feasible. I do wonder though at what breaking point it just makes sense to hire an international worker full-time and when that investment is worth it. Given your explanation, it definitely seems that PEO is the best route.

davismwfl 7y ago
I think there could be multiple different things that could be a trigger, or just a good milestone to use. But in general I wouldn't consider it until I had reliable, consistent revenue coming in (or had significant investment dollars) and had established all my basic business practices and that they are working pretty much on auto pilot. There is just so much to do in the beginning that you want to minimize any unnecessary tasks. There are really talented and qualified people all over the globe, keeping it closer to your timezone in the early days just reduces cognitive load on unnecessary struggles. While I only mentioned the costs and extra work in setting this up, there are other costs which are more hidden. For example, communication delays on a project that isn't well defined (every startup ever) which requires above average feedback and iteration (totally normal) means added delays. Usually I assume with a newer remote team that is 6+ hrs ahead/behind me it will add one extra week per month of schedule to account for the delays etc. So if it would take normally 4 weeks, I'd estimate it to be 5 weeks. Sometimes of course, low coordination or well defined projects means that is only 1 day, but other times it means it is 3 weeks. This is hard to predict and is highly dependent on your experience setting up and working with remote workers, and their experience working remote. I am highly in favor of remote work, and I both employ people remotely and work remotely myself and have done so for many years. A team that is setup and has worked remote before won't consistently have these types of delays, but it is very common with newer remote teams. Good luck!

davismwfl 7y ago

I think there could be multiple different things that could be a trigger, or just a good milestone to use. But in general I wouldn't consider it until I had reliable, consistent revenue coming in (or had significant investment dollars) and had established all my basic business practices and that they are working pretty much on auto pilot. There is just so much to do in the beginning that you want to minimize any unnecessary tasks. There are really talented and qualified people all over the globe, keeping it closer to your timezone in the early days just reduces cognitive load on unnecessary struggles. While I only mentioned the costs and extra work in setting this up, there are other costs which are more hidden. For example, communication delays on a project that isn't well defined (every startup ever) which requires above average feedback and iteration (totally normal) means added delays. Usually I assume with a newer remote team that is 6+ hrs ahead/behind me it will add one extra week per month of schedule to account for the delays etc. So if it would take normally 4 weeks, I'd estimate it to be 5 weeks. Sometimes of course, low coordination or well defined projects means that is only 1 day, but other times it means it is 3 weeks. This is hard to predict and is highly dependent on your experience setting up and working with remote workers, and their experience working remote. I am highly in favor of remote work, and I both employ people remotely and work remotely myself and have done so for many years. A team that is setup and has worked remote before won't consistently have these types of delays, but it is very common with newer remote teams. Good luck!