Australian businesses outsource to India for good reasons: access to experienced engineers, sensible costs and a working day that overlaps reasonably well with the east coast. The projects that go smoothly are the ones where a few basics are agreed before work starts.
We have built and supported platforms for Australian clients, including auction websites handling tens of thousands of lots and a specialist wine and whisky auction house. The points below come from that work.
Working hours and overlap
India is four and a half to five and a half hours behind the Australian east coast, depending on daylight saving. In practice that gives a comfortable window from late morning to early evening in Sydney or Melbourne. Perth has an even larger overlap. Agree the actual meeting window with the people who will work on your project, and remember it shifts slightly when daylight saving starts and ends.
Write things down
Clear written requirements save more time than extra calls. Agree deliverables, exclusions and acceptance criteria for each milestone, and keep a short record of decisions. This lets both sides check progress against the same scope and avoids arguments later.
- A written scope with what is included and what is not
- Acceptance criteria for each milestone
- A shared log of decisions and open questions
Contracts, IP and ownership
Make sure the agreement states clearly that you own the code and other work produced. Keep repositories, domains, hosting and app store accounts in your business name, and give the development team access through their own accounts.
Privacy and security
If the project involves personal information, discuss how it will be handled under the Australian Privacy Principles. Agree who can access production systems, how credentials are shared and what happens to data and access when the engagement ends.
Releases and support
Plan for life after launch from the start. Decide who approves releases, how urgent issues are reported and what response times you need. A small support retainer is often the simplest way to keep a site or app secure and up to date.
Starting well
A short discovery phase or a small first project is a good way to test the relationship. It shows how the team estimates, communicates and handles feedback before you commit to a larger build.
