Manifesto
ERP transformation would always be a gamble. We refused to accept that.
Most ERP projects start unmeasured: readiness is guessed, scope is assumed from interviews, decisions hinge on a consultant. The result: overruns, needless modules, unadopted systems. There is a better way.
What is the MindDX approach?
The MindDX approach is a way of working that starts ERP/CRM decisions with measurement rather than brand preference: maturity is measured first, scope is then discovered from evidence, and every step leaves a traceable artifact that feeds the next one. This page explains that stance and its order — how the measuring is done is on the methodology page, what comes out of it is on the sample outputs page.
What we see
The enemy: transforming blind
Blind start
Big-bang projects launched with no objective answer to “are we ready?”.
Assumed scope
Scope guessed from interviews, not data; surprises and needless modules erupt in UAT.
Person-bound knowledge
Every decision hinges on a consultant; knowledge stays in people and walks out the door.
Our convictions
Measure first. Then transform.
- You can't transform what you haven't measured.Every journey starts with a maturity measurement (Checkup).
- Scope is not assumed, it's discovered.Real need surfaces through evidence, not interviews.
- Design on evidence, not opinion.Every design decision rests on the prior step's evidence.
- Knowledge must compound in the system, not in people.Every step produces a traceable artifact.
- AI drafts, an expert approves.AI does the repetitive work; a consultant reviews the critical calls.
- Transformation is not a project, it's ongoing maturity.The score is re-measured each release and climbs.
- Transparent pricing is trust.A delivery with a fixed scope sells at a fixed price — no man-day surprises.
The method
From conviction to method: five steps
A stance is only worth as much as the sequence it turns into. These five steps are the backbone of every MindDX engagement — and their order is not a preference but a dependency: each step consumes the previous one's output.
Measure
Before watching demos or collecting proposals, put the current state into numbers: how much of the process is written down, how clean the master data is, who owns which decision. Without measurement every later step rests on a guess.
Diagnose
Turn the measurement into a finding. “Stock accuracy is low” is an observation; “which warehouse and which product group concentrate the post-count corrections” is a diagnosis. The diagnosis tells you which problem is worth solving.
Write the criterion
Write the definition of success before you start — with a number and a date. “Going live” is not a success criterion; “month-end close drops from five working days to two” is. The criterion must be verifiable independently of the vendor.
Order phases by dependency
Let technical dependency set the phase order — not module appetite or the vendor's delivery calendar. If a phase cannot run without the previous phase's output, the order is not negotiable.
Tie acceptance to evidence
At the end of each phase the record should not read “it works”, but “this scenario, with this data, was run by this person and passed”. Where acceptance is not tied to evidence, the handover meeting turns into a debate.
The product chain
From measurement to live support: six steps, one chain
The output of each step is the input of the next — you never start from scratch.
MindDX Checkup
Measure your digital and AI maturity across the technology, process and leadership dimensions. Receive an expert-reviewed, decision-ready report.
MindDX Discover
Clarify your real needs with AI-assisted discovery; turn them into a prioritized, clear digital roadmap.
MindDX Design
Your implementation plan, configuration steps and acceptance tests — tied to your roadmap and traceable.
MindDX Train
Your team is ready for the new system: role-based training documents, quizzes and completion certificates — participants join by personal link, no account needed.
MindDX Process
The process x-ray: verifies with event data that the transformation actually works — by measurement, not by declaration.
MindDX Support
Support grounded in the knowledge base of the system you bought — we stay at your side after go-live.
The difference
Old way versus the diagnosis-first way
The two paths do not do the same work in a different order; they take the same decisions at a different level of information. The gap becomes visible when you look at it decision by decision.
| Decision | Old way | Diagnosis-first way |
|---|---|---|
| Scope | At proposal time, with the least information | After measurement, based on findings |
| Product selection | First question: which brand? | Last question: which capability, by which criterion? |
| Phase order | By the vendor's delivery schedule | By technical dependency |
| Acceptance criterion | “We went live” | Written scenario + evidence + named approver |
| Weight of the budget | On setup and mechanical work | On diagnosis and decision quality |
| Owner of the risk | Entirely the customer | Shared, tied to the criterion |
Selection discipline
Not a product name — a capability category
The most visible consequence of the diagnosis-first path is where product selection sits in the sequence. The decision is made not with a brand name but with three parts: which capability, by which criterion, under which precondition.
That triad also generates the questions you put to the vendor — and those questions become the skeleton of the specification. The brand question does not disappear; it moves to the end. Whether a product is the right choice is a question that can only be answered once capability and criterion are written down.
A concrete example
Capability
“Bill-of-materials management” is a capability category.
Criterion
“Can revision history be kept on a multi-level BOM?” is that category's criterion.
Precondition
“Product master data must be de-duplicated” is that capability's precondition.
The long-form account of this approach — five steps, comparison and examples: Diagnosis-first ERP: what the new way looks like in practice
Behind the scenes
An AI agent behind every step — the human's role varies by product
Each agent takes on the repetitive work of one module. What the human does there VARIES by product — on some deliverables a consultant reviews and approves, on others the entitled customer generates it themselves. The “human role” column below is read from the assurance registry; it is not written separately for this page.
| Agent | What it does | Which decision it supports | The human's role | Where the output lives |
|---|---|---|---|---|
| Diagnostic Agent | Measures maturity across 8 dimensions and reports it with a confidence score | Where to start — which dimension to tackle first | An expert consultant reviews and approves — final after review | MindDX Checkup |
| Discovery Agent | Surfaces the real need from evidence and writes it up as fit/gap | Scope — what standard covers and what needs adaptation | Self-service; consultant-guided on older Odoo versions | MindDX Discover |
| Audit Agent | Scans the installed system department by department and produces an action list | What to fix first in the existing implementation | A consultant reviews and approves | MindDX Audit |
| Design Agent | Writes the configuration instructions and the acceptance tests | How the setup is done and what counts as “passed” | The entitled customer generates it; consultant approval is stamped on the document | MindDX Design |
| Training Agent | Produces role-based training documents and quizzes | Who needs to learn what — and whether they did | The entitled customer generates it; quizzes are scored deterministically and results are visible to consultant and manager — no consultant approval | MindDX Train |
| Verification Agent | Derives the actual process flow from event data | Whether the transformation actually works — by measurement, not declaration | Partner (ProcessMind) delivery, consultant-guided | MindDX Process |
Why MindDX
Your trusted advisor — with four assurances
Unbiased measurement
Our measurement and discovery steps are solution-independent — you start from your company's reality, not through a vendor's lens.
Supervised AI
Speed from AI, accountability from humans: your measurement reports (Checkup and Audit) are reviewed by our experienced consultants.
Regional compliance depth
Local and regional regulations are observed at every step — GDPR compliant with EU (Frankfurt) data residency; your reports are suitable for government support program applications.
Transparent pricing
The price is given once what you get is written down, and it does not move unless the scope moves. No surprise costs, no surprise man-days.
Frequently Asked Questions
About our approach
What does the “measurement-first” approach mean?
Why organisation and interaction first, technology second?
Is MindDX software or consulting?
Don't you sell a specific ERP/CRM?
Is MindDX an AI tool?
What this unlocks
From chaos to confidence
- A measured startYou know where you stand and where to start by score, not intuition.
- Less reworkWhen scope fits reality, surprises, needless modules and overruns shrink.
- Adoption that sticksEvidence-based design and role-based training make the system actually get used.