South Australia (SA), Australia
AI development for Adelaide teams, handed over in writing
Magic Ship is one shop in Vancouver, British Columbia. Between Vancouver and Adelaide there is no same-day overlap to sell you, so the engagement is built the other way around: everything that matters is written down, and the day you start is the day after ours finished.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Adelaide, Australia
- your clock
- UTC+09:30 (Australia/Adelaide)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Adelaide
No shared working day, so the loop is written
Adelaide 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.
Removing the shared hour removes the interruptions with it. A full Vancouver day of uninterrupted build time, handed over in writing, tends to move a project further than a day punctuated by four calls.
- 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 Adelaide 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 Adelaide buyers usually bring us
The record for Adelaide lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
defense shipbuilding
Drawings, change orders and inspection records span decades of hulls, and the retrieval design has to keep one hull from answering for another.
Recall gets measured before anybody comments on the wording, because a fluent answer drawn from the wrong passage is the worst outcome on offer.
Closest service line: Knowledge bases and retrieval
wine
Vintage records, vineyard data and distribution history are small, messy datasets where a tool layer beats a model every time.
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
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 Adelaide changes what you are buying.
The five lines we sell
Same five lines everywhere, Adelaide 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
If you are comparing markets, these are the other Australia entries in the record set.
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.