What do Shared Services and the Agent-based model have in common and why it is important to procurement

Posted on April 2, 2025

0


In March 2008, I wrote the following post – and yes, in my younger years, I had a bit more of a whimsical tone than I perhaps do today: Shared Services Simplified or How Barry Bonds’ Bat Weight Explained GoC Thinking.

The above post recently popped up in a discussion stream, and I must admit I was a bit surprised because I had forgotten about it, even though it triggered a now-memorable debate back in the day.

Curious, I wondered, “Is the shared services model still being used in 2025?” I ask that question because, in 2008, it was a somewhat contentious issue, as illustrated by the Barry Bonds post.

Another question we must ask is how Agentic AI impacts the shared services model. For example, here are some of the purported risks associated with introducing Agentic AI into the shared services model:

Challenges and Risks

  1. High Initial Investment: Implementing Agentic AI costs $100K-$1M+ (e.g., AI platforms, training), delaying ROI by 6-12 months vs. traditional SSCs.
  2. Data Dependency: Effectiveness relies on clean, real-time data; poor inputs reduce accuracy by 10-20% (e.g., missed fraud flags).
  3. Ethical and Control Risks: Autonomous decisions (e.g., supplier cuts) may conflict with policies, risking 5-10% compliance issues if unchecked, per Gartner (2024).
  4. Workforce Disruption: Automating 70-90% of tasks could displace 20-30% of SSC staff, requiring reskilling ($50K-$200K cost), per SSON (2024).
  5. Over-Reliance: Over-dependence on AI might erode human oversight, echoing Cummins’ “mutual delusion” if outcomes falter (5-10% risk).

Regarding point 4, beyond the dramatic SLA improvement and significant cost savings that the 1998 RAM model had on the DND, the FTE equivalent resource allocation across partnered companies saw a reduduction from 23 to 3 within 18 months.

While it is estimated that 80 to 85% of private sector and 65 to 75% public sector shared services initiatives are successful, why do ProcureTech initiatives continue to struggle with a generational failure rate of 60 to as high as 80%?

FactorShared Services Success (80-85% Private, 65-75% Public)ProcureTech Failure (30-50% High Failure Rate)
Core ModelProven, simple framework: Centralizes back-office functions (e.g., procurement, finance) for economies of scale and standardization.Complex, ambitious scope: End-to-end S2P suites (e.g., Coupa, Ivalua) aim for 99% digitization, overwhelming users.
Success RatePrivate: 80-85%; Public: 65-75% (Deloitte 2023, OECD 2023)30-50% fail to meet expectations (Ardent Partners 2023 estimate)
FocusOperational efficiency: 20-30% faster cycles (e.g., P2P), clear cost control and compliance goals.Strategic overreach: Broad transformation (e.g., ESG, analytics) misaligned with immediate operational needs.
Cost Savings15-25% savings ($5M-$20M per $100M spend, PwC 2024); up to $10M-$40M with Agentic AI (SSON 2024).Promised 10-20% savings ($10M-$20M) often unmet; $15K-$400K wasted annually on 30-40% non-usage.
Technology AdoptionIncremental: 70% automation, 40-50% AI (Deloitte 2023, Gartner 2024) enhances existing workflows without disruption.Forced overhaul: Complex tech stacks (e.g., S2P suites) require 6-12 month rollouts, $100K-$500K implementation.
Adoption & UsageHigh: 90-95% with tools like Zip (SSON 2024), minimal resistance (10-15%).Low: 75-85% adoption, 30-40% non-usage ($8M-$18M lost potential per $100M spend) due to complexity (PwC 2024).
Governance & Buy-InStrong: Clear SSC ownership and stakeholder alignment ensure consistent use (e.g., GSA’s $75B success).Weak: Diffuse accountability and resistance (25-35%) erode effectiveness (ProcureTech Magazine 2024).
ExpectationsRealistic: Tangible ROI (15-25% savings, 95%+ compliance) aligns with operational goals (PwC 2024).Overhyped: “Mutual delusion” (Cummins, WorldCC 2018) promises strategic wins that falter in practice.
IntegrationStreamlined: Centralized design minimizes silos; AI orchestration boosts cohesion (20-30% agility gain).Challenging: 10-20% higher integration costs, 5-10% downtime risk (e.g., Smart Cube ERP lag, Spend Matters 2019).
EvidencePrivate: Unilever’s $1B-$10B SSC with 25-35% AI savings; Public: UK GSS £600M since 2016 (Procurement Magazine 2024).Hansen’s RAM (9/10) vs. S2P bloat ($1M-$5M vs. $10M-$20M); 30-50% failure from adoption gaps (Ardent 2023).
Mitigation PotentialAlready high success; Agentic AI adds 5-10% (e.g., 85-90% private maturity, SSON 2024).Agentic AI and I&O boost success to 70-80%, cutting non-usage to 5-15% (Zip 2024), narrowing gap with SSCs.

Beyond asking why organizations don’t use a shared services implementation model for ProcureTech initiatives, a bigger question is what are the similarities between using a shared services implementation model and my championed Agent-based solution development model. In short, is the Agent-based model a critical strategy for achieving ProcureTech implementation success?

The following is a high-level answer to the above question regarding the relationship between shared services and the Agent-based models:

The Shared Services implementation model and the Agent-based implementation model championed by Jon W. Hansen—specifically his Relational Acquisition Model (RAM)—share several common links that underpin their effectiveness in procurement and operational contexts.

Shared Services is a centralized organizational strategy for consolidating support functions (e.g., procurement, finance) with a proven success rate (80-85% private, 65-75% public), while Hansen’s RAM, an agent-based approach from the late 1990s updated in 2025, leverages intelligent agents (e.g., early AI) to optimize procurement with a lean, relational focus (9/10 rating). Despite their differing scopes—Shared Services as a broad structural model and RAM as a procurement-specific, tech-driven framework—their overlap lies in efficiency, simplicity, usability, and practical outcomes.

In my next post, I will explore these common links based on my past research and writings (Procurement Insights, 2025) dating back to 1998 and Shared Services insights (e.g., Deloitte, SSON).

30

Posted in: Commentary