Texas (TX), United States
AI development for Austin teams, on your working day
We build AI products from Vancouver, British Columbia, and we work with Austin teams remotely. There is no Austin office and there never has been. The reason the arrangement works anyway is arithmetic: 6 shared hours a day is most of a working day.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Austin, United States
- your clock
- UTC-06:00 (America/Chicago)
- overlap
- 6 hours a day, 09:00-15:00 in Vancouver
- presence
- remote only, no office in Austin
6 hours of your day, every working day
Austin runs 2 hours ahead of Vancouver. On a normal working day the two calendars overlap from 09:00 to 15:00 Vancouver time, which is 11:00 to 17: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 Austin buyers usually bring us
The record for Austin 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
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.
Feedback speed is the lever nobody wants to pull. If the suite takes twenty minutes, no agent workflow survives contact with it.
Closest service line: Codebase and team optimization
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.
The rest is the same everywhere: we scope it, we build a thin slice against your real data, and we hand back something your own team can maintain. No retainer you cannot cancel and no seat licences.
The five lines we sell
Same five lines everywhere, Austin 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.