Wisconsin (WI), United States
AI development for Madison teams, on your working day
Magic Ship is an AI development agency in Vancouver, British Columbia. We have no office in Madison and nobody on the ground there. What we do have is 6 hours of your working day, every working day, which is enough to review, pair and fix things while you are still at your desk.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Madison, 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 Madison
6 hours of your day, every working day
Madison 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.
Practically, it means your team can treat us as another desk in the building for most of the day: same standup, same review queue, same afternoon scramble when something breaks.
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 Madison buyers usually bring us
The record for Madison lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
biotech
Protocols, study reports and regulatory correspondence answer the same questions repeatedly. Structure-aware ingestion of the report format is most of the work.
Chunking follows the structure of the document instead of a character count, which is the whole difference between a useful index and an expensive one.
Closest service line: Knowledge bases and retrieval
higher education
Faculty and staff need the failure modes as much as the workflows, so sessions run on their own courses and repos and end with a written practice they keep.
Sessions run on your codebase, your tickets and your constraints. A vendor demo teaches nothing that survives the following Monday.
Closest service line: Training and enablement
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 Madison changes what you are buying.
The five lines we sell
Same five lines everywhere, Madison 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
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.