Pennsylvania (PA), United States
AI development for Pittsburgh teams, inside your afternoon
The shop sits in Vancouver, British Columbia, and works with Pittsburgh teams at a distance. Your day and ours share 5 hours. That is enough for the conversations that need voices, and not enough to run a project on calls, which is fine.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Pittsburgh, United States
- your clock
- UTC-05:00 (America/New_York)
- overlap
- 5 hours a day, 09:00-14:00 in Vancouver
- presence
- remote only, no office in Pittsburgh
What fits in a 5-hour window
The overlap is real and it is bounded. Pittsburgh sits 3 hours ahead of Vancouver, so the shared part of the day runs 09:00 to 14:00 our time and 12:00 to 17:00 yours.
A partial overlap punishes projects that run on meetings and rewards ones that run on written acceptance criteria. We build for the second kind, which is how we would run it anyway.
What moves to writing is not a downgrade. A daily handoff note at the end of the Vancouver day, decisions logged when they are made, and review on the pull request itself means your morning starts with the answer rather than with a meeting invitation.
What Pittsburgh buyers usually bring us
The record for Pittsburgh lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
robotics
Simulation and control repos need fast local runs and hard boundaries before an agent can help, otherwise every suggestion costs a review cycle.
Small diffs, explicit boundaries and locally runnable checks are what make agent output reviewable instead of merely plausible.
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.
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.
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, Pittsburgh 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 of United States, all of it worked remotely from Vancouver.
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.