How South African SMEs can identify processes worth automating

What happened

Many small and medium-sized businesses are under pressure to digitise, but the word can make the job sound larger than it is. Digitisation does not have to begin with replacing every system or launching a multi-year transformation programme. It can begin with one operational path that repeatedly consumes time: responding to a lead, reconciling a document, scheduling field work or approving an internal request.

South Africa's digital skills strategy frames digital capability as a broad economic and workforce priority. At business level, the practical question is more immediate: where will a better flow of information produce a measurable improvement for customers or staff? That question creates a more useful automation backlog than starting with whichever technology is receiving the most attention.

Why it matters

SMEs have less capacity to absorb poor implementation. A workflow that creates a second source of truth, adds another login or fails when one person is absent can increase operational fragility. The first automation candidates should therefore be frequent, rules-based enough to standardise and visible enough to evaluate. High-volume work with clear inputs and outcomes usually provides a safer learning environment than rare, highly variable decisions.

Look for four signals. The same information is captured more than once. Work waits in an inbox for someone to notice it. Staff regularly ask for progress updates because no shared status exists. Exceptions are discovered late, after a deadline or customer promise has already been affected. A process showing several of these signals is likely carrying avoidable coordination cost.

Our perspective

We recommend scoring candidates against operational value and implementation readiness. Value considers time lost, customer impact, error cost and visibility. Readiness considers whether the trigger is clear, the required data is available, the rules can be described and an owner is willing to maintain the process. A high-value process with very low readiness may need simplification before automation.

Start with a short observation period. Follow real work from request to outcome, including the unofficial spreadsheets, WhatsApp messages and verbal approvals that sit outside the documented process. These are not side details; they often reveal the actual handoffs an automation must support. The result should be a small, credible first release that makes the work easier to own and easier to improve.

Local operating conditions should shape the design rather than appear as an afterthought. Mobile access, intermittent connectivity, customer channel preferences and the cost of adding another specialised tool may all influence the right architecture. A resilient workflow should preserve a clear queue and recover cleanly when a service is unavailable. Practical fit creates more value than a technically ambitious system that staff cannot rely on every day.