In a recent post, I applied the Hansen Fit Score™ retrospectively to three entities — SAP (1990), Ariba (1997), and SAP Ariba (2012) — to ask a question the industry has never formally answered: what would the structural diagnostic have shown before the failures arrived?
The answer was uncomfortable. Across 35 years of technological advancement, the HFS™ composite score declined. More capability. More integration. More market presence. Lower score.
That post established a principle I called acquisition physics: ProcureTech acquisitions resolve to the lower Behavioral Alignment score — not the higher one. The acquiring organization’s structural DNA dominates. Ariba’s 5.0 did not lift SAP’s 3.0. SAP’s 3.0 consumed Ariba’s 5.0.
A principle demonstrated once is a finding. Demonstrated across three independent acquisition chains spanning three decades, it becomes something closer to a law — what the three graphics in this series collectively reveal as the physics of enterprise software evolution: a repeating structural force that operates regardless of the vendor name, the acquisition rationale, the ownership model, or the era in which it occurs.
This post tests it against Oracle and Coupa.
Why These Two Series
The Oracle series is the most dramatic acquisition chain in enterprise software history — an 18-month hostile takeover that generated DOJ antitrust challenges, European Commission intervention, customer revolts, and 6,000 immediate layoffs. If acquisition physics holds under those conditions, it holds everywhere.
The Coupa series introduces a variable the SAP and Oracle chains did not have: private equity ownership. Thoma Bravo’s $8 billion acquisition of Coupa in February 2023 added a financial extraction dynamic — margin expansion, cost reduction, exit timeline pressure — that restructures behavioral incentives in ways that neither a founder-led company nor a public company faces in the same form. And uniquely, the Coupa series allows the HFS™ to operate in predictive mode: the Cirtuo and Scoutbee acquisitions are recent enough that the forecast can be published on record before the outcomes are known.
That is what a structural diagnostic framework makes possible. And what no sponsored analyst firm can do.
Series II: JD Edwards → PeopleSoft → Oracle (2000–2005)
Three entities. Five years. The largest single-point behavioral collapse in the series.
JD Edwards — circa 2000 (Independent Era)
JD Edwards earned its reputation the hard way — 23 years of independent operation, a genuine mid-market customer-first orientation, and technical architecture that gave it a loyal installed base that persisted well past the acquisition. The Denver roots mattered. The culture produced a Behavioral Alignment score that no subsequent acquirer could sustain.
Technical Capability: 7.5/10 Genuine depth in manufacturing, distribution, and mid-market ERP. OneWorld’s platform-independent architecture was technically sophisticated for its era.
Behavioral Alignment: 6.5/10 The highest in this series at point of entry. Customer-first DNA, outcome-oriented implementation model, practitioner trust built over two decades of independent operation.
HFS™ Composite: ~7.0/10 — MODERATE RISK
PeopleSoft — circa 2003 (Post-JDE Merger)
PeopleSoft acquired JD Edwards in July 2003 for $1.7 billion — a friendly merger designed to create the world’s second-largest enterprise software company. Within days, Oracle launched its hostile bid. What followed was an 18-month siege that consumed the organizational attention PeopleSoft needed for customer success.
Organizations fighting for survival do not optimize for implementation quality. The behavioral alignment score reflects that reality.
Technical Capability: 7.0/10 The combined platform had real breadth. The JDE integration added capability. The technical case was coherent.
Behavioral Alignment: 5.0/10 A 1.5-point drop from JDE’s independent score — not because PeopleSoft was a bad organization, but because absorbing a major acquisition while simultaneously fighting a hostile takeover is not a condition under which customer outcomes improve. Ninety-five percent of PeopleSoft and JDE users surveyed in 2003 said they did not want Oracle’s bid to succeed. That number reflects something real about the behavioral model customers experienced.
Risk Designation: ELEVATED — with a trajectory warning. The siege was ongoing. The score was declining in real time.
HFS™ Composite: ~6.0/10 — ELEVATED RISK
Oracle — circa 2005 (Post-Hostile Takeover)
The deal closed January 7, 2005. Oracle fired 6,000 of PeopleSoft’s 11,000 employees within one month. The DOJ and European Commission had both filed antitrust challenges before the acquisition was complete. The behavioral model was set before a single customer migration began.
Here is where acquisition physics demonstrates its most uncomfortable implication: Oracle’s technical capability score is the highest in this series at 8.5. The combined entity — Oracle E-Business Suite, PeopleSoft, JD Edwards — had genuine technical depth. The platform breadth was real.
It did not matter.
Technical Capability: 8.5/10 The highest technical score across all three acquisition series. Real breadth, real depth, real engineering capability.
Behavioral Alignment: 2.5/10 Oracle’s founding behavioral model — database-led, vendor-controlled, implementation risk transferred to the client — was already established before PeopleSoft existed. The hostile takeover did not create a new behavioral model. It imposed the existing one at scale.
The 3.7-point gap between Technical Capability (8.5) and HFS™ Composite (4.8) at the Oracle acquisition point is the largest single-point divergence across all three series. Technical capability and behavioral alignment moved in opposite directions simultaneously. That is not an anomaly. It is acquisition physics at maximum expression.
The Oracle Arc — Summary Table
Entity
Year
Technical
Behavioral Alignment
Risk
HFS™
JD Edwards
2000
7.5
6.5
Moderate
~7.0
PeopleSoft
2003
7.0
5.0
Elevated ↓
~6.0
Oracle
2005
8.5
2.5
SRD-E
~4.8
Each acquisition resolved to the lower Behavioral Alignment score. JDE’s 6.5 became PeopleSoft’s 5.0. PeopleSoft’s 5.0 became Oracle’s 2.5. The acquiring organization’s structural DNA dominated every time.
Series III: Coupa (2006–2025+)
Four phases. One direction. And a reminder that the HFS™ has always been a prospective diagnostic — applied before outcomes are known, not after. The Coupa forecast simply makes that visible in real time.
Coupa — circa 2006 (Founding Era)
Procurement Insights published what is likely the industry’s first formal independent white paper on Coupa in 2009 — three years before mainstream analyst coverage began. The founding-era observation matters here because it establishes a baseline that the subsequent ownership changes can be measured against honestly.
Rob Bernshteyn’s Business Spend Management positioning was genuinely outcome-oriented in the founding era. The BSM thesis — that procurement technology should deliver measurable business outcomes, not just process automation — was a real behavioral differentiator from SAP and Oracle’s Technology→Process→People inversion.
Technical Capability: 6.0/10 Early-stage platform. The technical promise was real but not yet at enterprise depth.
Behavioral Alignment: 6.5/10 The highest Behavioral Alignment score in Coupa’s history. Outcome-focused, practitioner-oriented, independent before the growth clock began running.
HFS™ Composite: ~6.3/10 — MODERATE RISK
Coupa Public — circa 2022 (Peak Public Company Era)
The growth clock that began running at IPO (2016) had been running for six years by 2022. Twenty-one acquisitions. Revenue pressure. Analyst attention. The behavioral model that produced a 6.5 Behavioral Alignment score at founding had been subordinated — gradually, then decisively — to the imperatives of public market growth.
This is the same pattern the SAP series showed at the Ariba founding stage: a declining score in motion. The difference is that Coupa’s decline was faster, because the public market growth clock is less patient than the enterprise software market of the 1990s.
Technical Capability: 8.0/10 The platform had real breadth by 2022. Twenty-one acquisitions produced genuine capability across spend management, supplier management, and contract lifecycle.
Behavioral Alignment: 3.5/10 A 3.0-point drop from founding. Implementation support as a function had been structurally deprioritized relative to new logo acquisition. The gap between what was sold and what was delivered had widened materially.
HFS™ Composite: ~5.0/10 — HIGH RISK
Coupa PE-Owned — circa 2023 (Thoma Bravo, $8 Billion)
Thoma Bravo’s acquisition playbook across enterprise software is well-documented: Sailpoint, Barracuda, Sophos, Proofpoint. The pattern is consistent — take private, cut costs, optimize margins, acquire to build platform value, position for exit. The typical hold period is three to five years.
This introduces a structural tension that the SAP and Oracle series did not contain in the same form. Implementation support teams are cost centers. PE playbooks reduce cost centers. Exit timelines may conflict with the long-term product investment that complex enterprise implementations require. Leagh Turner replaced Rob Bernshteyn as CEO in November 2023 — the founder’s behavioral orientation formally departed with the leadership change.
Technical Capability: 7.5/10 Rationalization of the platform under PE ownership produced some technical consolidation. Real capability remained.
Behavioral Alignment: 2.8/10 PE ownership does not improve Behavioral Alignment. The incentive structure makes improvement structurally unlikely within a standard exit timeline. The score reflects the operational reality, not a judgment about intent.
Cirtuo (May 2025) introduced AI-powered category management capability — a genuine technical addition. Scoutbee (October 2025) extended supplier intelligence. Both acquisitions add real technical depth. The “autonomous spend management” repositioning reflects a coherent technical vision.
The behavioral alignment question is not whether these acquisitions add capability. They do. The question is the same one the SAP, Oracle, and Coupa series have already answered: does adding technical capability inside a deteriorating behavioral model improve the composite score?
Across every series examined, the answer is no.
Technical Capability: 8.0 (forecast) Cirtuo and Scoutbee restore the technical ceiling to public-era levels. The platform is genuinely capable.
Behavioral Alignment: 2.5 (forecast) Thoma Bravo’s PE ownership structure has not changed. The exit clock is running. Implementation support remains a cost center. No structural mechanism exists for behavioral alignment improvement within the current ownership model.
Risk Designation: SRD-E (forecast)
HFS™ Composite: ~4.3/10 — HIGH RISK (FORECAST)
This forecast is published on record. If it holds, the acquisition physics law is validated across three independent series. If it does not hold — if Coupa demonstrates material behavioral alignment improvement under PE ownership — the Hansen Fit Score™ methodology gets refined accordingly. Either outcome is informative. Only one outcome is likely.
The Coupa Arc — Summary Table
Entity
Phase
Technical
Behavioral Alignment
Risk
HFS™
Coupa
2006 — Founding
6.0
6.5
Moderate
~6.3
Coupa Public
2022 — Public Peak
8.0
3.5
High
~5.0
Coupa PE-Owned
2023 — Thoma Bravo
7.5
2.8
SRD-E
~4.6
Coupa + Cirtuo + Scoutbee
2025+ — Forecast ▼
8.0
2.5
SRD-E
~4.3
The Pattern Across Three Series
“Across vendors, decades, and ownership models, acquisitions and PE deals systematically trade Behavioral Alignment for technical scale — and the HFS™ arcs make that trade visible.”
Technical Rises. HFS™ Falls.
Three acquisition chains. Three decades. Three different structural contexts — a SAP-era mega-acquisition, a hostile takeover, and a private equity buyout. The same result every time.
Entity at Acquisition
Pre-Acquisition HFS™
Post-Acquisition HFS™
Change
SAP Ariba (2012)
5.8 (Ariba)
4.8
−1.0
Oracle PeopleSoft (2005)
6.0 (PeopleSoft)
4.8
−1.2
Coupa PE-Owned (2023)
5.0 (Public)
4.6
−0.4
Coupa + Cirtuo/Scoutbee (2025+)
4.6
4.3 (forecast)
−0.3
The composite score declines at every acquisition point. The direction does not change with the ownership structure, the acquisition rationale, the technical capability of the combined entity, or the era in which it occurs.
That is not coincidence. It is a structural pattern with a structural explanation: behavioral alignment is an organizational property, not a technical one. You cannot acquire your way to better behavioral alignment. You can only build it — or lose it.
In every acquisition chain examined across three decades, the composite score resolved to the lower Behavioral Alignment score — without exception.
The Cycle That Repeats
When the three series are viewed as a sequence rather than three separate assessments, a structural pattern emerges that no single series makes visible on its own.
Enterprise software evolves through a repeating five-stage cycle:
1. Innovation — A new platform or category emerges with genuine technical promise and outcome-oriented behavioral DNA. Early-stage Behavioral Alignment scores are real.
2. Consolidation — Growth pressure, acquisition activity, and market scaling begin subordinating customer outcomes to revenue imperatives. Behavioral Alignment starts declining.
3. Behavioral Collapse — Acquisition physics takes hold. The combined entity resolves to the lower Behavioral Alignment score. Technical capability continues rising. The composite HFS™ score falls.
4. Implementation Failure — The gap between what is sold and what is delivered becomes undeniable. The 80% failure rate is not random. It is the predictable harvest of a behavioral model whose decline was measurable before a single contract was signed.
5. Restart — The market declares the old platform obsolete, embraces a new wave of innovation, and the cycle begins again.
The ProcureTech industry has completed this cycle twice and is currently in stage three of the third.
Generation 1 — ERP Consolidation (SAP/Oracle era): Driver: technology centralization. The founding behavioral DNA of SAP’s Technology→Process→People inversion was present at R/2. The failures at Hershey, FoxMeyer, and Cadbury were not surprises. They were stage four.
Generation 2 — Enterprise Application Consolidation (PeopleSoft/Ariba era): Driver: acquisition scaling. JDE’s 7.0 HFS™ became Oracle’s 4.8 in five years. Ariba’s 5.8 became SAP Ariba’s 4.8 in fifteen. Both followed the same arc.
Generation 3 — ProcureTech SaaS and PE Ownership (Coupa era): Driver: private equity exit economics. The cycle now runs faster. Coupa’s Behavioral Alignment declined from 6.5 to 2.5 in under twenty years — a steeper drop than either previous generation, compressed by the combined pressure of public market growth clocks and PE exit timelines.
The AI wave is currently in stage one of the fourth cycle. The technical promise is real. The behavioral alignment questions are the same ones that were present — and answerable — at the start of every previous cycle.
What This Means for the Current Market
The ProcureTech market in 2026 is executing the same acquisition sequence at accelerated pace, with AI as the justification. The names are different. The platform acronyms are different. The acquisition press releases use different language.
The physics are identical.
Organizations currently evaluating procuretech platforms — particularly those under PE ownership, those that have completed multiple rapid acquisitions, or those repositioning existing products as AI-native — are looking at the same structural conditions that produced the scores above. The cycle does not pause because the technology has changed. It accelerates because the technology has changed, and the organizational operating model required to absorb it has not.
The HFS™ framework does not require a completed failure to identify elevated risk. It requires an honest answer to three structural questions. The archive contains 18 years of evidence that those questions were answerable before the failures arrived.
They remain answerable now. The fourth cycle is beginning. The diagnostic is the same one it was in 1990.
People first. Process second. Technology third.
In that order. Every time. Without exception.
This is Part II of an ongoing series applying the Hansen Fit Score™ retrospectively and predictively across major ProcureTech acquisition chains. [Part I — SAP, Ariba, and the DNA of ProcureTech Failure] establishes the methodology and the acquisition physics principle.
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-
Bonus Section: The Pattern in the Present Tense
The three acquisition series documented above span 1990 to 2025. But the physics of enterprise software evolution does not require a 35-year arc to become visible. It is operating right now — in three cases that have all surfaced within the past 24 months, each confirming a different dimension of the same structural law.
Millie, a procurement leader at Geosyntec, recently described in her own words what it felt like to transition from AdaptOne to Coupa after Blackstone’s acquisition of her organization drove transaction volumes past the point AdaptOne could sustain: “cookie cutter — this is what you get” and “the business is still like well why can’t we go back.” That is a practitioner inside the Coupa behavioral alignment decline confirming the forecast without knowing that is what she is describing — and it adds a dimension the acquisition series did not capture: acquisition physics operating on the customer side, forcing platform decisions that compound the vendor-side behavioral collapse already in motion.
Nipendo — which carried the highest independent HFS™ score in the archive at 8.7 — was acquired by American Express in January 2023. Within two years it had been sold off in pieces for $2 million and effectively ceased to exist as a procurement technology platform. That is not behavioral alignment decline. That is complete dissolution — acquisition physics at its most extreme expression, where the acquired entity does not resolve to the lower score but disappears entirely.
And KPMG — one of the firms that charges clients to navigate AI readiness and transformation strategy — announced an AI Spark Innovation awards program offering cash prizes materially larger than annual bonuses to incentivize its own consultants to adopt AI productively. Rob Fisher, KPMG US Vice Chair of Advisory, described the initiative as trying to unlock “grassroots innovation” by “bringing more carrots forward.” That is not the language of an organization executing a strategy. That is the language of an organization in stage two of the fourth cycle — where the growth clock is already running, the consolidation pressure is already present, and the readiness gap has not been diagnosed, let alone closed.
Three organizations. Three different expressions of the same structural pattern. All within the past 24 months.
If the physics of enterprise software evolution required decades to become visible, it could be dismissed as historical commentary. The fact that it is observable in real time — in a practitioner’s candid interview, in a $2 million dissolution of an 8.7-scored platform, and in a Big Four firm’s public admission that it cannot get its own people to use AI without prize money — is what elevates it from a retrospective framework to a living diagnostic.
The fourth cycle is not coming. It is already here. The question the Hansen Fit Score™ is designed to answer — are you ready to absorb what you are about to deploy? — has never been more urgent than it is right now.
Procurement Insights
The Physics of Enterprise Software Evolution: Oracle, Coupa, and the Law That Repeats Across Every Generation
Posted on March 13, 2026
0
By Jon W. Hansen | Procurement Insights
In a recent post, I applied the Hansen Fit Score™ retrospectively to three entities — SAP (1990), Ariba (1997), and SAP Ariba (2012) — to ask a question the industry has never formally answered: what would the structural diagnostic have shown before the failures arrived?
The answer was uncomfortable. Across 35 years of technological advancement, the HFS™ composite score declined. More capability. More integration. More market presence. Lower score.
That post established a principle I called acquisition physics: ProcureTech acquisitions resolve to the lower Behavioral Alignment score — not the higher one. The acquiring organization’s structural DNA dominates. Ariba’s 5.0 did not lift SAP’s 3.0. SAP’s 3.0 consumed Ariba’s 5.0.
A principle demonstrated once is a finding. Demonstrated across three independent acquisition chains spanning three decades, it becomes something closer to a law — what the three graphics in this series collectively reveal as the physics of enterprise software evolution: a repeating structural force that operates regardless of the vendor name, the acquisition rationale, the ownership model, or the era in which it occurs.
This post tests it against Oracle and Coupa.
Why These Two Series
The Oracle series is the most dramatic acquisition chain in enterprise software history — an 18-month hostile takeover that generated DOJ antitrust challenges, European Commission intervention, customer revolts, and 6,000 immediate layoffs. If acquisition physics holds under those conditions, it holds everywhere.
The Coupa series introduces a variable the SAP and Oracle chains did not have: private equity ownership. Thoma Bravo’s $8 billion acquisition of Coupa in February 2023 added a financial extraction dynamic — margin expansion, cost reduction, exit timeline pressure — that restructures behavioral incentives in ways that neither a founder-led company nor a public company faces in the same form. And uniquely, the Coupa series allows the HFS™ to operate in predictive mode: the Cirtuo and Scoutbee acquisitions are recent enough that the forecast can be published on record before the outcomes are known.
That is what a structural diagnostic framework makes possible. And what no sponsored analyst firm can do.
Series II: JD Edwards → PeopleSoft → Oracle (2000–2005)
Three entities. Five years. The largest single-point behavioral collapse in the series.
JD Edwards — circa 2000 (Independent Era)
JD Edwards earned its reputation the hard way — 23 years of independent operation, a genuine mid-market customer-first orientation, and technical architecture that gave it a loyal installed base that persisted well past the acquisition. The Denver roots mattered. The culture produced a Behavioral Alignment score that no subsequent acquirer could sustain.
Technical Capability: 7.5/10 Genuine depth in manufacturing, distribution, and mid-market ERP. OneWorld’s platform-independent architecture was technically sophisticated for its era.
Behavioral Alignment: 6.5/10 The highest in this series at point of entry. Customer-first DNA, outcome-oriented implementation model, practitioner trust built over two decades of independent operation.
HFS™ Composite: ~7.0/10 — MODERATE RISK
PeopleSoft — circa 2003 (Post-JDE Merger)
PeopleSoft acquired JD Edwards in July 2003 for $1.7 billion — a friendly merger designed to create the world’s second-largest enterprise software company. Within days, Oracle launched its hostile bid. What followed was an 18-month siege that consumed the organizational attention PeopleSoft needed for customer success.
Organizations fighting for survival do not optimize for implementation quality. The behavioral alignment score reflects that reality.
Technical Capability: 7.0/10 The combined platform had real breadth. The JDE integration added capability. The technical case was coherent.
Behavioral Alignment: 5.0/10 A 1.5-point drop from JDE’s independent score — not because PeopleSoft was a bad organization, but because absorbing a major acquisition while simultaneously fighting a hostile takeover is not a condition under which customer outcomes improve. Ninety-five percent of PeopleSoft and JDE users surveyed in 2003 said they did not want Oracle’s bid to succeed. That number reflects something real about the behavioral model customers experienced.
Risk Designation: ELEVATED — with a trajectory warning. The siege was ongoing. The score was declining in real time.
HFS™ Composite: ~6.0/10 — ELEVATED RISK
Oracle — circa 2005 (Post-Hostile Takeover)
The deal closed January 7, 2005. Oracle fired 6,000 of PeopleSoft’s 11,000 employees within one month. The DOJ and European Commission had both filed antitrust challenges before the acquisition was complete. The behavioral model was set before a single customer migration began.
Here is where acquisition physics demonstrates its most uncomfortable implication: Oracle’s technical capability score is the highest in this series at 8.5. The combined entity — Oracle E-Business Suite, PeopleSoft, JD Edwards — had genuine technical depth. The platform breadth was real.
It did not matter.
Technical Capability: 8.5/10 The highest technical score across all three acquisition series. Real breadth, real depth, real engineering capability.
Behavioral Alignment: 2.5/10 Oracle’s founding behavioral model — database-led, vendor-controlled, implementation risk transferred to the client — was already established before PeopleSoft existed. The hostile takeover did not create a new behavioral model. It imposed the existing one at scale.
Risk Designation: SRD-E — Structural Risk, Ecosystem-level.
HFS™ Composite: ~4.8/10 — HIGH RISK
The 3.7-point gap between Technical Capability (8.5) and HFS™ Composite (4.8) at the Oracle acquisition point is the largest single-point divergence across all three series. Technical capability and behavioral alignment moved in opposite directions simultaneously. That is not an anomaly. It is acquisition physics at maximum expression.
The Oracle Arc — Summary Table
Each acquisition resolved to the lower Behavioral Alignment score. JDE’s 6.5 became PeopleSoft’s 5.0. PeopleSoft’s 5.0 became Oracle’s 2.5. The acquiring organization’s structural DNA dominated every time.
Series III: Coupa (2006–2025+)
Four phases. One direction. And a reminder that the HFS™ has always been a prospective diagnostic — applied before outcomes are known, not after. The Coupa forecast simply makes that visible in real time.
Coupa — circa 2006 (Founding Era)
Procurement Insights published what is likely the industry’s first formal independent white paper on Coupa in 2009 — three years before mainstream analyst coverage began. The founding-era observation matters here because it establishes a baseline that the subsequent ownership changes can be measured against honestly.
Rob Bernshteyn’s Business Spend Management positioning was genuinely outcome-oriented in the founding era. The BSM thesis — that procurement technology should deliver measurable business outcomes, not just process automation — was a real behavioral differentiator from SAP and Oracle’s Technology→Process→People inversion.
Technical Capability: 6.0/10 Early-stage platform. The technical promise was real but not yet at enterprise depth.
Behavioral Alignment: 6.5/10 The highest Behavioral Alignment score in Coupa’s history. Outcome-focused, practitioner-oriented, independent before the growth clock began running.
HFS™ Composite: ~6.3/10 — MODERATE RISK
Coupa Public — circa 2022 (Peak Public Company Era)
The growth clock that began running at IPO (2016) had been running for six years by 2022. Twenty-one acquisitions. Revenue pressure. Analyst attention. The behavioral model that produced a 6.5 Behavioral Alignment score at founding had been subordinated — gradually, then decisively — to the imperatives of public market growth.
This is the same pattern the SAP series showed at the Ariba founding stage: a declining score in motion. The difference is that Coupa’s decline was faster, because the public market growth clock is less patient than the enterprise software market of the 1990s.
Technical Capability: 8.0/10 The platform had real breadth by 2022. Twenty-one acquisitions produced genuine capability across spend management, supplier management, and contract lifecycle.
Behavioral Alignment: 3.5/10 A 3.0-point drop from founding. Implementation support as a function had been structurally deprioritized relative to new logo acquisition. The gap between what was sold and what was delivered had widened materially.
HFS™ Composite: ~5.0/10 — HIGH RISK
Coupa PE-Owned — circa 2023 (Thoma Bravo, $8 Billion)
Thoma Bravo’s acquisition playbook across enterprise software is well-documented: Sailpoint, Barracuda, Sophos, Proofpoint. The pattern is consistent — take private, cut costs, optimize margins, acquire to build platform value, position for exit. The typical hold period is three to five years.
This introduces a structural tension that the SAP and Oracle series did not contain in the same form. Implementation support teams are cost centers. PE playbooks reduce cost centers. Exit timelines may conflict with the long-term product investment that complex enterprise implementations require. Leagh Turner replaced Rob Bernshteyn as CEO in November 2023 — the founder’s behavioral orientation formally departed with the leadership change.
Technical Capability: 7.5/10 Rationalization of the platform under PE ownership produced some technical consolidation. Real capability remained.
Behavioral Alignment: 2.8/10 PE ownership does not improve Behavioral Alignment. The incentive structure makes improvement structurally unlikely within a standard exit timeline. The score reflects the operational reality, not a judgment about intent.
Risk Designation: SRD-E
HFS™ Composite: ~4.6/10 — HIGH RISK
Coupa + Cirtuo + Scoutbee — 2025+ (Forward Forecast)
Cirtuo (May 2025) introduced AI-powered category management capability — a genuine technical addition. Scoutbee (October 2025) extended supplier intelligence. Both acquisitions add real technical depth. The “autonomous spend management” repositioning reflects a coherent technical vision.
The behavioral alignment question is not whether these acquisitions add capability. They do. The question is the same one the SAP, Oracle, and Coupa series have already answered: does adding technical capability inside a deteriorating behavioral model improve the composite score?
Across every series examined, the answer is no.
Technical Capability: 8.0 (forecast) Cirtuo and Scoutbee restore the technical ceiling to public-era levels. The platform is genuinely capable.
Behavioral Alignment: 2.5 (forecast) Thoma Bravo’s PE ownership structure has not changed. The exit clock is running. Implementation support remains a cost center. No structural mechanism exists for behavioral alignment improvement within the current ownership model.
Risk Designation: SRD-E (forecast)
HFS™ Composite: ~4.3/10 — HIGH RISK (FORECAST)
This forecast is published on record. If it holds, the acquisition physics law is validated across three independent series. If it does not hold — if Coupa demonstrates material behavioral alignment improvement under PE ownership — the Hansen Fit Score™ methodology gets refined accordingly. Either outcome is informative. Only one outcome is likely.
The Coupa Arc — Summary Table
The Pattern Across Three Series
Technical Rises. HFS™ Falls.
Three acquisition chains. Three decades. Three different structural contexts — a SAP-era mega-acquisition, a hostile takeover, and a private equity buyout. The same result every time.
The composite score declines at every acquisition point. The direction does not change with the ownership structure, the acquisition rationale, the technical capability of the combined entity, or the era in which it occurs.
That is not coincidence. It is a structural pattern with a structural explanation: behavioral alignment is an organizational property, not a technical one. You cannot acquire your way to better behavioral alignment. You can only build it — or lose it.
In every acquisition chain examined across three decades, the composite score resolved to the lower Behavioral Alignment score — without exception.
The Cycle That Repeats
When the three series are viewed as a sequence rather than three separate assessments, a structural pattern emerges that no single series makes visible on its own.
Enterprise software evolves through a repeating five-stage cycle:
1. Innovation — A new platform or category emerges with genuine technical promise and outcome-oriented behavioral DNA. Early-stage Behavioral Alignment scores are real.
2. Consolidation — Growth pressure, acquisition activity, and market scaling begin subordinating customer outcomes to revenue imperatives. Behavioral Alignment starts declining.
3. Behavioral Collapse — Acquisition physics takes hold. The combined entity resolves to the lower Behavioral Alignment score. Technical capability continues rising. The composite HFS™ score falls.
4. Implementation Failure — The gap between what is sold and what is delivered becomes undeniable. The 80% failure rate is not random. It is the predictable harvest of a behavioral model whose decline was measurable before a single contract was signed.
5. Restart — The market declares the old platform obsolete, embraces a new wave of innovation, and the cycle begins again.
The ProcureTech industry has completed this cycle twice and is currently in stage three of the third.
Generation 1 — ERP Consolidation (SAP/Oracle era): Driver: technology centralization. The founding behavioral DNA of SAP’s Technology→Process→People inversion was present at R/2. The failures at Hershey, FoxMeyer, and Cadbury were not surprises. They were stage four.
Generation 2 — Enterprise Application Consolidation (PeopleSoft/Ariba era): Driver: acquisition scaling. JDE’s 7.0 HFS™ became Oracle’s 4.8 in five years. Ariba’s 5.8 became SAP Ariba’s 4.8 in fifteen. Both followed the same arc.
Generation 3 — ProcureTech SaaS and PE Ownership (Coupa era): Driver: private equity exit economics. The cycle now runs faster. Coupa’s Behavioral Alignment declined from 6.5 to 2.5 in under twenty years — a steeper drop than either previous generation, compressed by the combined pressure of public market growth clocks and PE exit timelines.
The AI wave is currently in stage one of the fourth cycle. The technical promise is real. The behavioral alignment questions are the same ones that were present — and answerable — at the start of every previous cycle.
What This Means for the Current Market
The ProcureTech market in 2026 is executing the same acquisition sequence at accelerated pace, with AI as the justification. The names are different. The platform acronyms are different. The acquisition press releases use different language.
The physics are identical.
Organizations currently evaluating procuretech platforms — particularly those under PE ownership, those that have completed multiple rapid acquisitions, or those repositioning existing products as AI-native — are looking at the same structural conditions that produced the scores above. The cycle does not pause because the technology has changed. It accelerates because the technology has changed, and the organizational operating model required to absorb it has not.
The HFS™ framework does not require a completed failure to identify elevated risk. It requires an honest answer to three structural questions. The archive contains 18 years of evidence that those questions were answerable before the failures arrived.
They remain answerable now. The fourth cycle is beginning. The diagnostic is the same one it was in 1990.
People first. Process second. Technology third.
In that order. Every time. Without exception.
This is Part II of an ongoing series applying the Hansen Fit Score™ retrospectively and predictively across major ProcureTech acquisition chains. [Part I — SAP, Ariba, and the DNA of ProcureTech Failure] establishes the methodology and the acquisition physics principle.
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-
Bonus Section: The Pattern in the Present Tense
The three acquisition series documented above span 1990 to 2025. But the physics of enterprise software evolution does not require a 35-year arc to become visible. It is operating right now — in three cases that have all surfaced within the past 24 months, each confirming a different dimension of the same structural law.
Millie, a procurement leader at Geosyntec, recently described in her own words what it felt like to transition from AdaptOne to Coupa after Blackstone’s acquisition of her organization drove transaction volumes past the point AdaptOne could sustain: “cookie cutter — this is what you get” and “the business is still like well why can’t we go back.” That is a practitioner inside the Coupa behavioral alignment decline confirming the forecast without knowing that is what she is describing — and it adds a dimension the acquisition series did not capture: acquisition physics operating on the customer side, forcing platform decisions that compound the vendor-side behavioral collapse already in motion.
Nipendo — which carried the highest independent HFS™ score in the archive at 8.7 — was acquired by American Express in January 2023. Within two years it had been sold off in pieces for $2 million and effectively ceased to exist as a procurement technology platform. That is not behavioral alignment decline. That is complete dissolution — acquisition physics at its most extreme expression, where the acquired entity does not resolve to the lower score but disappears entirely.
And KPMG — one of the firms that charges clients to navigate AI readiness and transformation strategy — announced an AI Spark Innovation awards program offering cash prizes materially larger than annual bonuses to incentivize its own consultants to adopt AI productively. Rob Fisher, KPMG US Vice Chair of Advisory, described the initiative as trying to unlock “grassroots innovation” by “bringing more carrots forward.” That is not the language of an organization executing a strategy. That is the language of an organization in stage two of the fourth cycle — where the growth clock is already running, the consolidation pressure is already present, and the readiness gap has not been diagnosed, let alone closed.
Three organizations. Three different expressions of the same structural pattern. All within the past 24 months.
If the physics of enterprise software evolution required decades to become visible, it could be dismissed as historical commentary. The fact that it is observable in real time — in a practitioner’s candid interview, in a $2 million dissolution of an 8.7-scored platform, and in a Big Four firm’s public admission that it cannot get its own people to use AI without prize money — is what elevates it from a retrospective framework to a living diagnostic.
The fourth cycle is not coming. It is already here. The question the Hansen Fit Score™ is designed to answer — are you ready to absorb what you are about to deploy? — has never been more urgent than it is right now.
Share this:
Related