Ho Chi Minh City, Vietnam
AI development for Ho Chi Minh City teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia. Ho Chi Minh City and Vancouver share no working hours at all, and that is stated up front because it changes how the work runs: written handoff at the end of each side's day, a loop that turns once every twenty-four hours, and nobody waiting on a meeting.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Ho Chi Minh City, Vietnam
- your clock
- UTC+07:00 (Asia/Ho_Chi_Minh)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Ho Chi Minh City
No shared working day, so the loop is written
Ho Chi Minh City is 15 hours ahead of Vancouver. When we start at 09:00 it is 00:00 on the next day for you, and when we stop at 17:00 it is 08:00 on the next day. On the same calendar date there is no hour where both sides are at work.
Treated properly it is the better arrangement. Nobody blocks on a meeting, every decision exists as text with a date on it, and the work moves while the other side sleeps instead of while the other side waits.
- 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 08:00, 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: 18:00 in Vancouver is 09:00 in Ho Chi Minh City 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 Ho Chi Minh City buyers usually bring us
The record for Ho Chi Minh City lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
software outsourcing
Delivery quality is the product, so training runs on client repos with the review standard fixed in advance and the failure modes written down.
Sessions run on your codebase, your tickets and your constraints. A vendor demo teaches nothing that survives the following Monday.
Closest service line: Training and enablement
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. Contracts are in English, and the engagement runs on written handoffs rather than on meeting attendance.
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 Ho Chi Minh City changes what you are buying.
The five lines we sell
Same five lines everywhere, Ho Chi Minh 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 Asia
Where else the same work happens in Asia, with the numbers redone per market.
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.