The Panorama Consulting 2026 survey of 170 organisations found roughly 30% of ERP projects finished over budget and 22.3% ran over schedule. The causes are visible before a project starts.
Twelve questions. Five minutes. An honest answer about whether you are ready.
No email required to see your score.
What this checks, and why
Four dimensions, because readiness is not one number. A business can be strong on three and fail on the fourth.
Data readiness
Why it matters: data migration is the most underestimated line in every ERP project, because it gets quoted before anyone looks at the data. Record count is irrelevant; quality is everything.
What we ask: whether you know your duplicate rate, whether critical fields are consistently populated, whether anyone has exported and inspected a real extract, and whether a named person understands the data’s history.
The honest signal: if nobody has looked at an extract, any migration estimate you have been given is a guess.
Process readiness
Why it matters: ERP implementation is the one moment when process change is politically possible. Businesses that automate a broken process end up with it permanently encoded and expensive to change.
What we ask: whether processes are documented, whether documented and actual practice match, whether anyone has authority to change how the business works, and whether two departments do the same thing differently.
The honest signal: if nobody can authorise a process change, you will rebuild your current inefficiencies at considerable expense.
Ownership readiness
Why it matters: ERP touches every department and therefore belongs to none. Without one named owner with authority and allocated time, decisions stall and timelines double in the gaps.
What we ask: whether there is a single named owner, whether they have decision authority, whether time has been formally allocated, and how many people must approve a significant decision.
The honest signal: “a steering committee” as the answer to “who decides” is the most reliable predictor of a slow project we know.
Scope readiness
Why it matters: 51% of over-budget projects in the Panorama data saw scope grow beyond the original plan.
What we ask: whether there is a written list of what is out of scope, whether success has been defined with numbers, whether a change process exists, and whether phase one has a boundary.
The honest signal: a project with no written exclusions has no boundary, and boundaries are what stop scope growth.
The twelve questions
Published so you can work through them without the tool if you prefer.
Data (questions 1–3)
1. Has anyone exported a real extract of your core data and looked at it in the last six months? Not opened the system — exported it and examined duplicate rates, null rates and format consistency. If nobody has, every migration estimate you have been given is a guess.
2. Do you know roughly what proportion of your customer or product records are duplicates? A number, even an approximate one. “Probably a few” is not a number. Duplicate rate is the single best predictor of migration effort.
3. Is there one person who understands the history of your data? Why two records exist for the same company. What the notes field is used for. Which fields stopped being maintained in 2021. Without this person, migration decisions stall.
Process (questions 4–6)
4. Are your core processes documented, and does the documentation match reality? These diverge in every business. The gap is where the surprises live.
5. Does anyone have authority to change how the business works? ERP implementation is the one moment when process change is politically possible. Without someone who can say “we are going to stop doing that”, you will encode your current inefficiencies permanently.
6. Do two departments do the same thing differently? Common, and it must be resolved before the build rather than during it. Resolving it during the build means building twice.
Ownership (questions 7–9)
7. Is there one named person accountable for this project? A name, not a committee.
8. Do they have authority to make decisions without convening a meeting? Authority, not just responsibility. The difference costs weeks.
9. Has their time been formally allocated? An existing full-time job plus an ERP project is not an allocation. Expect 20–40% of someone’s time through the project.
Scope (questions 10–12)
10. Is there a written list of what is out of scope? Not what is in — what is explicitly out. This is the boundary, and projects without one grow.
11. Have you defined success with numbers? “Month-end takes under a day. Double-bookings below one a month.” Without this, nobody can tell afterwards whether it worked.
12. Is there a written change process agreed before work starts? How changes are priced, how long a quote takes, who approves. Agreeing it mid-project, under pressure, goes badly.
What a weak score actually means
It does not mean do not proceed. It means fix the weak dimension first, and most of them are fixable in weeks at little cost.
| Weak dimension | What to do first | Typical time |
|---|---|---|
| Data | Export a real extract. Count duplicates and null rates. Start cleaning in the source system — your team can begin today without a supplier. | 2–6 weeks, in parallel |
| Process | Map how things actually work, not how they are documented. Identify who can authorise change. | 2–4 weeks |
| Ownership | Name one person. Allocate their time formally. Give them authority in writing. | 1 week |
| Scope | Write down what is out of scope and define success with numbers. | 1 week |
Three of these four cost you nothing but attention, and each one directly addresses a cause the Panorama data identifies.
The question most people get wrong
“Have you tested every integration, or only confirmed one exists?”
The Panorama 2026 data found that among projects that went over budget, 54.9% needed additional technology that was only discovered after the project began. That is the single largest cause in the study.
“They have an API” and “we have authenticated against it and pulled real records” are different statements. The gap between them is where the overruns live.
During discovery, insist that your supplier actually connects to every system. It takes a few days and it is the highest-value few days in the project.
Why readiness predicts outcome
The connection between these four dimensions and the failure data is direct, not theoretical.
Data readiness → the migration overrun. Migration is the most underestimated line in every ERP project because it gets quoted before anyone looks. A business that has inspected its own extract knows what it is buying; one that has not is accepting a guess.
Process readiness → automating a broken process. Where nobody can authorise change, the new system replicates the old one including the three-stage approval that exists because of an incident in 2017. Now it is encoded, and expensive to change.
Ownership readiness → the timeline. ERP touches every department and therefore belongs to none. Decision latency does not appear in any project plan and it is where a substantial share of elapsed time goes.
Scope readiness → the 51%. Scope grew in 51% of over-budget projects in the Panorama data. A written exclusions list and a priced change process are the two mechanisms that stop it.
The pattern worth noticing: none of these is about the software. The Panorama causes — technology discovered late, scope growth — and the Gartner finding on business-case attainment all point at decisions made before anyone writes code.
What this check cannot tell you
Whether you need an ERP at all. Many businesses that score well on readiness still do not need a full ERP — they need their accounting package, three integrations and one custom module at a quarter of the cost.
Which product to choose. That depends on headcount, sector and process. Comparison here.
What yours will cost. Too dependent on your data and your integrations. Ranges here.
Whether your supplier is any good. Different set of questions.
If you score well
You are ready to start discovery — process mapping, integration testing against real systems, and a data quality report, typically £6,000–£15,000 over two to four weeks.
The output should be yours, including a written build-or-buy recommendation and the right to take it to another supplier. That is how we run it.
How to fix each dimension
Specific actions, in the order that produces the most improvement per week spent.
Fixing data readiness — start today
Week 1: export a real extract of customers, products and open transactions. Open it. Sort by name and look for near-duplicates. Count how many required fields are empty.
Weeks 2–4: give your team the duplicate list and a bad-format report. They will fix more than any script, and correctly, because they know which record is right.
Ongoing: agree data entry standards so the problem stops regenerating. A cleanup without a standard is a cleanup you repeat in two years.
This has value whether or not the ERP project proceeds. It is the only readiness fix that improves the business on its own.
Fixing process readiness
Map what actually happens, by sitting with the people doing it rather than reading the procedure document. Two days produces more than two weeks of workshops.
Identify who can authorise change. If the answer is nobody, that is the finding, and it needs resolving at board level before a project starts.
Resolve departmental differences now. Where two sites do the same thing differently, decide which way is right before anyone builds to it.
Fixing ownership readiness
Name one person. Put it in writing. Allocate 20–40% of their time.
That is the whole fix and it takes a week. It is also the single highest-return action on this page, because decision latency affects both cost and duration more than most technical factors.
Fixing scope readiness
Write the exclusions list first. One page. “We are not replacing the accounting system. We are not building a mobile app in this phase.”
Define success with numbers, so there is something to measure against afterwards.
Agree the change process before work starts, including how changes are priced and who approves them.
What good looks like
A project that scores well across all four dimensions typically has:
- A data extract that has been inspected, with a known duplicate rate and a cleanup underway
- Processes mapped from observation, and a named person with authority to change them
- One owner with 20–40% of their time allocated and the ability to decide without a committee
- A written exclusions list, numeric success criteria, and an agreed change process
- A phase one that delivers real value within months rather than at the end
- Every integration tested during discovery rather than assumed
None of that requires a supplier. All of it can be done before you commission anything, and doing it is what separates the projects that land from the ones that appear in the overrun statistics.
Frequently asked questions
How do I know if my business is ready for ERP?
Readiness has four dimensions: data quality you have actually inspected, processes documented and changeable, a single named owner with authority and allocated time, and a written scope with defined exclusions. Weakness in any one predicts trouble.
What percentage of ERP projects fail?
It depends on the measure. Panorama’s 2026 survey of 170 organisations found roughly 30% over budget and 22.3% over schedule. Gartner projects over 70% will not fully meet their original business-case goals by 2027 — a stricter and different measure.
What is the most common cause of ERP overruns?
Technology discovered to be necessary only after the project began — 54.9% of over-budget projects in the Panorama data. Scope growth follows at 51%. Both are preventable in discovery.
How long does it take to get ready?
Usually four to eight weeks, mostly in parallel with other work. Naming an owner and writing a scope boundary take about a week each. Data cleaning takes longest and can start immediately.
Should I clean data before or during the project?
Before, in the source system, where possible. Your team understands the data better than any script, and the cleanup has value even if the project never happens.
Do I need to score well on all four dimensions?
Ideally. A single weak dimension can derail an otherwise well-run project — poor data quality in particular will extend a timeline regardless of how good everything else is.
Can we do readiness work ourselves?
Yes, all of it. Naming an owner and writing a scope boundary take about a week each. Data inspection and cleanup take longer and your team will do it better than any supplier, because they know which record is correct.
What if we score well but still are not sure we need an ERP?
Readiness and necessity are different questions. Many businesses that score well need their accounting package, two or three integrations and one custom module rather than a full ERP — at roughly a quarter of the cost. That comparison is here.
Does a low score mean we should not proceed?
No. It means fix the weak dimension first. Three of the four fixes cost attention rather than money, and all four directly address causes the research identifies.
Built and maintained by Jas Singh, Founder. Last updated 8 October 2026.
Figures from the Panorama Consulting 2026 ERP report (170 organisations, January 2025 – January 2026) and Gartner projections through 2027, reported via secondary sources. These measure different things and are cited as directional.
