Santiago Metropolitan (RM), Chile
AI development for Santiago teams, inside your afternoon
We are in Vancouver, British Columbia. You are in Santiago. Nobody from this shop is, and nobody pretends to be. The two working days touch for 4 hours, and that window is spent on decisions rather than on status.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Santiago, Chile
- your clock
- UTC-04:00 (America/Santiago)
- overlap
- 4 hours a day, 09:00-13:00 in Vancouver
- presence
- remote only, no office in Santiago
What fits in a 4-hour window
The overlap is real and it is bounded. Santiago sits 4 hours ahead of Vancouver, so the shared part of the day runs 09:00 to 13:00 our time and 13:00 to 17:00 yours.
A partial overlap punishes projects that run on meetings and rewards ones that run on written acceptance criteria. We build for the second kind, which is how we would run it anyway.
What moves to writing is not a downgrade. A daily handoff note at the end of the Vancouver day, decisions logged when they are made, and review on the pull request itself means your morning starts with the answer rather than with a meeting invitation.
What Santiago buyers usually bring us
The record for Santiago lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
mining
Geological reports, drill data and plant telemetry describe the same orebody in three formats, and the product is what makes them agree.
The eval harness gets built beside the first feature, so week three can prove that week two did not quietly make the output worse.
Closest service line: AI products, built end to end
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.
The golden-question set is the deliverable nobody thinks to ask for, and it is the only way to show that a change helped.
Closest service line: Knowledge bases and retrieval
Contracts, currency and where the data sits
Invoices are in US dollars. The engagement is remote, the contract is in English, and the working overlap is written into the schedule.
Everything else is the same as it would be for a client down the street from us: scope, a thin slice in week one, then weekly increments you can stop at any time. The distance changes the schedule, not the contract.
The five lines we sell
Same five lines everywhere, Santiago 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 South America
Same treatment, different clocks, and in some cases a different answer.
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.