Digital Transformation, South Africa

Why South African transformation should start with how the business works

Many South African SMEs have grown by adding tools as problems appeared. A desktop accounting package handled the books, a separate system arrived for point of sale, a CRM was trialled by one sales manager, and the gaps were filled with spreadsheets and email. Every addition made sense at the time. The combined result is often slow month-ends, disputed reports and staff who spend hours moving data between systems.

Replacing everything with one new platform does not solve that by itself. If nobody has agreed how a credit application should be approved, or who may create a new supplier, the new system simply records the same disagreements. So my first stage examines the business:

• how customers are onboarded, quoted, invoiced and collected, including debit orders and account customers
• how suppliers are vetted, documented and paid, and how B-BBEE supporting documents are tracked
• how stock moves between depots, branches and customers
• which reports management relies on and how they are produced
• what staff actually do when power or connectivity fails

People and skills matter as much as process. Experienced finance and IT staff can be hard to recruit and retain, so the plan must not depend on one specialist who might leave. Detailed process redesign can continue through process consulting for South African companies where needed.

Power, connectivity and other South African drivers

Some pressures on South African businesses are unusual enough to shape the whole roadmap.

Power and connectivity. Scheduled power cuts have eased and returned at different times, and connectivity varies by area and provider. A transformation plan cannot assume that every site is always online. For each critical process I agree what happens during an interruption: whether capture continues offline, how long a branch can operate on paper, and how records are reconciled afterward. These rules then become requirements for every vendor, not an afterthought.

Tax data. VAT returns to SARS depend on clean invoice, supplier and import data. SARS has signalled interest in modernizing VAT reporting, and possible e-invoicing has been discussed. Until rules are confirmed, the sensible step is to make invoice data structured and reliable. Your accountant or tax practitioner confirms treatment and any new obligations.

Personal information. POPIA affects how customer, employee and supplier data is collected, shared and kept, including in cloud and AI tools. The roadmap records where personal information flows so your information officer can review it.

Payments and banking. Debit orders, EFTs and newer instant payment options all need to reach the books without manual capture.

Each driver feeds the plan. None becomes a separate project running on its own.

Ordering ERP, CRM, automation, reporting and the website

The roadmap's purpose is to put change in a sequence the business can absorb while still trading. After the diagnostic, a South African SME's plan often follows this pattern:

1. Groundwork. Agree standards for customers, suppliers and items, appoint data owners, clean the records in Sage, Pastel or spreadsheets, and write the resilience rules. Some companies keep their accounting package for a while, which is recorded as a deliberate choice.
2. Core system. Put in place, or repair, the financial and operational system of record, with VAT, multi-branch stock and supplier documentation designed in, and a cutover planned around VAT periods and outage risk. The platform decision sits with ERP consulting in South Africa.
3. Customers and sales. Introduce or repair the CRM so tenders, RFQs, credit applications and orders pass to the core cleanly.
4. Automation and reporting. Take routine sign-offs, payment reminders and supplier document filing out of inboxes, then build management dashboards that do not depend on a spreadsheet expert.
5. Website and lead engine. Connect the website and campaigns to the CRM so inquiries can be traced to orders. The South African SEO work belongs here.

Every stage carries a named lead, the prerequisites it depends on, its cost drivers and the gate that must be passed before moving on. Hosting choices, backup connectivity and power arrangements at key sites are listed as dependencies where they apply.

Adoption across head office, depots and branches

A plan only works if people use what it delivers. In South African companies, the people affected often range from head office finance teams to depot supervisors, drivers and branch counter staff, with very different levels of comfort with technology and different home languages.

I plan adoption as part of every phase:

• a champion at each branch or depot who tests early versions and supports colleagues
• training on your own transactions, recorded so staff can revisit it, with Afrikaans, isiZulu or other home-language job aids produced in-house or by a training firm where useful
• mobile and tablet screens for staff who work away from desks
• simple written fallback procedures for outages, practised before go-live rather than discovered during one
• a switch-off date for legacy spreadsheets and paper books once a process has migrated

The engagement runs in English, with remote workshops held during South African business hours, which overlap comfortably with India. If a site loses power during a session, it is rescheduled or the recording is shared. On-site visits can be arranged for key milestones by agreement.

I also watch for quiet resistance after each go-live: duplicate records, approvals outside the system and requests for the old reports. Those signals guide the next steering discussion.

Governance, independence and a sober view of AI

A roadmap needs ownership beyond the consultant. I help set up governance suited to a South African SME or subsidiary: an executive sponsor, a steering group on a fixed cycle, a responsible manager for every process area and master data set, and phase reviews that describe outcomes in operational terms. Where the business is part of a group, the governance clarifies which decisions are local and which need head office approval.

My role differs from that of vendors and implementers. A vendor licenses software, and an implementer earns from configuration and development. I work only for the company: defining needs, comparing proposals on equal terms, checking delivery against the roadmap and raising problems before they turn into variations or disputes. No vendor or implementer pays me any commission or referral fee.

AI can help, but it is not a starting point. Once supplier, customer and item data are reliable, AI tools can read supplier invoices, sort inbound email or draft routine responses, with a person checking the result. Before that, they mostly accelerate existing errors. POPIA questions about sending personal information to external AI services should go to your information officer or legal advisor. AI therefore appears in the later stages of the roadmap, once the groundwork is complete.

Read more about the general method on the digital transformation consulting page, or contact me to discuss your roadmap.