Most pages about hiring a workflow automation consultant are written by people selling workflow automation consulting. This one is too, so here is the useful part up front: the four things a good consultant should hand you, how to spot one who is really a software reseller, and the three situations where you should not hire one at all.
What a workflow automation consultant actually does
Strip out the jargon and the job has two halves. The first is finding out, with numbers, which parts of your week are worth automating. The second is building the ones that are, inside the tools you already run, and leaving your team able to live with the result. Most of the value sits in the first half. Most of the marketing is about the second.
That order matters because tools are the cheap part. Every mainstream platform can move data from an email into a spreadsheet. None of them can tell you whether that task costs you eight hours a year or four hundred, and that single number decides whether a build is worth doing (the arithmetic is set out in our guide to AI workflow automation in Melbourne). A consultant who skips the counting is guessing on your behalf.
It is also why the role overlaps with an AI automation consultant more than the job titles suggest. AI is increasingly the step inside a workflow that reads the document or sorts the enquiry, but the decision about which workflow to touch first is the same arithmetic either way.
The four things a workflow automation consultant should hand you
Whatever the engagement is called, good automation consulting produces four concrete outputs. If you cannot point to each of them at the end, you paid for opinions.
1. A costed task ledger
A list of the repetitive tasks in scope, each with minutes per run, runs per week and annual hours. It is the most useful document in the whole engagement and the one most often skipped. A short illustrative example:
- Supplier invoice entry: 12 minutes, 40 times a week. 416 hours a year.
- Weekly management report: 3 hours, once a week. 156 hours a year.
- New supplier onboarding: 45 minutes, twice a month. 18 hours a year.
The third task is the one people usually want automated first, because it is fiddly and everyone dislikes it. The ledger says leave it alone. That is the ledger doing its job.
2. A ranked shortlist, with things crossed off
The ledger turned into a decision: what gets built, in what order, and what does not get built at all. A shortlist with nothing crossed off is a sales document. Ranking by annual hours rather than by irritation is most of the trick, and it is the measure-first step of the ATTACK Method.
3. A fixed-scope build
One workflow at a time, scoped small enough to finish and verify, at a fixed fee agreed before work starts. Our own work follows the same pattern. One defined workflow for a technology business went from scope to live in a fortnight. A reporting automation for a multi-site food retail operator returned roughly 15 hours a week, about 780 hours a year, and the full breakdown is in the automated business reporting case study. Neither required new software.
4. A handover your team can actually use
A plain-language runbook covering what the automation does, how it fails and who gets told when it does, plus a named person inside your business who owns it. If the only person who understands the workflow is the consultant, you have bought a dependency. This is also where AI training stops being a separate project: the team that inherits an automation has to be comfortable working alongside it.
When you do not need a workflow automation consultant
Three situations, and in each of them hiring one is money you do not need to spend.
- The fix is already in software you pay for. Email rules, bank feeds in your accounting software, a CRM's built-in follow-up sequences. If one task in one tool can be solved by a setting, turn the setting on. Nobody needs to be paid to find it for you.
- Your whole ledger is small. Add up the annual hours across every repetitive task you can think of. If the total is under about 50 hours a year, no build will pay back, and no consultant should tell you otherwise.
- The process is still changing. If the way you quote, onboard or report changes every month, automating it locks in this month's version. Settle the process by hand first, then automate the version that has stopped moving.
If you are unsure which side of the line you sit on, the free automation scorecard gives a quick first read before you talk to anyone.
How to tell an automation consultant from a software reseller
Plenty of automation consulting is a platform sale with a discovery call in front of it. Three questions sort them out quickly.
- "Which tool would you use?" Asked in the first conversation, a good consultant says it depends on what the ledger shows. A reseller names the platform straight away.
- "What would you tell us not to automate?" If the answer is nothing, the incentive is volume, not payback.
- "How is the fee set?" Hourly billing rewards long projects. A fixed fee agreed up front puts the scoping risk on the consultant, where it belongs.
It is also fair to ask whether they earn anything from the platforms they recommend. A referral arrangement is not automatically a problem, but you should hear about it before the recommendation, not after. That is the bar we scope our own process automation work against, and it is a fair one to hold anyone to.
Try this today
Build a three-line task ledger before you talk to any consultant, us included. Pick the three tasks your team repeats most. For each one, write down the minutes per run and the runs per week, multiply them, then multiply by 52 and divide by 60. You now have annual hours per task, which is the first number any good workflow automation consultant would ask you for. If all three together come to under 50 hours a year, you probably do not need one yet. If one of them runs into the hundreds, you have your first brief.