Alaska (AK), United States
AI development for Anchorage teams, on your working day
The shop is in Vancouver, British Columbia, and it is one person deep. Anchorage clients are worked with remotely, on a schedule that happens to line up: 7 hours of every working day sit inside both calendars at once.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Anchorage, United States
- your clock
- UTC-09:00 (America/Anchorage)
- overlap
- 7 hours a day, 10:00-17:00 in Vancouver
- presence
- remote only, no office in Anchorage
7 hours of your day, every working day
Anchorage runs 1 hour behind Vancouver. On a normal working day the two calendars overlap from 10:00 to 17:00 Vancouver time, which is 09:00 to 16:00 where you are.
A window that size means questions get answered while they still matter. Nobody sits on a blocker overnight, and a bad assumption gets caught in the hour it was made rather than in the following sprint.
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 Anchorage buyers usually bring us
The record for Anchorage lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
air cargo
Booking, tracking and customs systems each speak their own dialect, and the job is a typed tool per dialect with an explicit contract and real retry behaviour.
Reconciliation and idempotency are designed in at the start, because retrofitting them after the first duplicate transaction is expensive.
Closest service line: Forward-deployed engineering
energy
Operational data is high volume and low tolerance for a wrong answer, so the eval harness and the fallback behaviour get built before the interface.
Acceptance criteria are fixed before each weekly increment, which turns "is it working" into a question with a yes or a no.
Closest service line: AI products, built end to end
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 Anchorage work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Anchorage 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
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.