Every acquisition comes with a number. A synergy projection bold enough to justify the deal, structured enough to survive a CFO review, and ambitious enough to set expectations that procurement is then quietly expected to meet.
The problem is that procurement rarely has what it needs to deliver, unified data, aligned systems, cross-entity supplier visibility, or a shared operating model that both teams have agreed to.
When integrations underdeliver, they rarely announce it. What gets communicated is a
- “Longer than expected integration timeline.”
- “Phased approach to systems consolidation.”
- “Synergy number that gets quietly revised in the next earnings call.”
And somewhere in the middle of all of it, procurement is expected to show savings.
This post draws on 25 years of procurement M&A experience across Fortune 500 organizations, to break down the two structural failures that account for most value destruction in post-merger procurement, what successful integrations consistently do differently, and how to protect your synergy projections in the 90 days that matter most.
🎧 Watch the full podcast here:
Scaling Procurement Across Acquisitions: What Breaks First and How to Fix It | Beyond Procurement
The gap between the boardroom and the ground, That’s Where Acquisition Value Disappears
Every acquisition looks clean from the top.
On paper, leadership sees:
- Consolidated supplier bases with unified leverage
- Shared contracts driving measurable savings
- An eight-figure synergy number in the CFO’s model
- A procurement function that will “align quickly”
On the ground, the reality is different:
- Two teams that each believe their processes are the right ones
- Two ERP instances running in parallel with no shared data layer
- A CPO burning political capital trying to impose a model that was never designed for the company they just acquired
- Dashboards showing different numbers for the same KPIs
The gap between these two worlds is where acquisition value disappears.
Failure #1: The Phase 2 trap
When the deal closes, the pressure hits immediately. Show early wins. Announce headcount synergies. Declare savings. Move fast enough that the board stays confident.
In that environment, systems integration starts to feel like unglamorous, detailed work that can wait. So, it is scheduled. It becomes Phase 2.
In conversation Amr is direct about where that leads:
“When we start, we are not ready with a blueprint on how the systems will be merging. We are leaving it as a second phase. And this is another point that makes mergers and acquisitions fall or fail totally, or delay getting the actual fruits that you are expecting.”
Without a shared data layer, there is no shared visibility. Without shared visibility, the KPIs being reported upward are built on two different definitions of the same numbers. The savings model starts drifting from reality, quietly and consistently, until someone has to explain the gap in a board meeting.
Then comes the enforcement trap.
Leaders arrive with a procurement operating model, sometimes one that took 18 months and a significant budget to design and try to impose it wholesale on the acquired entity. The logic feels sound: this model worked before; it will work again.
The problem is that the acquired entity is not a blank canvas.
“You are coming and saying, I have spent millions buying Oracle or SAP, it should be working. You are trying to put the mosaic on. It is not a puzzle anymore.”
The mosaic looks coherent from a distance. Colorful, structured, and attractive. Get closer, and the pieces don’t actually fit. It holds together on paper and breaks down in execution. By the time that becomes visible, the integration timeline has already slipped, sometimes by a full year.
Failure #2: The ego tax
The second failure is harder to name in a steering committee. It does not appear on the risk register. But it may be the most consistently damaging pattern in post-merger procurement.
Upon asking him what CPOs must stop doing the moment a deal closes, and he does not hesitate:
“They should not listen to their ego. They should understand that they are not knowledge owners.”
This does not look like an arrogance. It looks like competence. A CPO who has led successful transformations, who knows what good procurement looks like, and who makes fast decisions under pressure. That profile is exactly what organizations hire for.
But in an integration, that same decisiveness becomes the problem. It shuts down the listening that the situation actually requires.
“Go into any meeting with a very agile mindset that you want to listen to, the sponge. Listen, then react. You are not a teacher. You are not a professor.”
What gets lost when leaders stop listening:
- Supplier relationships built over years, held in someone’s memory and not in any system
- Local compliance nuances that no due diligence document ever captured
- Informal workflows that actually function better than the documented ones
- Institutional knowledge that took a decade to build
A CPO who arrives with answers rather than questions overrides all of it, and in doing so, destroys the very “power of two” the acquisition was built to capture.
What successful integrations have in common
Goals were clear, measurable, and agreed upon by both teams before anyone started talking about systems or or org structures.
The acquisitions that consistently deliver their promised value share one quality, in Amr’s experience. The planning happened before the deal closed, not after.
“One of the best acquisitions that I have seen in my whole life, when the pre-planning for the acquisition was done in the right way. We have our own blueprint. A blueprint that is not prejudiced to any side. It is a blueprint of success.”
The leaders who execute this well follow a clear sequence:
- Common KPIs before common processes. Establish a shared language first
- Common data before common org structure. Give people something real to align around
- Shared ownership of the blueprint. Let both teams build it together, not inherit it
“The easiest way to find the common language is to explain what my KPIs are. Put it in front of you. Let the people see it. Let people understand it. Let people feel that this is yours.”
The smarter way to solve the system’s problem
Common KPIs need a common data layer to mean anything. And in an integration context, that data layer must work across two entities without forcing either one to abandon what it already runs.
Most integration teams assume systems consolidation means picking one platform and migrating everyone onto it. That is exactly the kind of decision that triggers resistance, delays, and the enforcement trap Amr described. It does not have to work that way.
ewiz procure is built specifically to sit on top of what you already run, not replace it. That matters a lot in an M&A context:
It connects to your existing stack on both sides:
- SAP, Oracle, MS Dynamics, and NetSuite on the ERP side
- Coupa, SAP Ariba, Jaggaer, and Zycus on the S2P side
And gives procurement leadership a unified operating picture from day one.
What teams typically see once it’s running:
- 8–12% cost savings
- 30% faster procurement cycles
- 27% lower process costs
- 25% better supplier performance
- ~50% faster supplier onboarding
The technology should support integration, not create a new battlefield within it.
Humility and Urgency: The 25-Year Pattern
“I am really astonished that I still see companies not investing heavily in their capabilities of the teams or their data capabilities from the AI perspective.”
The solutions exist. The lessons from decades of integrations across EMEA are well understood. What is missing, more often than not, is two things working together at the same time.
The humility to listen before leading. And the urgency to treat systems as a Day 1 priority, not a Phase 2 aspiration.
The deals that bleed value rarely fail at the negotiation table. They fail in the 90 days after: the blueprint was not ready, the ego was too loud, and the systems were scheduled for later.
In procurement integration, later is usually too late.
Your integration risk is highest in the first 90 days
The integrations that deliver don’t wait until Phase 2 to get serious about systems and data. If your deal has closed, or is closing, the next 90 days are your highest-leverage window.
We’ll help you validate your procurement integration blueprint before the gaps become the story.
No pitch decks, no generic demos. Just a direct conversation about where your integration stands and what it needs.
