Oslo, Norway
AI development for Oslo teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia. Oslo and Vancouver share no working hours at all, and that is stated up front because it changes how the work runs: written handoff at the end of each side's day, a loop that turns once every twenty-four hours, and nobody waiting on a meeting.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Oslo, Norway
- your clock
- UTC+01:00 (Europe/Oslo)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Oslo
No shared working day, so the loop is written
Oslo 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.
Removing the shared hour removes the interruptions with it. A full Vancouver day of uninterrupted build time, handed over in writing, tends to move a project further than a day punctuated by four calls.
- 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 Oslo. 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 Oslo buyers usually bring us
The record for Oslo lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
offshore energy
Well files, inspection reports and vendor documentation run to millions of pages, and the retrieval design has to pin an answer to a well and a date.
Recall gets measured before anybody comments on the wording, because a fluent answer drawn from the wrong passage is the worst outcome on offer.
Closest service line: Knowledge bases and retrieval
shipping
Vessel systems, port calls and documentation flows each need their own integration, built against live data and real timeouts.
Business rules become typed tools with explicit contracts, because a rule that lives in a prompt is a rule that drifts.
Closest service line: Forward-deployed engineering
Contracts, currency and where the data sits
Invoices are in euros or US dollars. Norway is in the EEA, so GDPR applies to what we index and the storage region is agreed before anything is ingested.
The commercial part stays deliberately boring. Fixed acceptance criteria per increment, weekly shipping, and a written record of every decision. Nothing about working from Vancouver instead of Oslo changes what you are buying.
The five lines we sell
Same five lines everywhere, Oslo 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
Where else the same work happens in Europe, with the numbers redone per market.
Start a project
Say what you are trying to build and what has already been tried. The reply is from a senior engineer, and it will tell you if the shape of the work is wrong before it tells you anything else.