California (CA), United States
AI development for San Diego teams, on your working day
Vancouver, British Columbia is where the work gets done, and San Diego is one of the markets it gets done for. Nobody from this shop sits in San Diego. The 8-hour daily overlap is what makes that a detail rather than a problem.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- San Diego, United States
- your clock
- UTC-08:00 (America/Los_Angeles)
- overlap
- 8 hours a day, 09:00-17:00 in Vancouver
- presence
- remote only, no office in San Diego
8 hours of your day, every working day
San Diego runs on the same clock as Vancouver. On a normal working day the two calendars overlap from 09:00 to 17:00 Vancouver time, which is 09:00 to 17:00 where you are.
That is enough overlap to work the way a colocated team does. Pull requests get reviewed the hour they land, a design question gets settled on a call instead of in a thread, and an incident at your end finds somebody awake at ours.
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 San Diego buyers usually bring us
The record for San Diego 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.
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
defense
Requirements documents and compliance evidence need retrieval that cites the paragraph, plus deployment inside your own boundary rather than ours.
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
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.
Everything downstream of that is deliberately unremarkable. Fixed acceptance criteria, weekly shipping, a written decision log, and a first reply that tells you if San Diego work of this shape is not something we should take.
The five lines we sell
Same five lines everywhere, San Diego 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.