Lazio (LAZ), Italy
AI development for Rome teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia. Rome and Vancouver share no working hours at all, and that is stated up front because it changes how the work runs: written handoff at the end of each side's day, a loop that turns once every twenty-four hours, and nobody waiting on a meeting.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Rome, Italy
- your clock
- UTC+01:00 (Europe/Rome)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Rome
No shared working day, so the loop is written
Rome 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.
Treated properly it is the better arrangement. Nobody blocks on a meeting, every decision exists as text with a date on it, and the work moves while the other side sleeps instead of while the other side waits.
- 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: 08:00 in Vancouver is 17:00 in Rome. 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 Rome buyers usually bring us
The record for Rome lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
public administration
Legislation, guidance and internal procedure answer most questions, provided retrieval quotes the passage and shows which version it came from.
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
tourism
Availability, pricing and local knowledge have to come from your systems, because a model that improvises an opening time creates a support ticket.
The eval harness gets built beside the first feature, so week three can prove that week two did not quietly make the output worse.
Closest service line: AI products, built end to end
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 Rome work of this shape is not something we should take.
The five lines we sell
Same five lines everywhere, Rome 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
More entries from the Europe list, each written the same way as this one.
Start a project
Describe what is broken or what you want built. The reply comes from the engineer who would build it, and it covers scope, timeline and fit before anything else.