North Brabant (NB), Netherlands
AI development for Eindhoven teams, handed over in writing
The desk is in Vancouver, British Columbia. Eindhoven 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
- Eindhoven, Netherlands
- your clock
- UTC+01:00 (Europe/Amsterdam)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Eindhoven
No shared working day, so the loop is written
Eindhoven 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.
That is not an apology. A loop that turns once every twenty-four hours, in writing, is a faster way to build software than a calendar full of half-attended calls, and it forces the decisions into a form somebody can read six months later.
- 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 Eindhoven. 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 Eindhoven buyers usually bring us
The record for Eindhoven lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
semiconductor equipment
Tool documentation, recipes and field service reports are the corpus, and retrieval has to keep one tool generation from answering for another.
The golden-question set is the deliverable nobody thinks to ask for, and it is the only way to show that a change helped.
Closest service line: Knowledge bases and retrieval
electronics
Test rigs, PLM systems and supplier feeds each need their own integration, validated against live data before anybody trusts a number on a dashboard.
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
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 else is the same as it would be for a client down the street from us: scope, a thin slice in week one, then weekly increments you can stop at any time. The distance changes the schedule, not the contract.
The five lines we sell
Same five lines everywhere, Eindhoven 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 of Europe, all of it worked remotely from Vancouver.
Start a project
Write down the problem in whatever form you have it. You get a straight answer about scope, timeline and whether this is work we should be doing at all.