MindDX Assess · paid entry
Decide first. Then build.
Assess lets you decide with evidence what needs to change, why and in what order — before you invest in the transformation. Fixed fee, consultant-led, software-independent.
The scan shows where you are. Assess shows why you are there, what needs to change and what should happen next.
Inputs
Don’t just tell us how you work. Show us.
The best evidence shows how the work actually runs. We start with what you have and complete the rest together.
MindDX consultants watch and review screen recordings; a finding enters the evidence register only with consultant approval.
How it works
Five steps, one decision.
- 01Start: the route is set — new system or live system — and the scope boundary is drawn.
- 02Checkup: a consultant-approved digital maturity baseline is produced.
- 03Evidence: documents, data, recordings and interviews are gathered; each finding is tied to its source.
- 04Analysis: current-state findings, risks, priorities and improvement opportunities, where the evidence supports them.
- 05Decision: the Validated Scope is presented; the next step is yours.
Assess is completed in about two weeks (around 10 working days). We set the session dates together, around your team's calendar; the start and end dates follow from that plan.
ProcessMind × MindDX: Process visibility from partner technology; the decision stays with MindDX.
MindDX uses ProcessMind as partner technology in process intelligence and process mining work. ProcessMind is not a module of MindDX Platform. Within Assess, where applicable, our consultants may use ProcessMind to support current-state process visibility from process evidence.
What remains MindDX’s work
- Evidence review
- Findings
- Scope
- Decision
A process view is not a standard output of every Assess; it is used where the evidence allows. Assess does not include a ProcessMind licence in your name.
About ProcessMindDeliverables
What you hold at the end of Assess.
Digital maturity baseline
The consultant-approved Checkup output.
Evidence register
The findings, recorded with their sources.
Current-state findings
How the work really runs today; with a current-state process view where applicable.
Risks and improvement opportunities
Risks seen early and the opportunities that carry value, where the evidence supports them.
Priorities
What to address first, and what later.
Validated Scope
A Validated Scope for a new system; a Validated Improvement Scope for a live one. The input to an Implement proposal.
What does an Assess output look like?Synthetic example
The schematic shows the structure of the outputs an Assess delivers.
| Source | Finding | Status |
|---|---|---|
| SOP · PDF | Approval step documented but skipped on the floor | Consultant-approved |
| Report · XLSX | Stock counted weekly, planning runs daily | Consultant-approved |
| Screen recording | Order entry repeated in two systems | Under review |
| Finding | Risk | Priority |
|---|---|---|
| Stock counted weekly, planning runs daily | Plan not based on real stock | 1 |
| Order entry repeated in two systems | Data inconsistency | 2 |
| Approval step skipped on the floor | Control gap | 3 |
- Priority 1 · Inventory and warehouse
- Priority 2 · Planning
- Out of scope · Finance
Next step
Continuing to Implement is a separate decision; it does not start on its own.
Method
What is the difference between process validation and scope validation?
- Process validation
- Shows with evidence how the work actually runs today: interviews, observation and records. The process on the floor, not the one in the document.
- Scope validation
- Sets out, independently of any software, what changes, why and in what order. Its result is the Validated Scope.
The method, step by step
Why before the ERP project starts?
The importance of process and scope validation lies in the timing. Organisations often buy a system before changing how they operate; the project starts and the real scope only emerges later. The problem is not that these decisions are made, but that they are made late: a missing decision causes rework. That is why the commercial frame rests on the validated scope too: not man-days, but a fixed price based on the validated scope.
How is it done, step by step?
- Interviews and observation. Process owners and the users who actually do the work are interviewed; screenshots and short screen recordings show how the work is really done.Output in Assess: Current-state findings
- Process map with BPMN. The flow is drawn in a shared notation: tasks, decision points and responsibilities. BPMN is the standard process notation that business units and technical teams read the same way. BPMN in the glossaryOutput in Assess: A current-state process view, where applicable
- Gap / Fit against standard software capabilities. Requirements are compared with standard software capabilities: what the standard covers is separated from what remains a gap.Output in Assess: Not a standard Assess output; the full Gap / Fit is produced in Implement
- Evidence register. Each finding is tied to its source and enters the evidence register only with consultant approval.Output in Assess: Evidence register
- Prioritisation and risks. What to address first and what later is decided; risks become visible early, where the evidence supports them.Output in Assess: Risks and improvement opportunities · Priorities
- Validated Scope. What changes, why and in what order is brought together in one scope.Output in Assess: Validated Scope; on a live system, the Validated Improvement Scope
Common mistakes
- Beginning with a software demo.
- Documenting the process as it should be instead of the real one.
- Skipping the users who actually do the work.
- Leaving data ownership and data quality for later.
- Turning every exception into customisation.
Scope validation in a small business
The logic is the same, only lighter: fewer people are interviewed and the evidence register is shorter. Start with the order-to-cash and purchasing flows; money and materials pass through these two.
The consultant’s role: software-independent validation
The consultant validates process and scope independently of any software: Assess does not start from a product, it starts from evidence. Findings enter the evidence register only with consultant approval; the product decision comes after the evidence, that is, after the Validated Scope.
Two routes
New system or live system?
Assess follows one of two routes. They are alternatives; both are not run by default. The fee is the same on either.
New system
Before you select or implement a new ERP or business system.
- Checkup
- Discover Scope
- Current-state view · where applicable
- Validated Scope
A Validated Scope that becomes the input to an Implement proposal.
Assess for a new systemLive system
When an installed system is not delivering the expected result.
- Checkup
- Audit
- Process evidence · findings
- Validated Improvement Scope
A Validated Improvement Scope showing what to improve.
Assess for a live systemFirst the process is validated: how the work actually runs today is evidenced through interviews, observation and records. Then the scope is validated: what changes, why and in what order is decided. In Assess this runs in five steps and ends with the Validated Scope; it is software-independent, and the product decision comes after the evidence.
Assess is completed in about two weeks (around 10 working days). We set the session dates together, around your team's calendar; the start and end dates follow from that plan.
At the end of Assess you receive the digital maturity baseline, the evidence register, current-state findings, risks and improvement opportunities, priorities and the Validated Scope. The full Gap / Fit and target-state process design are not standard Assess outputs; they are produced in Implement.
Assess is there to see this before the project. If the evidence does not support an area, that area is deferred or kept out of scope with its reasons; the Validated Scope contains only what the evidence supports. Continuing to Implement is a separate decision; it does not start on its own.
Because Assess is a decision product, not a sale of hours. Its scope is defined up front; the fee does not grow with time spent.
No. Assess is complete in itself; Implement does not start on its own. If you continue, the net amount you actually paid for Assess is credited against Implement.
The Assess outputs are delivered to you and remain yours to use. The Checkup methodology, the instrument and the MindDX method remain MindDX intellectual property.
The scan shows where you are; it is online and free. Assess shows why you are there, what needs to change and what should happen next; it is consultant-led, evidence-based and fixed-fee.
Start with what you have: process documents, reports, system exports, screenshots or short screen recordings. We agree on what is missing in the first conversation.
Within Assess, where applicable, MindDX consultants use ProcessMind. Assess does not include a ProcessMind licence in your name.
Not for every Audit. An Odoo Audit can measure the live installation using read-only methods when the required access has been separately authorised and established; a consultant agrees the access arrangements with you. For Zoho and abas ERP, Audit does not require direct access to your installed system: it is conducted without a direct live-system connection, using structured questionnaires, customer-provided documents and consultant evaluation. Audit’s measurement methods make no changes to your system; the report becomes final after consultant review.
Assess is a fixed fee — no hourly or day rates, and the same fee on the new-system and the live-system route. The fee for your region is confirmed with a consultant first.
Yes. Pre-Assess is a free pre-assessment session of about an hour with the MindDX team: your current systems and needs are reviewed for the first time and, where appropriate, you receive a tailored Assess proposal. Pre-Assess is optional; you can also start Assess directly.
Other firms do a free pre-analysis. Why pay for MindDX Assess?
Because the purpose is different. A free pre-analysis is usually done to qualify a sale. Assess is done to give you a decision.
| — | Typical free pre-analysis | MindDX Assess |
|---|---|---|
| Purpose | Qualify the opportunity, prepare a proposal | Give you an evidence-based decision |
| Evidence | Mostly conversation and assumption | An evidence register built from documents, data, recordings and interviews |
| Process visibility | Usually based on description | A current-state view from process evidence, where applicable |
| Verification | The sales team’s reading | Consultant-approved findings |
| Findings | Often built around one product | Tied to their source and reasoned; risks and priorities where the evidence supports them |
| Neutrality | Can be shaped by the product to be sold | Software-independent; the product decision comes after the evidence |
| Outputs | Often stays an appendix to a proposal | Delivered to you and remain yours to use |
| Next step | A proposal | A validated scope; if you continue to Implement, the net Assess amount you paid is credited |
What Assess is not
- A free presales call
- Proposal preparation
- A free workshop
- Day-rate consulting
Make the decision with evidence.
Start Assess, or talk to a consultant first; together we will establish which route fits.
MindDX AssessFixed fee · no hourly or day rates
If you continue to Implement, the net amount you actually paid for Assess is credited against Implement.
Want to see where you stand first? Free Digital Maturity Scan
Would you rather talk to our team first? A free pre-assessment session of about an hour: Pre-Assess