What a Workflow Automation Consultant Actually Does in Johannesburg
How an automation consultant diagnoses tangled approval chains and connects the systems you already run, without ripping anything out.
What It Is
A workflow automation consultant assesses how work actually moves through your organisation, finds where it stalls, and designs a custom automation that connects the systems you already use. This is not a product you buy off a shelf. It is a tailored orchestration layer built around your specific approval hierarchies, document types, and business rules, so the ERP, the document store, and the inboxes finally hand work to each other instead of relying on a person to carry it.
The consultant's value is partly technical and partly diagnostic. They see the bottlenecks your team has quietly normalised, the 'that's just how we do it' steps that add days, and they know which of those can be removed, which can be automated, and which genuinely need a human decision.
The Story
A financial services firm in Sandton runs twelve different approval workflows spanning legal, compliance, finance, and operations. Each one lives somewhere different, an email thread here, a shared drive there, three separate software platforms in between. The COO spends roughly eight hours a week doing nothing but chasing approvals: pinging people, forwarding attachments, asking who has the latest version. This quarter the firm missed two client deadlines, not because anyone did poor work, but because the paperwork got stuck between systems that do not talk to each other. The work was done. The routing failed.
Why It Matters
Johannesburg's corporate environment is high-stakes and fast-moving, and delays in an approval chain translate directly into lost revenue, frustrated clients, and worn-down staff. When a decision that should take hours takes days, deals slip and people burn out chasing signatures.
A consultant brings an outside perspective and a method. Rather than selling you new software to replace what you have, they build on top of your existing stack, which keeps cost and disruption low. The point is not to digitise a broken process faster; it is to fix the flow first, then automate it. For a firm juggling a dozen disconnected workflows, that is the difference between adding headcount to cope and reclaiming the hours you already pay for.
How It Works
A consultant typically works in four phases.
1. Discovery. Map the current workflows as they truly run, not as the manual says. Document every decision point, who owns it, what triggers it, and where work waits. This is where the real bottlenecks surface.
2. Architecture design. Propose a lightweight orchestration layer that sits above your existing systems, ERP, document management, email, rather than replacing them. The systems stay; a coordinating layer routes work between them.
3. Implementation. Build the API connectors, webhook subscriptions, and a rules engine that encodes your approval hierarchies and exception paths. Anything the rules cannot resolve routes to a named human, so automation never becomes a black hole.
4. Handover. Train your team, document the system so it is not a mystery when the consultant leaves, and set up monitoring and support. On compliance, because these workflows carry financial and personal data, access is scoped per role, every routing action is logged, and records are retained in line with POPIA.
When To Use It
Bring in a consultant when the symptoms are measurable. A good signal is approval cycles that regularly take more than 48 hours, or five or more systems that do not integrate and force staff to copy work between them by hand. Another is a team spending more than ten hours a week on manual follow-ups, the chasing, forwarding, and version-hunting that produces nothing new.
It is also the right moment when you are about to scale. Processes that limp along at current volume tend to break when volume doubles, and it is far cheaper to fix the flow before growth than to fight fires during it. If your approvals are fast, your systems already integrate, and follow-up is not eating your week, you may not need this yet.
A Worked Example
A legal firm in Sandton engaged a consultant to automate contract approval. In discovery, the consultant mapped 47 distinct decision points across the process, an eye-opener for a firm that assumed it had 'a few steps'. They built API connectors to the document management system and the ERP, then deployed a rules engine encoding who must approve what, in which order, and what happens on exception.
The result: approval time fell from five days to roughly four hours, because work now moves the instant a step completes instead of waiting in an inbox. The firm estimated it recovered around 120 partner hours a month, time previously lost to chasing, which is comparable to the capacity of two junior associates, freed without a single new hire. Crucially, the ERP remained the single source of truth; nothing was ripped out.
Summary
A workflow automation consultant diagnoses where work stalls, redesigns the flow, and builds a custom orchestration layer that connects the systems you already run. For Johannesburg and Sandton businesses living with tangled, multi-system approval chains, that means decisions in hours instead of days, hours reclaimed from manual follow-up, and processes that hold up as you scale. The discipline that separates a good engagement from a disappointing one is simple: fix the process before you automate it, keep a human on every path the rules cannot resolve, and build on your existing stack rather than forcing a costly rip-and-replace.
Frequently Asked Questions
Will we have to replace our existing systems?
No. The approach builds an orchestration layer on top of your current ERP, document management, and email, connecting them through APIs and webhooks. Your systems stay in place and your ERP remains the single source of truth; the automation coordinates work between them.
How long before we see results?
It depends on how many workflows and systems are involved, but a focused first workflow on systems that already expose APIs is usually a matter of weeks. Most of the effort is in discovery, mapping how work truly flows, rather than in the build itself.
What happens to approvals the rules can't handle?
They route to a named human with full context attached. The rules engine handles the routine, high-volume paths, and anything ambiguous or exceptional is escalated to a person rather than silently stalling.
Written by
Donovan Tiemie
South African systems architect, HR compliance founder, and published author. He designs POPIA- and CCMA-compliant automation for mid-market businesses (50–1000 employees) from Oudtshoorn, serving clients nationally.
About Donovan TiemieReady to scale? Contact or WhatsApp on +27 073 136 3243