Short answer
Start not with a list of programs but with your own processes: describe how you work, what is mandatory, which integrations you need and how many users there will be. Then compare solutions by how well they fit your processes, the total cost over several years, integration options and vendor support.
Steps
1. Describe your processes. Orders, purchasing, inventory, production, invoices — how they work today and how they should work in future.
2. Define the must-haves. What must the system definitely do? What is “nice to have”?
3. Integrations. Which systems must it connect to — accounting, online store, bank, e-invoicing, industry systems?
4. Users and permissions. How many people will work in it, in which roles, and do customers or partners need access?
5. Total cost. Licences, rollout, customisation, maintenance — for at least 3–5 years.
6. A demo with your own data. Ask to see your typical process, not a standard presentation.
Warning signs
- “We’ll customise it later” about your critical process.
- It’s unclear how the data will be migrated.
- Integrations are promised, but there are no examples.
If no solution fits
If customising an off-the-shelf ERP costs almost as much as a new system, consider a custom system. A requirements description will be useful either way — see how to write a technical specification.