Oregon (OR), United States
AI development for Portland teams, on your working day
The shop is in Vancouver, British Columbia, and it is one person deep. Portland clients are worked with remotely, on a schedule that happens to line up: 8 hours of every working day sit inside both calendars at once.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Portland, 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 Portland
8 hours of your day, every working day
Portland 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.
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 Portland buyers usually bring us
The record for Portland 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.
The written practice belongs to your team afterwards, because a workflow that only a contractor understands is a workflow you rent forever.
Closest service line: Codebase and team optimization
athletic apparel
Size charts, product copy and returns history feed one retrieval layer, and the eval harness is what stops a fit answer from being politely invented.
We ship something narrow early and widen it, because scope found in production costs less than scope argued about in a document.
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.
Everything else is the same as it would be for a client down the street from us: scope, a thin slice in week one, then weekly increments you can stop at any time. The distance changes the schedule, not the contract.
The five lines we sell
Same five lines everywhere, Portland 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.