Choosing the right ERP system for your business

An Enterprise Resource Planning (ERP) system is the operational backbone of most mid-sized and large businesses. It integrates finance, procurement, inventory, manufacturing, HR, and other core functions into a single platform, replacing the patchwork of spreadsheets, standalone applications, and manual processes that many organisations rely on.

Choosing the right ERP is a high-stakes decision. Get it right, and you unlock efficiency, visibility, and scalability. Get it wrong, and you face years of pain, millions in wasted investment, and an organisation that’s worse off than where it started.

This guide is for South African business leaders evaluating ERP options - whether you’re implementing for the first time, outgrowing your current system, or replacing a legacy platform that’s reached end of life.

When you need an ERP

Not every business needs a full ERP system. But several signals suggest you’ve outgrown your current approach:

Data silos - your finance team, operations team, and sales team each have their own version of the truth, maintained in separate systems or spreadsheets
Manual reconciliation - staff spend significant time transferring data between systems, reconciling numbers, and correcting inconsistencies
Limited visibility - leadership can’t get a real-time, consolidated view of business performance without someone spending days compiling reports
Scaling pain - processes that worked when you were smaller are breaking down as volume, complexity, or headcount grows
Compliance pressure - regulatory requirements demand audit trails, controlled access, and reporting capabilities your current systems can’t provide
Integration failures - your applications don’t talk to each other, or they’re held together by brittle, custom-built integrations

If several of these resonate, it’s time to seriously evaluate ERP options.

Types of ERP deployment

Cloud ERP

The ERP vendor hosts and maintains the application in their data centres. You access it via a web browser. Updates are applied automatically.

Advantages:

Lower upfront cost (subscription-based pricing)
Faster deployment
Automatic updates and maintenance
Accessible from anywhere
Scales elastically

Considerations:

Ongoing subscription cost may exceed on-premise TCO over a long period
Less customisation flexibility (by design - this is usually a good thing)
Data resides with the vendor (important for data sovereignty under POPIA)
Dependent on internet connectivity

On-premise ERP

You purchase licences and run the software on your own infrastructure (or in a hosted data centre you manage).

Advantages:

Full control over data, customisation, and upgrade timing
No dependency on internet connectivity for core operations
May be required by specific regulatory or contractual obligations

Considerations:

High upfront capital expenditure
You’re responsible for infrastructure, patching, and maintenance
Upgrades are disruptive and often deferred, accumulating technical debt
Scaling requires additional hardware investment

Hybrid ERP

Some organisations run core modules on-premise while using cloud-based modules for less sensitive functions, or vice versa. This can be a pragmatic transitional approach but adds integration complexity.

For most South African mid-market businesses today, cloud ERP is the default starting point. The maturity of cloud platforms, combined with South Africa’s improving connectivity infrastructure, makes the benefits compelling. On-premise should be a deliberate choice driven by specific requirements, not a default.

Working with a business technology consulting partner helps you evaluate which deployment model aligns with your specific requirements, constraints, and growth trajectory.

Evaluation criteria

Functionality and fit

Start with your requirements, not the vendor’s feature list. Document your core business processes, identify the must-have capabilities, and distinguish them from nice-to-haves. Key areas to evaluate:

Financial management - general ledger, accounts payable/receivable, fixed assets, multi-currency, tax compliance (particularly South African VAT handling)
Supply chain and inventory - procurement, warehousing, logistics, demand planning
Manufacturing (if applicable) - production planning, BOM management, shop floor control, quality management
Human capital management - payroll (South African payroll is complex), leave management, recruitment, performance management
CRM and sales - pipeline management, quoting, order processing, customer service
Reporting and analytics - standard reports, ad hoc analysis, dashboards, regulatory reporting

No ERP will match your requirements perfectly out of the box. Evaluate how well the standard functionality covers your core needs and how easily gaps can be addressed through configuration (preferred) or customisation (cautiously).

Scalability

Your ERP needs to support your business not just today, but five to ten years from now. Evaluate:

Can the system handle your projected transaction volumes, user counts, and data growth?
Does the platform support expansion into new business units, geographies, or lines of business?
What’s the vendor’s roadmap - are they investing in the platform’s future, or is it in maintenance mode?

Integration

No ERP exists in isolation. It needs to connect with your other systems - e-commerce platforms, CRM, business intelligence tools, banking systems, industry-specific applications. Evaluate:

