No more open-ended man-day invoices.Buy outcomes, not man-days.We offer Implement at a fixed price based on the validated scope.

Implement · Design and implementation

Take the validated scope to go-live ready.

Implement takes the human-approved Validated Scope as its input: Discover Deep Dive, Gap / Fit and Blueprint, Design, controlled implementation, Test & UAT, Train. The result is the Go-Live Ready state, accepted by human approval.

Output

Go-Live Ready · test and acceptance evidence · a prepared team

Capability familyNot every engagement includes every step; which ones apply is written into the Validated Scope. AI does not set the scope, the price or the go-live; people make those decisions.

01 · Within scope

Discover Deep Dive

Deep analysis within the validated scope. Needs and constraints become clear at process level.

02 · Output

Gap / Fit + Blueprint

Not a separate product: the output of the Deep Dive. It shows whether the need is met by standard capability; where custom development is required, it becomes justified and controlled.

03 · Capability

Design

Approved decisions become the technical design; Design is the input to configuration and development.

04 · Implementation

Controlled implementation

Configuration; adaptation or development only where the scope requires it. Every change is tied to the approved design and proceeds under consultant control.

05 · Acceptance

Test & UAT

Tests are tied to acceptance criteria; user acceptance testing is run with the business. Acceptance is given by human approval.

06 · Capability

Train

Team readiness. Users and process owners are prepared for the new way of working.

Fixed price based on the validated scope.

The Implement proposal follows from the scope validated in Assess and confirmed by human approval. No hourly or day rates are published.

What you receive

Discover Deep Dive
A gap/fit analysis and the Blueprint.
Design
A configuration guide, a technical design (only where gaps require development), and test and acceptance scenarios.
Controlled implementation
Configuration; adaptation or development where the scope requires it, tied to the approved design.
Train
Training documents and a deterministically scored exam; results are visible to the consultant and the manager.
Go-Live Ready
Test and acceptance evidence, a prepared team; acceptance is given by human approval.

No hourly or day rates.Fixed price based on the validated scope.

The price rests on the scope validated in Assess; it is not fixed until the scope is validated.

Consulting method

What is ERP implementation consulting, and how do you choose a consultancy?

ERP implementation consulting
The service that guides a company in setting up its ERP software around its own processes and putting it to use: scope, configuration, adaptation or development where needed, data migration, integration, training, testing and go-live. The aim is not to install software but to turn a validated scope into a working system.
Validated Scope
What will change, why and in what order, established with evidence and independently of any software before an implementation commitment. It is the output of Assess and the input of Implement.
Gap / Fit
The comparison of requirements with the capabilities of standard software: what the standard covers is separated from what remains a gap. At MindDX it is produced in Implement’s Discover Deep Dive, together with the Blueprint.
Services, phases, selection criteria and the contract

Why does implementation consulting matter?

In ERP projects, most problems come not from the software but from scope and preparation. Organisations often buy a system before they change how they work; the project starts, the real scope appears later, and a missing decision creates rework. The value of implementation consulting is that decisions are taken on time, with evidence and in writing.

Which services does implementation consulting cover?

  • Analysis and scope: Processes, existing systems and data are reviewed; what goes live, in what order and within which limits is put in writing.
  • Configuration: Company structure, product and stock settings, sales and purchasing flows, approvals and permissions are set up with the software’s standard settings.
  • Adaptation and development: Where the standard is not enough, tied to the approved design; without touching the core code, in a way that does not break upgrades.
  • Data migration: Data from the old system is cleaned, mapped and transferred; the transfer is rehearsed in a test environment.
  • Integrations: The ERP is connected to e-commerce, banking, e-document, production and reporting systems.
  • Training: Users are trained on their own processes, with their own data; key users are prepared to support the rest of the team.
  • Testing and user acceptance testing: Each process is tested end to end with realistic scenarios; acceptance is given by the people who will do the work.
  • Go-live and support: The go-live date, the final data transfer and the support plan for the first days are set in advance; in live use, questions and new needs are handled.

