Missouri (MO), United States
AI development for St. Louis teams, on your working day
We build AI products from Vancouver, British Columbia, and we work with St. Louis teams remotely. There is no St. Louis 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
- St. Louis, 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 St. Louis
6 hours of your day, every working day
St. Louis 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.
It also means demos happen live rather than as a recording. Watching somebody use what we built, while we can still change it that day, is worth more than any written status report.
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 St. Louis buyers usually bring us
The record for St. Louis lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
agricultural technology
Field telemetry arrives sparse and noisy. The model is the small half; gap handling and an alert threshold you can defend in front of a grower is the rest.
You get a running product with its own test suite and enough documentation for your team to take it over, not a prototype with our commit history in it.
Closest service line: AI products, built end to end
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.
Recall gets measured before anybody comments on the wording, because a fluent answer drawn from the wrong passage is the worst outcome on offer.
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 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, St. Louis 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
Send the problem. If it is a fit, you get scope and a timeline. If it is not, you get told that in the first reply instead of after a discovery process.