The time zone is a number, so use the number
India has no daylight saving and the UK does. Gujarat is UTC+5:30, so the gap is 5.5 hours while the UK is on GMT and 4.5 hours once it moves to BST. Set a 09:00–17:30 UK office day against a 09:00–19:00 IST studio day and the shared time is about 4.5 hours in winter and about 5.5 hours in summer.
| Season | UK time | India time | Shared hours |
|---|---|---|---|
| January | 09:00–13:30 | 14:30–19:00 | 4.5 h |
| July | 09:00–14:30 | 13:30–19:00 | 5.5 h |
That is enough for a daily check-in, a weekly review and questions answered the same morning. It is not enough for a team that wants an engineer sitting in every meeting. Decide which one you need before you compare quotes, because it changes who you should be talking to. Some of the work also happens while you are offline, which helps when the brief is clear and hurts when it is not.
Personal data has to get to India lawfully
If the system will hold personal data about people in the UK, UK GDPR and the Data Protection Act 2018 apply. India is not covered by a UK adequacy decision, so personal data that leaves the UK for work done in India needs a lawful transfer mechanism — usually the ICO's International Data Transfer Agreement, or the UK Addendum to the EU standard contractual clauses, together with a transfer risk assessment.
The simplest way to reduce this is to design the work so the problem barely arises. Develop and test on synthetic data, host production in a cloud account you own, and give the studio access through accounts you control and can revoke. Where the build allows it, live personal data never needs to leave your infrastructure at all. None of this is legal advice — take the specifics to your own solicitor or data protection officer.
What the contract should cover
A cross-border build leans on its contract more than a local one, because the usual fix for a misunderstanding — walking down the corridor — is not available. These are the terms worth settling in writing before work starts, whichever studio you choose.
| Term | What to settle | Why it matters |
|---|---|---|
| Scope and acceptance | A written scope, and what "done" means for each milestone | Most disputes are about what was agreed, not about quality |
| IP assignment | A signed, written assignment of copyright to you, effective on final payment | UK law needs an assignment of copyright to be in writing and signed |
| Payment | A schedule tied to milestones, the invoicing currency, and who bears transfer fees | Currency and fee surprises are avoidable |
| Data protection | A data processing agreement and the transfer mechanism, if personal data is involved | UK GDPR applies to the data, wherever the developer sits |
| Subcontracting | Whether any work is subcontracted, and under what confidentiality | It decides who actually has access to your systems |
| Termination and handover | What you receive if the project stops, and when | You should never be left holding half a system you cannot run |
| Governing law | Which country's law applies and where disputes are heard | It decides how enforceable everything else is |
| Defects after launch | How long defects are corrected at no charge, and what counts as one | Launch is not the end of the risk |
Ownership has to be in writing, from day one
Agree in the contract that the repository, infrastructure accounts, credentials and design files become yours on final payment, and that the work is created in accounts you own or can take over. Under UK law an assignment of copyright has to be in writing and signed by the person assigning it, so "you own it" in an email thread is not the same thing as an assignment. Ask your solicitor to confirm the wording. This studio's published position is that ownership of deliverables transfers on final payment; its Terms & Conditions and Refund Policy set out the rest.
Ask how you will see progress
The strongest protection in a remote project is not a clause, it is visibility. Ask to see a working build, on a real URL, every week. A status deck describing progress you cannot click tells you what someone wants you to think. Something deployable every week tells you where the project actually is, while a change of direction is still cheap.
Ask who actually writes the code
In any agency, the person who sells the project and the person who builds it can be different people, and sometimes the building is passed to a third party you never meet. Ask directly who will write the code, whether any of it is subcontracted, and whether you will speak to that person. At a deliberately small studio the honest answer is that the person on the call is the person on the keyboard.
Be careful with the lowest quote
A low day rate is not a low cost if the build needs rework. A sound way to compare is to ask each studio for a range first, a firm number once the architecture is settled, and a clear answer on whether that number is held. Distance does not make a studio cheaper or dearer; senior attention on the whole build is what costs money, and it is worth asking whether the quote includes it.
- Where will you be working from, and what hours overlap with mine?
- How will personal data reach you, and which transfer terms do you sign?
- Who owns the code, the accounts and the design files, and from when?
- Can I see a working build every week?
- Who writes the code, and is any of it subcontracted?
Where this applies

