Australia-specific AI considerations for operators
What's different about deploying AI in an Australian business — privacy, data residency, talent, regulation.
Most AI tooling is built in the US for US customers. If you run an Australian business, four things are different and worth knowing about.
1. Data residency
By default, most AI providers will route your data to the US. For most B2B services that's fine. For health, finance, education, and government work, it's not. You need explicit Australian or in-region residency, in writing. AWS Sydney, Azure Australia East, and Google Sydney all support most of the major models now. Use them.
2. Privacy Act + APPs
The Australian Privacy Principles are stricter than US norms in two areas: collection notices (you must tell people what you're collecting and why, even if it's an AI) and consent for sensitive information (health, financial, biometric). Build the consent flow before you turn the system on, not after.
3. Talent
Senior AI builders in Australia are scarce and expensive. Most of the genuinely good ones are working remote for US companies on US salaries. If you're hiring in-house, expect $200k–$350k for a builder with real production experience. Most $1M–$50M businesses can't justify that — agency or contractor is usually the right call until you're past $20M.
4. Regulation
Australia is moving slower than the EU on AI regulation but faster than the US. The voluntary AI Safety Standard (Sept 2024) is a good baseline. Health and finance have additional draft rules incoming. None of this is paralysing if you build to the standard now — and we do.
Build to the AI Safety Standard from day one. It's coming for everyone eventually.