Outsourcing software development from the UK: a practical guide for 2026

Onshore, nearshore, offshore

Onshore means a UK team. Nearshore usually means Europe within a couple of hours of London: Poland, Romania, Portugal and Spain are common choices. Offshore means further away, most often India, South East Asia or South Africa. The labels matter less than two practical questions: how much of your working day the team shares, and how much of the work it can own without you managing it hour by hour.

Where UK companies build, compared

South Africa sits in an unusual spot: offshore by distance, nearshore by clock. Johannesburg does not change its clocks, so it is one hour ahead of London in summer and two in winter, and English is the language of business and code. We wrote up why companies outsource to South Africa.

Buy an outcome, not hours

Staff augmentation is the cheapest-looking line on a spreadsheet and the most expensive way to discover that nobody owned the outcome. If nobody on your side has the time and the skill to run developers day to day, buy the outcome instead.

The contract: seven things it must say

1. Intellectual property: everything written for you is assigned to you, on payment at the latest, with a licence for any pre-existing components the supplier reuses.
2. Accounts: repositories, cloud hosting, domains and third-party services are set up in your name from day one.
3. Scope and change: a written scope that says what is out as well as what is in, and changes quoted before they are built.
4. Payment: milestones tied to deliverables you accept on a staging environment, not to dates.
5. Data protection: processor terms under Article 28 of the UK GDPR, the list of sub-processors, and the transfer safeguard if the supplier is outside the UK.
6. Law and disputes: English or Scots law is common and reasonable to ask for; agree how a dispute would actually be resolved.
7. Exit: a handover clause covering documentation, credentials and a short transition, whoever ends the contract.

UK GDPR: when a team abroad counts as a transfer

This is the rule most companies miss. Under the UK GDPR, making personal data accessible to a separate company outside the UK is a restricted transfer, even if the data never leaves a London data centre. The UK regulator's guidance, updated in January 2026, counts remote access, and its own example is an overseas IT contractor reaching UK servers over a VPN (guidance). Your own employees working abroad are not a transfer; a supplier's staff are.

Where the destination has a UK adequacy regulation, that covers it: the EEA countries do, as do Switzerland, New Zealand, Israel, South Korea and a few others. South Africa, India and most offshore destinations do not, so you need a safeguard, either the International Data Transfer Agreement (IDTA) or the UK Addendum to the EU's standard contractual clauses, and a transfer risk assessment. Since the Data (Use and Access) Act 2025, that assessment asks whether protection at the destination is "not materially lower" than in the UK, judged reasonably and proportionately.

South Africa has its own comprehensive data protection law, POPIA, enforced by an independent Information Regulator, which gives the assessment something solid to rest on. Design helps as much as paperwork: keep personal data in a UK region, give the supplier access only to what the work needs, use test data where you can, and log access. More in UK GDPR for software products.

VAT: usually a reverse charge

Most business-to-business services are treated as supplied where the customer belongs, so a UK business buying software development from abroad pays no VAT on the invoice and accounts for it under the reverse charge on its own return (HMRC Notice 741A). A fully taxable business reclaims it on the same return, so the cash cost is nil; a partly exempt business may not recover all of it. South African suppliers can generally zero-rate services exported to non-resident customers, so no South African VAT is added either, though work done for you while you are physically in South Africa can be an exception.

IR35: rarely an issue for a fixed-price project

The off-payroll working rules (IR35) are aimed at individuals working through their own companies in what would otherwise be employment. When you contract a company to deliver a defined project, and it decides how the work is done and who does it and carries the risk of getting it wrong, HMRC treats that as a fully contracted-out service outside the rules (ESM10010). HMRC also says the rules do not apply where the worker is not chargeable to UK tax, which covers non-UK-resident staff working outside the UK (ESM10025).

Look again if anyone will work while physically in the UK, or if the arrangement is labour supply in substance: individual developers taking day-to-day direction from your team.

R&D tax relief: the catch with overseas teams

For accounting periods beginning on or after 1 April 2024, under the merged R&D scheme and the enhanced scheme for R&D-intensive companies (ERIS), payments to contractors for R&D carried out overseas, and externally provided workers who are not on a UK payroll, generally do not qualify (CIRD150500). The exception is narrow: the conditions the R&D needs (geographical, environmental, social, legal or regulatory) must be absent from the UK and wholly unreasonable to replicate there. Cost and the availability of workers are expressly disregarded (CIRD151100).

If relief was part of your budget, compare quotes net of it. The difference in price is often larger than the relief, but it is a number to check with your adviser, not an assumption to make.

Making it work day to day

• One decision-maker on your side who answers within a day.
• A standing weekly demo on a staging environment, and written updates you can forward.
• Shared hours for standups and reviews, agreed before the work starts.
• Your tools: the team works in your chat, your repository and your issue tracker, not the other way round.
• Security basics: single sign-on and multi-factor authentication on every account, least-privilege access, and an offboarding checklist.
• A short written scope for every phase, so nobody is guessing what done means.

Red flags when choosing a supplier

• A price before any questions.
• Code, hosting or domains kept in the supplier's accounts.
• No design before engineering, or design handed to "a partner".
• Day rates with no estimate of the total, or an estimate with no scope behind it.
• No named people: you meet sales, and a different team builds.
• Vague answers about data protection and transfers.

Outsourcing to Niddo

We are a software product studio in Johannesburg: one team that designs, engineers and runs software, in your working day, at a fixed price in pounds with no VAT added. See how we work with UK companies, or tell us what you are building.