Which phases does an ERP implementation project go through?

  1. Validating the scope. What will change, why and in what order is established with evidence before an implementation commitment. At MindDX: Assess · the Validated Scope, the input of Implement
  2. Gap / Fit and solution design. Requirements are compared with standard capability; where custom development is needed, it is justified. Approved decisions become the technical design. At MindDX: Discover Deep Dive · Design
  3. Configuration and development. Configuration; adaptation or development where the scope requires it. Every change is tied to the approved design. At MindDX: Controlled implementation
  4. Data migration and integration. Data is cleaned, mapped, transferred and rehearsed; the connections are set up. At MindDX: Controlled implementation, as far as the Validated Scope sets it out
  5. Testing and acceptance. Tests are tied to acceptance criteria; user acceptance testing is run with the business side. At MindDX: Test and UAT · acceptance is given by human approval
  6. Training and go-live readiness. Users and process owners are prepared for the new way of working; the go-live plan is set in advance. At MindDX: Train · Go-Live Ready
  7. After go-live. Go-live is not an ending but a new measurement point: the live system is measured and improved within the agreed scope. At MindDX: Transform · Process and Support, together or separately

Consultant and customer team: who is responsible for what?

  • The consultant: Method, design, configuration and development where needed, integration, training and running the tests. The MindDX role is set by product and scope; the role and the scope are written explicitly into every proposal.
  • The customer team: Process owners and key users take the decisions and are responsible for cleansing and owning the data, the test scenarios and acceptance. The time the team sets aside for analysis, testing and training does not show in proposals, but it is there in every project.
  • Together: People take the scope and acceptance decisions. AI does not set the scope, the price or the go-live.

What should you look for when choosing a consultancy?

  • Method: Is the scope validated with evidence before the project, or does the work start from a software demo?
  • Pricing model: Is the price based on the days spent, or on a validated scope?
  • References in your sector: The experience of a company with similar processes shows far more than a prepared presentation.
  • Development policy: Is the choice between standard features, adaptation and development made together with the upgrade plan?
  • Data and integration: Who is responsible for data migration and the connections, and how are they rehearsed before go-live?
  • A local team: Training, testing and go-live need a team that speaks the same language and knows local regulation.
  • Roles: Is the work of the consultant and of your own team written explicitly into the proposal?

What should you check in the contract?

  • Scope: Is it written down what is included and what is out of scope, and what is the scope based on?
  • Basis of the fee: Is the fee tied to the days spent, or to the work to be done?
  • Scope changes: If the scope changes, how is the decision taken, and who approves it?
  • Deliverables: Which documents are delivered: the Gap / Fit and the Blueprint, the design, test and acceptance evidence, training documents?
  • Acceptance criteria: Against which criteria, and with whose approval, is acceptance given?
  • Data: Who is responsible for data migration and data ownership?
  • After go-live: How are support and upgrades continued?

Common challenges and success factors

  • Beginning with a software demo: the real scope appears after the project has started.
  • Over-customisation: rebuilding the old system in code over a standard process leaves a load that has to be moved at every upgrade.
  • Under-estimated data quality: if duplicate and inconsistent data is carried into live use, the new system looks unreliable from day one.
  • Leaving out the users who actually do the work.
  • Training left to the end: if users see the system for the first time in go-live week, both testing and training stay shallow.

Success factors

  • The scope validated with evidence before the project.
  • Decisions taken on time and in writing; every change tied to the approved design.
  • Standard features first; adaptation or development only with a reason.
  • Process owners and key users involved from start to finish.
  • Acceptance tied to acceptance criteria and given by human approval.

In small and mid-sized businesses

The logic is the same, only lighter: fewer people are interviewed and the scope is narrower. The right start is often a few core flows, for example order-to-cash and purchasing; money and materials pass through these two. A consultant adds value where regulation and e-documents, data migration, integration or a scope that will grow are involved, because these decisions are harder to correct later if they are not set up right from the start.

How is the cost set?

The cost of an ERP project is more than the licence: implementation consulting, data migration, integration, training, internal team time and an allowance for upgrades are items too. There are two models for the consulting fee: with man-day billing the invoice grows with time; a fixed price based on the validated scope ties the fee to the work to be done and requires the scope to be validated before the project starts. The real amounts follow from the validated scope.

The MindDX approach

At MindDX, implementation consulting starts from evidence, not from software. Assess first: the scope is validated independently of any software, and the output is the Validated Scope. Then Implement, at a fixed price based on the validated scope. The method is the same for the products in the solution portfolio, such as Odoo, abas, Zoho and Pipedrive; the MindDX role is set by product and scope.

Frequently asked

Frequently asked questions about Implement