Texas (TX), United States
AI development for San Antonio teams, on your working day
Magic Ship is one shop in Vancouver, British Columbia, working remotely with clients in San Antonio. No local address, no local number, and no pretence otherwise. The overlap does the work an office would have done: 6 hours a day, live.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- San Antonio, 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 San Antonio
6 hours of your day, every working day
San Antonio 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.
Practically, it means your team can treat us as another desk in the building for most of the day: same standup, same review queue, same afternoon scramble when something breaks.
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 San Antonio buyers usually bring us
The record for San Antonio lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
cybersecurity
Security teams want agent output they can review line by line, which means small diffs, checks the agent runs itself, and rules scoped per path.
Worked examples of good output, in your own code, teach a team more than any document about prompting we could write.
Closest service line: Codebase and team optimization
military
Doctrine, requirements and evidence packages need retrieval that cites the paragraph and runs inside your own boundary rather than on our infrastructure.
Access rules apply inside the index at retrieval time, never as a filter bolted onto the answer after the fact.
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.
Past that, the mechanics are ordinary. A scoping call, a written scope, weekly increments, and an invoice that matches what shipped. The one thing distance changes is when in your day the questions arrive.
The five lines we sell
Same five lines everywhere, San Antonio 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
Describe what is broken or what you want built. The reply comes from the engineer who would build it, and it covers scope, timeline and fit before anything else.