Northern Territory (NT), Australia
AI development for Darwin teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia. Darwin 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
- Darwin, Australia
- your clock
- UTC+09:30 (Australia/Darwin)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Darwin
No shared working day, so the loop is written
Darwin is 17.5 hours ahead of Vancouver. When we start at 09:00 it is 02:30 on the next day for you, and when we stop at 17:00 it is 10:30 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.
- A handoff note goes out at the end of every Vancouver working day: what shipped, what broke, and what needs a decision from you.
- You read it at 10:30, or whenever your day starts, and review the pull requests it points at.
- Decisions are logged as they are made, in the repository, so neither side has to reconstruct why something was done.
- A blocking question arrives with a proposed answer attached, so the default outcome is progress rather than a stalled day.
One live call a week, and it is scheduled honestly: 15:30 in Vancouver is 09:00 in Darwin 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 Darwin buyers usually bring us
The record for Darwin lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
liquefied natural gas
Plant documentation, cargo records and long-term contracts are the reference set, and answers have to name the cargo or the train they came from.
Chunking follows the structure of the document instead of a character count, which is the whole difference between a useful index and an expensive one.
Closest service line: Knowledge bases and retrieval
defense
Requirements documents and compliance evidence need retrieval that cites the paragraph, plus deployment inside your own boundary rather than ours.
Access rules apply inside the index at retrieval time, never as a filter bolted onto the answer after the fact.
Closest service line: Knowledge bases and retrieval
Contracts, currency and where the data sits
Invoices are in Australian or US dollars. The engagement crosses a border and a date line, so payment terms and delivery dates are written with the date offset spelled out.
The commercial part stays deliberately boring. Fixed acceptance criteria per increment, weekly shipping, and a written record of every decision. Nothing about working from Vancouver instead of Darwin changes what you are buying.
The five lines we sell
Same five lines everywhere, Darwin 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 Australia
More entries from the Australia 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.