Oklahoma (OK), United States
AI development for Oklahoma City teams, on your working day
An AI development agency, one desk, Vancouver, British Columbia. For Oklahoma City that means a remote engagement with an unusually generous overlap - 6 hours a day - and no story about a local presence that does not exist.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Oklahoma City, 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 Oklahoma City
6 hours of your day, every working day
Oklahoma City 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 wide changes what is possible: pairing on a hard retrieval bug, walking through eval results together while both of you can still change the run, and shipping a fix the same afternoon it was reported.
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 Oklahoma City buyers usually bring us
The record for Oklahoma City lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
energy
Operational data is high volume and low tolerance for a wrong answer, so the eval harness and the fallback behaviour get built before the interface.
The first slice is thin and runs end to end: one real workflow, one real data source, and an agent with tools that change something rather than describe it.
Closest service line: AI products, built end to end
aviation maintenance
Service manuals, airworthiness directives and task cards are the daily reference. Retrieval has to return the task card, not a summary of what it probably says.
Most retrieval failures are ingestion failures, so the early weeks go into parsing and chunking rather than into rewording a prompt.
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, Oklahoma City 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.