Texas (TX), United States
AI development for Dallas teams, on your working day
Magic Ship is an AI development agency in Vancouver, British Columbia. We have no office in Dallas and nobody on the ground there. What we do have is 6 hours of your working day, every working day, which is enough to review, pair and fix things while you are still at your desk.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Dallas, 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 Dallas
6 hours of your day, every working day
Dallas 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.
That is enough overlap to work the way a colocated team does. Pull requests get reviewed the hour they land, a design question gets settled on a call instead of in a thread, and an incident at your end finds somebody awake at ours.
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 Dallas buyers usually bring us
The record for Dallas lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
telecommunications
Network inventory, provisioning and billing systems are the integration surface, and each one has retry semantics that a prompt cannot express.
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
financial services
Research, filings and internal policy are the corpus. Hybrid search with metadata filters as hard constraints, plus span citations, or it does not ship.
Hybrid search beats embeddings alone in nearly every corpus we have opened, and metadata filters behave as hard constraints or they are not filters.
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.
The commercial part stays deliberately boring. Fixed acceptance criteria per increment, weekly shipping, and a written record of every decision. Nothing about working from Vancouver instead of Dallas changes what you are buying.
The five lines we sell
Same five lines everywhere, Dallas 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
If you are comparing markets, these are the other United States entries in the record set.
Start a project
Say what you are trying to build and what has already been tried. The reply is from a senior engineer, and it will tell you if the shape of the work is wrong before it tells you anything else.