What does AI automation actually cost in Australia?

I spent part of July 2026 reading the pricing page of every automation agency in Queensland I could find, which took considerably less time than you’d expect, because almost none of them publish one. What they publish instead is a calendar link, and the calendar link has two explanations, one of which the industry would prefer you didn’t hear about.

The legitimate explanation is that the same sentence, “we want to automate our invoicing”, describes an $800 job at one business and a $16,000 job at the business next door, and the variance between them has almost nothing to do with invoicing. Quoting that blind isn’t pricing, it’s guessing, and a guess that comes in low is materially worse for you than no number at all, because you will make plans around it.

The less legitimate explanation is that a number on a website is a number you can be held to.

So here is what AI automation actually costs in Australia, as honestly as we can put it, short version first, because most people reading this are doing it in between two other obligations.

The short version

• The single biggest determinant of your price is whether the software you already run has a good API. An API is a door in a piece of software that other software is allowed to use, and when the door is there and it’s wide, connecting things is quick, safe work. When it isn’t, somebody has to build a way in, and that is the point where hundreds turn into thousands.
• “It has an API” is not the same claim as “it has the API you need.” Most mainstream business software has one now, and what varies enormously is how much of the product the API can actually reach.
• The genuinely expensive case is usually not old software. It’s a portal. Government systems, insurer claiming systems, anything constructed on the assumption that a human will log in and click. Sometimes an API exists and you must apply for permission to be allowed near it.
• AI has cut the cost of building. It has not cut the cost of understanding. There are two good studies pointing in opposite directions, both are true, and the gap between them is approximately our entire job. The evidence is presented below.
• What the Australian market publishes, as at July 2026: around $250 an hour where anyone quotes hourly, $1,500 for a fixed audit, project work from $5,000 up past $50,000, and retainers between $1,500 and $2,000 a month. Most agencies publish no figures whatsoever.
• Ours starts lower than the published field, and every part is a known number. A Blueprint from $380, a fixed build quoted from it (simple jobs usually $1,500 to $3,000), then keeping it alive from $190 a month with no minimum term. See how that compares with typical automation agency pricing.
• The thing that quietly doubles a quote is exceptions, not volume. A process carrying four “except when” rules costs far more than a process carrying none, and the exceptions live in your staff’s heads rather than in your software.
• The ongoing amount is not a subscription for nothing. “Why does everything have to be SAAS these days? Can’t I pay you once to design the program and actually purchase it from you?” asked an owner on r/smallbusiness, and it is the right question. Where the answer is yes, we sell exactly that: a build you own outright. The monthly, where you want one, buys a person noticing failures before you do, and being the name on the hook when something breaks.

That’s the lot. Everything below is the same argument with the evidence attached.

What Australian automation agencies actually charge

Almost nobody publishes, which is the first useful fact to have. When we went through the Queensland and national field in July 2026, most of the market was quote-only behind a free discovery call, and exactly four firms had real figures on their own live pages, and the four deserve reading closely, because together they describe the shape of the market:

• About $250 an hour for complex or custom integration work, from In Cahoots Co, who note it can vary; they were the only openly hourly pricer we found.
• $5,000 for a single focused workflow, past $50,000 for a full suite, and retainers from $1,500 a month, from Advancer, the most transparent pricer in the state.
• From $2,000 a month, from Spruik.
• $1,500 for a fixed audit, credited toward a build, with builds typically $10,000 and up, from Growthsmith, who sell to larger businesses than the ones we write for, which is why their floor sits where it does.

All four figures are self-reported, on live pages we read on 15 July 2026, and pricing pages change, so treat them as a snapshot rather than a quotation. The shape holds regardless of the exact numbers: if you run a fourteen-person business, most of the published market starts above you.

The thing that decides your price

Software talks to other software through an API, and an API is a door. It has a lock on it, and it has a list, and the list says what you are allowed to do once you are through. When both pieces of software have a good door, the integration is a substantially known quantity, and a competent person connects them in an afternoon.

When one of them doesn’t, somebody has to build a way in, which means watching how a human performs the task and then writing something that performs the same clicking, reliably, at three in the morning, without falling over when the vendor moves a button in September. It works. It costs multiples of the first case, and it requires more looking after for the rest of its operational life.

That is most of the variance in automation pricing. Not the cleverness of what you asked for. The doors. Owners keep discovering this from the wrong side: one on r/smallbusiness collected quotes above $10,000 to connect WooCommerce to Salesforce, then did the job himself in a day with Zapier, because both products have good doors and nobody quoting him said so.

A good API · hours Job software Xero job #204 job #205 job #206 connected · it just runs

No API · weeks provider portal Log in Session expired script

The assumption to check first

The instinct is that new software has APIs and older or simpler software doesn’t, and the instinct is reasonable and mostly wrong. Take WordPress, the example everybody reaches for. It has had a REST API built into its core since version 4.7, which shipped in December 2016, with nothing to install and no plugin required, as its own developer handbook sets out. We half assumed the opposite ourselves until we went and looked, which is the kind of admission you should want from anyone who quotes you.

So the real question is not whether your software has an API. It is how far into the product the API reaches.

Two store platforms, both with APIs, very different bills

Squarespace and Shopify both sell you a hosted shop, both have real APIs, and the price of the identical request still differs, which makes them the cleanest comparison available.

Squarespace publishes nine Commerce APIs: analytics, contacts, discounts, inventory, orders, products, profiles, transactions and webhook subscriptions. For a real set of jobs that is entirely enough, but the list is commerce-shaped. You cannot create or update pages or blog posts through it, its webhook coverage is narrower than the alternative, which means some changes must be polled for on a timer rather than arriving the moment they happen, and the Profiles API is in maintenance mode.

