Istanbul, Turkey
AI development for Istanbul teams, handed over in writing
One shop, Vancouver, British Columbia. Istanbul sits on the other side of a full day, so nothing about this engagement runs on meetings. It runs on written handoffs, logged decisions and review that happens while the other side is asleep.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Istanbul, Turkey
- your clock
- UTC+03:00 (Europe/Istanbul)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Istanbul
No shared working day, so the loop is written
Istanbul is 11 hours ahead of Vancouver. When we start at 09:00 it is 20:00 on the same day for you, and when we stop at 17:00 it is 04:00 on the next day. On the same calendar date there is no hour where both sides are at work.
There is a real cost and it is worth naming: an answer to a blocking question can take a working day to reach you. We handle it by sending the proposed answer with the question, so silence means agreement rather than a lost day.
- 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 04: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: 06:00 in Vancouver is 17:00 in Istanbul. 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 Istanbul buyers usually bring us
The record for Istanbul lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
textiles
Order data, mill capacity and quality reports feed the same tool layer, and the useful output is a schedule change rather than a paragraph.
The interface is the final quarter of the job. Everything before it is the tool layer and the tests that keep the tool layer honest.
Closest service line: AI products, built end to end
manufacturing
Procedures, drawings and shift reports hold the answers. Getting them out is an ingestion problem far more often than it is a model problem.
Answers cite the passage they came from. A retrieval system without span-level citation gets used twice and then quietly abandoned.
Closest service line: Knowledge bases and retrieval
Contracts, currency and where the data sits
Invoices are in euros or US dollars. Contracts are in English, and the schedule is written against your working days.
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, Istanbul 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.