Tokyo, Japan
AI development for Tokyo teams, handed over in writing
We build AI products from Vancouver, British Columbia, and we work with Tokyo teams without a single shared working hour. No office there, no staff there. What replaces the shared day is a written handoff, decisions logged as they are made, and review that happens on your morning rather than in a call.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Tokyo, Japan
- your clock
- UTC+09:00 (Asia/Tokyo)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Tokyo
No shared working day, so the loop is written
Tokyo is 17 hours ahead of Vancouver. When we start at 09:00 it is 02:00 on the next day for you, and when we stop at 17:00 it is 10:00 on the next day. On the same calendar date there is no hour where both sides are at work.
The honest version of this is a selling point. You get a full uninterrupted Vancouver day of work delivered as a written handoff, and we get your review waiting for us in the morning. Two shifts a day, no overtime.
- Everything built during our day lands in one written note before we close the laptop. No status meeting stands in for it.
- Your morning starts with that note and a set of pull requests to review, which is a better start than a calendar invitation.
- Every decision worth arguing about is written down where the code is, with the reasoning and the date attached.
- Questions come with a recommendation, because a question that needs a reply before work continues costs a full day here.
One live call a week, and it is scheduled honestly: 16:00 in Vancouver is 09:00 in Tokyo on the next day. Neither side takes a bad hour for that one. The call simply lands on two different calendar dates, which is a scheduling detail rather than a hardship.
What Tokyo buyers usually bring us
The record for Tokyo lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
electronics
Test rigs, PLM systems and supplier feeds each need their own integration, validated against live data before anybody trusts a number on a dashboard.
We work embedded with your team, or with your customer teams, and the unit of delivery is a deployment rather than a document.
Closest service line: Forward-deployed engineering
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.
Chunking follows the structure of the document instead of a character count, which is the whole difference between a useful index and an expensive one.
Closest service line: Knowledge bases and retrieval
Contracts, currency and where the data sits
Invoices are in US dollars or yen. Specification detail up front is welcome and it makes the written handoff easier, because the decisions are already recorded.
The rest is the same everywhere: we scope it, we build a thin slice against your real data, and we hand back something your own team can maintain. No retainer you cannot cancel and no seat licences.
The five lines we sell
Same five lines everywhere, Tokyo 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
Each one has its own page, its own overlap arithmetic and its own industries.
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.