Scotland, United Kingdom
AI development for Aberdeen teams, handed over in writing
One shop, Vancouver, British Columbia. Aberdeen sits on the other side of a full day, so nothing about this engagement runs on meetings. It runs on written handoffs, logged decisions and review that happens while the other side is asleep.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Aberdeen, United Kingdom
- your clock
- UTC+00:00 (Europe/London)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Aberdeen
No shared working day, so the loop is written
Aberdeen is 8 hours ahead of Vancouver. When we start at 09:00 it is 17:00 on the same day for you, and when we stop at 17:00 it is 01: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.
- 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 01: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: 09:00 in Vancouver is 17:00 in Aberdeen. 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 Aberdeen buyers usually bring us
The record for Aberdeen lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
offshore energy
Well files, inspection reports and vendor documentation run to millions of pages, and the retrieval design has to pin an answer to a well and a date.
Access rules apply inside the index at retrieval time, never as a filter bolted onto the answer after the fact.
Closest service line: Knowledge bases and retrieval
subsea engineering
Inspection video logs, ROV reports and equipment files are the record. Retrieval has to return the report and its date, not a plausible summary.
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 pounds or US dollars, whichever your accounts payable prefers. UK GDPR applies to whatever we index, so storage region and log retention are agreed in writing before ingestion starts.
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, Aberdeen 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 United Kingdom
Same treatment, different clocks, and in some cases a different answer.
Start a project
Send the problem rather than a job spec. You get an answer on scope, timeline and whether we are the right shop, written by the person who would do the work.