Bangkok, Thailand
AI development for Bangkok teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Bangkok and no shared working hours with it. What that buys you is a full day of build time delivered as a written handoff, waiting when you sit down.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Bangkok, Thailand
- your clock
- UTC+07:00 (Asia/Bangkok)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Bangkok
No shared working day, so the loop is written
Bangkok 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 Bangkok 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 Bangkok buyers usually bring us
The record for Bangkok lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
tourism
Availability, pricing and local knowledge have to come from your systems, because a model that improvises an opening time creates a support ticket.
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
automotive manufacturing
Failure reports, tooling changes and line documentation are the knowledge. Retrieval that names the exact build and plant is the line between useful and hazardous.
Most retrieval failures are ingestion failures, so the early weeks go into parsing and chunking rather than into rewording a prompt.
Closest service line: Knowledge bases and retrieval
Contracts, currency and where the data sits
Invoices are in US dollars. Contracts are in English, the work is remote, and the schedule is written against your working days.
Past that, the mechanics are ordinary. A scoping call, a written scope, weekly increments, and an invoice that matches what shipped. The one thing distance changes is when in your day the questions arrive.
The five lines we sell
Same five lines everywhere, Bangkok 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
If you are comparing markets, these are the other Asia entries in the record set.
Start a project
Say what you are trying to build and what has already been tried. The reply is from a senior engineer, and it will tell you if the shape of the work is wrong before it tells you anything else.