Nebraska (NE), United States
AI development for Omaha teams, on your working day
We build AI products from Vancouver, British Columbia, and we work with Omaha teams remotely. There is no Omaha 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
- Omaha, 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 Omaha
6 hours of your day, every working day
Omaha 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 Omaha buyers usually bring us
The record for Omaha lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
insurance
Policy wordings, endorsements and claims files need clause-level retrieval with the version and jurisdiction pinned, or the answer is guesswork with a citation.
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
data centers
Capacity systems, ticketing and monitoring have to be wired together before an assistant is anything more than a chat window over a wiki.
Integrations are validated against live traffic: auth, pagination, rate limits, retries, and the failure modes that only surface under real load.
Closest service line: Forward-deployed engineering
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.
Everything else is the same as it would be for a client down the street from us: scope, a thin slice in week one, then weekly increments you can stop at any time. The distance changes the schedule, not the contract.
The five lines we sell
Same five lines everywhere, Omaha 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
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.