Victoria (VIC), Australia
AI development for Melbourne teams, handed over in writing
Magic Ship is an AI development agency in Vancouver, British Columbia, with no presence in Melbourne and no shared working hours with it. What that buys you is a full day of build time delivered as a written handoff, waiting when you sit down.
- base
- vancouver, bc, canada (UTC-08:00)
- market
- Melbourne, Australia
- your clock
- UTC+10:00 (Australia/Melbourne)
- overlap
- none on the same date, written handoff instead
- presence
- remote only, no office in Melbourne
No shared working day, so the loop is written
Melbourne is 18 hours ahead of Vancouver. When we start at 09:00 it is 03:00 on the next day for you, and when we stop at 17:00 it is 11: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.
- 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 11:00, 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:00 in Vancouver is 09:00 in Melbourne 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 Melbourne buyers usually bring us
The record for Melbourne lists two industries. Here is the part of each one that turns into an engagement, and the service line it lands under.
higher education
Faculty and staff need the failure modes as much as the workflows, so sessions run on their own courses and repos and end with a written practice they keep.
The written notes stay with the team, and they are written to be edited rather than filed.
Closest service line: Training and enablement
health care
Clinical and administrative documents demand citation and access control at retrieval time, not a disclaimer at the bottom of the answer.
Most retrieval failures are ingestion failures, so the early weeks go into parsing and chunking rather than into rewording a prompt.
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 Melbourne changes what you are buying.
The five lines we sell
Same five lines everywhere, Melbourne 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
Where else the same work happens in Australia, with the numbers redone per market.
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.