The conversation should begin with operations, not software
In a South African business, the case for a new ERP often starts with a familiar problem: information lives in too many places. Finance works from one set of figures, operations from another, and teams spend valuable time reconciling the two. Buying a platform before understanding these handovers can turn an existing process problem into an expensive technology problem.
Map the work as it really happens
Bring finance, procurement, operations and customer-facing teams into the same discussion. Follow a transaction from its first request through approval, delivery and reporting. Note where information is copied between systems, where approvals stall and where staff rely on spreadsheets to bridge gaps. These details matter more than a long wish list of features.
Make local requirements part of discovery
South African organisations should evaluate their actual reporting, tax, privacy, banking and operational requirements with qualified advisers. Businesses working across African markets may also need to consider differences in currencies, connectivity, subsidiaries and approval structures. These needs should be tested against the proposed solution rather than assumed to be standard.
A useful next step
Before issuing an ERP request for proposal, agree who owns each business process, what data needs cleaning, which integrations are essential and how success will be measured six months after launch. That gives vendors a clearer brief and leadership a more realistic investment decision.
Planning a similar initiative? Talk to our team about a practical starting point.
Talk to an advisor