The short answer
AWLabs is a custom software and AI development company based in Sydney that delivers projects remotely to organisations in every Australian capital, travelling for workshops when being in the room matters. Remote delivery works when there's a fixed update rhythm, a shared working window across time zones, and in person sessions at the moments that shape the project: strategy sessions, key design decisions and user testing.
Key takeaways
- Our team is in Sydney; we work remotely with organisations elsewhere in Australia and travel for workshops and testing.
- Queensland, Western Australia and the Northern Territory don't observe daylight saving, so time gaps with Sydney change between October and April.
- Perth is 2 hours behind Sydney in winter and 3 hours behind in summer, which still leaves 6 to 7 shared working hours a day.
- Privacy law differs by state: Queensland, the Northern Territory and Tasmania have public sector privacy laws, Western Australia passed the Privacy and Responsible Information Sharing Act 2024, and South Australia has no privacy Act of its own.
- Hyperscale cloud regions in Australia are in Sydney, Melbourne and, for Azure, Canberra; that's where data sits regardless of where users are.
Do you work with organisations outside Sydney?
Yes. Our team is based in Sydney and we deliver remotely to organisations in every Australian capital and regional centre, travelling for workshops when being in the room matters. We don’t have offices in other cities and we won’t pretend to. What we do have is a delivery model built for distance: a fixed update rhythm, written decisions, shared working hours, and time in person placed where it changes the outcome.
This page explains how that works in practice, including the parts that are genuinely harder across distance and how we handle them.
How do time zones and daylight saving affect a project?
Australia runs three standard time zones, and because Queensland, Western Australia and the Northern Territory don’t observe daylight saving, the gaps between cities change twice a year. New South Wales, Victoria, South Australia, Tasmania and the ACT move their clocks forward. Daylight saving started on Sunday 4 October 2026 and ends on Sunday 4 April 2027.
What 10am in Sydney looks like elsewhere:
| City | April to October (no daylight saving) | October to April (daylight saving) |
|---|---|---|
| Sydney, Melbourne, Canberra, Hobart | 10:00 | 10:00 |
| Brisbane | 10:00 | 9:00 |
| Adelaide | 9:30 | 9:30 |
| Darwin | 9:30 | 8:30 |
| Perth | 8:00 | 7:00 |
Shared working hours, assuming both sides work 9am to 6pm local time:
| City | Shared hours in winter | Shared hours in summer |
|---|---|---|
| Brisbane | 9 | 8 |
| Adelaide | 8.5 | 8.5 |
| Darwin | 8.5 | 7.5 |
| Perth | 7 | 6 |
The practical rule: schedule meetings with Perth and Darwin between late morning and mid afternoon Sydney time, and remember that a Brisbane client’s 5pm is Sydney’s 6pm for half the year. We put the time zone in every calendar invite and state times in both zones in writing.
What does the update rhythm look like?
Remote projects run on a fixed cadence so nobody has to wonder what’s happening. You get an update every Tuesday and Friday, Sydney time, with access to test the latest work. Sprint length is set for each build.
| When | What | Format |
|---|---|---|
| Tuesday | Progress, open questions and decisions needed, with access to test the latest work | Written update and test link |
| As needed | Working session on anything blocked, with the people who can decide | 30 to 60 minute video call |
| Friday | Progress, open questions and decisions needed, with access to test the latest work | Written update and test link |
| End of each stage | You review the stage and accept it | Video call |
Everything that’s decided gets written down in the same place. That habit matters more for remote delivery than any tool, because it means a stakeholder in Perth who missed a call can catch up in five minutes.
When do we travel to you?
We travel when a decision needs several people to see the same thing at the same time, or when we need to watch real users. These are the sessions that lose most over video:
- Strategy sessions with several stakeholders. Walking through the audit and the build scope with the business owner, subject matter experts and IT.
- Design sign-off for complex workflows. Where several teams have to agree how work flows between them.
- User testing. Sitting beside the people who’ll use the system, especially field or operational staff.
- Go-live support for operational systems. Being present when a system that runs the business switches over.
Everything else, including the build, code review, updates and most meetings, works well remotely. Travel is scoped and priced into your Schedule of Work so you know the cost before you sign.
What’s genuinely harder when your developer is interstate?
Three things get harder at a distance, and it’s better to plan for them than to pretend they don’t exist. If none of these can be managed, a developer in your own city may be the better choice, and that’s a reasonable decision.
- Informal context. A local team picks up how your business works over coffee and in corridors. Remotely, that context has to be gathered on purpose, which is why the Discovery Audit goes deep and why we interview the people who do the work, not only the managers.
- Access to physical sites. Warehouses, clinics, depots and job sites can’t be understood on a video call. If the software is used in the field, we plan at least one site visit into your Schedule of Work.
- Stakeholder attention. It’s easier to skip a video call than a meeting in your own boardroom. A fixed calendar of decision points, set up in week one, keeps the right people involved.
What doesn’t get harder is the engineering. Code review, testing, deployment and monitoring work the same whether the client is in Parramatta or Perth.
Does it matter where your data is hosted?
Where your users are doesn’t decide where your data lives; the cloud region does. At the time of writing, the Australian regions of the major clouds are:
- AWS: Sydney (
ap-southeast-2) and Melbourne (ap-southeast-4) - Microsoft Azure: Australia East (New South Wales), Australia Southeast (Victoria), Australia Central and Central 2 (Canberra)
- Google Cloud: Sydney (
australia-southeast1) and Melbourne (australia-southeast2)
A Perth or Brisbane system will usually run in one of these regions, with a second region for backups or failover. Latency within Australia is rarely a problem for business applications. Our data residency vs data sovereignty explainer covers why region choice matters and what it doesn’t solve.
How does privacy law change from state to state?
The Commonwealth Privacy Act 1988 covers most private businesses everywhere in Australia, but state and territory laws cover their own public sectors and, in some places, health information. Per the OAIC:
| Jurisdiction | State or territory privacy law position |
|---|---|
| NSW, Victoria, ACT | Public sector privacy laws, plus health privacy laws that private health providers must also follow |
| Queensland, Northern Territory, Tasmania | Privacy laws that apply only to their public sectors |
| Western Australia | The Privacy and Responsible Information Sharing Act 2024, passed for the WA public sector |
| South Australia | No privacy Act of its own; an administrative instruction covers the public sector |
For a private company this rarely changes the build. For a state agency or a health provider, it changes which principles the system is designed to and how data breaches are reported. The city pages for Melbourne, Brisbane and Canberra cover those states in detail.
How AWLabs delivers across Australia
We’re a Sydney team led by founder Andy Taleb, who has been building software professionally since 2019 and running All Webbed Up since 2021. AWLabs launched in mid 2026 as a new, separate company, a partnership with exceptional developers and founders. Every engagement starts with an NDA and our Discovery Audit, a fixed fee credited in full against the build. After two strategy sessions you receive a fixed price for an agreed scope. We work Sydney business hours, with the overlap windows above. You own what we build for you once it is paid for: you can see and test the code while we build, and the full repository and logins are handed over after the final payment. We can host your data in Australian cloud regions. If your data must stay in Australia, tell us before you sign and we write it into your Schedule of Work. If you’re comparing firms, our guides on how to choose a software development company and how to choose an AI development company set out the questions to ask. If you’re weighing a local team against offshore delivery, our onshore vs offshore guide is a fair comparison. See how we work or our custom app development service.
Frequently asked questions
Do you have offices outside Sydney?
No. Our only office is in Five Dock, Sydney. We don't list addresses or phone numbers in other cities because we don't have them. We travel to you for workshops and testing when it's worth it.
When is it worth flying someone in?
For strategy sessions where several stakeholders need to agree on scope or design, and for user testing with people who aren't comfortable on video calls. For routine demos and check-ins, video works well and saves you travel costs.
Who pays for travel?
Travel for agreed sessions on site is scoped and priced into your Schedule of Work up front, so there are no surprise invoices. If a project needs no travel, none is charged.
How do you handle Perth's time difference?
We schedule shared meetings in the middle of the day, when Perth mornings overlap Sydney afternoons, and keep asynchronous updates written so nothing depends on a live call. In summer that overlap is roughly 9am to 3pm Perth time.
What is a software development company?
A software development company designs, builds and maintains software for other organisations, as opposed to selling one packaged product. The work usually runs from discovery and design through engineering, testing and deployment to ongoing support. An AI development company does the same with AI models at the centre of the system, such as knowledge search, document processing or agents.
How do we choose the best software development company in Australia?
There isn't one best firm for every project, whatever the ranking lists say. Shortlist on fit: relevant experience, who actually writes the code, when IP is assigned to you and when you get the repository and logins, how they test, and how they price. Directory reviews help, but a paid scoping step, such as our Discovery Audit, tells you far more about how a firm works.
Is remote delivery slower?
Not if it's run properly. The build itself happens at a desk wherever the team is. Delays in remote projects usually come from unclear decisions, which is why we hold the sessions where big decisions get made in person.
Do you work with businesses in Perth, Adelaide, Darwin, Hobart and regional Australia?
Yes. We deliver remotely from Sydney to every Australian capital and to regional centres, and travel for workshops, site visits and user testing when being there changes the outcome. Hobart keeps Sydney time, Adelaide is 30 minutes behind all year, and Darwin and Perth run further behind. Even Perth in summer leaves about 6 shared working hours a day, so we book live sessions inside that window and keep every decision in writing.
How will we get progress updates if we're interstate?
Twice a week, every Tuesday and Friday, Sydney time. Each update is written, covers progress, open questions and the decisions we need from you, and comes with access to test the latest work. Video working sessions are booked whenever something is blocked, and you review and accept each stage on a call, so a stakeholder in another state can catch up in minutes rather than waiting for the next meeting.
Can our data be hosted in our own state?
Only if your state has a major cloud region. At the time of writing, AWS, Azure and Google Cloud run Australian regions in Sydney and Melbourne, and Azure also runs two in Canberra. A system for a Perth, Brisbane, Adelaide, Darwin or Hobart organisation usually sits in one of those regions, with a second region for backups. The data still stays in Australia, and latency is rarely a problem for business software.
This page is general information about Australian law and regulation, current at the date shown. It is not legal advice. Get advice from a qualified lawyer about your circumstances.
Sources
- Daylight saving in NSW, NSW Government
- State and territory privacy legislation, Office of the Australian Information Commissioner
- AWS Regions and Availability Zones, Amazon Web Services
- Azure geographies, Microsoft
- Google Cloud locations, Google Cloud