Process map
Request → prepare → review → handoverThree people own different decisions. The review handover has no definition of complete.
For Australian owners choosing which process is worth fixing first
An automation audit with a clear decision at the end.
Find the process worth fixing, the dependencies that could stop it and the scope a builder can actually quote. Our audit is a paid diagnostic, credited on signing. We agree its fee and boundaries before work begins.
From source documents to a useful decision
A closer look +
Who it is for
When the ideas outnumber the clear decisions.
For Australian owners with too many possible automation ideas, a fragile collection of existing workflows or an unclear business case. Bring the people who receive the work, a few representative records and the systems involved. You do not need to arrive with a platform choice.
What changes for you
01
A process map with owners and missing handovers
02
Ranked opportunities with explicit assumptions
03
A dependency and failure review
04
A written first-build scope and recommendation
Example system · Simulated business data
A diagnostic you can put on the table.
Opportunity ranking
First candidate · standardise the handoverFrequent rework is a hypothesis to measure. Do not turn an unmeasured estimate into promised savings.
Dependency review
Access and identity are unresolvedConfirm the destination can preserve the existing job reference before quoting the write.
Written scope
Build one accepted handoverInclude the required fields, approval owner, acceptance tests and missing-run check.
Illustrative packet contents. Your diagnostic is based on your records and agreed scope. The audit is paid and credited on signing.
Start with actual work, not a wish list
We follow a representative item through the business. Where did it arrive, who checked it, where did it wait and what did the next person have to reconstruct? A conversation with the process owner is paired with records that show how the work behaves.
For an existing automation estate, we review what each workflow owns, its trigger, credentials, dependencies and exception path. We ask which business outputs should arrive even when the platform dashboard has no error. Access is limited to what the agreed diagnostic requires.
- Representative normal and exception records
- Current workflow inventory and account owners
- Observed volumes and handling-time assumptions
- Data sensitivity and access constraints
Rank the opportunity and the uncertainty together
We compare frequency, repeatability, time spent, rework and the consequence of getting it wrong. A high-volume task with clear rules may be a better first build than a broad agent with unclear authority. We include the internal effort needed to keep either option useful.
The estimate distinguishes released capacity from cash savings. Reducing handling time does not automatically reduce payroll or create more revenue. We put the assumptions and likely operating costs beside the potential benefit so you can challenge the recommendation.
Leave with a scope, not another discovery loop
The final packet names the recommended first slice, required access, implementation boundaries, acceptance cases and unresolved dependencies. It separates work ready to quote from work that needs vendor confirmation or a business decision.
We walk through the recommendation with you. You can proceed, narrow the build, change the process first or stop. The paid diagnostic is credited on signing; the written commercial scope records how that applies. You decide separately whether to commission the build.
The example shows our design approach using simulated records. It is not a client case study or a measured performance result.
What it costs
Price the scope and the operation.
This is a paid diagnostic credited on signing. We do not publish a fixed audit fee because the number of processes, systems, stakeholders and existing workflows changes the work. Your written audit scope confirms the fee, access boundaries and deliverables before we begin. The build tiers below describe implementation, not the audit fee.
We put the build scope, fee and payback estimate in writing using your baseline. You own the accounts, workflows and documentation. Software, hosting and AI usage are separate operating costs.
Automation builds
From $3,500 AUDOne process, rebuilt to run without you. Monitoring and documentation included.
Typical projects
$3,500 to $12,000 AUDSeveral connected processes across two or more systems, where the data needs cleaning first.
Complex AI agent systems
$12,000 to $25,000 AUDAgents that read unstructured information, decide and write back, with human review and a full audit trail.
Ongoing care plans
$750 to $2,500 AUD per monthPriced on how much you run and what your business loses the day one of them stops.
When something breaks
A clear owner. A safe next step.
For existing automations we inspect failed runs, empty results and missing triggers, then identify the operational owner and recovery gaps. The diagnostic does not include taking over production incidents or changing live workflows unless separately agreed.
We account for a failed run, an empty result and a run that never starts. Your written care scope names alert ownership, recovery responsibilities and change boundaries. Support commitments belong in that scope.
Care is month to month and can be cancelled without penalty. You keep the system and its documentation, with no lock-in.
See ongoing supportBefore you decide
Your questions, answered
Is the audit free?
No. It is a paid diagnostic credited on signing. We confirm the fee and agreed deliverables before starting. The introductory call helps establish whether this diagnostic is the right next step.
Do we have to commission the build afterwards?
The audit gives you a recommendation and a written scope to decide from. You can choose to proceed, defer the work or use the findings with another builder. A diagnostic is not an automatic implementation commitment.
Will you change our live automations during the audit?
The diagnostic scope defines access and review activity. Production changes, new integrations and incident remediation are separate work unless explicitly included and authorised.
How long does an automation audit take?
We agree the timing after confirming the processes, systems and people involved. Availability of records and access matters. We do not promise the same turnaround for one handover and a whole automation estate.
Who owns the accounts and the finished system?
You do. We build in accounts you control and hand over the workflows, access map, documentation and available exports. Another capable operator can take over. Platform licences and subscriptions remain subject to their own terms.
How do you price the work and ongoing support?
Builds start from $3,500 AUD. Connected builds are $3,500 to $12,000 AUD and larger systems are $12,000 to $25,000 AUD. Care is separate at $750 to $2,500 AUD per month. We confirm the scope and fee in writing. Software, hosting and AI usage sit outside the build fee. Care is month to month and can be cancelled without penalty.
A useful first conversation
Bring the process you want a clearer answer on
Show us a representative record, the tools involved and what the next person needs. We will discuss a useful first scope and the decisions it depends on.
Book a call