Alberta (AB), Canada
AI development for Edmonton teams, on your working day
We build AI products from Vancouver, British Columbia, and we work with Edmonton teams remotely. There is no Edmonton office and there never has been. The reason the arrangement works anyway is arithmetic: 7 shared hours a day is most of a working day.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Edmonton, Canada
- your clock
- UTC-07:00 (America/Edmonton)
- overlap
- 7 hours a day, 09:00-16:00 in Vancouver
- presence
- remote only, no office in Edmonton
7 hours of your day, every working day
Edmonton runs 1 hour ahead of Vancouver. On a normal working day the two calendars overlap from 09:00 to 16:00 Vancouver time, which is 10: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 Edmonton buyers usually bring us
The record for Edmonton 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.
Acceptance criteria are fixed before each weekly increment, which turns "is it working" into a question with a yes or a no.
Closest service line: AI products, built end to end
public administration
Legislation, guidance and internal procedure answer most questions, provided retrieval quotes the passage and shows which version it came from.
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
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.
Beyond that, the shape of an engagement does not change with distance: a scoping call, a thin end-to-end slice, then weekly increments against acceptance criteria fixed in advance. If we are not the right shop for Edmonton work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Edmonton 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
Each one has its own page, its own overlap arithmetic and its own industries.
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.