What automation costs, what it saves and who owns it
An automation is worth it when it saves more than it costs to own, gives your team better work and has a named owner who keeps it under control.
Renzo Demartini, Chartered Accountant and finance executive · · 5 min read Drafted with AI, reviewed and spot-checked by me.
Exhibit 1What does an A$12K automation cost to own in year 1?
The build quoteCost to own, year 1
Build priceA$12KA$12K
Cost to own, year 1A$12KA$27K
Cautious savingA$20KA$20K
The quote is A$12K against A$20K of cautious saving. It looks like an easy yes.
Add your team’s time, running costs and upkeep: A$27K, so year 1 does not pay back.
The A$12K quote costs A$27K to own in year 1 against A$20K saved: judge the total, not the quote.
Illustrative figures, not client data.
In short
Judge an automation on what it costs to own over a year, not on the build price: your team’s time, running costs and upkeep count too.
The saving is usually hours, fewer errors and faster information, and hours are only cash if they replace overtime, a contractor or a hire.
Before it runs on live records, require a named owner, acceptance examples, a written routine, failure handling shown and support limits in writing.
The first question is usually what an automation will cost to build. The better one is what it costs to own, and what it gives back.
From 2023, I automated payroll, accounts payable and the month-end with Zapier and Power Query, and removed more than 500 labour hours a year. Those are hours, not dollars, and I claim no cash saving. Hours like that only last when someone in the business owns the workflow after the build.
What it costs to own
Exhibit 2
The A$12K quote is less than half of the A$27K it costs to own in year 1
Illustrative year-1 costs for a fictional business, excl. GST. Against a cautious saving of A$20K, year 1 does not pay back.
Show the figures
A$ thousands
Build
A$12K
Your team’s time
A$5K
Running costs
A$4K
Upkeep
A$6K
Illustrative figures, not client data.
Exhibit 3
Four costs sit behind the quote, and the build is only one
01
The build
A fixed scope, with testing and handover included. Everything after it depends on how clearly that scope was written.
02
Your team’s time
Someone agrees the acceptance examples, tests with real records and learns the routine. It’s capacity rather than extra cash, but it’s real.
03
Running costs
AI model usage, workflow software and any extra licences, usually paid monthly. Ask to see them before you commit.
04
Upkeep
Monitoring, fixes and small changes after go-live. Someone does them, whether that’s your own team or a builder under a written agreement.
A cheap build with heavy upkeep can cost more over a year than a careful build that runs quietly. Judge the total, not the quote.
What it gives back
Exhibit 4
The saving shows up in four places, and rarely as a cheque
01
Hours
Re-keying, chasing and checking that people now do by hand. Count them from the current routine, not from a vendor’s estimate.
02
Fewer errors
A duplicate bill caught before it is paid. A report that doesn’t need correcting after the board has read it.
03
Faster information
Figures ready on a set day, so decisions don’t wait for a spreadsheet.
04
Better work for the team
The waiting and the re-keying go, not the judgement. A routine in one person’s head becomes a written one.
Exhibit 5
Hours are cash only if they replace spend. Otherwise they are capacity
A cash saving
Replaces overtime
Replaces a contractor
Replaces a hire you would otherwise make
Capacity
Hours freed, with no spend avoided
Still worth having, if you decide in advance what the team will do with it
Exhibit 6 · Try itYear 1: what it costs against what it savesPut in your own figures for the build, your team’s hours, running costs and upkeep. Add a cautious value for the time and problems saved. See whether it pays back in year 1, then check it is ready to go live.Open the calculator ↓Close ↑
Illustrative figures from your own inputs. Not a quote and not a promise of savings. Upkeep covers monitoring, fixes and small changes after go-live.
Use a cautious monthly value. If running costs and upkeep together cost more each month than that value, the workflow never pays back. Narrow the scope, or pick a workflow with more at stake.
Its sample pays back: change it to your own figures.
More detail
Done well, automation takes the waiting and the re-keying, not the judgement. The people who copied figures between systems now check the exceptions the workflow holds for them. That is better work, and it uses what they know about the business.
It also reduces key-person risk. A routine that lived in one person’s head becomes a written one, with a named backup. A new starter can learn it from a page.
The risk runs the other way too. A workflow that silently stops is harder to manage than a manual process everyone can see. The team needs to know what the workflow does, what it hands to them and who to call when it fails.
What drives the cost and the risk
Exhibit 7
Three things set the cost and the risk, and you can agree each before the build
Driver
What raises cost or risk
Agree before the build
The result you need
A vague ask: ‘we need automation’
A report on a set day, a record for another system or an approval with an owner
The state of the records
Missing fields, duplicates and history to migrate
Which clean-up is yours
The controls
A workflow that changes a record or pays a supplier
Approvals, permissions and exceptions, designed in
The number of screens says little. Records that start messy stay expensive to own, so agree before the build which clean-up is yours.
More detail
‘We need automation’ leaves too much open. A report ready on a set day, a record that must reach another system, an approval with a clear owner: each can be scoped and valued.
A workflow that prepares information for a person to review carries less risk than one that changes a record or pays a supplier. Approvals, permissions and exceptions are part of the design, not an extra.
Who owns it after go-live
Exhibit 8
Nothing runs on live records until five things are in writing
01Acceptance examples
Representative inputs and the result each should give, including a missing record and a duplicate. ‘It looks right’ isn’t acceptance.
02A named owner
With a backup and the access list: which accounts and permissions it uses.
03A written routine
A short note on what runs, when and which checks stay with people.
04Failure handling, shown
What happens when a source can’t be reached, who is told and what the team does meanwhile.
05Support limits
What upkeep covers, and what needs a new scope.
Exhibit 9 · The workflow
From one workflow to a clean handover
What gets caught: A missing failure plan is caught at step 5, ‘Handover gate’.
1 of 7 · The checklist2 of 7 · The record3 of 7 · Claude reads4 of 7 · Rules match5 of 7 · The gap6 of 7 · A person decides7 of 7 · The outcome
Claude reads
Rules check
A person decides
You agreed what handover means.
Five items in writing, before anything runs on live records.
Then the acceptance record comes in.
12 of 12 examples pass. It looks ready.
Handover checklist
Before it runs live5 items
Agreed in writing at the start
WorkflowApproved jobs to Xero draft invoices
Acceptance examples12 of 12 pass
Named ownerOwner and backup
Failure planXero-down path shown
Support limitsIn writing
Acceptance record
Acceptance recordAt handover
Tested on a copy, not live records
WorkflowBuilt and tested
Acceptance examples12 of 12 pass
Named ownerAccounts lead, backup named
Failure planOpen, not shown
Support limitsAgreed in writing
Claude (Anthropic’s AI model) reads both.
Claude turns the checklist and the record into the same fields. It doesn’t sign anything off.
Plain rules match them, line by line.
The same handover gate for every workflow.
Read by ClaudeRequired · Handover checklist
Read by ClaudeIn the record · Acceptance record
WorkflowRequired: Approved jobs to Xero
✓
WorkflowIn the record: Built and tested. Matches
Acceptance examplesRequired: 12 of 12 pass
✓
Acceptance examplesIn the record: 12 of 12 pass. Matches
Named ownerRequired: Owner and backup
✓
Named ownerIn the record: Accounts lead, backup. Matches
Failure planRequired: Xero-down path shown
✕
Failure planIn the record: Open, not shown. Doesn’t match
Support limitsRequired: In writing
✓
Support limitsIn the record: In writing. Matches
✓12 of 12 examples pass
✓Owner and backup named
✕Xero-down path not shown
The gap, in items.
One of five handover items is still open.
Handover items
Open at handover1 of 5the Xero-down path
Items required
5
Items checked
4
Acceptance examples passing
12 of 12
Open
Xero-down failure path
12 of 12 examples passing is not enough on its own.
It waits for the workflow owner.
Nothing runs live until a person decides. Here, that’s you.
AL
Accounts leadWorkflow owner · message from the handover gate
In testing. Not on live records.
Needs your decision
Every example passes, but nobody has shown what happens when Xero can’t be reached. Sign off now, ask to see the Xero-down test, or reject the handover?
You decide: pick one to see what happens, or the run goes with “Ask to see the Xero-down test”.
It doesn’t run live yet.
Claude (Anthropic’s AI model) reads. Rules check. A person decides.
Live, 1 item openIt runs on live records with the Xero-down path never shown.
Live on real records, with the open item on file as the accounts lead’s decision.
Acceptance recordSample
Handover sign-offApproved with notes
Workflow
Approved jobs to Xero draft invoices
Status
Live on real records
Open
Xero-down failure path
Signed off with 1 of 5 items open: the Xero-down path was never shown. My decision, on the record.
Note by the accounts lead
Claude read the checklist and the acceptance record into the same five fields.
The handover gate found 4 of 5 items checked: the Xero-down failure path was never shown.
The accounts lead signed off with the failure plan still open, on the record as their decision.
With the Xero-down path shown on a test copy, the accounts lead signs off and it runs live from the next working day.
In testingNothing runs live until the failure path is shown.
A session booked to see the Xero-down path run on a test copy.
CalendarBookedSample
Tomorrow10:00 am
Show the Xero-down path, on a test copy
With
The builder and the accounts lead
Show
Where approved jobs wait while Xero is down, and how they go through once it is back
Until then
In testing, not on live records
Agenda drafted by ClaudeBooked by the accounts lead
Claude read the checklist and the acceptance record into the same five fields.
The handover gate found 4 of 5 items checked: the Xero-down failure path was never shown.
The accounts lead asked to see the Xero-down path run on a test copy before signing off. It stays in testing until then.
With the Xero-down path shown on a test copy, the accounts lead signs off and it runs live from the next working day.
Rejected. In testing.Handed back: 1 of 5 items open.
An email to the builder saying why the handover was rejected.
EmailSentSample
From
Accounts lead
To
The builder
Subject
Handover not accepted: failure plan open
Hi, thanks: all 12 acceptance examples pass and 4 of the 5 handover items are checked.
The failure plan is still open: nobody has shown what happens when Xero can’t be reached. Please run the Xero-down path on a test copy and hand it over again.
Drafted by ClaudeSent by the accounts lead
Claude read the checklist and the acceptance record into the same five fields.
The handover gate found 4 of 5 items checked: the Xero-down failure path was never shown.
The accounts lead rejected the handover and sent it back to the builder with the failure plan named.
With the Xero-down path shown on a test copy, the accounts lead signs off and it runs live from the next working day.
Sample data: a fictional business and workflow.
ClaudeWhere Claude helps
Reads sample paperwork before the build to show what it must handle
Drafts the operating note from the build for the workflow owner to check
Summarises test results against each acceptance example
RulesWhat the rules check
Every acceptance example passes before go-live
Every account and permission the workflow uses has a named owner
The failure path is tested: source down, record missing, a duplicate
PersonWhat a person decides
The workflow owner agrees scope, assumptions and exclusions in writing
The workflow owner signs off acceptance, not the builder alone
Any change in scope is costed and agreed before work continues
NoWhat Claude doesn’t do
Make a vague scope cheaper or safer
Replace testing with your own people and your own records
Take on open-ended support after handover
Sample data. Claude reads, plain rules check, and you make the decision. Press run to watch it get caught.
Every live workflow needs one named owner in the business. Not the builder, and not ‘the team’. The owner approves changes, holds the access list and decides what happens when it fails. Name a backup for when they’re away.
More detail
Ownership has three parts. Maintenance keeps the workflow correct when a form, a role or a supplier’s system changes. Monitoring tells the owner about failed or held items before a customer notices. Change control treats each change like a small build: costed, agreed, tested and written down.
What to ask and what to decide
Exhibit 10
Five things management can produce on request show a workflow is owned
Ask management for
What it shows
A register of live workflows
Each one’s purpose, owner, backup and the data it touches
An acceptance record for each
Signed by the owner, not the builder alone, with open items dated
A short run report
Failures, held items and how long they waited
A change log
What changed, who approved it and what it cost against the estimate
Cost against saving
Running costs and upkeep against budget; hours or errors saved against the approving case
Exhibit 11
Your decision is one of three: approve it, narrow the scope or say not yet
Approve it
The five things are in writing and management can show them
Narrow the scope
Running costs and upkeep cost more a month than the saving: narrow it, or pick a workflow with more at stake
Not yet
The records are not clean
A board doesn’t need to read the code. It needs evidence that every workflow touching money, customers or reporting has an owner and runs under control. If management can produce these on request, the workflow is owned. If it can’t, the business is relying on the builder’s memory. For the checks a report needs before it reaches the board, see management reporting that drives decisions.
What to do first
Exhibit 12
One workflow, one calculator, one owner is enough for this week
01Pick one workflow
One you are considering, or already run.
02Put its figures in the calculator
Use a cautious monthly value for what it saves.
03Ask your team who would own it
One named person, not the builder, with a backup.
04Decide
Approve it, narrow the scope or say ‘not yet’ until the records are clean.
Common questions
What does an AI automation cost to own after the build?
Running costs (AI model usage and workflow software, usually billed monthly), upkeep when forms, roles or systems change, and some of your team’s time to review exceptions. Ask to see the running costs before you commit, and count all of it over the first year.
How do I know if an automation will pay for itself?
Compare what it costs to own in the first year with a cautious value for the hours and errors it saves. Hours count as cash only if they replace overtime, a contractor or a hire; otherwise they are capacity. If running costs and upkeep cost more each month than the value saved, it never pays back.
Who should own an automated workflow once it’s live?
One named person in the business, not the builder, with a backup. They approve changes, hold the access list and decide what happens when it fails. If someone else maintains it, a written agreement says what’s covered.
Chartered Accountant (CA ANZ) and finance executive, based in Canberra. Practical AI and automation for SMEs, and adviser to owners, CEOs and boards on integration and finance.
Want one workflow scoped, built and handed over at a fixed price? Works Better starts with a workflow audit. Changing how the whole business runs its finance and systems? I lead that change hands-on.
Renzo Demartini