Abu Dhabi, United Arab Emirates
AI development for Abu Dhabi teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Abu Dhabi 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
- Abu Dhabi, 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 Abu Dhabi
No shared working day, so the loop is written
Abu Dhabi 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.
- 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 05: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: 21:00 in Vancouver is 09:00 in Abu Dhabi 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 Abu Dhabi buyers usually bring us
The record for Abu Dhabi lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
energy
Operational data is high volume and low tolerance for a wrong answer, so the eval harness and the fallback behaviour get built before the interface.
Model choice comes last. Tool boundaries, the data model and the failure path are settled before anybody argues about which provider to call.
Closest service line: AI products, built end to end
sovereign investment
Diligence packs, mandates and portfolio reporting need retrieval with strict entitlement filters and citations back to the source document.
Hybrid search beats embeddings alone in nearly every corpus we have opened, and metadata filters behave as hard constraints or they are not filters.
Closest service line: Knowledge bases and retrieval
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, Abu Dhabi 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
Tell us what you are trying to build. A senior engineer reads every message and answers on scope, timeline and fit. If your problem is not one we should take, that is the first thing you will hear.