Scotland, United Kingdom
AI development for Glasgow teams, handed over in writing
We build AI products from Vancouver, British Columbia, and we work with Glasgow teams without a single shared working hour. No office there, no staff there. What replaces the shared day is a written handoff, decisions logged as they are made, and review that happens on your morning rather than in a call.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Glasgow, United Kingdom
- your clock
- UTC+00:00 (Europe/London)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Glasgow
No shared working day, so the loop is written
Glasgow 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.
- 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: 09:00 in Vancouver is 17:00 in Glasgow. 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 Glasgow buyers usually bring us
The record for Glasgow lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
engineering
Calculation packages, standards and past project files are the asset. Retrieval that returns the standard and its edition is what an engineer will actually use.
Recall gets measured before anybody comments on the wording, because a fluent answer drawn from the wrong passage is the worst outcome on offer.
Closest service line: Knowledge bases and retrieval
financial services
Research, filings and internal policy are the corpus. Hybrid search with metadata filters as hard constraints, plus span citations, or it does not ship.
It starts with your documents and your own analysts writing the questions the system has to get right before anyone will trust it.
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.
Everything else is the same as it would be for a client down the street from us: scope, a thin slice in week one, then weekly increments you can stop at any time. The distance changes the schedule, not the contract.
The five lines we sell
Same five lines everywhere, Glasgow 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
Each one has its own page, its own overlap arithmetic and its own industries.
Start a project
Write down the problem in whatever form you have it. You get a straight answer about scope, timeline and whether this is work we should be doing at all.