Auckland, New Zealand
AI development for Auckland teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia. Auckland and Vancouver share no working hours at all, and that is stated up front because it changes how the work runs: written handoff at the end of each side's day, a loop that turns once every twenty-four hours, and nobody waiting on a meeting.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Auckland, New Zealand
- your clock
- UTC+12:00 (Pacific/Auckland)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Auckland
No shared working day, so the loop is written
Auckland 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.
Treated properly it is the better arrangement. Nobody blocks on a meeting, every decision exists as text with a date on it, and the work moves while the other side sleeps instead of while the other side waits.
- The Vancouver day ends with a written summary: shipped, broken, blocked, and the one thing we need you to decide.
- That summary is waiting at 13:00 your time, alongside the diffs it refers to.
- The decision log lives in the repository rather than in a chat thread, so it is still readable a year later.
- Anything that would block us gets asked as a proposal you can approve in a sentence, not as an open question.
One live call a week, and it is scheduled honestly: 13:00 in Vancouver is 09:00 in Auckland 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 Auckland buyers usually bring us
The record for Auckland lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
financial services
Research, filings and internal policy are the corpus. Hybrid search with metadata filters as hard constraints, plus span citations, or it does not ship.
Answers cite the passage they came from. A retrieval system without span-level citation gets used twice and then quietly abandoned.
Closest service line: Knowledge bases and retrieval
logistics
Carrier APIs, warehouse systems and customer portals all break differently under load, which is why the integration work is the project.
Integrations are validated against live traffic: auth, pagination, rate limits, retries, and the failure modes that only surface under real load.
Closest service line: Forward-deployed engineering
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.
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, Auckland 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 entries from the Oceania list, each written the same way as this one.
Start a project
Describe what is broken or what you want built. The reply comes from the engineer who would build it, and it covers scope, timeline and fit before anything else.