Utah (UT), United States
AI development for Salt Lake City teams, on your working day
We build AI products from Vancouver, British Columbia, and we work with Salt Lake City teams remotely. There is no Salt Lake City office and there never has been. The reason the arrangement works anyway is arithmetic: 7 shared hours a day is most of a working day.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Salt Lake City, United States
- your clock
- UTC-07:00 (America/Denver)
- overlap
- 7 hours a day, 09:00-16:00 in Vancouver
- presence
- remote only, no office in Salt Lake City
7 hours of your day, every working day
Salt Lake City 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.
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 Salt Lake City buyers usually bring us
The record for Salt Lake City lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
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.
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
financial services
Research, filings and internal policy are the corpus. Hybrid search with metadata filters as hard constraints, plus span citations, or it does not ship.
Chunking follows the structure of the document instead of a character count, which is the whole difference between a useful index and an expensive one.
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 Salt Lake City work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Salt Lake City 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
Each one has its own page, its own overlap arithmetic and its own industries.
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.