At times like this, outsourcing the development of your software to an engineering team aboard is a popular route to delivering a product at lower cost. But how often does it work, and is it an effective method or just a false economy? MD for Solutions & Consultancy, Charlie Sell looks at the pros and cons of outsourcing development to an offshore team.

The risks of outsourcing

Over the years, I’ve worked with many clients who have experimented with outsourced development. One model involves a handful of experts in a London office and 100 mid-level developers in India. In theory, each team plays to its own strengths, but in this blended approach the outcome is often plagued by difficulties with quality control, troubleshooting, bug fixing and frustration.

If an engineer has a question that could be answered in 30 seconds, everyone is in the same room (or on Slack), English is their first language and there’s an understanding of the culture among the team, it will get solved quickly and efficiently.

In distributed team situations where the engineer has no relationship with senior colleagues 10,000 miles away – and especially if a them-and-us culture exists – the engineer may not have the confidence to raise the query at all, or if they do, may not get an answer and productivity is lost.

I’ve seen companies attempt to build remote teams in places like Ukraine where the language barrier has been the main driver of issues, though there are also risks in setting up in countries with political uncertainty.

Cultural differences can also derail a project. In India, language is not a barrier as their English is often excellent, but engineering teams have a tendency to agree rather than challenge, which can cause huge problems.

Nine times out of 10, outsourcing is done because of price but unless you consider these barriers and weight up the many factors, it can proves to be a false economy that dooms your project to failure.


Weighing up the benefits

Speed to market, quality and cost all play into the decision to outsource some or all of your engineering capability. On the one hand, an outsourcing solution may take more time but be delivered more cost effectively, whereas internal teams will get you there quicker but at greater cost.

Sometimes, offshore teams are seen as the solution to situations where UK teams are under pressure to deliver and extra resource is needed to avoid technical debt. There’s a perception that many hands make light work, but the experience of many of our clients over the years shows that rarely happens.

Flexibility is another attractive feature of outsourcing your technology, as it enables you to quickly upscale resource in your team. You can triple your engineering capacity almost immediately, and downsize it too. If you’re working towards a major product release or need resource for a specific project, outsourcing can support the delivery and avoid redundancies afterwards.

If you’re attracted by these and other upsides to outsourcing, just bear in mind there will still be an upfront investment of your time and energy to transfer knowledge and expertise across to the remote team.


How can outsourcing be done right?

Fortunately, there is rarely a question mark over ability, as engineers in locations like India or Africa will be every bit as good as engineers in Europe.

The success stories we hear from clients all share common themes, where risks are mitigated by leadership and guidance.

Instead of outsourcing to a third-party, the most effective models involve embedding a company’s own people into an outsourced office, where they can develop relationships, train and mentor the new team.

Some of our clients have set up a new office, sent their leadership and welcomed the offshore team’s senior staff back to the UK to fully share knowledge and integrate the teams.

A software company I know are a great example of a company that has chosen outsourcing and supported it with a great strategy.  They chose to create an engineering hub in Poland, but made it their engineering headquarters and moved their CTO and many of the senior engineers there.

It’s also next to a technical university which they sponsor, ensuring they get the best graduates as they leave. For the graduates, the company is an attractive proposition as they can learn from internationally-minded engineers and sector leaders and benefit from a proper training and development infrastructure.

Engineers are treated the same wherever they are in the business, and viewed more as rock stars than a rock bottom cost solution. That model, making use of access to talent, is very different to most peoples’ assumptions on outsourcing, yet it’s a fantastic example where everyone wins.

If however you still really want to outsource your entire operation to a third-party, then look for subject matter experts who have greater experience than you. This kind of model is effective for founders who have an idea, see an opportunity, but lack the technical knowledge, but it relies completely on expertise and trust.

There are always arguments in favour working with remote teams, and always risks that must be considered. What’s important is that your strategy fits your business and products, and that once you’ve made your decision, you fully commit. For tech-first businesses with teams in multiple countries, the engineers must have the same capability and get the same respect if you the relationship is to succeed.


If you’d like to discuss the pros and cons of outsourcing your development team, then get in touch with us.