California (CA), United States
AI development for San Francisco teams, on your working day
Vancouver, British Columbia is where the work gets done, and San Francisco is one of the markets it gets done for. Nobody from this shop sits in San Francisco. The 8-hour daily overlap is what makes that a detail rather than a problem.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- San Francisco, 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 Francisco
8 hours of your day, every working day
San Francisco 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.
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 San Francisco buyers usually bring us
The record for San Francisco lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
venture capital
Memos, data rooms and portfolio reporting are the corpus, and the value shows up when retrieval can hold one company and one round as a hard filter.
Access rules apply inside the index at retrieval time, never as a filter bolted onto the answer after the fact.
Closest service line: Knowledge bases and retrieval
software
The repo is the constraint on how much AI-assisted work you keep. Context files, scoped rules and checks the agent can run itself come first.
The deliverable is committed to your repository. Context files, path-scoped rules, and checks an agent can run against its own output.
Closest service line: Codebase and team optimization
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 Francisco work of this shape is not something we should take.
The five lines we sell
Same five lines everywhere, San Francisco 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.