England, United Kingdom
AI development for Oxford teams, handed over in writing
The desk is in Vancouver, British Columbia. Oxford is far enough around the world that our working days do not touch on the same date, which is a fact worth stating in the first paragraph rather than discovering in week two. The work is handed over in writing instead.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Oxford, United Kingdom
- your clock
- UTC+00:00 (Europe/London)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Oxford
No shared working day, so the loop is written
Oxford 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.
That is not an apology. A loop that turns once every twenty-four hours, in writing, is a faster way to build software than a calendar full of half-attended calls, and it forces the decisions into a form somebody can read six months later.
- 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 Oxford. 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 Oxford buyers usually bring us
The record for Oxford lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
higher education
Faculty and staff need the failure modes as much as the workflows, so sessions run on their own courses and repos and end with a written practice they keep.
It usually pairs with the codebase work, because training sticks once the repository has already been made legible to an agent.
Closest service line: Training and enablement
life sciences
Study documents, protocols and submissions have rigid structure, and honouring that structure at ingestion time is what makes retrieval accurate.
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
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, Oxford 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.