Newfoundland and Labrador (NL), Canada
AI development for St. John's teams, inside your afternoon
We are in Vancouver, British Columbia. You are in St. John's. Nobody from this shop is, and nobody pretends to be. The two working days touch for 3.5 hours, and that window is spent on decisions rather than on status.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- St. John's, Canada
- your clock
- UTC-03:30 (America/St_Johns)
- overlap
- 3.5 hours a day, 09:00-12:30 in Vancouver
- presence
- remote only, no office in St. John's
What fits in a 3.5-hour window
The overlap is real and it is bounded. St. John's sits 4.5 hours ahead of Vancouver, so the shared part of the day runs 09:00 to 12:30 our time and 13:30 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 St. John's buyers usually bring us
The record for St. John's lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
offshore energy
Well files, inspection reports and vendor documentation run to millions of pages, and the retrieval design has to pin an answer to a well and a date.
Hybrid search beats embeddings alone in nearly every corpus we have opened, and metadata filters behave as hard constraints or they are not filters.
Closest service line: Knowledge bases and retrieval
ocean technology
Sensor data comes back in bursts from platforms that go offline for weeks, so ingestion has to tolerate gaps without inventing continuity.
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
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, St. John's 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
Same treatment, different clocks, and in some cases a different answer.
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.