Tamil Nadu (TN), India
AI development for Chennai teams, handed over in writing
The desk is in Vancouver, British Columbia. Chennai is far enough around the world that our working days do not touch on the same date, which is a fact worth stating in the first paragraph rather than discovering in week two. The work is handed over in writing instead.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Chennai, India
- your clock
- UTC+05:30 (Asia/Kolkata)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Chennai
No shared working day, so the loop is written
Chennai is 13.5 hours ahead of Vancouver. When we start at 09:00 it is 22:30 on the same day for you, and when we stop at 17:00 it is 06:30 on the next day. On the same calendar date there is no hour where both sides are at work.
There is a real cost and it is worth naming: an answer to a blocking question can take a working day to reach you. We handle it by sending the proposed answer with the question, so silence means agreement rather than a lost day.
- The Vancouver day ends with a written summary: shipped, broken, blocked, and the one thing we need you to decide.
- That summary is waiting at 06:30 your time, alongside the diffs it refers to.
- The decision log lives in the repository rather than in a chat thread, so it is still readable a year later.
- Anything that would block us gets asked as a proposal you can approve in a sentence, not as an open question.
One live call a week, and it is scheduled honestly: 19:30 in Vancouver is 09:00 in Chennai on the next day. That hour is outside our working day and inside yours. We take the awkward end of it, because it is our job to be reachable.
What Chennai buyers usually bring us
The record for Chennai lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
automotive
Supplier portals, warranty systems and dealer software rarely offer a clean API, so integrations either get validated against real traffic or they are decoration.
Without a rule about what goes back into the platform, this work becomes a treadmill, so that rule is agreed at the first account.
Closest service line: Forward-deployed engineering
software services
Teams here ship in someone else s codebase every week, which makes a portable practice worth more than any single tool rollout.
People ship real changes during the session, which is the only version of this that changes behaviour once we leave.
Closest service line: Training and enablement
Contracts, currency and where the data sits
Invoices are in US dollars. Contracting with a Canadian vendor is common enough that your finance team will have the paperwork pattern already.
The rest is the same everywhere: we scope it, we build a thin slice against your real data, and we hand back something your own team can maintain. No retainer you cannot cancel and no seat licences.
The five lines we sell
Same five lines everywhere, Chennai included. Most engagements are one of them, sometimes two.
- AI products, built end to end
- Knowledge bases and retrieval
- Codebase and team optimization
- Training and enablement
- Forward-deployed engineering
The languages, models and infrastructure underneath all five are listed on the Magic Ship stack page, with what each one is good for and where it is the wrong choice.
Other markets in India
More of India, all of it worked remotely from Vancouver.
Start a project
Send the problem. If it is a fit, you get scope and a timeline. If it is not, you get told that in the first reply instead of after a discovery process.