Antioquia (ANT), Colombia
AI development for Medellin teams, inside your afternoon
The shop sits in Vancouver, British Columbia, and works with Medellin teams at a distance. Your day and ours share 5 hours. That is enough for the conversations that need voices, and not enough to run a project on calls, which is fine.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Medellin, Colombia
- your clock
- UTC-05:00 (America/Bogota)
- overlap
- 5 hours a day, 09:00-14:00 in Vancouver
- presence
- remote only, no office in Medellin
What fits in a 5-hour window
The overlap is real and it is bounded. Medellin sits 3 hours ahead of Vancouver, so the shared part of the day runs 09:00 to 14:00 our time and 12: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 Medellin buyers usually bring us
The record for Medellin lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
textiles
Order data, mill capacity and quality reports feed the same tool layer, and the useful output is a schedule change rather than a paragraph.
The first slice is thin and runs end to end: one real workflow, one real data source, and an agent with tools that change something rather than describe it.
Closest service line: AI products, built end to end
software development
Test generation is the usual first wedge: low risk, easy to measure, and it exposes exactly where the codebase is illegible to an agent.
The written practice belongs to your team afterwards, because a workflow that only a contractor understands is a workflow you rent forever.
Closest service line: Codebase and team optimization
Contracts, currency and where the data sits
Invoices are in US dollars. Contracts are in English, and the shared working hours are named in the statement of work so nobody guesses.
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, Medellin 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 rather than a job spec. You get an answer on scope, timeline and whether we are the right shop, written by the person who would do the work.