England, United Kingdom
AI development for Birmingham teams, handed over in writing
Magic Ship is one shop in Vancouver, British Columbia. Between Vancouver and Birmingham there is no same-day overlap to sell you, so the engagement is built the other way around: everything that matters is written down, and the day you start is the day after ours finished.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Birmingham, United Kingdom
- your clock
- UTC+00:00 (Europe/London)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Birmingham
No shared working day, so the loop is written
Birmingham 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.
It also produces a better record than a colocated project would. Everything of consequence exists as written text with a date on it, because writing is the only channel available.
- 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 01: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: 09:00 in Vancouver is 17:00 in Birmingham. 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 Birmingham buyers usually bring us
The record for Birmingham lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
automotive
Supplier portals, warranty systems and dealer software rarely offer a clean API, so integrations either get validated against real traffic or they are decoration.
Recurring patterns get pushed back into your platform, so the next account receives a supported capability rather than another one-off.
Closest service line: Forward-deployed engineering
professional services
The billable hour is the constraint. Training on live engagements, with the failure modes named up front, is what changes how a team works.
The written notes stay with the team, and they are written to be edited rather than filed.
Closest service line: Training and enablement
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.
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, Birmingham 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
If you are comparing markets, these are the other United Kingdom entries in the record set.
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.