Why three years
An industrial ERP is mostly paid for after signature: configuration, data migration, training, upgrades and operations. Three years cover the project, the first year of use and at least one upgrade.
Year 1 — project
- Diagnosis and pilot
- Configuration and custom work
- Data migration
- Training and cutover
- Subscription
Year 2 — use
- Subscription
- Operations and support
- Data corrections
- Requested improvements
Year 3 — evolution
- Subscription
- Operations and support
- Upgrade
- Regression testing
The cost lines to price
- Subscription or licenses, per user, module or environment.
- Diagnosis, scoping and pilot.
- Configuration and custom development.
- Migration and cleansing of master data.
- Interfaces: CAD, EDI, machines, carriers, bank.
- Training for key users and operators.
- Hosting, backups, monitoring and support.
- Upgrades and regression testing.
Cost drivers
The number of users matters less than the number of distinct flows, data quality, the number of interfaces and the share of custom work. A development is paid twice: when it is built, then at every upgrade.
Hidden costs
Your teams’ time is the first forgotten cost: workshops, testing, data migration, training and double entry during cutover. Add the productivity dip of the first weeks and the data corrections found in production.
Comparing two offers
Build a table by cost line and by year, on the same scope and at the same date. An offer without data migration or upgrades is not cheaper: it is incomplete.
Limits
We do not publish a typical amount: without a diagnosis, an average figure misleads more than it helps. Orders of magnitude are given after scoping, in days and by cost line.