Quebec (QC), Canada
AI development for Montreal teams, inside your afternoon
We are in Vancouver, British Columbia. You are in Montreal. Nobody from this shop is, and nobody pretends to be. The two working days touch for 5 hours, and that window is spent on decisions rather than on status.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Montreal, Canada
- your clock
- UTC-05:00 (America/Toronto)
- overlap
- 5 hours a day, 09:00-14:00 in Vancouver
- presence
- remote only, no office in Montreal
What fits in a 5-hour window
The overlap is real and it is bounded. Montreal sits 3 hours ahead of Vancouver, so the shared part of the day runs 09:00 to 14:00 our time and 12:00 to 17:00 yours.
We spend that window on the things that are expensive in writing. Scope calls, eval walkthroughs, and the awkward conversation about what to cut. Everything else moves to text on purpose.
What moves to writing is not a downgrade. A daily handoff note at the end of the Vancouver day, decisions logged when they are made, and review on the pull request itself means your morning starts with the answer rather than with a meeting invitation.
What Montreal buyers usually bring us
The record for Montreal lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
aerospace
Certification evidence has to trace to a document revision, so retrieval returns the clause and the revision it came from rather than a confident paraphrase.
The golden-question set is the deliverable nobody thinks to ask for, and it is the only way to show that a change helped.
Closest service line: Knowledge bases and retrieval
video games
Build pipelines, telemetry and support volume are where the measurable wins are, and each one needs evals drawn from your own sessions.
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
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, Montreal 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.