England, United Kingdom
AI development for Leeds teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Leeds 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
- Leeds, United Kingdom
- your clock
- UTC+00:00 (Europe/London)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Leeds
No shared working day, so the loop is written
Leeds 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.
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.
- 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 Leeds. 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 Leeds buyers usually bring us
The record for Leeds lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
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.
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
legal services
Matter files and precedent are the corpus. Span-level citation is not a feature request, it is the condition of a lawyer using the thing twice.
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.
Everything downstream of that is deliberately unremarkable. Fixed acceptance criteria, weekly shipping, a written decision log, and a first reply that tells you if Leeds work of this shape is not something we should take.
The five lines we sell
Same five lines everywhere, Leeds 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
More entries from the United Kingdom 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.