Häufig gestellte Fragen
What is ERP readiness and why does it matter?
ERP readiness describes the organisational, data-related and resource-related maturity a company needs to pull off an ERP project successfully — regardless of which software is chosen later. Studies and project reviews have shown the same pattern for years: ERP projects rarely fail because of the technology, but because of unclear processes, poor master data, missing management support and underestimated internal effort. Companies that honestly assess their own maturity before the selection enter vendor conversations with realistic expectations and avoid burning expensive consulting days on groundwork they could have done themselves.
How does this readiness check work?
The check asks 12 questions across four dimensions: processes and organisation, data and systems, resources and budget, and strategy and change. Each answer scores 0, 1 or 2 points, for a maximum of 24; the evaluation shows the total, the score per dimension and recommends concrete next steps with matching guides for the weakest areas. The questions reflect the factors that most frequently decide between success and failure in project reviews. Your answers are processed entirely in your browser and are not transmitted to us or to any third party.
From what score should a company start the ERP selection?
As a rule of thumb: from around 15 of 24 points, a company is mature enough to enter structured market screening and vendor conversations, provided no single dimension collapses completely. Between 9 and 14 points, it is worth working on the weakest dimensions — say, master data quality or the release of key users — in parallel to a first market orientation. Below 9 points, we advise against negotiating contracts already: consulting bought at this stage tends to flow into groundwork that would have been cheaper to do internally. The thresholds are practical guide values from project experience, not scientifically exact boundaries.
Does the self-assessment replace a professional readiness analysis?
No — the check is a structured self-assessment and deliberately compact, so that management and the project team get a shared picture in ten minutes. A professional readiness or maturity analysis by a neutral selection advisor goes considerably deeper: it samples process documentation and data quality, interviews departments and uncovers blind spots that self-reporting systematically paints too positively. The self-test works best as a first step and a basis for discussion — for example, by having several executives fill it in independently and then discussing the differences. Diverging assessments between management and the departments are often the most valuable finding of all.
How long does it take to build up missing readiness?
That depends heavily on the starting point, but typical timeframes can be named: solid documentation of the core processes is achievable in two to four months in a mid-sized company, a serious master data cleansing takes three to six months depending on data volume and ideally runs in parallel to the selection phase. A prioritised requirements document comes together in four to eight weeks if the departments are involved. The order matters: clarify sponsor and project management first, because without a mandate and capacity the remaining groundwork fizzles out. Realistically, a company with a low readiness score should plan six to twelve months of lead time before the actual selection starts.
Are my answers stored or transmitted?
No. The check runs entirely in your browser: the evaluation is calculated by JavaScript directly on this page, no answers are sent to our server or to third parties, and nothing is stored permanently in the browser either. If you reload the page, the test starts over. If you want to keep the result, note down the total and dimension scores or print the page after completing the assessment.