Maharashtra (MH), India
AI development for Mumbai teams, handed over in writing
Magic Ship is one shop in Vancouver, British Columbia. Between Vancouver and Mumbai there is no same-day overlap to sell you, so the engagement is built the other way around: everything that matters is written down, and the day you start is the day after ours finished.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Mumbai, India
- your clock
- UTC+05:30 (Asia/Kolkata)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Mumbai
No shared working day, so the loop is written
Mumbai 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.
It also produces a better record than a colocated project would. Everything of consequence exists as written text with a date on it, because writing is the only channel available.
- 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 Mumbai 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 Mumbai buyers usually bring us
The record for Mumbai lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
financial services
Research, filings and internal policy are the corpus. Hybrid search with metadata filters as hard constraints, plus span citations, or it does not ship.
Hybrid search beats embeddings alone in nearly every corpus we have opened, and metadata filters behave as hard constraints or they are not filters.
Closest service line: Knowledge bases and retrieval
film production
Scripts, schedules and rights records are the working data. A tool that reads them is useful; a model that guesses at them is a liability.
The interface is the final quarter of the job. Everything before it is the tool layer and the tests that keep the tool layer honest.
Closest service line: AI products, built end to end
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.
Past that, the mechanics are ordinary. A scoping call, a written scope, weekly increments, and an invoice that matches what shipped. The one thing distance changes is when in your day the questions arrive.
The five lines we sell
Same five lines everywhere, Mumbai 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 entries from the India list, each written the same way as this one.
Start a project
Say what you are trying to build and what has already been tried. The reply is from a senior engineer, and it will tell you if the shape of the work is wrong before it tells you anything else.