But you suggested getting rid of the existing team in favour of a remote team in another country, because remote is more efficient. You lose more than you'll gain in the cost savings.
I'm fully on board with remote teams across the globe, especially when it means engineers can be on call while the sun is up.
Do it becuase it gives you access to talent, not because it's cheaper or remote is "efficient".
In fact, it's even more of an illustration for what i'm trying to say. Let's assume all remote hurdles have been lifted, 100%. So, if I'm hiring for a new group initially based in Australia, what makes me recruit from a pool of 25mil people vs. 250mil people in Pakistan and 1400mil in India? Why in this case even have an Australian engineering team, ever?
My point was that remote teams across countries, and in some cases timezones, can work. But replacing a team just becuase you can get cheaper engineers is destructive.
Build a remote team on purpose, or let your team move to locations that requires them to work remote.
The point I'm trying to make is focus on the team and what's best for them. If it's a new team why limit yourself to one country.
> Why in this case even have an _________ engineering team, ever?
The same reason some engineers command more renumeration than others (in the same market), you find good talent and want them on board.