Guangdong (GD), China
AI development for Shenzhen teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Shenzhen 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
- Shenzhen, China
- your clock
- UTC+08:00 (Asia/Shanghai)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Shenzhen
No shared working day, so the loop is written
Shenzhen is 16 hours ahead of Vancouver. When we start at 09:00 it is 01:00 on the next day for you, and when we stop at 17:00 it is 09: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.
- The Vancouver day ends with a written summary: shipped, broken, blocked, and the one thing we need you to decide.
- That summary is waiting at 09:00 your time, alongside the diffs it refers to.
- The decision log lives in the repository rather than in a chat thread, so it is still readable a year later.
- Anything that would block us gets asked as a proposal you can approve in a sentence, not as an open question.
One live call a week, and it is scheduled honestly: 17:00 in Vancouver is 09:00 in Shenzhen 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 Shenzhen buyers usually bring us
The record for Shenzhen lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
consumer electronics
Device telemetry, support systems and firmware release tooling all need integrating before anything smart happens, and each one has its own failure modes.
Reconciliation and idempotency are designed in at the start, because retrofitting them after the first duplicate transaction is expensive.
Closest service line: Forward-deployed engineering
hardware manufacturing
Firmware and tooling repos are where agent help stalls first. Fast builds, scoped rules and a worked example in the repo are what shifts it.
Small diffs, explicit boundaries and locally runnable checks are what make agent output reviewable instead of merely plausible.
Closest service line: Codebase and team optimization
Contracts, currency and where the data sits
Invoices are in US dollars. Cross-border data rules are strict, so the practical shape is a system that runs inside your own cloud account and stays there.
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, Shenzhen 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
More entries from the Asia list, each written the same way as this one.
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.