Idaho (ID), United States
AI development for Boise teams, on your working day
We build AI products from Vancouver, British Columbia, and we work with Boise teams remotely. There is no Boise 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
- Boise, United States
- your clock
- UTC-07:00 (America/Boise)
- overlap
- 7 hours a day, 09:00-16:00 in Vancouver
- presence
- remote only, no office in Boise
7 hours of your day, every working day
Boise 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 Boise buyers usually bring us
The record for Boise 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.
It opens with an audit of where AI already helps in your repository and where it produces work your reviewers throw away.
Closest service line: Codebase and team optimization
food processing
Recipes, allergen data and audit records have to answer precisely. Retrieval with hard filters per site and per product line is the whole design.
The golden-question set is the deliverable nobody thinks to ask for, and it is the only way to show that a change helped.
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 Boise work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Boise 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
Same treatment, different clocks, and in some cases a different answer.
Start a project
Write down the problem in whatever form you have it. You get a straight answer about scope, timeline and whether this is work we should be doing at all.