What timezone overlap can we expect?

Four to six hours of live overlap with the UK and Europe, and three to four with the US East Coast, by working an afternoon-to-evening India schedule. Australia and New Zealand overlap in the morning. US West Coast is the hardest case and works on a two-to-three hour early-morning window plus asynchronous handover.

Who owns the intellectual property?

You do, assigned on payment, stated explicitly in the contract. All code is delivered into your repositories, and credentials and infrastructure stay in your accounts throughout. There is no arrangement where the work sits on my infrastructure and you licence it back.

Can our data stay inside the EU, UK or US?

Yes. Cloud resources are provisioned in whichever region you require, and for AI work the model provider is chosen to match — including self-hosted open-weight models where content cannot leave your infrastructure at all. This is an architecture decision worth settling before any build starts, because it is expensive to reverse.

How does invoicing work?

Invoices are issued in GBP, EUR, USD, CAD or AUD, paid by international bank transfer or Wise. Indian export-of-service rules mean no VAT or GST is charged to overseas clients; your own reverse-charge treatment applies as usual. Payment terms are typically net 15 or net 30.

Working With Clients in the US, Europe & Australia

Q: Can you sign our MSA, NDA and DPA?

Yes. Most engagements run on the client's own paperwork rather than mine. For EU and UK clients that normally means a GDPR data processing agreement with standard contractual clauses; for US clients an MSA with a statement of work. I am happy to be added as a subprocessor where your customers require disclosure.

I work from India with clients across the United States, the UK and Europe, Canada, Australia and New Zealand. If you are weighing up an India-based technical partner, the questions below are the ones that actually decide it — so they are answered here rather than left for a first call.

Timezone overlap, stated honestly

I work an afternoon-to-evening India schedule, which puts the working day squarely against European and East Coast hours rather than at the edges of them.

UK, Ireland & Western Europe — four to six hours of live overlap, effectively a shared working afternoon.
US East Coast — three to four hours, typically your morning.
US Central & Mountain — two to three hours, early in your day.
US West Coast — the hardest case. Two to three hours on an early-morning call window, with the rest handled asynchronously.
Australia & New Zealand — comfortable morning overlap; often the easiest of the group.

For West Coast work I would rather say plainly that most collaboration will be asynchronous than promise a full overlapping day and disappoint you in week two. In practice that means detailed written handovers, recorded walkthroughs where a live demo would otherwise be needed, and one reliable scheduled call rather than several ad-hoc ones.

Contracting and IP

Engagements normally run on your paperwork, not mine — your MSA, your NDA, your data processing agreement. Intellectual property is assigned to you on payment and stated explicitly in the contract.

Code is delivered into your repositories from the first commit. Cloud accounts, domains, model-provider keys and third-party services stay in your name throughout. There is no arrangement where the work lives on my infrastructure and gets licensed back to you, and nothing is held as leverage at the end of an engagement.

Data protection and residency

For EU and UK clients, a GDPR data processing agreement with standard contractual clauses is the normal basis, and I am comfortable being named as a subprocessor where your own customers require disclosure. Canadian clients under PIPEDA and Australian clients under the Privacy Act are handled on the same footing.

Where data residency is a hard requirement, cloud resources are provisioned in your region and AI work is architected to match — up to self-hosted open-weight models so that no content leaves your infrastructure. That last option costs more and is somewhat less capable than frontier hosted models, so it is worth deciding deliberately at the start rather than discovering the constraint mid-build.

For EU clients specifically, the AI Act's transparency and risk-classification duties are worth establishing during discovery. Most of what I build sits well outside the high-risk categories, but knowing that with certainty is cheaper than assuming it.

Accessibility and public-sector requirements

Public bodies and regulated organisations across these markets carry accessibility obligations — Section 508 and ADA expectations in the US, the European Accessibility Act and EN 301 549 across the EU, AODA in Ontario, and WCAG 2.1 AA in Australian government digital standards. They converge on WCAG, which is the standard I build to rather than something bolted on at the end.

Invoicing, currency and tax

Invoices are issued in GBP, EUR, USD, CAD or AUD and paid by international bank transfer or Wise. Under Indian export-of-service rules no VAT or GST is charged to overseas clients; your own reverse-charge or self-assessment treatment applies as normal. Terms are typically net 15 or net 30, with larger pieces of work broken into milestones.

How communication actually works

A shared channel in whatever you already use — Slack, Teams, or email if you prefer. A written update at the end of each working day covering what moved, what is blocked and what is next, so that you have something to read when your day starts and I have gone offline. One scheduled call a week rather than several improvised ones.

The failure mode with distributed work is not the distance, it is silence. Written updates are the thing that fixes it, and they are non-negotiable in how I work.