UK and EU buyers · one Indian entity
We have no UK entity.
Here is what we do about it.
HeadlineHQ is one company, registered in Delhi. No London office. No Dutch holding company. No US subsidiary standing behind the invoice. If this went wrong, you would be chasing a contract 6,700 km from your desk. We are not going to pretend that is comfortable.
So read the rest of this page as what we put in its place. If you want to check the Delhi half of that sentence first, we publish what being registered in Delhi actually means, including what we do not have.
Four hours, inside your day
London
Your desk
08:30 – 13:30
4 hours
07:00
13:00
19:00
Our desk, today
13:00 – 18:00 IST
- Entity
- One company, Delhi. Nothing else.
- Your repository
- Yours from the first commit
- Live overlap
- Four hours, every working day
The objection against us is fair. It is also half an argument.
The case for staying local is written down in plenty of places, and the sharpest version runs like this.
Different legal system.
Different courts.
If the team goes quiet, your options are thin.
All three are true.
UK · legal risk in offshore development
Here is the half that never gets finished. Suing a supplier is already a bad outcome, including a supplier in Manchester. Across a border it is worse. The usual advice to a UK buyer is an ICC or LCIA arbitration clause, written and then never used. Nobody wins a storefront back in a courtroom. You win a payment, months after the launch date you needed.
Which makes the useful question a different one.
Not whose courts. This: on the worst day of this relationship, what is already in your hands?
Two answers below. Both are checkable in week one rather than promised for later.
Your repository. Your account. Your billing. From the first commit.
You open the repository. Your GitHub organisation, your card on file, your admin rights. Then you add us as collaborators. Nothing else changes hands.
We do not build in our own account and transfer it at the end. There is no handover event, because there is nothing left to hand over. Want us gone on a Tuesday afternoon? Remove our access on Tuesday afternoon. The code has not moved an inch.
- The repository
- Your GitHub organisation
- The card on file
- Yours
- Admin rights
- Yours
- Us
- Collaborators you added
6 August 2026
None of this is our invention. It is the standard advice to anyone buying software. Create the repository under your own organisation at the start, then add the supplier as a collaborator, so ownership and possession never come apart.
What is unusual is how few suppliers actually do it. The transfer at the end is leverage. Hand it over on day one and the final invoice has to be earned rather than held for ransom.
Your next developer starts by cloning something you already own.
Not by waiting on a reply from Delhi.
The 8-to-12 hour time difference you have read about is not yours.
That figure belongs to a North American buyer. Yours is smaller, and you can check it in about a minute.
What you have read
8 – 12 hours
From your desk
- 4h 30m
- London, late March to late October
- 5h 30m
- London, the rest of the year
- 3h 30m
- Amsterdam and Berlin, their summer
India runs on UTC+5:30 and never moves its clocks. Britain sits on UTC+0 through winter and UTC+1 through summer. So a London desk and a Delhi desk are four and a half hours apart from late March to late October. Five and a half for the rest of the year. Amsterdam and Berlin are closer again. Three and a half hours across their summer.
Our commitment is four hours of live overlap, every working day, inside your office hours. Today that sits at roughly 1pm to 6pm here, which puts us with you from 08:30 to 13:30 in London. Your clocks go back in October. Ours never do. So we move, and the four hours holds.
Four hours is not a heroic number, and we chose it for exactly that reason. A supplier promising nine hours of overlap is describing a good week. That promise dies the first time somebody has a dentist appointment. Four hours survives a normal year with leave in it, which is the only kind worth printing.
Five questions worth putting to every agency on your list, including us.
01
Entity
Where is your legal entity, and what would enforcing this contract actually cost me?
Ours: India. One entity, Delhi, nothing else. Enforcement would be slow and expensive. True of any supplier outside your own courts, and we would rather say it here than let you find it in a footnote.
02
Repository
Whose account owns the repository on day one?
Ours: yours.
03
Overlap
How many hours a day are you awake while I am at my desk?
Ours: four, minimum, every working day, inside your office hours.
04
Continuity
If the engineer who wrote this leaves in March, who reads the code in April?
We have not published an answer.
05
Exit
On the day we stop working together, what do I already hold?
The code in full, because it never sat anywhere else.
Three of the five we answer in public, above, with our name against them. Two we do not.
Ask all five anyway, of us and of everyone else you are talking to, then notice who changes the subject.
What we have not promised you.
Three things a buyer in your position should want, and which are not in writing yet.
- A named engineer instead of a pool.
Not in writing
- A written handover if the relationship ends.
Not in writing
- A second engineer who already knows your project.
Not in writing
We could have written a paragraph that sounds like all three while committing to none. It is done constantly. You have probably read one this week without noticing, and this page exists to refuse that trick.
When any of the three is decided, it appears here with the date it took effect. Until then, the section says what it says.
Two good reasons to close this page.
If your board requires a supplier with a registered entity in the UK or the EU, we do not qualify.
Nothing above changes that, and saying so early saves us both a fortnight.
If you are looking outside your own market because a local quote came in high, be careful what you find.
The cheap end of this trade is cheap for reasons that surface around month six. We do not compete there, and our headless Shopify engagements are priced accordingly.
Where the two outside claims on this page come from.
What it supports
Source
Published
Creating the repository under your own organisation is the standard control
6 Aug 2026
The entity, the four-hour overlap and the repository practice are our own statements. Nobody has audited them, and this page carries no client name, no review count and no response-time promise.
Book a 30-minute call inside your working hours.
Pick a morning slot in your own time zone. Before we speak you get the overlap window and the repository setup in writing. Read both without a salesperson in the room.
Bring the five questions. If we are the wrong fit you will hear it on the call, not in a proposal three weeks later.
01
Entity
02
Repository
03
Overlap
04
Continuity
05
Exit