Baden-Wurttemberg (BW), Germany
AI development for Stuttgart teams, handed over in writing
We build AI products from Vancouver, British Columbia, and we work with Stuttgart teams without a single shared working hour. No office there, no staff there. What replaces the shared day is a written handoff, decisions logged as they are made, and review that happens on your morning rather than in a call.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Stuttgart, Germany
- your clock
- UTC+01:00 (Europe/Berlin)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Stuttgart
No shared working day, so the loop is written
Stuttgart 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.
The honest version of this is a selling point. You get a full uninterrupted Vancouver day of work delivered as a written handoff, and we get your review waiting for us in the morning. Two shifts a day, no overtime.
- 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 Stuttgart. 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 Stuttgart buyers usually bring us
The record for Stuttgart lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
automotive
Supplier portals, warranty systems and dealer software rarely offer a clean API, so integrations either get validated against real traffic or they are decoration.
Without a rule about what goes back into the platform, this work becomes a treadmill, so that rule is agreed at the first account.
Closest service line: Forward-deployed engineering
industrial engineering
Drawings, method sheets and change history are the reference. Structure-aware parsing of the drawing set is where most of the schedule goes.
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
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 rest is the same everywhere: we scope it, we build a thin slice against your real data, and we hand back something your own team can maintain. No retainer you cannot cancel and no seat licences.
The five lines we sell
Same five lines everywhere, Stuttgart 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
Each one has its own page, its own overlap arithmetic and its own industries.
Start a project
Send the problem rather than a job spec. You get an answer on scope, timeline and whether we are the right shop, written by the person who would do the work.