Why Is SAP Ariba Still Around?
Unpacking Procurement's Costly Legacy
If you've been around digital procurement long enough, you've heard the groans when someone mentions SAP Ariba. Nico Bac, founder of Digital Procurement Now and former digital transformation lead at P&G, recently ignited a fierce debate on LinkedIn by openly questioning why companies continue to use—and worse, newly purchase—SAP Ariba. Bac candidly described his painful experience of investing over $10 million into an Ariba implementation that ultimately failed, despite having top talent like Katherine Storer (now Chief Supply Chain Officer at Berlin Packaging) on the project.
This isn't a new frustration. Industry commentator Jason Busch of Spend Matters once famously said, “Ariba doesn’t have customers, it has prisoners.” A sentiment echoed by many procurement professionals in Bac's discussion. But why does this sentiment persist, and why is Ariba still pervasive?
The Persistent Prison of SAP Ariba
Bac’s bold statement triggered a flood of opinions from procurement and technology leaders, and several key themes emerged:
Inertia and Market Reputation: Mohan Sundar, a general manager in global procurement, cited legacy inertia and fear of change as central reasons Ariba remains popular. He argued companies often stick to familiar, reputed solutions even when they underperform, highlighting how market perception trumps real-world functionality. This aligns with Yuri Hembitski’s observation that research houses consistently rank Ariba as a leading solution, perpetuating its status despite operational drawbacks.
Supplier Frustration and Poor Adoption: Bac and others stressed supplier dissatisfaction as a significant issue. Pierrick L’Ebraly, founder of ProcurEye, pointed out that supplier engagement frequently gets overlooked during procurement software selection, leading to frustration and resistance. He noted newer platforms like Zip aim to improve user experience but have yet to fully solve supplier adoption challenges.
Implementation Nightmares and Cost Overruns: Many commentators, including Bac, expressed deep frustration over implementation challenges. Tanya W., an SAP innovator, emphasized that projects typically go over budget regardless of the tool chosen. She blamed consultants overselling ‘best practices’ and organizations accepting unrealistic expectations. This resonates with experiences shared by Benjamin Wenn, who revealed his organization recently replaced Ariba with a slimmer, modern alternative due to overwhelming dissatisfaction.
Is the Problem Ariba or the Implementation Approach?
Some commenters argued the real issue isn't SAP Ariba itself, but rather poor project management and unrealistic expectations. Sangram Mohanty, an SAP expert, noted: "There is no perfect tool. It all depends on how you use or manage it." He argued that implementation strategy and expectation management significantly influence success.
However, Bac strongly countered this narrative, stressing the repeated failures and high costs he personally experienced. Bac's frustration highlights the deeper tension between user experience, functionality, and market dominance by large, legacy systems like Ariba.
Alternatives and the Future of Procurement Technology
The discussion wasn't purely about bashing Ariba; it quickly evolved into a broader conversation on alternatives. Fakhruddin K., a business intelligence expert, advocated strongly for Ivalua, praising its high configurability and analytical capabilities. Yet, Mohanty warned that highly customized solutions often become costly to maintain, creating new headaches post-implementation.
Viswa Kuppuswami, CEO of Zumen, highlighted the broader need for a fundamental shift in how organizations approach procurement technology. He argued against overly modular approaches, advocating for more holistic, stakeholder-inclusive platforms that genuinely integrate supplier needs. Kuppuswami stressed that too many solutions force suppliers onto cumbersome portals, unlike CRM platforms, which never burden customers similarly.
Leadership and Bold Decision-Making
The LinkedIn thread repeatedly circled back to leadership accountability. John A. Johnson, a CIO and transformation executive, posed an essential question: Did procurement and finance thoroughly evaluate business architecture, processes, and capability alignment before choosing Ariba? He suggested many procurement teams chase product functionality without sufficient alignment to business realities, setting themselves up for failure.
This viewpoint aligns with Bac's call for procurement leaders to be "bold" and take charge, explicitly stating their technology needs rather than passively accepting corporate defaults driven by IT or historical inertia. Raymond Grieger humorously suggested making IT responsible for supplier adoption to shift perspectives—underscoring the need for alignment between procurement, IT, and operational realities.
Is AI the Solution or Another Trap?
Looking ahead, commentators like Mohanty highlighted AI’s potential impact on procurement technology. He argued current assessments might soon feel outdated, as AI promises to significantly alter the procurement landscape by enhancing data management and automating routine processes. This adds urgency to the debate, as companies must position themselves correctly today to leverage AI-driven procurement solutions effectively tomorrow.
Breaking Free From the Procurement Prison
Dr. Elouise Epstein humorously recognized Bac's outspoken frustration, noting the value of publicly sharing such candid experiences to prevent others from repeating costly mistakes. The overarching message from procurement experts is clear: companies must stop accepting subpar solutions out of inertia or misplaced loyalty. They must rigorously challenge vendor claims, critically evaluate long-term total cost of ownership, and align procurement solutions closely with user and supplier needs.
Bac’s experience serves as a cautionary tale that choosing the wrong procurement technology isn't just costly—it can become an operational prison. Organizations need leadership bold enough to demand better, teams diligent enough to assess true organizational needs, and solutions flexible enough to grow alongside changing procurement landscapes.
As procurement continues evolving rapidly, organizations must urgently reconsider their technology choices. The dialogue initiated by Bac underscores the critical necessity for procurement leaders to reclaim control, ensuring technology empowers rather than imprisons their operational capabilities.
What’s your experience with SAP Ariba or other procurement platforms? Are procurement leaders bold enough in their technology choices, or are they still trapped by inertia and market reputation? Share your insights and experiences—let’s keep the conversation going.
 | A guest post by
|