Brussels-Capital Region (BRU), Belgium
AI development for Brussels teams, handed over in writing
Magic Ship is one shop in Vancouver, British Columbia. Between Vancouver and Brussels 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
- Brussels, Belgium
- your clock
- UTC+01:00 (Europe/Brussels)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Brussels
No shared working day, so the loop is written
Brussels is 9 hours ahead of Vancouver. When we start at 09:00 it is 18:00 on the same day for you, and when we stop at 17:00 it is 02: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.
- 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 02: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: 08:00 in Vancouver is 17:00 in Brussels. That hour is outside our working day and inside yours. We take the awkward end of it, because it is our job to be reachable.
What Brussels buyers usually bring us
The record for Brussels lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
european institutions
Multi-lingual policy archives and procedure documents need chunking that respects the document structure and citations a policy officer can verify.
The golden-question set is the deliverable nobody thinks to ask for, and it is the only way to show that a change helped.
Closest service line: Knowledge bases and retrieval
logistics
Carrier APIs, warehouse systems and customer portals all break differently under load, which is why the integration work is the project.
Every integration ships with its failure path written down: what retries, what alerts, and what a human is expected to look at.
Closest service line: Forward-deployed engineering
Contracts, currency and where the data sits
Invoices are in euros. GDPR makes storage location a design question rather than a footnote, so the index, the logs and the model calls get pinned to European regions where your provider offers them, and that is settled in week one.
The commercial part stays deliberately boring. Fixed acceptance criteria per increment, weekly shipping, and a written record of every decision. Nothing about working from Vancouver instead of Brussels changes what you are buying.
The five lines we sell
Same five lines everywhere, Brussels 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 Europe
If you are comparing markets, these are the other Europe 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.