New Brunswick (NB), Canada
AI development for Moncton teams, inside your afternoon
The shop sits in Vancouver, British Columbia, and works with Moncton teams at a distance. Your day and ours share 4 hours. That is enough for the conversations that need voices, and not enough to run a project on calls, which is fine.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Moncton, Canada
- your clock
- UTC-04:00 (America/Moncton)
- overlap
- 4 hours a day, 09:00-13:00 in Vancouver
- presence
- remote only, no office in Moncton
What fits in a 4-hour window
The overlap is real and it is bounded. Moncton 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.
A partial overlap punishes projects that run on meetings and rewards ones that run on written acceptance criteria. We build for the second kind, which is how we would run it anyway.
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 Moncton buyers usually bring us
The record for Moncton lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
logistics
Carrier APIs, warehouse systems and customer portals all break differently under load, which is why the integration work is the project.
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
customer contact centres
Deflection numbers are easy to fake and hard to earn. The build that works pairs retrieval over real policy with an eval set drawn from transcripts.
The eval harness gets built beside the first feature, so week three can prove that week two did not quietly make the output worse.
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.
The rest is the same everywhere: we scope it, we build a thin slice against your real data, and we hand back something your own team can maintain. No retainer you cannot cancel and no seat licences.
The five lines we sell
Same five lines everywhere, Moncton 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
Write down the problem in whatever form you have it. You get a straight answer about scope, timeline and whether this is work we should be doing at all.