California (CA), United States
AI development for Los Angeles teams, on your working day
We build AI products from Vancouver, British Columbia, and we work with Los Angeles teams remotely. There is no Los Angeles office and there never has been. The reason the arrangement works anyway is arithmetic: 8 shared hours a day is most of a working day.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Los Angeles, 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 Los Angeles
8 hours of your day, every working day
Los Angeles 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.
It also means demos happen live rather than as a recording. Watching somebody use what we built, while we can still change it that day, is worth more than any written status report.
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 Los Angeles buyers usually bring us
The record for Los Angeles lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
entertainment
Rights data, scheduling and asset metadata decide what can even be shown, so the product starts with those constraints instead of the model.
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
aerospace
Certification evidence has to trace to a document revision, so retrieval returns the clause and the revision it came from rather than a confident paraphrase.
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
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.
Beyond that, the shape of an engagement does not change with distance: a scoping call, a thin end-to-end slice, then weekly increments against acceptance criteria fixed in advance. If we are not the right shop for Los Angeles work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Los Angeles 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.