I like to think of offices like a node process. Ideally you should have a tight event loop (your core team) who are physically located in the same location. That could consist of just founders, or founders + a few key employees.
Then, if you develop the right APIs, you can effectively run the rest of your team asynchronously.
But, from past experience in three completely virtual companies, not having people in the same timezone / a drivable distance is the company equivalent of blocking i/o.
Regarding your specific sitch... I'd say early on you want to be together 24/7. If you're past initial prototype / first customers and you're comfortable moving at the same pace, you can probably parcel it out a bit more.
I like to think of offices like a node process. Ideally you should have a tight event loop (your core team) who are physically located in the same location. That could consist of just founders, or founders + a few key employees.
Then, if you develop the right APIs, you can effectively run the rest of your team asynchronously.
But, from past experience in three completely virtual companies, not having people in the same timezone / a drivable distance is the company equivalent of blocking i/o.
Regarding your specific sitch... I'd say early on you want to be together 24/7. If you're past initial prototype / first customers and you're comfortable moving at the same pace, you can probably parcel it out a bit more.