Minnesota (MN), United States
AI development for Minneapolis teams, on your working day
Magic Ship is one shop in Vancouver, British Columbia, working remotely with clients in Minneapolis. No local address, no local number, and no pretence otherwise. The overlap does the work an office would have done: 6 hours a day, live.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Minneapolis, United States
- your clock
- UTC-06:00 (America/Chicago)
- overlap
- 6 hours a day, 09:00-15:00 in Vancouver
- presence
- remote only, no office in Minneapolis
6 hours of your day, every working day
Minneapolis runs 2 hours ahead of Vancouver. On a normal working day the two calendars overlap from 09:00 to 15:00 Vancouver time, which is 11:00 to 17:00 where you are.
With a window like that, most decisions never become documents. We review together, we cut scope together, and the written record exists for the archive rather than as the only channel.
The parts that still get written down are written down anyway: acceptance criteria, the decision log, and what changed in each weekly increment. A shared clock is not an excuse for an undocumented project.
What Minneapolis buyers usually bring us
The record for Minneapolis lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
medical devices
Design history files and regulatory submissions have to be traceable end to end, so retrieval carries the document identifier and the revision.
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
retail
Catalogue, inventory and returns data drive every useful answer, so the tool layer over those systems is built before anything conversational.
The eval harness gets built beside the first feature, so week three can prove that week two did not quietly make the output worse.
Closest service line: AI products, built end to end
Contracts, currency and where the data sits
Invoices are in US dollars. A US buyer engaging a Canadian company is routine, and the form your accounts team will ask for is a W-8BEN-E, which we have ready before the first invoice.
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 Minneapolis changes what you are buying.
The five lines we sell
Same five lines everywhere, Minneapolis 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 United States
If you are comparing markets, these are the other United States entries in the record set.
Start a project
Tell us what you are trying to build. A senior engineer reads every message and answers on scope, timeline and fit. If your problem is not one we should take, that is the first thing you will hear.