Shopify describes its Admin API as letting you build things that extend the Shopify admin itself, which is a different species of promise from a fixed list of endpoints.

The practical version is this: if what you want is the simple case, “when an order comes in, do this”, both platforms are fine and the price is similar. If what you want touches content, or needs to know the instant something changed rather than within fifteen minutes, one is a morning’s work and the other becomes a conversation about workarounds. Same request, same category of software, different number at the bottom of the quote.

When you ask us to price something, the question we are silently asking is not “does it have an API”. It is “does the API go where this job needs to go”.

The expensive case: portals

The genuinely costly work is rarely old software. It is portals: government systems, insurer claiming, compliance lodgement, anything designed around the assumption that a person will log in and click.

The NDIS is the cleanest Australian example, and it is more nuanced than “no API”. The scheme’s own provider guidance describes two routes into the NDIA systems. You can integrate directly, which begins with contacting the Digital Partnership Office before you even apply, or you can integrate indirectly through a software developer or aggregator who is already an approved digital partner. Everybody else uploads a CSV or works the portal by hand.

So the API exists and you cannot simply go and get a key for it, which is a third category of expensive, and the category that surprises people. The cost isn’t engineering. It is eligibility, approvals and waiting.

If your business runs on a portal like that, be sceptical of anyone who quotes you quickly.

What AI changed, and what it didn’t

This is the loudest part of the industry’s current pitch, so it deserves actual evidence, and the two best studies available disagree with each other, which is the most useful thing about them.

In a controlled experiment published in 2023, 95 developers recruited on Upwork were randomly split and asked to write an HTTP server in JavaScript from scratch, as fast as they could, and the group with an AI assistant finished 55.8 percent faster. Worth knowing that the authors work for Microsoft and GitHub, who sell the tool being tested. Worth knowing more that the task was a small new program written from nothing, which is close to the best case these tools have.

Then in 2025 the research nonprofit METR ran a randomised controlled trial with 16 experienced developers across 246 real tasks on large open-source projects most of them had worked on for years, and with AI tools available they were 19 percent slower. The same developers, asked afterwards, estimated the AI had made them 20 percent faster. METR now labels the result historical, because it measured the tools of early 2025 and the tools move. The caveat is theirs, and we pass it on.

Put the two studies side by side and the contradiction resolves. AI is fast at writing something new that nobody has to already understand, and it is not reliably fast inside a large existing system that a person spent years learning.

A small new program on form.submit validate("email") return ok(200) 55.8% faster

A codebase with history if legacy ? ? 19% slower

An automation build is both cases at once. The connector code, the transformations, the plumbing: that is the small-new-program case, it genuinely is cheaper than it was three years ago, and we charge less than we would have in 2023 for precisely that reason. Understanding your business is the hard case, because nobody has documented it, the person who knows the exception is on leave, and the org chart is not how the work happens. No model shortens that. The information isn’t written down anywhere for a model to read.

So AI has taken real money off the build and almost nothing off the understanding, and anyone telling you AI made the whole thing cheap is quoting the first half.

What you are actually paying for

Which brings us to the unglamorous part, where the majority of the risk lives. Before anything gets built, somebody has to establish the boring facts:

• How the business actually runs, as opposed to how it gets described in a meeting.
• Who is involved, and which of them holds a step in their head rather than in a system.
• What software you are on, and which of it is load-bearing.
• Whether a system can be replaced, or whether we build around it because too much depends on it not moving.
• If something is genuinely past it, what the plan is for getting off it without breaking a pay fortnight. That is its own project with its own price, not something to smuggle into an automation quote.

Every expensive automation failure we have read about, and we have read a considerable number of them, comes from skipping that work. The one that stays with us worked exactly as sold and nearly took the business with it.

This is why the Blueprint is charged for separately and identified as such on the invoice. If it were free it would be a sales call, and it would be rushed, because free things get rushed.

How to make it cheaper

Genuinely, not as a sales move:

• Run mainstream software. Xero, ServiceM8, Cliniko, monday.com, Asana, Shopify. Popular means documented, and documented means hours instead of days.
• Cut the exceptions before you automate. Every “except when it’s a commercial job” doubles a branch, some of those rules are load-bearing, and several are habits nobody has questioned since 2019. Deleting one is free.
• Be willing to change the process slightly. The cheapest automation is often 90 percent of what you asked for, arranged the way the software already wants to work.
• Start with the one thing that hurts, not a suite. The first automation pays for the second.
• Ask whether it’s a package. If you are on common software wanting a common thing, most of it may already exist, and you should not pay custom rates for it.
• Turn on what you already own. Xero has invoice reminders, and your job software probably has templates you’ve never opened. We’ll tell you this before we quote you, and we do it more often than is commercially clever.

What we do with all of this

We work with your budget, and we mean that in a specific way rather than a warm one. The price has three parts, and you see each one before it’s spent: a Blueprint from $380, a fixed build quoted from that Blueprint and approved before work starts, then keeping it alive from $190 a month with no minimum term. If the build is too much in one go, it can be spread over 6 or 12 months. And if you’d rather own the thing outright and run it yourself, everything is documented so that owning it is actually possible. We do all of it from Melbourne, for businesses across Australia, and distance changes none of the arithmetic above.

Whether your job counts as simple or complex isn’t something a pricing page can settle. It comes out of one conversation about what you are running, how large the team is, and what is currently the worst part of your week. The full numbers are set out here, and yours goes in writing after we talk.

Bring us your most annoying task. If a $30 app already does it, that is the honest answer you will get, and it will cost you nothing.