Nova Scotia (NS), Canada
AI development for Halifax teams, inside your afternoon
Magic Ship is an AI development agency in Vancouver, British Columbia, working remotely with teams in Halifax. We are not in Halifax and we will not pretend to be. Your day and ours meet for 4 hours, and the engagement is built around that window rather than around wishing it were longer.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Halifax, Canada
- your clock
- UTC-04:00 (America/Halifax)
- overlap
- 4 hours a day, 09:00-13:00 in Vancouver
- presence
- remote only, no office in Halifax
What fits in a 4-hour window
The overlap is real and it is bounded. Halifax sits 4 hours ahead of Vancouver, so the shared part of the day runs 09:00 to 13:00 our time and 13:00 to 17:00 yours.
Use it for decisions, not status. Status is a document you can read at your own hour; a decision is the thing worth spending a live hour on, and there are only a few of those a week.
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 Halifax buyers usually bring us
The record for Halifax lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
shipping
Vessel systems, port calls and documentation flows each need their own integration, built against live data and real timeouts.
Without a rule about what goes back into the platform, this work becomes a treadmill, so that rule is agreed at the first account.
Closest service line: Forward-deployed engineering
ocean technology
Sensor data comes back in bursts from platforms that go offline for weeks, so ingestion has to tolerate gaps without inventing continuity.
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 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.
Past that, the mechanics are ordinary. A scoping call, a written scope, weekly increments, and an invoice that matches what shipped. The one thing distance changes is when in your day the questions arrive.
The five lines we sell
Same five lines everywhere, Halifax 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
Where else the same work happens in Canada, with the numbers redone per market.
Start a project
Say what you are trying to build and what has already been tried. The reply is from a senior engineer, and it will tell you if the shape of the work is wrong before it tells you anything else.