Hesse (HE), Germany
AI development for Frankfurt teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Frankfurt 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
- Frankfurt, Germany
- your clock
- UTC+01:00 (Europe/Berlin)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Frankfurt
No shared working day, so the loop is written
Frankfurt 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.
- 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 Frankfurt. 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 Frankfurt buyers usually bring us
The record for Frankfurt lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
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
data centers
Capacity systems, ticketing and monitoring have to be wired together before an assistant is anything more than a chat window over a wiki.
We work embedded with your team, or with your customer teams, and the unit of delivery is a deployment rather than a document.
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. German buyers usually want that in the statement of work, and it belongs there.
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 Frankfurt changes what you are buying.
The five lines we sell
Same five lines everywhere, Frankfurt 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 Germany
More entries from the Germany 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.