Dubai, United Arab Emirates
AI development for Dubai teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia. Dubai 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
- Dubai, United Arab Emirates
- your clock
- UTC+04:00 (Asia/Dubai)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Dubai
No shared working day, so the loop is written
Dubai is 12 hours ahead of Vancouver. When we start at 09:00 it is 21:00 on the same day for you, and when we stop at 17:00 it is 05: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.
- 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: 21:00 in Vancouver is 09:00 in Dubai 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 Dubai buyers usually bring us
The record for Dubai lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
logistics
Carrier APIs, warehouse systems and customer portals all break differently under load, which is why the integration work is the project.
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
real estate
Leases, valuations and property data are the input, and the product that works reads the actual lease rather than summarizing a summary.
You get a running product with its own test suite and enough documentation for your team to take it over, not a prototype with our commit history in it.
Closest service line: AI products, built end to end
Contracts, currency and where the data sits
Invoices are in US dollars. Working weeks differ, so the schedule is written against your working days rather than ours, and delivery dates are set in your calendar.
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, Dubai 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
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.