On November 10, 2026, Qantas announced a multi-year partnership with Accenture to modernise its back-end systems, processes and data. The airline says it runs on more than 1,000 legacy applications "that were never designed to work together." Some of the services its corporate functions provide will move to Accenture, "delivered mostly by its teams in India and some in Australia, and in time be transformed further with automation and AI." Around 850 roles are expected to be affected over the coming years, with the first wave of changes in place by mid-2027. The Guardian reported that the first cuts target finance, procurement, human resources and marketing at an airline with about 32,000 employees.
CEO Vanessa Hudson called the pace of change "unprecedented" and said "standing still is not an option for us." The Sydney Morning Herald quoted her on why Qantas chose a partner: "through a partner we can access the data and AI skills that every industry in the world is competing for, because we cannot hire at the pace this work needs." The airline described the model as processes moving to India to be analysed and simplified, with automation added, before they come back into Australian operations as an AI function. The Australian Services Union responded that "the cost of technology change should not be borne by the workers who have kept the airline running for years."
Those are the facts as reported. Everything below is my opinion.
My position: bringing in a partner because you cannot hire AI and data skills fast enough is a smart move, but outsourcing a process you do not fully understand only moves the mess somewhere else. Keep ownership of the redesign and keep the people who know why the work is done the way it is, or you end up renting back your own business.
The capacity argument is the honest part
The most honest line in the whole announcement is "we cannot hire at the pace this work needs." That is true for almost every company trying to modernise right now. Data engineers, platform architects and people who have actually shipped AI into production are scarce, and the companies that need them most are usually the ones with the oldest systems.
I run a remote software consultancy, so I see this from the partner side every week. Clients come to us because they need skills they cannot recruit in time. Using a partner for capacity is not a failure. Pretending you can build a full data and AI team from scratch inside a year usually is.
Where these deals go wrong
The risk is not that the work moves to India. Where work gets done has mattered less every year, and good teams deliver across time zones all the time. The risk is that the process moves before anyone has written down why it works the way it does.
A finance or procurement workflow that has run for twenty years carries exceptions, workarounds and approvals that nobody documented. They live in the heads of the people doing the job. When those people leave in the same wave as the process, the partner inherits the steps without the reasons. Add automation to a process nobody fully understands and you get the same mistakes, only faster.
Qantas says the work will come back as an AI function. My question is: back to whom? If the team receiving it has nobody left who knew the old version, the company now depends on its partner to explain its own operations.
What I would do instead
Name an owner for every process before any role moves. That person stays, signs off on the redesign and is accountable for the result.
Capture the exceptions first. Spend the first weeks recording the edge cases, the manual fixes and the approvals that only exist by habit.
Measure outcomes, not transferred headcount. Cycle time, error rates, cost per transaction and customer impact tell you whether the redesign worked. The number of roles moved tells you nothing.
Pair your people with the partner's specialists. Knowledge should flow both ways, so the skill comes back with the process instead of staying with the vendor.
Be honest early. People who hear about changes through the press stop sharing what they know, and that knowledge is exactly what the project needs.
A fair counterpoint
To be fair, Qantas says it remains a net employer, with more than 4,400 new operational roles created since 2023, and it has committed to consulting staff and unions and to redeployment where possible. It is also dealing with high fuel costs, so part of this is ordinary cost pressure. A partner with tens of thousands of specialists can genuinely move faster than an internal hiring plan. My point is only about the order of operations: understand and own the work, then decide who runs it and where.
The payoff
Earlier in my career, as a partner, I helped grow a software consulting firm from about $6M to $60M in under three years. The clients who got the most value from us always kept a strong owner on their side of the table, someone who knew the business well enough to challenge our work. Through AI Rescue & Technology Consulting, TDZ Pro provides developers, DevOps, QA, and PMs vetted over years of delivery, on a top-1% talent bench, working alongside your team so the knowledge stays with you.
Want a partner that adds AI capacity while your team keeps ownership? Visit tdzpro.com.
What do you think? Is outsourcing an AI transformation the fastest way to modernise, or the fastest way to lose control of your own processes? I would like to hear your view in the comments.
Top comments (0)