Pricing in AUD

What this actually costs.

We quote a fixed price in AUD after a free discovery call, so the ranges below are honest ballparks, not the final number. They are ranges because the real figure depends on your systems, your volume and how much of the work needs judgment. Every package sells a defined outcome, not an amount of our time.

Automation Sprint

One workflow, live, in two weeks.

$6,000–$9,0002 weeks
You get

One automated workflow running in production at the end of week two. Not a prototype, not a plan.

Best for. A single high-volume, well-understood process. Invoice capture, CRM updates, a document extraction step, one report that someone builds by hand every week.

What is included
  • A short discovery call to pick the one workflow worth automating
  • The workflow built, deployed and running on your own infrastructure
  • Error handling and alerting so you know when it needs a look
  • A runbook and a handover call so your team can operate it
What is not
  • A platform, a dashboard, or a second workflow
  • Ongoing changes after handover (that is Care)
  • Deep integration work across three or more systems (that is Build)
Scope a Sprint

Ongoing Care

We keep it running and evolving.

$2,000–$6,000 /monthMonthly, cancel anytime
You get

Monitoring, maintenance and a set number of change requests each month.

Best for. The months just after a Build, when the process is still settling and you would rather we caught the problems than your customers did.

What is included
  • Monitoring and alerting on the systems we built
  • Maintenance when a model, an API or a dependency changes underneath you
  • A set number of change requests each month, agreed up front
  • A direct line to the engineers who built it, not a ticket queue
What is not
  • A lock-in contract (you cancel any month you like)
  • New systems from scratch (that is a Sprint or a Build)
  • Third-party costs, which stay on your own accounts

You own the code and the infrastructure from day one. If you cancel Care, the system keeps running, because it lives on your accounts, not ours. In practice most clients take Care for a few months while the process settles, then stop. That is the outcome we are aiming for.

Talk About Care

How we arrive at a number

The discovery call is where the number comes from. We map the workflow you want automated, watch how it actually runs rather than how the process document says it runs, and count the things that make it harder: how many systems it touches, how much of it needs judgment, how bad a wrong answer is, and how clean the data underneath is.

Then we quote a fixed price in AUD for a defined outcome. Fixed scope, agreed before we build. No hourly billing that expands, no surprise invoices. If the work turns out harder than we thought, that is on us, because we set the price.

What we will tell you not to buy

A large part of the first conversation is finding out what you should not spend money on. If a workflow is fully deterministic, an AI agent is the wrong tool: slower, more expensive and less predictable than a plain integration. If a platform already does the job, we will point you at the platform rather than build you a worse one.

We would rather quote a smaller Sprint that clearly pays for itself than a Build you do not need yet. Starting with the highest-volume workflow instead of the hardest one is usually the cheaper path to something that works.

What is not in these numbers

Third-party costs sit outside the price and on your own accounts, at cost, never marked up. That means model API usage, cloud hosting, and any SaaS licences the system needs. They are billed in your name so you can see exactly what they cost and keep them if you ever stop working with us. We do not resell infrastructure, and we do not hold your system on our accounts.

What people ask us about price.

Why ranges instead of a single fixed price?

Because we quote the real number after a discovery call, not before. The range tells you the ballpark honestly. The final figure is fixed scope in AUD, agreed before we build. A firm price quoted before anyone has seen your systems is a guess dressed up as certainty, and the client always pays for that guess later.

What happens if a Sprint runs over?

That is our problem, not your invoice. The Sprint is a fixed price for a defined outcome: one workflow live in production. If it takes us longer than two weeks to get there, we finish it. Selling you a second sprint to finish the first one is exactly the hourly-billing trap we built this pricing to avoid.

Can we start with a Sprint and move to a Build later?

Yes, and it is often the sensible order. A Sprint proves the highest-volume workflow is worth automating and shows you how we work, for a small commitment. If it earns its place, a Build extends it into the full system. You are never forced to size the whole thing up front.

Is Ongoing Care required?

No. Care is optional every month and you cancel whenever you like. You own the code and the infrastructure, so the system keeps running without us. Most clients take Care for a few months after a Build while things settle, then stop. We would rather you came back for the next project than stayed on a retainer you no longer need.

Do you charge for the audit?

No. The first call is free and runs about thirty minutes. We map the workflow, tell you honestly whether it is worth automating, and quote it in AUD. Sometimes the honest answer is that you should not automate anything yet, and we will say so on that call rather than sell you a project.

What about third-party costs like model APIs, hosting and SaaS licences?

Those are billed to your own accounts at cost, never marked up. Model API usage, cloud hosting and any SaaS licences sit on your billing, in your name, so you can see exactly what they cost and you keep them if you ever stop working with us. We do not resell infrastructure.

Get a real number in AUD.

Book a free automation audit. We map the workflow, tell you honestly whether it is worth automating, and quote fixed scope in AUD.

  • Free 30-min audit
  • Fixed scope in AUD
  • Week-2 working build
Week 1Process mappingWe watch how the work actually happens, not how the doc says it does.
Week 2First working buildA live automation handling real data. Not a demo, not slides.
Week 6–8In productionError handling, alerting, runbooks. Handed over, documented, yours.