Alberta (AB), Canada
AI development for Calgary teams, on your working day
Vancouver, British Columbia is where the work gets done, and Calgary is one of the markets it gets done for. Nobody from this shop sits in Calgary. The 7-hour daily overlap is what makes that a detail rather than a problem.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Calgary, 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 Calgary
7 hours of your day, every working day
Calgary 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.
That is enough overlap to work the way a colocated team does. Pull requests get reviewed the hour they land, a design question gets settled on a call instead of in a thread, and an incident at your end finds somebody awake at ours.
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 Calgary buyers usually bring us
The record for Calgary 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.
We ship something narrow early and widen it, because scope found in production costs less than scope argued about in a document.
Closest service line: AI products, built end to end
financial services
Research, filings and internal policy are the corpus. Hybrid search with metadata filters as hard constraints, plus span citations, or it does not ship.
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
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 downstream of that is deliberately unremarkable. Fixed acceptance criteria, weekly shipping, a written decision log, and a first reply that tells you if Calgary work of this shape is not something we should take.
The five lines we sell
Same five lines everywhere, Calgary 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 entries from the Canada list, each written the same way as this one.
Start a project
Describe what is broken or what you want built. The reply comes from the engineer who would build it, and it covers scope, timeline and fit before anything else.