Stockholm (AB), Sweden
AI development for Stockholm teams, handed over in writing
We build AI products from Vancouver, British Columbia, and we work with Stockholm 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
- Stockholm, Sweden
- your clock
- UTC+01:00 (Europe/Stockholm)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Stockholm
No shared working day, so the loop is written
Stockholm 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.
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 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 Stockholm. 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 Stockholm buyers usually bring us
The record for Stockholm lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
software startups
The first production surface matters more than the roadmap. A thin end-to-end slice in week one tells you what the rest is going to cost.
We ship something narrow early and widen it, because scope found in production costs less than scope argued about in a document.
Closest service line: AI products, built end to end
financial technology
Core systems, ledgers and payment rails each carry their own auth, pagination and rate limits, and none of it survives being described in a prompt.
Progress is counted in deployments rather than features, which is the only honest way to measure this kind of work.
Closest service line: Forward-deployed engineering
Contracts, currency and where the data sits
Invoices are in euros or US dollars. 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, Stockholm 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
Send the problem. If it is a fit, you get scope and a timeline. If it is not, you get told that in the first reply instead of after a discovery process.