Saskatchewan (SK), Canada
AI development for Regina teams, on your working day
An AI development agency, one desk, Vancouver, British Columbia. For Regina 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
- Regina, Canada
- your clock
- UTC-06:00 (America/Regina)
- overlap
- 6 hours a day, 09:00-15:00 in Vancouver
- presence
- remote only, no office in Regina
6 hours of your day, every working day
Regina 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 Regina buyers usually bring us
The record for Regina lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
agriculture
Agronomy notes pile up season by season in spreadsheets and inboxes. Indexed by crop, plot and year they answer questions; left alone they are archaeology.
It starts with your documents and your own analysts writing the questions the system has to get right before anyone will trust it.
Closest service line: Knowledge bases and retrieval
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
Contracts, currency and where the data sits
This is a domestic engagement. Invoices are in Canadian dollars, the contract is Canadian, and nothing crosses a border on the way to you or on the way back.
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, Regina 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 Canada
More of Canada, 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.