Mexico City (CMX), Mexico
AI development for Mexico City teams, on your working day
Magic Ship is one shop in Vancouver, British Columbia, working remotely with clients in Mexico City. No local address, no local number, and no pretence otherwise. The overlap does the work an office would have done: 6 hours a day, live.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Mexico City, Mexico
- your clock
- UTC-06:00 (America/Mexico_City)
- overlap
- 6 hours a day, 09:00-15:00 in Vancouver
- presence
- remote only, no office in Mexico City
6 hours of your day, every working day
Mexico City runs 2 hours ahead of Vancouver. On a normal working day the two calendars overlap from 09:00 to 15:00 Vancouver time, which is 11:00 to 17:00 where you are.
With a window like that, most decisions never become documents. We review together, we cut scope together, and the written record exists for the archive rather than as the only channel.
The parts that still get written down are written down anyway: acceptance criteria, the decision log, and what changed in each weekly increment. A shared clock is not an excuse for an undocumented project.
What Mexico City buyers usually bring us
The record for Mexico City 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.
Access rules apply inside the index at retrieval time, never as a filter bolted onto the answer after the fact.
Closest service line: Knowledge bases and retrieval
manufacturing
Procedures, drawings and shift reports hold the answers. Getting them out is an ingestion problem far more often than it is a model problem.
Recall gets measured before anybody comments on the wording, because a fluent answer drawn from the wrong passage is the worst outcome on offer.
Closest service line: Knowledge bases and retrieval
Contracts, currency and where the data sits
Invoices are in US dollars. Under USMCA, cross-border services contracting between our two countries is routine, and the paperwork is not the hard part.
The commercial part stays deliberately boring. Fixed acceptance criteria per increment, weekly shipping, and a written record of every decision. Nothing about working from Vancouver instead of Mexico City changes what you are buying.
The five lines we sell
Same five lines everywhere, Mexico City 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 North America
More entries from the North America list, each written the same way as this one.
Start a project
Describe what is broken or what you want built. The reply comes from the engineer who would build it, and it covers scope, timeline and fit before anything else.