Nevada (NV), United States
AI development for Las Vegas teams, on your working day
Vancouver, British Columbia is where the work gets done, and Las Vegas is one of the markets it gets done for. Nobody from this shop sits in Las Vegas. The 8-hour daily overlap is what makes that a detail rather than a problem.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Las Vegas, United States
- your clock
- UTC-08:00 (America/Los_Angeles)
- overlap
- 8 hours a day, 09:00-17:00 in Vancouver
- presence
- remote only, no office in Las Vegas
8 hours of your day, every working day
Las Vegas runs on the same clock as Vancouver. On a normal working day the two calendars overlap from 09:00 to 17:00 Vancouver time, which is 09:00 to 17:00 where you are.
With a window like that, most decisions never become documents. We review together, we cut scope together, and the written record exists for the archive rather than as the only channel.
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 Las Vegas buyers usually bring us
The record for Las Vegas lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
hospitality
Property systems, rates and guest history are the live state an assistant has to read before it is anything more than a scripted chat widget.
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
conventions
Schedules, exhibitor data and attendee questions change hourly, so the useful build is an agent reading live state rather than a static help page.
Model choice comes last. Tool boundaries, the data model and the failure path are settled before anybody argues about which provider to call.
Closest service line: AI products, built end to end
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 Las Vegas changes what you are buying.
The five lines we sell
Same five lines everywhere, Las Vegas 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 entries from the United States list, each written the same way as this one.
Start a project
Tell us what you are trying to build. A senior engineer reads every message and answers on scope, timeline and fit. If your problem is not one we should take, that is the first thing you will hear.