Arizona (AZ), United States
AI development for Phoenix teams, on your working day
Vancouver, British Columbia is where the work gets done, and Phoenix is one of the markets it gets done for. Nobody from this shop sits in Phoenix. The 7-hour daily overlap is what makes that a detail rather than a problem.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Phoenix, United States
- your clock
- UTC-07:00 (America/Phoenix)
- overlap
- 7 hours a day, 09:00-16:00 in Vancouver
- presence
- remote only, no office in Phoenix
7 hours of your day, every working day
Phoenix runs 1 hour ahead of Vancouver. On a normal working day the two calendars overlap from 09:00 to 16:00 Vancouver time, which is 10: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 Phoenix buyers usually bring us
The record for Phoenix 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.
We prove one wedge and then widen it. Rewriting the whole practice on day one is how these efforts die.
Closest service line: Codebase and team optimization
health care
Clinical and administrative documents demand citation and access control at retrieval time, not a disclaimer at the bottom of the answer.
Most retrieval failures are ingestion failures, so the early weeks go into parsing and chunking rather than into rewording a prompt.
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.
The commercial part stays deliberately boring. Fixed acceptance criteria per increment, weekly shipping, and a written record of every decision. Nothing about working from Vancouver instead of Phoenix changes what you are buying.
The five lines we sell
Same five lines everywhere, Phoenix 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 entries from the United States list, each written the same way as this one.
Start a project
Say what you are trying to build and what has already been tried. The reply is from a senior engineer, and it will tell you if the shape of the work is wrong before it tells you anything else.