Skane (M), Sweden
AI development for Malmo teams, handed over in writing
One shop, Vancouver, British Columbia. Malmo 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
- Malmo, Sweden
- your clock
- UTC+01:00 (Europe/Stockholm)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Malmo
No shared working day, so the loop is written
Malmo 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.
- A handoff note goes out at the end of every Vancouver working day: what shipped, what broke, and what needs a decision from you.
- You read it at 02:00, or whenever your day starts, and review the pull requests it points at.
- Decisions are logged as they are made, in the repository, so neither side has to reconstruct why something was done.
- A blocking question arrives with a proposed answer attached, so the default outcome is progress rather than a stalled day.
One live call a week, and it is scheduled honestly: 08:00 in Vancouver is 17:00 in Malmo. 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 Malmo buyers usually bring us
The record for Malmo lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
life sciences
Study documents, protocols and submissions have rigid structure, and honouring that structure at ingestion time is what makes retrieval accurate.
It starts with your documents and your own analysts writing the questions the system has to get right before anyone will trust it.
Closest service line: Knowledge bases and retrieval
video games
Build pipelines, telemetry and support volume are where the measurable wins are, and each one needs evals drawn from your own sessions.
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
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.
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 Malmo work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Malmo 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 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.