You're probably expecting us to say that off-shoring is a bad idea, you should never do it, it's scary, etc. And we should, as it is direct competition to our services. But the truth is, off-shoring can be a good idea in some circumstances. That's why all the big four banks have been doing it for years. It's not inherently bad, it just has to be managed well.

If you have the below skills/capabilities in-house, then off-shoring can be a good way to save money on development costs:

• Time and ability to work with a team in a different timezone
• Understanding of cultural differences and communication styles
• Strong project management skills
• Ability to clearly define requirements and expectations

If you think you have the above capabilities and are prepared to manage the risks, then here are some tips for you to help you succeed:

• Write your requirements in User Stories format and include acceptance criteria for each story. This will help ensure that everyone has a clear understanding of what needs to be built and how it will be tested.
• Ensure you have access to the source code from day one. Download a copy of the codebase if not each day, then each week at minimum.
• Have the off-shore team provide you with the technical documentation before starting the project. Have this reviewed by someone technical.
• You'll generally have better results if you have the design done locally and provide it to the off-shore team.
• Ensure you have a contract in place that includes clear deliverables, timelines, and payment terms.

If you don't have those capabilities, or you need help managing the risks, then we can help consult so that you are in a better position to succeed. Check out the Cyprusays case study for an example of how we helped a client successfully manage an off-shoring relationship.

Still have questions? Give us a call or send us a message to understand more without any pushy sales tactics.