Hiring Developers in India as a UK Startup: IR35, UK GDPR, IP and R&D Tax Relief (2026)

For a UK startup, hiring developers in India is legal, common and typically 60 to 70% cheaper. The catch is that the compliance risk is not where most founders look for it. IR35 gets the attention. The things that actually bite are Indian worker classification, UK GDPR transfers, IP assignment and the loss of R&D tax relief.

This guide covers each one, what the engagement options are, and what to put in the contract. We are an India-based agency, so we have a commercial interest in this topic. We have tried to make the trade-offs honest, including the ones that do not favour us. This is general information, not legal or tax advice. Have a UK accountant and solicitor review your setup.

For the cost side of the decision, see our senior developer rates in India and the broader offshore team guide.

IR35: usually a non-issue (but not the whole story)

IR35 and the off-payroll working rules exist to stop UK-based workers using personal service companies to avoid employment taxes. A developer who is not UK-resident and does all their work in India is, in general, outside UK income tax and National Insurance, so there is nothing for IR35 to reclassify.

That does not mean "no classification risk". It moves to India. Indian authorities look at substance, meaning control, integration into your business and economic dependence. A developer who works full-time, to your schedule, on your tools, taking your instructions, can be treated as an employee under Indian labour law whatever the contract says. India's consolidated Labour Codes, which came into effect in November 2025, tighten some of the rules on how pay is structured. If that happens you can face exposure for things like provident fund, gratuity and notice obligations.

There is a second, subtler risk. A team in India that performs your core business functions, or someone there who habitually concludes contracts for you, can create a permanent establishment under Article 5 of the UK-India double taxation treaty, giving India a claim to tax part of your profits. Engineering roles carry much less of this risk than sales roles, but get it checked if you plan to build a large team.

Four ways to hire, and what each one risks

The agency route shifts the employment compliance to the vendor. The agency is the employer, handles Indian payroll and statutory contributions, and replaces a developer who leaves. That is why most pre-seed to Series A UK startups use it. The trade-off is that you pay the agency margin, and your continuity depends on the vendor.

Individual contractors look cheapest, but the saving shrinks once you account for classification risk, IP clean-up and the cost of a project stalling when one person disappears. We see a lot of those rescues, as covered in our guide to rescuing a failed outsourced project.

UK GDPR: Indian developers and your customer data

If your Indian team can see personal data of UK individuals, that is a restricted transfer under UK GDPR. India does not have a UK adequacy decision, so you need an Article 46 safeguard in place. The ICO offers two:

• the International Data Transfer Agreement (IDTA), a standalone UK contract; or
• the UK Addendum to the EU Standard Contractual Clauses, if you already use the EU SCCs.

You should also document a transfer risk assessment and list the Indian vendor as a processor in your records and privacy notice.

The cheapest compliance control is to avoid the transfer. Developers rarely need real customer data:

• use synthetic or anonymised data in development and staging;
• keep production access limited to a small named group, with MFA and logging;
• keep production databases in a UK or EU cloud region, even if the developers are elsewhere;
• remove production access when a project ends.

India is also bringing in its own law. The Digital Personal Data Protection Rules were notified in November 2025, with the main obligations for data fiduciaries phased in over roughly 18 months, around May 2027. Your Indian vendor will have its own duties under that regime, so ask how they are preparing.

IP ownership: get it in writing

Under UK law, a contractor or agency generally owns the copyright in what it writes unless it assigns that copyright to you in writing. This catches founders out more than any tax rule. Your contract should include:

1. An express assignment of all IP in the deliverables to your company, effective on creation or payment, not "on completion".
2. A moral-rights waiver or non-assertion clause, drafted so it holds up under both UK and Indian law (ask your solicitor to check the Indian side).
3. A back-to-back assignment between the agency and each developer. Ask to see the clause.
4. A confidentiality and non-use clause that survives termination.
5. A third-party code and open-source warranty, with a list of licences used.
6. Repository ownership. Code lives in a GitHub or GitLab organisation you own from day one, and the agency commits to it. Never accept code delivered only by zip file at the end.

VAT and R&D tax relief

Two UK tax points that routinely surprise founders:

• VAT. B2B services from a supplier outside the UK are generally subject to the reverse charge. If you are VAT-registered you account for the VAT on your return and, where you can reclaim input VAT, the net effect is usually nil. Do not assume that the Indian invoice is simply VAT-free.
• R&D tax relief. Since the merged scheme began in April 2024, relief on contracted-out R&D and externally provided workers is generally limited to UK-based expenditure. Overseas spend qualifies only where the conditions of the research make it necessary to carry it out abroad. A lower price does not meet that test. If your product is genuinely R&D-heavy and relief matters to your cash flow, model the offshore saving against the lost relief before committing. This can change the answer for some startups.

Time zones: how much overlap you actually get

India Standard Time is UTC+5:30 with no daylight saving. London is UTC+0 in winter and UTC+1 in summer.

In practice, a UK founder gets a live window from early morning to early afternoon, and the Indian team keeps working after you finish. Many teams shift Indian working hours an hour later to extend the overlap. Run standups, design reviews and releases inside the overlap window, and keep everything else asynchronous with written tickets and recorded demos.

A 10-point contract checklist

1. Fixed scope or clear rate card, with a change-request process.
2. Express IP assignment and moral-rights waiver.
3. Back-to-back IP clauses between vendor and developers.
4. Code in your repository from day one.
5. NDA that survives termination.
6. IDTA or UK Addendum if personal data is accessible.
7. Named personnel, with notice before swapping senior developers.
8. Right to audit security practices, and breach notification within 24 to 72 hours.
9. Governing law (England and Wales) and a dispute process that works across borders.
10. Handover and exit terms, including documentation, credentials and a transition period.

Work with a team that has done this for UK startups

We are an India-based product studio working with startups in the UK, US and Australia. We contract under B2B agreements, assign IP to you on payment, work in your repositories and give you a weekly demo. If you want to sanity-check an engagement model, we will walk you through it, including telling you when a different route fits better. See how we work with UK clients, look at the hire a developer options, or book a free call.

This article is general information and not legal, tax or immigration advice. Rules change, so confirm with qualified UK and Indian advisers before you commit.