Service
AI automation consulting and audits
The expensive mistake in AI automation is not picking the wrong model. It is automating the wrong process: something visible and annoying rather than something frequent and costly. The audit exists to put a defensible order on the work before anyone writes code, and it is deliberately sold separately from the build so the recommendation is not shaped by what we would like to be hired to build.
You might recognise
- Leadership wants an AI strategy and nobody can say where to start.
- You have run pilots that demoed well and never reached production.
- Different teams are buying different AI tools with no shared plan.
How it runs
Four steps, in this order.
- 01
Interview and observe
Conversations with the people who actually do the work, not only the people who describe it. Where the documented process and the real one differ is usually where the opportunity is.
- 02
Map and measure
Each candidate process gets written down with its frequency, its handoffs, its exception rate, and the time it consumes. Your numbers, gathered during the audit, not industry benchmarks.
- 03
Score feasibility
Against three axes: how mechanical the judgement is, whether the systems can be reached programmatically, and what a mistake costs. Candidates that fail the third axis are ruled out regardless of how attractive the first two look.
- 04
Rank and cost
A sequenced plan with build estimates, the order that reduces risk fastest, and an explicit list of what we recommend you do not automate.
What you get
Deliverables
- A written process map of every candidate workflow
- A feasibility score per candidate, with the reasoning shown
- A ranked build sequence with cost estimates
- An explicit do-not-automate list, with reasons
- A walkthrough session with your team, and the document to keep
FAQ
About automation audit
Do we have to hire you for the build afterwards?
No, and the audit is priced as a standalone piece of work for that reason. The deliverable is written so another team, or your own engineers, can execute from it. An audit that only makes sense if you also buy the build is a sales document, not an audit.
How long does it take?
It is fixed-scope and agreed before we start, sized to the number of processes in the scope. Scope and timeline are set in writing at the outset rather than discovered as we go.
What do you need from us?
Time with the people who do the work, and read access to enough of the systems to see how the process really flows. No production write access is needed for an audit.
What if the answer is that we should not automate anything?
Then that is the deliverable, with the reasoning written out. It is a genuine possible outcome. Knowing which of your processes should stay human is worth the same as knowing which should not.
Related reading
Tell us what the work looks like
Describe the process you want off your team plate. You will get a straight answer on whether agents are the right tool for it, including when they are not.