Quick answer
ERP projects connect processes that may currently live in separate spreadsheets and teams. Before asking for software, map how an order, service request or stock movement passes between sales, operations, finance and management.
Practical scope
For each step, identify who enters data, who approves it and which record should be authoritative. List the reports the business actually uses, with sample fields and calculation rules. Historical data may need cleaning before migration; decide what must move and what can remain in an archive.
Rollout is an operational change. Ask vendors how they will run workshops, configure or develop workflows, test real scenarios and train each team. Consider a phased launch rather than changing every department at once. Agree acceptance criteria, ownership of data and a support plan for the first months after go-live.
What to define before requesting proposals
- End-to-end processes and authoritative records
- Approvals, exceptions and management reports
- Data cleaning, migration and reconciliation
- Phased rollout, training, acceptance and support
Questions to ask service providers
- How will workshops turn current work into system rules?
- Which real scenarios form acceptance tests?
- Who owns data correction and change management?
How to assess the answers
Treat ERP as an operating change, not only software installation. A phased scope with named process owners reduces ambiguity and launch risk.
Related planning guides
Next step: Put these decisions into one project brief, then ask providers to respond to the same scope.