Does the ERP have native integrations with systems you already use?
What APIs and integration tools does it provide?
How complex and costly are custom integrations?

Consider how ERP integration fits into your broader data analytics and database engineering and web application engineering capabilities - your ERP will likely need to exchange data with customer-facing applications, reporting platforms, and data warehouses.

Total cost of ownership

ERP costs extend far beyond the licence or subscription fee:

Implementation - consulting, configuration, data migration, integration development, testing
Training - initial and ongoing user training
Customisation - modifications to meet unique requirements (a significant cost driver)
Infrastructure - for on-premise deployments: servers, networking, backups, DR
Ongoing support - vendor maintenance fees, internal support staff, third-party support contracts
Upgrades - for on-premise systems, major upgrades can cost as much as the initial implementation

Map out costs over a 5–7 year horizon for a realistic comparison between options.

Vendor stability

Your ERP vendor is a long-term partner. Evaluate their financial health, market position, customer base, and strategic direction. A vendor that’s acquired, pivots strategy, or goes into decline can leave you stranded on an unsupported platform.

For the South African market, also consider:

Does the vendor have a local presence or partner network?
Are there experienced implementation consultants available locally?
Does the system handle South African-specific requirements (VAT, BBBEE reporting, labour law compliance)?

The selection process

A structured selection process reduces the risk of choosing the wrong system:

Requirements gathering - document your business processes and requirements through workshops with key stakeholders from every affected department
Market scan - identify 4–6 potential vendors that appear to match your requirements and size
RFI/RFP - send a structured request for information to shortlisted vendors
Demonstrations - require vendors to demonstrate their software using your scenarios and data, not their standard sales demo
Reference checks - speak to existing customers in similar industries and of similar size, particularly in South Africa
Proof of concept - for your top 1–2 candidates, a limited proof of concept validates fit in practice, not just on paper
Contract negotiation - negotiate licensing, implementation terms, SLAs, and exit provisions before signing

Implementation pitfalls

ERP implementation has a well-documented history of cost overruns, delays, and outright failures. The most common pitfalls:

Insufficient executive sponsorship - ERP projects affect the entire organisation. Without visible, sustained leadership support, resistance and competing priorities will derail the project.
Excessive customisation - every customisation adds cost, complexity, and upgrade risk. Challenge every request for customisation by asking whether the business process can be adapted to the standard software instead.
Poor data migration - migrating dirty, inconsistent data into a clean new system is a recipe for disaster. Data cleansing must happen before migration, not after.
Inadequate testing - rushing through testing to meet deadlines is the most common cause of go-live failures. Budget sufficient time for unit testing, integration testing, user acceptance testing, and performance testing.
Neglecting change management - an ERP changes how people work every day. Without proper communication, training, and support, users will resist the new system and find workarounds that undermine its value.
Big bang vs phased rollout - going live with everything at once maximises risk. A phased approach - by module, by business unit, or by location - is usually safer, even if it takes longer.

Change management for ERP

Change management deserves special emphasis because it’s the factor most correlated with ERP success or failure:

Start early - change management begins during requirements gathering, not at go-live
Communicate the why - people need to understand why the change is happening and what’s in it for them
Identify champions - recruit influential users in each department to advocate for the new system and support their colleagues
Invest in training - role-specific, hands-on training delivered close to go-live. Generic classroom sessions months in advance don’t stick.
Provide go-live support - have extra support resources available for the first few weeks after go-live, when problems are concentrated
Measure adoption - track system usage, identify areas of low adoption, and address the root causes

Building your cloud architecture around ERP

For cloud ERP deployments, your ERP becomes a critical component of your cloud architecture. Consider how it connects to your identity management, networking, security controls, backup strategy, and disaster recovery plan. An ERP that’s isolated from the rest of your technology architecture will create new silos even as it eliminates old ones.

Make the right choice

Choosing an ERP is a decision you’ll live with for a decade or more. Taking the time to evaluate thoroughly, select carefully, and implement methodically pays dividends for years. Rushing the decision because of pressure to “just pick something” is how organisations end up with expensive systems that don’t fit.

Contact our team to discuss your ERP evaluation. We’ll help you define requirements, assess options, and plan an implementation that delivers the efficiency, visibility, and scalability your business needs to grow.