Choosing a software partner in Sydney: questions to ask

Choosing who builds or looks after your software is one of the more important decisions a growing business makes. A polished proposal does not tell you much. How a partner answers some practical questions tells you a great deal. Here are the ones worth asking.

1. Who will actually do the work?

Ask who will be on your project, what their experience is, and whether the people you meet in the sales conversation are the people you will work with. Find out who is accountable for the outcome and how you reach them.

2. Where are they, and when are they available?

Time zone and business hours matter more than people expect. If questions regularly wait a day for an answer, projects slow down. A team that works in your time zone and is easy to reach means problems are solved the same day. If any part of the work is done elsewhere, ask for it to be explained clearly.

3. How do they handle changes to scope?

Requirements always change once people see real software. Ask how change is requested, estimated and approved, and how they keep the budget visible. A good partner has a calm, simple process for this and does not hide behind the contract.

4. How will you know how the project is going?

Ask what you will see and how often: regular demonstrations of working software, a short written update, clear risks and decisions. If the answer is “we will let you know when it is done”, be cautious.

5. Can they show relevant work, and will they let you talk to customers?

Look for examples close to your situation. Ask for references and speak to them. Ask what went wrong on a past project and how it was handled. Honest answers are a good sign.

6. How do they think about security and privacy?

Ask how they protect your data, how access is controlled, and where information is stored. If your project involves personal information, ask how they handle it in line with Australian privacy requirements. You should hear specifics, not slogans.

7. Who owns the code and the data?

You should own what you pay for, including the code and your data, and be able to take it elsewhere. Ask about documentation and what the handover looks like if you ever change provider.

8. What happens after launch?

Software needs ongoing care. Ask who fixes bugs, applies updates and handles problems, how quickly, and what it costs. Choosing a partner who can also support the system after launch avoids a gap at the moment it matters most.

9. How do they price the work?

Fixed price, time and materials, or a mix: each has trade-offs. Ask them to explain which suits your project and why, and what is and is not included. Be wary of a price that is far below everyone else’s, because the difference tends to reappear later.

10. How do they say no?

A good partner will tell you when something is a bad idea, when you do not need to build it, or when a different approach would cost less. If everything you suggest is greeted with “yes, no problem”, ask how they handle disagreement.

Warning signs

• Vague answers about who does the work.
• No visible progress for weeks at a time.
• Pressure to sign quickly.
• Unwillingness to share references or explain their process.
• A contract that makes it hard to get your code or data back.

What good looks like

A partner who is easy to reach, explains things plainly, shows working software early, is honest about trade-offs, and is still around to look after what they built.

If you are comparing options, we are glad to talk through what we would do on your project and where we would be the wrong fit. We are a Sydney-based, Australian-operated team and believe in being clear from the first conversation.