Ile-de-France (IDF), France
AI development for Paris teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Paris 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
- Paris, France
- your clock
- UTC+01:00 (Europe/Paris)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Paris
No shared working day, so the loop is written
Paris 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.
- 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 Paris. 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 Paris buyers usually bring us
The record for Paris lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
luxury goods
Client history, product provenance and brand rules constrain everything a model may say, so the guardrails and the eval set are the deliverable.
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
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.
It starts with your documents and your own analysts writing the questions the system has to get right before anyone will trust it.
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.
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, Paris 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.