Most ERP failures are blamed on software. Look closely and you’ll find a leadership decision made too quickly, or delegated too far down. The CEO signed the cheque, the CFO wanted cleaner books, the COO was told it would be “fine,” and IT was handed the project. Nobody owned the risk.
That is the real problem with digital transformation: it is sold as a technology project and fails as a business one.
The odds are not kind
One study of Indian manufacturers put unsuccessful ERP implementations at 60 to 70 percent. Another source found that 51 percent of businesses face operational disruption at go-live. Abroad, Spar in South Africa switched on SAP at one distribution centre in 2023; store deliveries faltered and group turnover took an estimated R1.6 billion hit. Hershey squeezed a 48-month plan into 30 months and watched its share price fall 8 percent in a day.
Closer home, Bata India told analysts that ERP costs earlier carried as capex were expensed in one go, and linked muted growth partly to the rollout. Not a collapse, but proof that even a well-run, listed business ends up explaining its ERP to investors. A promoter-led business doing ₹80 crore has no such cushion.
What each CXO must own
Research on Indian retail names the usual culprits: weak user involvement, thin top-management commitment, resistance to change, and unrealistic schedules. Every one of those is a leadership failure, not a technical one.
- CEO or Founder: Own the outcome, not the vendor call. Decide what the business should do better in twelve months, and say it in one sentence. If you can’t, you’re not ready.
- CFO: Own data discipline. Duplicate masters, unreconciled stock and receivables don’t fix themselves in migration; they travel into the new system faster.
- COO: Own the dispatch and production floor. If your operations head is not in the design room, you are building something they will quietly work around.
- CIO or IT head: Own security, access, and integrations, but not the business case. That belongs upstairs.
Five questions to ask before you sign
Put these to your vendor and your own team if the answers are vague, pause.
- What exactly goes live first, and what happens if it fails?
- Who in our team has the authority to say “not ready”?
- How will we dispatch and invoice if the system is down for a week?
- What percentage of our item, customer and vendor data has been cleaned?
- Which numbers will leadership trust within 60 days?
A de-risking sequence that actually works
- Name the single painful flow. Usually inventory or order-to-cash. Prove value there first.
- Phase it. Odoo ERP lets modules go live one at a time, which makes a rollout something you can reverse.
- Run parallel. Keep the old system through one or two close cycles. It’s dull, and it protects careers.
- Audit data before go-live, not after. Set a date only once the data audit is signed off.
- Connect CRM to stock and finance early, so sales and accounts quote the same number.
- Fix scope, let the date move. Never the other way round.
Anyone promising a complete ERP solution across every function in six weeks is selling you a Hershey. A sensible Odoo solution looks modest on a slide and far better in month six.
FAQs
Who should own an ERP transformation?
A named business leader, usually the CEO or CFO, with IT as an enabler. If ownership sits only with IT, expect adoption problems.
How long does a phased rollout take?
Usually a few months per module, depending on data quality and process ownership. Quotes of weeks for everything deserve a second question.
Is Odoo suitable for a ₹50–300 crore business?
Often, especially in trading, light manufacturing and project-led work where modules can be added in stages. Fit depends on process clarity more than revenue.
What is the earliest warning sign?
People keep the old spreadsheet open “just in case.” If it’s still open in month three, adoption is failing.
