ERP consulting: frequently asked questions

Consulting decides what the system should do and how the project should be structured. Implementation builds it. Consulting produces requirements, a gap analysis, a concept and a roadmap with an estimate. Implementation produces a configured, tested, live system. Consulting can stand alone, for instance when you are still choosing a system; when we implement, it forms the first phase of the project.

No. If your requirements point to a different system or to keeping what you have, we say so. Our consulting fee does not depend on a subsequent implementation, and the recommendation reflects that.

For a single company with a handful of processes, a few weeks from first workshop to roadmap. For groups with several entities and many processes, two to three months. The length is driven by the number of business areas and how quickly your team can attend workshops and review documents.

Time from the people who do the work, in half day workshops per business area, and a few hours per week from a project lead who can make or obtain decisions. Examples of your documents and reports, and access to your current systems or exports from them. The more of this is ready before we start, the faster the phase runs.

A requirements document per business area, a gap analysis against standard Odoo with a recommended approach for each gap, a target concept your team has validated in a demo database, and a phased roadmap with an estimate and the internal resources each phase needs. These documents are yours whether or not we go on to implement.