Lombardy (LOM), Italy
AI development for Milan teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Milan 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
- Milan, Italy
- your clock
- UTC+01:00 (Europe/Rome)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Milan
No shared working day, so the loop is written
Milan 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.
Removing the shared hour removes the interruptions with it. A full Vancouver day of uninterrupted build time, handed over in writing, tends to move a project further than a day punctuated by four calls.
- 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 02: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: 08:00 in Vancouver is 17:00 in Milan. 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 Milan buyers usually bring us
The record for Milan lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
fashion
Season data, supplier lead times and product copy converge on one system, and the eval set is what keeps generated copy inside the brand rules.
Week one puts something running in your environment against real state, because an agent that can only talk teaches nobody anything about the hard part.
Closest service line: AI products, built end to end
banking
Policy documents, product terms and audit trails are the corpus, and an answer without a citation to the governing clause is worse than no answer at all.
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 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.
Everything downstream of that is deliberately unremarkable. Fixed acceptance criteria, weekly shipping, a written decision log, and a first reply that tells you if Milan work of this shape is not something we should take.
The five lines we sell
Same five lines everywhere, Milan 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
Where else the same work happens in Europe, with the numbers redone per market.
Start a project
Tell us what you are trying to build. A senior engineer reads every message and answers on scope, timeline and fit. If your problem is not one we should take, that is the first thing you will hear.