A developer in Melbourne and a developer offshore can both build software that works. What changes between them is everything around the code: how many working hours you share, who you actually talk to, where your customers' details are kept, and who looks after the software once it is running.
So the choice is less about the code than about how the job will run for the next few years. Ask both kinds of developer the same questions, and the answers usually make the choice for you.
Why do businesses look offshore?
Usually for the rate. An hourly rate is easy to compare, and a lower one is a fair reason to look.
It is one number in a longer sum, though. Custom software is mostly understanding the job, connecting it to your tools and keeping it working after it ships. The code is the smallest part. A lower rate on the smallest part can hold up across the rest, or it can be eaten by it. You find out by asking about the rest.
What changes when you share a working day?
How fast a question gets answered. Building software for a business throws up dozens of small questions. What happens when a customer pays half? Which of three phone numbers is the right one? Does a cancelled booking still count towards the month?
Each one needs an answer from someone who knows the business.
When the developer's day overlaps yours, a question asked at 10 am is answered by 11. When it does not, the question waits for the next morning, and so does the work behind it. Across a whole build, those overnight waits add up to weeks.
It shows up again after launch. If the booking page stops taking payments on a Saturday morning, it matters who is awake.
Who will you actually talk to?
Ask this of any developer, local or not. In some firms a salesperson runs the first meeting, someone else works out what you need, and a third person writes the code without ever hearing you describe the job.
Every handover between them is a place where a detail can drop.
The question to ask is simple: will the person who understands my business be the one who designs the software, and can I talk to them directly?
Does it matter whether they can see the work?
For some jobs, a lot. Much of what makes software fit is noticed in the room: the sticky note on the reception screen, the second spreadsheet someone keeps, the step a team leader does from memory. A developer who watches the job being done once tends to find the exception nobody thought to mention.
A video call is enough for plenty of jobs. For work that happens at a front desk, on a gym floor or in a club's office, being in the same city makes it easy to go and look.
Where will your data be kept?
Ask where the software stores your customers' details, which country those servers are in, and who on the developer's side can open them. Then ask your accountant or adviser whether any of that changes your own obligations.
This applies to a Melbourne developer just as much. A local firm can still keep everything overseas. What matters is that you know, and that it is written down.
Who looks after it once it is live?
This question separates suppliers more than location does. Software needs looking after for as long as it runs. Things move. A supplier changes their app, prices go up, a new starter needs access, and the way you work changes.
Ask who watches the software after launch, how they find out when something stops, and how fast they respond. A developer who builds and then leaves hands you something nobody on your team can change. Where they are makes no difference to that.
How do we work?
We are in Melbourne, and we build custom software for one business at a time. Every job starts with one call about how the business runs and where the hours go. Each system is tested on real work before anyone relies on it, and watched after it ships.
When the way the business works changes, the software changes with it.
We work this way because the build is the start. Most of what software is worth to a business arrives in the years it runs, and someone has to be there for those years.
Where does the choice go wrong?
- Comparing rates without comparing scope. One quote includes connecting your tools and bringing your records across. The other leaves both out. Line them up item by item before you compare totals.
- Choosing on the first meeting. The person in the first meeting may never touch your software. Ask to meet whoever will.
- No plan for after launch. If the answer to "who fixes it at the weekend?" is vague, the quote is not the full price.
- Assuming local means your data stays here. Ask every developer where it lives, wherever their office is.
In short
- A good developer can be anywhere. The work around the code is what changes.
- Shared working hours turn overnight waits into answers within the hour.
- Talk directly to the person who will design and build it.
- Ask every developer where your data is kept, and get the answer in writing.
- Who looks after the software after launch matters more than where it was built.
One step for this week
Write down five questions your team answered last week that needed someone who knows the business: an exception, a judgement call, a "we usually do it this way". Then ask each developer you are considering how they would get answers to questions like those during a build, and how quickly.
Their answer tells you how the build will feel. If you would like a developer in Melbourne for it, custom software built around how your business already runs is what we build.



