Skip to content

MindDX Assess

Validate what will be done before implementation starts.

If the scope is not clear, the price cannot be either. Assess measures first and binds the scope to evidence; only then is a price fixed.

€3,500 + VAT · fixed fee

For engagements in Türkiye.

In this region sales run through MindDX partners; the list price is confirmed with the partner for your region.

New Implementation

Software decisionMade
Implementation readinessOpen

How many of these are written down and approved today?

  1. 01Scope
  2. 02Process
  3. 03Need
  4. 04Ownership
  5. 05Data
  6. 06Decision
  7. 07Risk
  8. 08Organisation

Composition

MindDX Checkup + MindDX Discover

Only the scoping step of Discover.

Validated Scope
Variant
New Implementation
Composition
MindDX Checkup + MindDX Discover — Only the scoping step of Discover.
Output
Validated Scope
Partner pricing
In this region sales run through MindDX partners; the list price is confirmed with the partner for your region.
Control
Consultant review · expert approval where required

NOT included in scope

  • Blueprint
  • Discover Deep Dive
  • MindDX Design
  • MindDX Implement
  • MindDX Transform

How it runs

Checkup is a self-service survey reviewed by an expert; Discover Scope structures the scope department by department. On older Odoo versions the step is consultant-guided.

What happens next

The Validated Scope is the input to an Implement proposal. That is not a commitment: not every Assess turns into an Implement, nor does it need to.

On which systems

Checkup is software-independent and works across all five systems. Scope discovery is self-service on Odoo 19, Zoho and abas, and consultant-guided on older Odoo versions.

Via a partnerTalk to a consultant (20 min)View the guide

Live System

InstallationComplete
Usage effectivenessNot measured

How many of these are measured and backed by evidence today?

  1. 01Modules
  2. 02Departments
  3. 03Process loss
  4. 04Adoption
  5. 05Customisation
  6. 06Custom modules
  7. 07Licensing
  8. 08Data quality

Composition

MindDX Checkup + MindDX Audit

Scope is derived by scanning the live system.

Validated Improvement Scope
Read-onlyEvidence-boundConsultant-controlledTraceable
Variant
Live System
Composition
MindDX Checkup + MindDX Audit — Scope is derived by scanning the live system.
Output
Validated Improvement Scope
Partner pricing
In this region sales run through MindDX partners; the list price is confirmed with the partner for your region.
Control
Consultant review · expert approval where required

NOT included in scope

  • Discover Scope
  • Blueprint
  • Discover Deep Dive
  • MindDX Design
  • MindDX Implement
  • MindDX Transform

How it runs

Alongside the Checkup survey, the live system is scanned read-only: the customisation inventory, module and usage data are read. There is no write path into the system; the report becomes final after consultant review.

What happens next

The measurement can lead to several actions and NONE of them is automatic: no action may be needed, configuration may be enough, Train · Process · Support · Design · Implement may fit, or several together. You decide; MindDX prepares the evidence.

On which systems

The read-only scan of the live system is for Odoo installations today; on Zoho and abas the measurement is questionnaire-based.

Via a partnerTalk to a consultant (20 min)View the guide

What Assess is not

  • A free pre-sales call
  • A workshop
  • An Odoo partner assessment
  • An attempt to replace your current partner
  • A tool for selling a re-implementation

MindDX is neutral towards the software vendor, your current partner, your in-house IT team and your earlier implementation decisions. The customer report recommends no product. That does not mean MindDX is not an implementer — we do implement, and we say so plainly here.

Where the measurement comes from

The digital-maturity measurement is a software-independent capability and comes inside both Assess variants; it is not a separate buying decision. Measurement alone does not validate scope — what validates scope is Assess itself. MindDX Checkup

Frequently Asked Questions

About the products

Are MindDX Assess and MindDX Checkup the same thing?
No. Checkup is a software-independent maturity MEASUREMENT and can also be bought on its own. Assess is a commercial product: on top of Checkup it adds Discover Scope or Audit depending on your situation, and produces a validated scope. Checkup measures; Assess measures and binds the scope to evidence.
Can I buy both Assess variants together?
No — they are alternatives, not complements. A company is either setting up a new system or already running one. Selling both would mean billing the same measurement twice.
Is the Blueprint included in Assess?
No. The Blueprint is the output of Discover's deep-dive step and is produced within Implement. Assess validates the scope; it does not produce a design document.
Why is there no figure outside Türkiye?
Because no list price has been fixed for that region, and guessing one would be a commitment we cannot keep. In this region sales run through MindDX partners and the price is confirmed with the partner.
How is scope defined before an ERP project starts?
Scope is defined from how processes actually run today, not from a list of desired features. In order: (1) map which departments run which processes; (2) write down the tools each process uses today — including side spreadsheets and informal approval routes; (3) separate what standard software covers from what it does not (fit/gap); (4) decide each gap: change the process, adapt the software, or leave it out of scope; (5) bind the decisions, with their reasons, into a written scope document. Step 2 is the critical one: unrecorded flows (a list kept in a spreadsheet, a verbal approval) come back as "scope changes" during testing if they are not written down. MindDX runs these steps inside Assess, and the output is a validated scope.
How is an ERP fit-gap analysis done?
Fit-gap is done at the level of process steps; done at module level it misleads. For each process step, ask three questions: does the standard software cover this step as-is (fit), does it not (gap), or can the process be adapted to the standard (alignment)? Each gap is then classified — a legal requirement, a real business differentiator, or merely habit. That distinction matters: turning habit-driven gaps into customisations raises the cost of every future upgrade, permanently. The output is a list carrying a decision and a reason for each gap; a gap with no decision is not scope, it is open risk. At MindDX this analysis happens inside Discover, and each gap is given an identity and carried into the design documents.

All questions and answers →