Canterbury, New Zealand
AI development for Christchurch teams, handed over in writing
The desk is in Vancouver, British Columbia. Christchurch is far enough around the world that our working days do not touch on the same date, which is a fact worth stating in the first paragraph rather than discovering in week two. The work is handed over in writing instead.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Christchurch, New Zealand
- your clock
- UTC+12:00 (Pacific/Auckland)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Christchurch
No shared working day, so the loop is written
Christchurch is 20 hours ahead of Vancouver. When we start at 09:00 it is 05:00 on the next day for you, and when we stop at 17:00 it is 13:00 on the next day. On the same calendar date there is no hour where both sides are at work.
There is a real cost and it is worth naming: an answer to a blocking question can take a working day to reach you. We handle it by sending the proposed answer with the question, so silence means agreement rather than a lost day.
- Everything built during our day lands in one written note before we close the laptop. No status meeting stands in for it.
- Your morning starts with that note and a set of pull requests to review, which is a better start than a calendar invitation.
- Every decision worth arguing about is written down where the code is, with the reasoning and the date attached.
- Questions come with a recommendation, because a question that needs a reply before work continues costs a full day here.
One live call a week, and it is scheduled honestly: 13:00 in Vancouver is 09:00 in Christchurch on the next day. Neither side takes a bad hour for that one. The call simply lands on two different calendar dates, which is a scheduling detail rather than a hardship.
What Christchurch buyers usually bring us
The record for Christchurch lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
aerospace
Certification evidence has to trace to a document revision, so retrieval returns the clause and the revision it came from rather than a confident paraphrase.
The golden-question set is the deliverable nobody thinks to ask for, and it is the only way to show that a change helped.
Closest service line: Knowledge bases and retrieval
agricultural technology
Field telemetry arrives sparse and noisy. The model is the small half; gap handling and an alert threshold you can defend in front of a grower is the rest.
Week one puts something running in your environment against real state, because an agent that can only talk teaches nobody anything about the hard part.
Closest service line: AI products, built end to end
Contracts, currency and where the data sits
Invoices are in New Zealand or US dollars. The date offset is large enough that every deadline in the contract carries the timezone it is measured in.
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 Christchurch work, you get told that in the first reply rather than after a proposal.
The five lines we sell
Same five lines everywhere, Christchurch 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 Oceania
More of Oceania, all of it worked remotely from Vancouver.
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.