```it takes dedication to manage an offshore team, a daily standup is not enough, you need to communicate effectively.``` Think about it this way: Any project

```it takes dedication to manage an offshore team, a daily standup is not enough, you need to communicate effectively.``` Think about it this way: Any project is composed of the business domain knowledge and execution skills. It's relatively easy to find off-shore dev teams with ok to good technical skills. It's a lot harder to communicate what you want built, how it should function and all the business rules that should be incorporated to a group of strangers who have different cultural contexts and cues and who most likely speak English as a second language. Off-shore dev teams are missing a whole lot of context that you or I may take for granted. Are you going to be able to manage a dev team without that context the same way you would manage a on-site dev team? Probably not. Some things that will help significantly in transferring that knowledge are requirement documents, technical specs, wireframes/mockups (all that documentation that startups neglect). You should probably be looking for demos on a regular basis. Managing an off-shore team is often a full-time job, especially when getting the project off the ground.