Short answer: A business is ready for ERP when it has an owner-level sponsor, a defined problem it is solving, reasonably accurate current stock and receivables data, a named internal project owner with real time allocated, agreement on which existing process will change, and budget for training as well as software. Most failed ERP projects fail on these points rather than on software selection. The strongest single predictor of failure is treating ERP as an IT purchase instead of an operational change.
ERP Trends · Pakistan
ERP Readiness Checklist: 12 Questions Before You Spend a Rupee
Most failed ERP projects were already failing before anyone chose the software.
By Pearl Solutions · Updated September 2026 · 11 min read
We have delivered ERP since 2006, which means we have also seen projects that did not go well — ours and other people's. The pattern is consistent enough to be useful.
Failed ERP projects are almost never failures of software selection. By the time the software is being chosen, the outcome is largely already determined by things that have nothing to do with which system was picked.
Below are twelve questions we use to assess readiness. Answer them honestly, before any vendor conversation. Scoring is at the end, and the useful part is not the score — it is knowing what to fix.
Section 1: Commitment
1. Does the owner or MD personally want this, or has it been delegated?
ERP changes how people work, and people resist that. When resistance appears — and it always does, around week six — it is settled by whoever has authority. If the owner is engaged, it gets settled. If the project was handed to the IT person or a manager, the resistance wins by attrition and the project quietly becomes a reporting tool nobody uses.
Ready: the owner is in the key sessions and makes the process decisions.
Not ready: "I have asked our IT guy to handle this and report back."
2. Can you name the specific problem you are solving?
"We need to modernise" and "everyone is using ERP now" are not problems. They are moods, and they produce unbounded projects because nothing defines when you are done.
Real problems sound like: we do not know our true stock position; we cannot tell which products make money; closing the month takes three weeks; we lose sales because nobody knows what is available.
Ready: two or three specific, painful, nameable problems.
Not ready: a general sense that things should be better.
3. Have you agreed that some current processes will change?
The single most expensive sentence in an ERP project is "can you make it work exactly the way we do it now?" Sometimes the answer should be yes. Frequently the current way exists because of a limitation that no longer applies, and preserving it means paying for customization to keep a workaround alive.
Ready: willing to adopt standard process where there is no real competitive reason not to.
Not ready: every existing habit is non-negotiable.
Section 2: Data
4. Do you know what stock you have?
Not perfectly — approximately. If a physical count today would land within a few percent of your records, you are fine. If it would be materially different, you have a counting problem, and an ERP will inherit it on day one.
Ready: records and reality are broadly aligned.
Not ready: nobody would be surprised by a 20% variance.
5. Do you have a clean list of products and customers?
Duplicates, three spellings of the same customer, products with no consistent code. This is the most commonly underestimated task in the entire project and it is the one that delays go-live most often.
It is also work only you can do, because only you know that "Ali Traders" and "Ali Trader Lahore" are the same account.
Ready: a master list exists, even if it needs tidying.
Not ready: product and customer data is scattered across several people's files.
6. Do you know who owes you money and how much?
If receivables are unclear now, they will be unclear after migration, and there will be an argument about whether the system caused it.
Ready: a current receivables list you would defend.
Not ready: "we would have to work it out."
Section 3: People
7. Who inside your business owns this project?
Not the vendor — you. Someone internal who knows the operation, has authority, and has time formally allocated. A name, with hours reserved.
This is the highest-correlation item on the whole list. Projects with a genuine internal owner succeed. Projects where the internal owner also has a full-time operational job go slowly and often stall, and it is nobody's fault because the arithmetic never worked.
Ready: a named person with real time freed up.
Not ready: "we will all pitch in."
8. Will the people who enter the data actually use it?
Owners approve ERP. Storekeepers, sales staff and accounts assistants determine whether it works, because they produce the data everything else depends on.
If they were not consulted, believe it is surveillance, or think it is temporary, they will maintain their parallel register. And a parallel register means you now have two systems and trust neither.
Ready: the team knows it is coming and understands why.
Not ready: it will be announced at go-live.
9. Have you budgeted for training, not just software?
An untrained team on a correctly configured system produces worse results than a trained team on an average one. Training is not the item to trim when the quote comes in higher than expected — it is the item that determines whether the rest of the spend returns anything.
Ready: training is a line in the budget.
Not ready: "our staff will pick it up."
Section 4: Scope and expectations
10. Are you starting with a defined first phase?
Attempting accounting, inventory, manufacturing, HR, CRM and e-commerce simultaneously is the most reliable way to fail. Every phase needs configuration, testing, training and a period where people are slower than before. Multiply that by six and the business stops functioning.
Ready: a first phase of two or three modules with a date.
Not ready: everything, together, by next quarter.
11. Do you have realistic expectations about the difficult period?
There is a stretch after go-live where things are harder, not easier. People are learning, data issues surface, and output dips. It is normal and temporary, and businesses that were not warned about it conclude the project has failed precisely when it is working as expected.
Ready: you expect a difficult stretch and have planned for it.
Not ready: you expect improvement from week one.
12. Are you choosing a partner, or buying software?
The software is largely a solved problem — several good platforms exist. The variable is who configures it for your business, how well they understand your operation, and whether they are still answering the phone in month eight.
Ready: evaluating partners on implementation history, references and support terms.
Not ready: comparing feature lists and picking the cheapest quote.
Scoring
| Ready answers | What it means | What to do |
|---|---|---|
| 10–12 | Genuinely ready | Start partner conversations now |
| 7–9 | Ready with specific gaps | Close the gaps first; most take weeks, not months |
| 4–6 | Not yet | Fix data and appoint an internal owner before spending |
| 0–3 | A project now would likely fail | Start with the problem definition, not the software |
A low score is useful information, not a verdict. Nearly every item on this list can be fixed in weeks by the business itself, at no cost, and doing so before you spend money is the highest-return work available in this entire process.
The three that matter most
If you only act on part of this list, act on these, because they carry the most weight in outcomes we have observed:
- Question 7 — a named internal owner with real time. Nothing else compensates for its absence.
- Question 1 — genuine owner commitment. It is what resolves the resistance that will definitely appear.
- Question 5 — clean product and customer data. It is the most underestimated task and the most common cause of delay.
What to do with your answers
If you scored well, the next step is evaluating partners rather than software, and question 12 tells you what to evaluate on.
If you scored poorly, you have just saved yourself a significant amount of money, because the gaps this list exposes are exactly the ones that surface halfway through an implementation when they are expensive to fix.
Either way, we are happy to go through it with you honestly — including telling you that you are not ready, which is a conversation we have regularly and one that tends to save everyone a difficult year.
Frequently Asked Questions
Readiness rests on six conditions: the owner or MD is personally engaged rather than having delegated the project, you can name two or three specific problems you are solving, your current stock and receivables data is broadly accurate, there is a named internal project owner with real time allocated, you accept that some existing processes will change, and training is budgeted alongside software. Failing several of these predicts a difficult project regardless of which system is chosen.
A named internal project owner who knows the operation, has authority, and has time formally allocated to the project. In practice nothing else compensates for its absence. The common failure is naming someone who also carries a full-time operational job, which means the project advances only in gaps that never appear, and it stalls without anyone being at fault.
No. Each module needs configuration, testing, training and a period where staff are slower than before, and running that across six modules simultaneously stops the business from functioning. A defined first phase of two or three modules with a target date is far more likely to succeed, and it produces a working system that funds confidence for the next phase.
Pearl Solutions Odoo implementations start from PKR with the final figure depending on user count, modules in scope, data migration and customization. The more useful budgeting point is that training and data cleanup should be funded rather than trimmed, because an untrained team on a well-configured system produces worse results than a trained team on an average one. Pearl Solutions is an Official Odoo Partner in Lahore with 400+ ERP implementations since 2006 and 30 Odoo implementations. Call +92 300 7774979 or email info@pearlsol.com.