California (CA), United States
AI development for San Jose teams, on your working day
The shop is in Vancouver, British Columbia, and it is one person deep. San Jose clients are worked with remotely, on a schedule that happens to line up: 8 hours of every working day sit inside both calendars at once.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- San Jose, 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 Jose
8 hours of your day, every working day
San Jose 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.
A window that wide changes what is possible: pairing on a hard retrieval bug, walking through eval results together while both of you can still change the run, and shipping a fix the same afternoon it was reported.
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 Jose buyers usually bring us
The record for San Jose lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
semiconductors
Verification and tooling repos are enormous and slow, so the first work is feedback speed and scoped rules, not a model upgrade.
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
enterprise software
Large product repos with heavy review culture need repo-level context files and test generation before agents stop producing work you throw away.
The written practice belongs to your team afterwards, because a workflow that only a contractor understands is a workflow you rent forever.
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.
The rest is the same everywhere: we scope it, we build a thin slice against your real data, and we hand back something your own team can maintain. No retainer you cannot cancel and no seat licences.
The five lines we sell
Same five lines everywhere, San Jose 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
More of United States, all of it worked remotely from Vancouver.
Start a project
Send the problem. If it is a fit, you get scope and a timeline. If it is not, you get told that in the first reply instead of after a discovery process.