Three Things That Cause ERP Projects to Fail

by Panorama Consulting Group | Jun 30, 2009

As we outlined in the four-part series of our 2008 ERP Report, most ERP projects go over budget, take longer than expected, and fail to deliver expected benefits. Based on this research of 1,300 ERP implementations across the globe, there are three common things that are likely to cause an ERP projects to fail:

  1. Choosing the wrong ERP software. Companies with failed ERP initiatives often try to force fit an ERP solution that isn’t right for their organization. Many organizations incorrectly assume that there are only a handful of viable options in the marketplace. There are dozens of viable ERP solutions, some focused on specific industry verticals that may be able to handle your specific business requirements more effectively than the better known packages. In addition, even for organizations that are considering only Tier I solutions, it is important to clearly define business requirements and have a thorough understanding of the solutions’ ability to meet those needs. These activities should be an integral part of your ERP software selection approach.
  2. Setting unrealistic implementation duration and cost expectations. As we often tell our clients, vendor sales reps make a living by selling software, not by setting realistic implementation expectations. The successful ERP initiatives in our study were much more likely to leverage internal and/or external expertise to help define a realistic and customized implementation plan and budget rather than rely on canned materials from a sales proposal. This should be a key part of your ERP selection and planning process.
  3. Failure to manage the ERP software vendor and ERP project scope. Once an ERP solution is selected, the real work begins. It is ultimately up to the implementing company – not the ERP vendor – to ensure the project is a success. Although the vendor and other third party consultants will bring valuable expertise to the project, organizations need to manage them as they would any other vendor or employee. This includes effectively managing project controls, customization requests, project scope, implementation strategy, etc. The ERP implementation planning process is an important first step, but the implementing company needs to carefully manage all aspects of the project throughout implementation.

Companies that successfully address the above three areas are much less likely to experience failed ERP implementations. More importantly, these three steps will get your organization started on the path to ERP success and benefits realization.

Your content goes here. Edit or remove this text inline or in the module Content settings. You can also style every aspect of this content in the module Design settings and even apply custom CSS to this text in the module Advanced settings.

Explore All Categories

Resource Center

  • The expanded Oracle and Google Cloud partnership embeds Gemini models directly inside Oracle Fusion Applications and NetSuite, moving an outside AI provider from an infrastructure option into the core application layer.
  • Buyers need to treat AI as an ERP selection criterion and ask which company's models power a platform's AI features and who controls the roadmap behind them.
  • ERP buyers evaluating a single finalist are now effectively evaluating two vendors, the software company and the AI provider behind its automation features.
  • Ignoring the risk of AI ERP vendor lock-in during selection can leave an organization bound to a single AI provider's pricing and release schedule.

AI is moving from an optional infrastructure choice to a built-in layer of the ERP applications.

Case in point: The expanded Oracle and Google Cloud partnership embeds Google's Gemini models directly inside Oracle Fusion Applications and NetSuite.

In other words, the model has moved from an optional infrastructure choice into the application layer itself.

Today, we are exploring what this shift means for ERP buyers and why AI as an ERP selection criterion now deserves the same scrutiny applied to functionality and total cost of ownership. We will also cover how to negotiate around AI ERP vendor lock-in before a contract is signed.

{CTA - insert "ai report" from Divi library}

What the Oracle and Google Cloud Partnership Actually Changes

Embedding an outside AI model inside business software is not new. Microsoft has built Dynamics 365 Copilot on OpenAI's models since 2023, and SAP announced in May 2026 that Anthropic's Claude would extend its Business AI platform and power agents inside Joule. Oracle's own cloud infrastructure already gave customers a choice of outside models, including Cohere and Meta's Llama.

What changed for Oracle is where the outside model sits. Earlier integrations, including Oracle's own infrastructure-layer offering, made an outside model something a developer or administrator had to configure deliberately. Oracle is now embedding Google's Gemini 3.1 Flash-Lite and Gemini 3.5 Flash models natively inside Fusion Applications and NetSuite, so the model shows up as default agent and automation capability built into the application itself.

(Oracle confirmed the details in its own official announcement, and Google Cloud has published its own technical notes on the underlying Gemini 3.1 Flash-Lite release.)

{video - https://vimeo.com/695804357}

Why AI Depth Deserves a Place in ERP Selection Criteria

Selection teams have spent two decades evaluating ERP platforms on module depth and total cost of ownership. Identifying the best ERP software meant comparing core financial and supply chain functionality side by side, and the depth of AI capability rarely factored into the decision.

Fast forward to today: ERP buyers are essentially evaluating two vendors (the ERP vendor and the AI vendor), even though only one name appears on the contract. Four questions now belong in every ERP selection process:

  • Model strategy - Is the AI model in the infrastructure layer or in the core applications?
  • Data portability - If the underlying AI provider changes, can the organization's historical data and trained configurations move with it?
  • Pricing exposure - Does AI usage carry its own consumption-based pricing layer that can shift independently of the core ERP license?
  • Roadmap dependency - How much of the vendor's AI roadmap depends on a partner's release schedule rather than its own?

Buyers already know how to run this kind of interrogation. The same scrutiny applied during an ERP or SCM software evaluation, now belongs in every AI feature demo.

About the author

Panorama Consulting Group is an independent, niche consulting firm specializing in business transformation and ERP system implementations for mid- to large-sized private- and public-sector organizations worldwide. One-hundred percent technology agnostic and independent of vendor affiliation, Panorama offers a phased, top-down strategic alignment approach and a bottom-up tactical approach, enabling each client to achieve its unique business transformation objectives by transforming its people, processes, technology, and data.

Avatar photo