Riyadh, Saudi Arabia
AI development for Riyadh teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Riyadh 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
- Riyadh, Saudi Arabia
- your clock
- UTC+03:00 (Asia/Riyadh)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Riyadh
No shared working day, so the loop is written
Riyadh is 11 hours ahead of Vancouver. When we start at 09:00 it is 20:00 on the same day for you, and when we stop at 17:00 it is 04: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 04: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: 06:00 in Vancouver is 17:00 in Riyadh. 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 Riyadh buyers usually bring us
The record for Riyadh 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.
We ship something narrow early and widen it, because scope found in production costs less than scope argued about in a document.
Closest service line: AI products, built end to end
public administration
Legislation, guidance and internal procedure answer most questions, provided retrieval quotes the passage and shows which version it came from.
Answers cite the passage they came from. A retrieval system without span-level citation gets used twice and then quietly abandoned.
Closest service line: Knowledge bases and retrieval
Contracts, currency and where the data sits
Invoices are in US dollars. The schedule follows your working week, and where the system runs is decided at the start because moving it later is expensive.
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, Riyadh 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
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.