Buying software in Perth means deciding how much distance you can absorb
This is one of the most isolated business communities of its size anywhere, and it changes the shape of a software purchase. The pool of local development firms is genuinely small relative to the size of the economy, most of the country's technology supply sits several hours ahead by clock and several hours away by plane, and offshore suppliers sit in the other direction.
So the first decision is not which firm. It is how much of the engagement you are willing to run without anyone in the room. Some projects tolerate that easily. Others, particularly those that require watching people work, negotiating between departments, or extracting knowledge from someone who has been doing a job for twenty years and has never written any of it down, do not.
What proximity actually buys, and what it does not
Being able to meet in person is worth most at three moments: the early sessions where you agree what the software must do, the point where two internal groups disagree about a process, and the rollout, where someone credible standing next to a frustrated user prevents the whole thing being abandoned.
It is worth much less during construction. Day-to-day engineering is already a written, asynchronous activity even when everyone shares a building. A reasonable compromise is a software supplier who will travel for the moments that matter and work remotely for the rest, with the travel written into the proposal rather than argued about later. Ask for that explicitly, including who pays and how many visits are assumed.
Do the time-zone arithmetic before you sign
An hours-ahead supplier and an hours-behind supplier produce completely different working days, and buyers rarely calculate it until the first week. Work out how many hours of genuine overlap you will have, then ask what happens inside that window. Overlap consumed entirely by a status meeting is wasted; overlap used for decisions and pairing is valuable.
Three practical rules help. Put the daily meeting at the start of the overlap, not the end, so questions raised have a chance of being answered the same day. Require that any question blocking work is written and visible rather than held until the call. And name one person on your side who can answer within the working day, because in a distributed arrangement decision latency, not engineering speed, is usually what sets the timeline.
You are competing with the resources sector for the same people
The local labour market has a characteristic that affects every quote you receive. Mining, energy and the engineering services around them pay well for technical staff, and they absorb developers, data specialists and integration engineers who might otherwise work for a software firm. That keeps local capacity tight and rates firm, and it means a small supplier can lose a key person to a resources client quickly.
Ask candidates how many permanent technical staff they employ, how long the proposed team members have been there, and what their plan is if someone leaves mid-project. Then make sure the answer is structural rather than reassuring: shared knowledge of each subsystem, code review by a second person, and documentation that lives with the code.
Shape the work so distance cannot hide problems
Long phases with a big reveal at the end are risky anywhere and dangerous when nobody can walk past a screen. Insist on small increments that produce something you can open and use, on a fixed rhythm, in an environment you control. Two weeks is a common cadence and the exact number matters less than the fact that it never slips.
Ask for access to the work in progress rather than reports about it. Read access to the repository, sight of the issue tracker, and an environment you can log into remove the need to trust a summary. A supplier who resists this is telling you something. A supplier who offers it before you ask has been through a difficult remote project already.
Verify what you cannot see for yourself
When you will not be visiting an office, ordinary due diligence has to do more work. Confirm the legal entity and how long it has traded. Ask for two references and actually call them, choosing one project that is older rather than the freshest success. Ask where production will be hosted and in whose account. Ask who holds administrative access and how it is revoked.
Also ask a question that sounds rude and is not: how many clients does the proposed lead currently carry? A named technical lead spread across four engagements is the single most common reason remote projects drift, and the answer is rarely volunteered.
Write the handover obligations in from day one
Distance makes an untidy ending worse, because you cannot simply turn up and collect things. Agree that the repository, the cloud accounts, the domains and the certificates are registered to your organisation from the beginning. Agree that deployment is documented well enough for a competent outsider to rebuild the environment. Agree a defined assistance period if you transition to another supplier, priced in advance so that leverage does not decide the fee.
None of this signals distrust. It signals that you have run a distributed engagement before, and suppliers read it that way.
Comparing software companies in Perth
Build a shortlist that deliberately mixes one local software firm with one or two from further afield, give them identical briefs, and compare not just the estimate but the working arrangement each proposes. The travel assumptions, the meeting rhythm, the named people and their availability are the parts that will determine whether this feels manageable in month four.
You can review verified software companies in Perth alongside the wider directory of software development firms, and request matched proposals through our offer request form. Where the brief extends into a mobile client for field staff, a public-facing platform or visibility in local search, see mobile app companies, web development companies and SEO agencies covering the same area.