Someone recently posed a question that I initially described as “out there” — but the more I sat with it, the more I realized it was not hypothetical at all.
The question: If the Hansen Fit Score™ had existed in 1990, what would SAP, Ariba, and SAP Ariba have scored?
The reason this question is less hypothetical than it appears is that the HFS™ is not a backward-looking scorecard. It is a structural diagnostic. It asks three questions that do not change by decade:
What is the technical promise?
What is the behavioral model?
Where does implementation risk actually sit — with the vendor, or with the customer?
Those questions were just as answerable in 1990 as they are today. Which means the scores are real. And the implications are uncomfortable.
A Necessary Clarification: Three Entities, Three Timelines
Before scoring, one structural point must be made.
Ariba did not exist in 1990. Keith Krach and his co-founders established Ariba in 1996. SAP Ariba did not exist until 2012, when SAP acquired Ariba for $4.3 billion. Treating these as a single entity across a 30-year timeline would produce a distorted score.
The honest retrospective requires three distinct assessments.
SAP — circa 1990 (R/2 era, R/3 on the drawing board)
This is the most historically grounded of the three scores, because the organizational model that produced every subsequent major failure was already fully formed by 1990.
The failures documented in the Procurement Insights archive — Hershey ($112M loss in 1999), FoxMeyer Drug (bankruptcy, 1996), Cadbury (£12M write-off), King County ($38M), City of Houston ($30M+) — are often treated as cautionary tales about what went wrong. The more precise reading is that they were predictable outcomes of a behavioral model whose DNA was set at founding.
Technical Capability: 8.0/10 R/2 was genuinely powerful for its era. The engineering depth was real. SAP earned its enterprise reputation on legitimate technical merit, and that merit should be acknowledged in any honest assessment.
Behavioral Alignment: 3.0/10 The Technology → Process → People inversion was not a later drift. It was the founding premise. “Configure your organization to fit our software” was the explicit value proposition from day one. The consulting dependency model — which transferred implementation risk from SAP to the customer while SAP collected license revenue regardless of outcome — was architecturally embedded before a single enterprise went live.
A score of 3.0 rather than a harsher 2.0 reflects one honest constraint: in 1990, the worst downstream pathologies had not yet fully manifested. The seeds were present. The harvest was still ahead.
Risk Designation: SRD-E (Structural Risk — Ecosystem) Big-bang implementation model. Mainframe dependency. Requirement for armies of certified consultants. Configuration complexity that made reversibility nearly impossible. Any organization signing with SAP in 1990 was making a decade-long commitment with asymmetric risk: the vendor captured the upside; the client absorbed the downside.
Composite HFS™: ~5.0/10 — HIGH RISK
Ariba — circa 1996–1997 (founding era, pre-bubble)
Ariba’s founding context matters. The mid-1990s procurement software market had a genuine problem to solve: enterprise spend was invisible, supplier relationships were managed through paper, and the efficiency opportunity was real. Ariba’s early platform addressed these with legitimate technical vision.
Technical Capability: 6.5/10 Early innovation is not the same as mature enterprise capability. A 6.5 reflects genuine promise while acknowledging that a founding-era platform serving a market that barely understood e-procurement yet was not delivering at the same depth as SAP’s decade-older R/2 architecture.
Behavioral Alignment: 5.0/10 This is where early Ariba meaningfully outscored its future acquirer. Keith Krach and the founding team came from a business results orientation. The early positioning was more outcome-focused than SAP’s. Customer success was not yet structurally subordinate to license revenue.
But the dot-com growth clock was already running. Venture capital timelines in the 1990s procurement software market were not friendly to the patience that complex implementation actually requires. The seeds of the later vendor-controlled data problem were present at founding, even if the harvest was still years away.
Risk Designation: MEDIUM — with a trajectory warning that a growth-model-driven 5.0 in Behavioral Alignment is not a stable 5.0. It was a declining score in motion.
Composite HFS™: ~5.8/10 — MODERATE RISK
SAP Ariba — circa 2012–2013 (post-acquisition)
This entity has been formally assessed in the Hansen Fit Score™ archive across a three-phase acquisition analysis, so this retrospective score has existing evidentiary grounding.
Technical Capability: 7.0/10 The combined platform had genuine breadth. The Ariba Network was a real strategic asset. The technical case for the acquisition was coherent.
Behavioral Alignment: 3.0/10 The acquisition merged SAP’s Technology → Process → People DNA with Ariba’s increasingly vendor-controlled data model. The result was not a stronger behavioral model. It was an organization that sold transformation outcomes while structurally making transformation harder. Customer lock-in deepened. Implementation complexity multiplied. The gap between what was sold and what was delivered widened further.
Risk Designation: SRD-E Enterprise ecosystem lock-in operating at two levels simultaneously — SAP and Ariba separately, then combined — with a pricing model that made exit prohibitively expensive and a consulting ecosystem that had grown dependent on perpetual implementation complexity.
Composite HFS™: ~4.8/10 — HIGH RISK
The Arc
Entity
Year
Technical
Behavioral Alignment
Risk
HFS™
SAP
1990
8.0
3.0
SRD-E
~5.0
Ariba
1997
6.5
5.0
Medium
~5.8
SAP Ariba
2012
7.0
3.0
SRD-E
~4.8
Two observations from this table that the market should sit with.
First: Ariba’s acquisition by SAP did not improve anything. It pulled Ariba’s Behavioral Alignment score down toward SAP’s floor rather than pulling SAP’s score up toward Ariba’s ceiling. This is not a coincidence specific to this transaction. Technology acquisitions in the ProcureTech space almost always resolve to the lower Behavioral Alignment score, not the higher one. The acquiring organization’s structural DNA dominates. This pattern repeats across the acquisition landscape the Procurement Insights archive has tracked for 18 years.
Second: The composite score declined across three decades of technological advancement. SAP in 1990: 5.0. SAP Ariba in 2012: 4.8. More capability. More integration. More market presence. And a lower HFS™ score. Technical progress without behavioral progress is not transformation. It is risk accumulation at enterprise scale. (Note with AI the risk accumulation combines with aceleration making failure become more evident sooner.)
What This Proves About the Framework
The retrospective scoring exercise demonstrates something worth stating directly.
The Hansen Fit Score™ is not a judgment rendered after failure. It is a structural diagnostic applied before deployment. It identifies the conditions that make failure far more likely — not every failure, but the pattern of failures that repeats across implementations, decades, and vendor generations.
The failures documented in the Procurement Insights archive beginning in 2007 were not new phenomena when they were documented. They were the predictable harvest of behavioral models whose DNA was set years earlier. Hershey failed in 1999. FoxMeyer failed in 1996. The organizational readiness gap that the Hansen Method™ addresses was present before those companies signed their contracts.
The archive did not invent the pattern. It made the pattern undeniable.
That is why the hypothetical question — what would the score have been in 1990? — is less hypothetical than it appears. The methodology asks structural questions. Structural questions are answerable across time. The scores above are not speculation. They are the application of a diagnostic lens to a historical record that has been independently accumulating since before the lens had a name.
A Final Thought
Thirty-five years have passed since SAP’s R/3 was being drawn on whiteboards. The industry has generated billions in license revenue, hundreds of analyst reports, thousands of implementation consulting engagements, and a documented 80% failure rate that has barely moved.
The technology changed. The behavioral model did not.
That is the only finding that matters for every organization currently evaluating an AI-driven procurement initiative. The vendor landscape is different. The acquisition names are different. The platform acronyms are different.
The DNA question is the same one it was in 1990.
People first. Process second. Technology third.
In that order. Every time. Without exception.
Jon W. Hansen is the founder of Hansen Models™ and creator of the Hansen Fit Score™, Hansen Method™, and RAM 2025™. The Procurement Insights blog has published over 3,300 independent documents since 2007. Hansen Fit Score™ assessments are available at https://hansenprocurement.com/resources/
The Hansen Fit Score™ is an independent assessment methodology. No compensation was received from any vendor referenced in this analysis.
Procurement Insights
If the Hansen Fit Score™ Had Existed in 1990: SAP, Ariba, and the DNA of ProcureTech Failure
Posted on March 13, 2026
0
By Jon W. Hansen | Procurement Insights
Someone recently posed a question that I initially described as “out there” — but the more I sat with it, the more I realized it was not hypothetical at all.
The question: If the Hansen Fit Score™ had existed in 1990, what would SAP, Ariba, and SAP Ariba have scored?
The reason this question is less hypothetical than it appears is that the HFS™ is not a backward-looking scorecard. It is a structural diagnostic. It asks three questions that do not change by decade:
Those questions were just as answerable in 1990 as they are today. Which means the scores are real. And the implications are uncomfortable.
A Necessary Clarification: Three Entities, Three Timelines
Before scoring, one structural point must be made.
Ariba did not exist in 1990. Keith Krach and his co-founders established Ariba in 1996. SAP Ariba did not exist until 2012, when SAP acquired Ariba for $4.3 billion. Treating these as a single entity across a 30-year timeline would produce a distorted score.
The honest retrospective requires three distinct assessments.
SAP — circa 1990 (R/2 era, R/3 on the drawing board)
This is the most historically grounded of the three scores, because the organizational model that produced every subsequent major failure was already fully formed by 1990.
The failures documented in the Procurement Insights archive — Hershey ($112M loss in 1999), FoxMeyer Drug (bankruptcy, 1996), Cadbury (£12M write-off), King County ($38M), City of Houston ($30M+) — are often treated as cautionary tales about what went wrong. The more precise reading is that they were predictable outcomes of a behavioral model whose DNA was set at founding.
Technical Capability: 8.0/10 R/2 was genuinely powerful for its era. The engineering depth was real. SAP earned its enterprise reputation on legitimate technical merit, and that merit should be acknowledged in any honest assessment.
Behavioral Alignment: 3.0/10 The Technology → Process → People inversion was not a later drift. It was the founding premise. “Configure your organization to fit our software” was the explicit value proposition from day one. The consulting dependency model — which transferred implementation risk from SAP to the customer while SAP collected license revenue regardless of outcome — was architecturally embedded before a single enterprise went live.
A score of 3.0 rather than a harsher 2.0 reflects one honest constraint: in 1990, the worst downstream pathologies had not yet fully manifested. The seeds were present. The harvest was still ahead.
Risk Designation: SRD-E (Structural Risk — Ecosystem) Big-bang implementation model. Mainframe dependency. Requirement for armies of certified consultants. Configuration complexity that made reversibility nearly impossible. Any organization signing with SAP in 1990 was making a decade-long commitment with asymmetric risk: the vendor captured the upside; the client absorbed the downside.
Composite HFS™: ~5.0/10 — HIGH RISK
Ariba — circa 1996–1997 (founding era, pre-bubble)
Ariba’s founding context matters. The mid-1990s procurement software market had a genuine problem to solve: enterprise spend was invisible, supplier relationships were managed through paper, and the efficiency opportunity was real. Ariba’s early platform addressed these with legitimate technical vision.
Technical Capability: 6.5/10 Early innovation is not the same as mature enterprise capability. A 6.5 reflects genuine promise while acknowledging that a founding-era platform serving a market that barely understood e-procurement yet was not delivering at the same depth as SAP’s decade-older R/2 architecture.
Behavioral Alignment: 5.0/10 This is where early Ariba meaningfully outscored its future acquirer. Keith Krach and the founding team came from a business results orientation. The early positioning was more outcome-focused than SAP’s. Customer success was not yet structurally subordinate to license revenue.
But the dot-com growth clock was already running. Venture capital timelines in the 1990s procurement software market were not friendly to the patience that complex implementation actually requires. The seeds of the later vendor-controlled data problem were present at founding, even if the harvest was still years away.
Risk Designation: MEDIUM — with a trajectory warning that a growth-model-driven 5.0 in Behavioral Alignment is not a stable 5.0. It was a declining score in motion.
Composite HFS™: ~5.8/10 — MODERATE RISK
SAP Ariba — circa 2012–2013 (post-acquisition)
This entity has been formally assessed in the Hansen Fit Score™ archive across a three-phase acquisition analysis, so this retrospective score has existing evidentiary grounding.
Technical Capability: 7.0/10 The combined platform had genuine breadth. The Ariba Network was a real strategic asset. The technical case for the acquisition was coherent.
Behavioral Alignment: 3.0/10 The acquisition merged SAP’s Technology → Process → People DNA with Ariba’s increasingly vendor-controlled data model. The result was not a stronger behavioral model. It was an organization that sold transformation outcomes while structurally making transformation harder. Customer lock-in deepened. Implementation complexity multiplied. The gap between what was sold and what was delivered widened further.
Risk Designation: SRD-E Enterprise ecosystem lock-in operating at two levels simultaneously — SAP and Ariba separately, then combined — with a pricing model that made exit prohibitively expensive and a consulting ecosystem that had grown dependent on perpetual implementation complexity.
Composite HFS™: ~4.8/10 — HIGH RISK
The Arc
Two observations from this table that the market should sit with.
First: Ariba’s acquisition by SAP did not improve anything. It pulled Ariba’s Behavioral Alignment score down toward SAP’s floor rather than pulling SAP’s score up toward Ariba’s ceiling. This is not a coincidence specific to this transaction. Technology acquisitions in the ProcureTech space almost always resolve to the lower Behavioral Alignment score, not the higher one. The acquiring organization’s structural DNA dominates. This pattern repeats across the acquisition landscape the Procurement Insights archive has tracked for 18 years.
Second: The composite score declined across three decades of technological advancement. SAP in 1990: 5.0. SAP Ariba in 2012: 4.8. More capability. More integration. More market presence. And a lower HFS™ score. Technical progress without behavioral progress is not transformation. It is risk accumulation at enterprise scale. (Note with AI the risk accumulation combines with aceleration making failure become more evident sooner.)
What This Proves About the Framework
The retrospective scoring exercise demonstrates something worth stating directly.
The Hansen Fit Score™ is not a judgment rendered after failure. It is a structural diagnostic applied before deployment. It identifies the conditions that make failure far more likely — not every failure, but the pattern of failures that repeats across implementations, decades, and vendor generations.
The failures documented in the Procurement Insights archive beginning in 2007 were not new phenomena when they were documented. They were the predictable harvest of behavioral models whose DNA was set years earlier. Hershey failed in 1999. FoxMeyer failed in 1996. The organizational readiness gap that the Hansen Method™ addresses was present before those companies signed their contracts.
The archive did not invent the pattern. It made the pattern undeniable.
That is why the hypothetical question — what would the score have been in 1990? — is less hypothetical than it appears. The methodology asks structural questions. Structural questions are answerable across time. The scores above are not speculation. They are the application of a diagnostic lens to a historical record that has been independently accumulating since before the lens had a name.
A Final Thought
Thirty-five years have passed since SAP’s R/3 was being drawn on whiteboards. The industry has generated billions in license revenue, hundreds of analyst reports, thousands of implementation consulting engagements, and a documented 80% failure rate that has barely moved.
The technology changed. The behavioral model did not.
That is the only finding that matters for every organization currently evaluating an AI-driven procurement initiative. The vendor landscape is different. The acquisition names are different. The platform acronyms are different.
The DNA question is the same one it was in 1990.
People first. Process second. Technology third.
In that order. Every time. Without exception.
Jon W. Hansen is the founder of Hansen Models™ and creator of the Hansen Fit Score™, Hansen Method™, and RAM 2025™. The Procurement Insights blog has published over 3,300 independent documents since 2007. Hansen Fit Score™ assessments are available at https://hansenprocurement.com/resources/
The Hansen Fit Score™ is an independent assessment methodology. No compensation was received from any vendor referenced in this analysis.
-30-
Share this:
Related