For a business with many teams, many systems or compliance obligations: a plan with every recommended build priced in writing, and no obligation to build anything. The first step is a short call.
Situation one
Competitors mention AI in their pitches. Your accountant asks about it. Someone on your team uses ChatGPT for drafts and nobody else knows what it's good for. There is a gap, and nobody can say where it is in your business.
Situation two
You're sure some of the week's work could be automated: the monthly reports, the re-keying, the chasing. But "somewhere" is not a business case, and you won't spend real money on a guess about your own operation.
Situation three
Every week there's a new tool, a new agency, a new promise. They can't all be right, and none of them knows how your business runs. So nothing gets picked, and that costs more than picking the wrong one.
All three are the same problem: nobody has measured where your time goes, so every AI decision so far has been a guess. The Systems Diagnostic replaces the guess with evidence from inside your business: what your current work costs, what automating each piece would return, and a fixed price on each build. We measure before you decide whether to build anything.
Every date is booked at onboarding, before the clock starts. Ten business days run from the workshop to the Diagnostics Review, whatever the size of your business, and if you move a date the clock pauses. Click any step for the detail.
The interviews check what was said in the workshop, and your own records check the interviews. Where they disagree about the same piece of work, we look into it, because that is often where the main findings are.
In person wherever that is practical, which is South-East Queensland by default: the education session and the workshop run on one day. Online, they run as two sittings on days 1 and 2.
An education session for your team first: what AI can and can't do, and how we decide whether something is worth automating at all. Then the workshop, where your people draw diagrams of how the business wins work, delivers it and runs day to day. The people who do the work draw them.
Your senior people sign off the diagrams before the workshop ends. Everything after uses them: each workflow we look at later is checked against them to see how much it matters to the business.
Where two groups contradict each other about who does what, we record it and leave it unresolved during the workshop. Those contradictions are usually where the main findings are.
After the workshop we sit down one-on-one with the principal and the owner of each shortlisted workflow, usually 3 to 6 people, run in parallel. What people tell us stays confidential: the Diagnostics Report carries themes and leaves out names.
This is where each workflow gets described in detail: what happens step by step, the edge cases, what goes wrong, what tools are used, and the workarounds and exceptions nobody writes on a form or says in front of colleagues.
We ask how the work is done. Working out what to automate is our job.
We check everything against the diagrams your senior people signed off. Each workflow is linked to the part of the business it serves, rated on how much it matters, and given a dollar value using one of the four methods below. Each figure comes from your records, the workshop or the interviews, and shows where it came from. Each recommended build gets a fixed price, and the figures and prices are written into your Diagnostics Report, sent on day 8, 48 hours before the Diagnostics Review, so you can read every number and price at your own desk first.
The long version covers the workshop block by block and the report section by section: Read the Diagnostic in detail.
Four ways to put a dollar value on a workflow. Each workflow gets the method that fits how the work is done.
Method one
Before automation
Post automation
Presented as a reduction in time and cost, or as a saving per period of time. Fits when a person was doing the whole task on a known cadence. It does not fit when the automation runs far more often than a person could.
Method two
Before automation
Post automation
Presented as an increase in capacity, or the equivalent value created. Used when the new capacity can be used to increase throughput, often where the process was a bottleneck, and when the automation removes waiting time while human input time stays the same.
Method three
Post automation
Post automation · repeating
Presented as an equivalent value per time period. Used when the value comes from having outputs that are always up to date. A labour saving understates this kind of work, because the automation runs far more often than a person ever could.
Method four
Before automation
Post automation
Presented as a reduction in failures or an increase in success rate. Used when the work is cheap to do by hand, so a time saving would not show its value. The value shows up as more customers won back, less rework and fewer mistakes reaching clients.
Worked examples. The figures are illustrative and do not come from client work. Your Diagnostics Report runs this arithmetic on your own hours and rates, with the working shown.
Fifteen to twenty-five pages, built from your own team's answers. Printed and bound if we're on site, and sent 48 hours before the Diagnostics Review, so you read every number and every price at your own desk before the meeting.
It is written as a set of findings. What your team said, verbatim. Where the time goes, from your own records where they exist and clearly marked as an estimate where they don't. Every automation candidate we found, including the ones we don't recommend building and the reasons.
Every recommended build has its own price. Each item is priced next to the problem it fixes, so you can take one item, three, or none.
You keep it either way. If you never build anything with us, you still own a documented map of how your business runs, a plan ranked by estimated return for the price, and a priced list any builder could work from. The full contents, section by section, are in the Diagnostic in detail.
Summary: the main findings
What your team told us: verbatim and anonymised
The friction map: where the week goes
Everything we found: every automation, ranked, including the ones we don't recommend
Tools and subscriptions: what you pay for now, which tools overlap, and when each one renews
The plan: what to build now, next and later, over 12 to 24 months
Recommended builds: each priced and ranked by estimated return for that price
The build order: what to build first, with an estimated price for each
What we left out, and why: a record of every item excluded
Appendices: a brief for each workflow · your tools and subscriptions · a summary of the data · a record of how things run today, for measuring results later
The full Systems Diagnostic is quoted to the size and complexity of your business, from A$3,900, ex GST. All figures AUD.
For complex cases
Quoted · invoiced at booking
The deliverables
For a business with many teams, many systems or compliance obligations, the full Systems Diagnostic, from A$3,900. The first step is the same short call.