Maharashtra (MH), India
AI development for Pune teams, handed over in writing
One shop, Vancouver, British Columbia. Pune sits on the other side of a full day, so nothing about this engagement runs on meetings. It runs on written handoffs, logged decisions and review that happens while the other side is asleep.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Pune, India
- your clock
- UTC+05:30 (Asia/Kolkata)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Pune
No shared working day, so the loop is written
Pune 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.
That is not an apology. A loop that turns once every twenty-four hours, in writing, is a faster way to build software than a calendar full of half-attended calls, and it forces the decisions into a form somebody can read six months later.
- A handoff note goes out at the end of every Vancouver working day: what shipped, what broke, and what needs a decision from you.
- You read it at 06:30, or whenever your day starts, and review the pull requests it points at.
- Decisions are logged as they are made, in the repository, so neither side has to reconstruct why something was done.
- A blocking question arrives with a proposed answer attached, so the default outcome is progress rather than a stalled day.
One live call a week, and it is scheduled honestly: 19:30 in Vancouver is 09:00 in Pune 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 Pune buyers usually bring us
The record for Pune 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.
We work embedded with your team, or with your customer teams, and the unit of delivery is a deployment rather than a document.
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.
A block of sessions across a few weeks beats one long day, because the practice needs real work in between sittings.
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.
Beyond that, the shape of an engagement does not change with distance: a scoping call, a thin end-to-end slice, then weekly increments against acceptance criteria fixed in advance. If we are not the right shop for Pune work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Pune 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
Each one has its own page, its own overlap arithmetic and its own industries.
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.