How to choose an ERP system for a growing business

Choosing an ERP is one of the most consequential technology decisions a growing business will make. Get it right and you build a foundation that supports the next five years of growth. Get it wrong and you spend those years working around a system that was never built for how your business actually operates. The problem is that most ERP selection processes focus on the wrong things.

What matters most: scalability, not features

Feature comparison spreadsheets are the default tool for ERP selection, and they are almost always misleading. Every modern ERP can generate an invoice, run a trial balance, and produce a VAT return. The differences that matter are structural: can the system handle a second entity without a separate installation? Can it support a new warehouse or a new currency without a reimplementation? Will it still perform when your transaction volume doubles? These are scalability questions, not feature questions, and they rarely appear on vendor checklists. A system that does everything you need today but cannot grow with you is a system you will replace in three years — and replacement costs are not just financial. They include months of disruption, retraining, and data migration risk.

The discovery process

Before you evaluate any software, you need to understand your own business processes with uncomfortable clarity. What does your order-to-cash cycle actually look like? Where do handoffs fail? Which reports does your leadership team rely on, and how much manual work goes into producing them? A proper discovery process maps your current workflows, identifies pain points, and defines what success looks like in measurable terms. This is not a technology exercise — it is a business exercise. Skip it and you will end up automating broken processes rather than fixing them. The best ERP implementations start with weeks of discovery before a single line of configuration is written.

Build vs buy vs configure

Growing businesses face three paths. Building a custom system gives you exactly what you want but saddles you with ongoing maintenance, security patches, and the risk that your one developer leaves. Buying an off-the-shelf product is fast but forces your processes into someone else's assumptions. The middle path — configuring a flexible platform to match your workflows — is usually the right answer for businesses in the mid-market. Modern cloud ERP platforms are designed to be configured, not customised. The distinction matters: configuration uses the vendor's supported tools and survives upgrades. Customisation writes code around the vendor's architecture and breaks with every update. If a vendor tells you their system needs heavy customisation to fit your needs, that is not a strength. It is a warning.

When to engage a partner

Most growing businesses do not have an internal team with deep ERP implementation experience, and they should not pretend otherwise. Engaging an implementation partner is not an admission of weakness — it is a risk management decision. A good partner brings pattern recognition from dozens of similar projects: they know which configuration choices cause problems at scale, which integrations are reliable, and which training approaches actually stick. The key is to engage early, during discovery rather than after you have already selected a product. A partner who only appears at implementation is a contractor. A partner who shapes the selection process is an advisor, and advisors deliver better outcomes. Look for partners who ask difficult questions about your business before they talk about software.