The feasibility study aims to find out if ERP5 core model can represent all the flows of resources (products, services, money,...) which need to be managed for a given business or if ERP5 extensions are required.

In general, no extensions should be required because standard ERP5 framework is sufficient to cover most business cases. However, since ERP5 is an ever evolving open source framework, it is not because the standard framework does not cover a specific business case that ERP5 should not be used. Extending ERP5 core is sometimes only a matter of days for an experienced engineer. Thus the cost of ERP5 extension is usually neglectable compared to the cost of the complete implementation.

The feasibility study should be conducted by a business analyst with an experience of multiple implementations of ERP5 projects and may sometimes require help from the designers of ERP5 core.

After this phase, it is sometimes necessary to set up an ERP5 prototype and to configure some key features so that users and managers can test the solution by handling real data. Thanks to our rapid application development environment and to our high level workflow engine, this kind of prototyping does not last more than a few days and can be achieved during an initial ERP5 training.

Prototyping is the right way to demonstrate all the capabilities of ERP5 and to be sure to make a good decision.