The short answer: a business is ready for an ERP when its operations have outgrown spreadsheets — when the cost of disconnected data (errors, delays, duplicated work, decisions made blind) is visibly higher than the cost of implementing one system. Readiness is about process and commitment, not company size.
We implement ERP systems for a living, which gives us a strange incentive to tell every company "yes, you're ready." We won't. A mistimed ERP project wastes more money than almost any other IT decision an SME can make. Here is the checklist we actually use in discovery calls.
Seven signals you are ready
1. Your numbers disagree with each other
Sales says one figure, the warehouse another, accounting a third. When departments keep their own records, disagreement is not a discipline problem — it is an architecture problem. An ERP exists precisely to make a customer, a product and an invoice exist once.
2. Month-end closing takes weeks
If your accountant spends the first two or three weeks of every month reconciling the previous one, you are paying a permanent tax that an integrated system removes. Businesses we migrate typically close in days afterwards.
3. Stock levels are educated guesses
You promise delivery based on what the spreadsheet says, then apologise based on what the warehouse finds. Live inventory — with reservations and reorder points — is one of the fastest paybacks in any ERP scope.
4. Approvals travel by email and disappear
Purchase requests, discounts, leave, expenses: if the approval trail lives in inboxes, you have no trail. Auditors notice. So do fraudsters.
5. Growth is multiplying the manual work
Adding a second warehouse, a new branch or a new sales channel and the coordination overhead grows faster than the revenue. Manual processes scale linearly with headcount; systems do not.
6. Reporting is retrospective and hand-built
Management sees performance quarterly, assembled by hand, too late to act. If your leadership team is steering by the rear-view mirror, integrated data is the fix — dashboards are just the visible surface of it.
7. Compliance is starting to demand it
E-invoicing mandates, audit requirements, certifications, investor due diligence: sooner or later an external party requires records your current tooling cannot produce. It is far cheaper to be ready than to scramble.
Four signs you are not ready
Your processes are undocumented and contested. An ERP encodes processes. If nobody agrees what the process is, the implementation becomes the argument — at consulting rates. Map processes first; we do this in discovery precisely because it is the cheapest place to fail.
Leadership wants to delegate the project entirely. ERP implementations succeed when an owner or senior manager makes decisions weekly. If the plan is "IT will handle it", the system will faithfully automate the wrong things.
You expect zero process change. "Configure it exactly like our spreadsheets" is the most expensive sentence in ERP. Packages embody standard processes for good reasons; fighting all of them means paying custom-software prices for packaged software.
The motivation is a discount or a trend. A licence promotion or a competitor's announcement is not a business case. The business case is the checklist above, with numbers attached.
What to fix first if you are not ready
- Document the five processes that matter — order-to-cash, purchase-to-pay, inventory, payroll-adjacent workflows, reporting. One page each, written by the people who do them.
- Clean your master data. Duplicate customers, inconsistent product codes and dead SKUs will poison any migration. Deduplicating before an ERP project costs a fraction of doing it during one.
- Name an internal owner. One person with authority, time, and the ear of leadership. This role predicts success better than any platform choice.
How the decision usually goes
In our experience, companies of 10–50 people usually discover that two or three of the seven signals apply strongly — and start with a focused scope (inventory + invoicing, say) rather than a big-bang rollout. Companies of 50–500 usually have five or more signals and need the phased, pilot-first approach we describe in our process.
Either way, the first step is the same: a written assessment of your current operations. It is a deliverable we produce in one to three weeks, and it is yours to act on — with us or with anyone else.