Is your business ready for ERP? Start with these questions.

The short answer: you are ready to explore ERP when the business can describe a meaningful operational problem, name people who understand the current work and make decisions about the desired change. You do not need a perfect process map or pristine data before the first conversation. You do need enough honesty to see where assumptions, duplicate capture and workaround habits are shaping the result.

ERP is often discussed as a software decision. In practice, it is also a change in how work is recorded, approved and seen across a business. The early questions should therefore help you decide whether the next step is process improvement, data cleanup, systems integration, an ERP implementation or a smaller project that removes a specific bottleneck.

Start with the work, not the module list

Choose one recurring business task and follow it from start to finish. It might be an enquiry becoming a quotation, a sale becoming an order, stock being received, a purchase being approved or a customer requesting account information. Ask who starts the task, what information they need, where they record it, who checks it, what exceptions occur and how the next person knows what to do.

This exercise exposes whether the problem is missing information, unclear ownership, repeated data entry, poor visibility or a system boundary. It also stops an ERP conversation from becoming a list of fashionable modules. A module is useful only when it supports a defined operating need and a team can own the decisions around it.

Look for the workarounds, too. Spreadsheets, shared inboxes and chat messages are not automatically a failure. They can reveal a useful local process. The question is whether they create avoidable risk, duplication or delay at the scale the business now needs to manage. Preserve what works; change what prevents the next step from being dependable.

Look at systems and data without pretending they are simple

Make a plain inventory of the systems that hold important information. For each one, ask what it is the source of truth for, who owns access, which fields are trusted and how information leaves or enters it. This is more useful than assuming every platform can connect cleanly. An integration may depend on API access, exports, permissions, data definitions and business rules that have not yet been documented.

Data readiness is similarly practical. Which records are duplicated, incomplete or out of date? What would a user need to search, report on or approve? Who is accountable for correcting information before it is migrated or connected? A new platform cannot make an unclear definition reliable on its own. Data cleanup, governance and exception handling are implementation work, not an afterthought.

When people or customer information is involved, make privacy and access questions part of discovery. Decide what personal information is needed for the task, who should be able to see it and how requests or corrections would be handled. This is a design and operating responsibility, not a badge a software project can grant.

Choose one priority and one owner

ERP projects become difficult when every operational wish is treated as equally urgent. Select a priority that has a visible business reason, such as reducing a repeated hand-off, gaining reliable stock visibility, standardising an approval or making a customer service step easier to track. Define the people affected and what evidence would show the change is working in the real process.

Then name an owner who can make decisions or bring the right people into the room. This is not necessarily the most technical person. It is someone with enough context and authority to resolve trade-offs about process, policy, timing and adoption. Without this ownership, important choices are likely to return as late rework.

Use the answers as a conversation starter, not a fabricated readiness score. If the task and owner are clear but data is uncertain, discovery can focus on the data. If the process itself is unclear, map it before selecting a platform. If the need is limited to one hand-off, a targeted integration or workflow improvement may be a better next move than a broad ERP programme.

Our business readiness questions turn these four areas — website, systems, data and priority — into a short self-assessment. They offer practical next steps in the browser. They do not send your answers anywhere automatically or claim to diagnose your business.