Ontario (ON), Canada
AI development for London teams, inside your afternoon
The shop sits in Vancouver, British Columbia, and works with London teams at a distance. Your day and ours share 5 hours. That is enough for the conversations that need voices, and not enough to run a project on calls, which is fine.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- London, Canada
- your clock
- UTC-05:00 (America/Toronto)
- overlap
- 5 hours a day, 09:00-14:00 in Vancouver
- presence
- remote only, no office in London
What fits in a 5-hour window
The overlap is real and it is bounded. London sits 3 hours ahead of Vancouver, so the shared part of the day runs 09:00 to 14:00 our time and 12:00 to 17:00 yours.
What we do not do is stretch that window by pretending either side works longer than it does. It is a fixed budget of shared hours a week, and it gets spent on purpose.
What moves to writing is not a downgrade. A daily handoff note at the end of the Vancouver day, decisions logged when they are made, and review on the pull request itself means your morning starts with the answer rather than with a meeting invitation.
What London buyers usually bring us
The record for London lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
insurance
Policy wordings, endorsements and claims files need clause-level retrieval with the version and jurisdiction pinned, or the answer is guesswork with a citation.
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
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
Contracts, currency and where the data sits
This is a domestic engagement. Invoices are in Canadian dollars, the contract is Canadian, and nothing crosses a border on the way to you or on the way back.
Beyond that, the shape of an engagement does not change with distance: a scoping call, a thin end-to-end slice, then weekly increments against acceptance criteria fixed in advance. If we are not the right shop for London work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, London 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 Canada
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.