Geneva (GE), Switzerland
AI development for Geneva teams, handed over in writing
The desk is in Vancouver, British Columbia. Geneva is far enough around the world that our working days do not touch on the same date, which is a fact worth stating in the first paragraph rather than discovering in week two. The work is handed over in writing instead.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Geneva, Switzerland
- your clock
- UTC+01:00 (Europe/Zurich)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Geneva
No shared working day, so the loop is written
Geneva 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 Geneva. 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 Geneva buyers usually bring us
The record for Geneva lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
private banking
Client files and product terms carry access rules that must apply at retrieval time, so entitlement filters are part of the index, not a wrapper.
Chunking follows the structure of the document instead of a character count, which is the whole difference between a useful index and an expensive one.
Closest service line: Knowledge bases and retrieval
international organizations
Reports, resolutions and country files span languages and decades. The design problem is filters that hold, not embedding choice.
Most retrieval failures are ingestion failures, so the early weeks go into parsing and chunking rather than into rewording a prompt.
Closest service line: Knowledge bases and retrieval
Contracts, currency and where the data sits
Invoices are in Swiss francs or US dollars. Swiss buyers almost always specify where data may sit, and that constraint shapes the architecture rather than being bolted on at the end.
Beyond that, the shape of an engagement does not change with distance: a scoping call, a thin end-to-end slice, then weekly increments against acceptance criteria fixed in advance. If we are not the right shop for Geneva work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Geneva 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
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.