Map the operating pressure
List the workflows causing delay, duplicate entry, approval uncertainty, stock blind spots, payroll difficulty, weak reconciliation or late management reporting.
Identify owners
Each critical process needs a responsible business owner who can confirm policy, exceptions and acceptance criteria. ERP cannot resolve internal ownership ambiguity by itself.
Inventory data and documents
Know where customer, supplier, employee, item, financial and historical records live, how clean they are and what must legally or operationally be retained.
Clarify infrastructure and integration constraints
State whether on-premise, private cloud or managed hosting is required and list external systems that must exchange data with the ERP.
Prepare for user acceptance
Choose responsible users who can test real scenarios. Demonstration approval is not a substitute for workflow validation.
Prepare a discovery pack before asking for a final proposal
The most useful discovery pack is small but concrete: organization chart and legal entities, branches, user groups, critical workflows, current systems, data sources, approval matrix, required reports, integrations, deployment constraints, implementation owners and the decisions management expects the ERP to improve.
This does not require months of documentation. It gives the implementation team enough evidence to distinguish product configuration from migration, integration and engineering work—and it exposes unanswered internal questions before they become quotation assumptions.
Readiness is visible in ownership, not enthusiasm
An organization is more ready when process owners can make decisions, finance can approve opening positions, data owners can clean masters, users can attend acceptance testing, IT can provide infrastructure/integration access and management can resolve cross-department disagreements. None of those conditions are solved by purchasing software.
When one of those owners is missing, record it as a project risk with a date and responsible person. A transparent readiness gap is manageable; an invisible one usually appears later as rework or delay.