Washington (WA), United States
AI development for Seattle teams, on your working day
We build AI products from Vancouver, British Columbia, and we work with Seattle teams remotely. There is no Seattle 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
- Seattle, 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 Seattle
8 hours of your day, every working day
Seattle 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 Seattle buyers usually bring us
The record for Seattle lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
cloud computing
Infrastructure repos punish guesswork. Fast local feedback, typed boundaries and worked examples in the repo are what make agent output reviewable.
Test generation is the usual first wedge: high value, low risk, and it shows exactly which parts of the codebase an agent cannot read.
Closest service line: Codebase and team optimization
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.
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.
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 Seattle work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Seattle 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 rather than a job spec. You get an answer on scope, timeline and whether we are the right shop, written by the person who would do the work.