British Columbia (BC), Canada

AI development in Vancouver, by somebody who lives here

Magic Ship is an AI development agency in Vancouver, British Columbia. This is the one market on this list where we are physically present, because it is where the desk is. Everywhere else is remote by definition; here it is a choice.

base
vancouver, bc, canada (UTC-08:00)
market
Vancouver, Canada
your clock
UTC-08:00 (America/Vancouver)
overlap
8 hours a day, 09:00-17:00 in Vancouver
presence
this is the home port

The one city where being in the room is on the table

Every other page in this set describes a remote engagement, because every other market is one. Vancouver is not. If a kickoff goes better around a table, we can be at yours, and a whiteboard session for a retrieval design costs a bus ride instead of a flight.

The clock argument disappears too. Your 09:00 is our 09:00, your incident at 16:30 on a Friday is our 16:30 on a Friday, and there is no handoff document standing in for a conversation. Most engagements still run mostly remote, because that is how the work gets done, but in person is a real option here and nowhere else on this list.

The local context is first-hand as well. We know which studios run which pipelines, what the hiring market for senior engineers actually looks like, and which parts of the tech scene here are load-bearing rather than loud. That knowledge is not researched. It is just where we live.

What Vancouver actually builds

The industries below are the ones this city runs on, and they are the ones we see most often from a desk inside it.

film and visual effects

Pipelines are bespoke per facility, so the win is tooling that reads shot state and asset dependencies rather than another general assistant.

The interface is the final quarter of the job. Everything before it is the tool layer and the tests that keep the tool layer honest.

Closest service line: AI products, built end to end

video games

Build pipelines, telemetry and support volume are where the measurable wins are, and each one needs evals drawn from your own sessions.

Model choice comes last. Tool boundaries, the data model and the failure path are settled before anybody argues about which provider to call.

Closest service line: AI products, built end to end

clean technology

Sensor histories, grid data and permitting documents pull in different directions, and the useful product is the one that reconciles them without a person in the loop.

You get a running product with its own test suite and enough documentation for your team to take it over, not a prototype with our commit history in it.

Closest service line: AI products, built end to end

Contracts, currency and the short version

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.

Engagements start with a scoping call, then a thin end-to-end slice, then weekly increments against fixed acceptance criteria. Being in the same city does not change the shape of that, it only shortens the feedback loop.

The five lines we sell

Same five lines everywhere. Most Vancouver engagements are one of them, occasionally two.

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.

Every market we work in

Start a project

Tell us what you are trying to build. We read every message, we answer on scope and fit, and if you would rather do that over coffee in this city, say so.

Start a project