Ontario (ON), Canada
AI development for Ottawa teams, inside your afternoon
We are an AI development agency based in Vancouver, British Columbia. Ottawa clients get a remote engagement with a real, bounded overlap: 5 hours a day when both sides are awake and working. Everything that does not fit in it moves to writing, deliberately.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Ottawa, 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 Ottawa
What fits in a 5-hour window
The overlap is real and it is bounded. Ottawa 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.
What we do not do is stretch that window by pretending either side works longer than it does. It is a fixed budget of shared hours a week, and it gets spent 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 Ottawa buyers usually bring us
The record for Ottawa lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
public administration
Legislation, guidance and internal procedure answer most questions, provided retrieval quotes the passage and shows which version it came from.
Chunking follows the structure of the document instead of a character count, which is the whole difference between a useful index and an expensive one.
Closest service line: Knowledge bases and retrieval
telecommunications
Network inventory, provisioning and billing systems are the integration surface, and each one has retry semantics that a prompt cannot express.
Business rules become typed tools with explicit contracts, because a rule that lives in a prompt is a rule that drifts.
Closest service line: Forward-deployed engineering
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 Ottawa work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Ottawa 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 rather than a job spec. You get an answer on scope, timeline and whether we are the right shop, written by the person who would do the work.