BP-036Grade B15 supporting cases (15 counted), 0 counter-examples
Judge an integration by customer retention and revenue health, not by synergy capture
The practice
Make the acquired and combined businesses' customer retention, sales and brand health the first test of a merger, and value the deal on the customers who will stay through integration.
Why it works
Cost synergies are visible and controllable, so integrations are often steered by them. Revenue is where integrations quietly lose value: customers leave during platform changes, sales forces are distracted, and brands starve of investment while savings targets are met. Synergy delivery is therefore not evidence that a deal is working. Valuing the deal on the customers likely to stay, protecting the acquired business's customer proposition while the back office is integrated, and treating early customer-quality signals as integration failures put the revenue risk on the scorecard. Integration savings cannot replace the renewal of a shrinking channel.
KB synthesis: the mechanism is the knowledgebase's own reasoning, drawn from the member lessons. Factual support is the case claims under evidence.cases and the research under evidence.research (R-refs).
How to apply it
- Put customer retention, like-for-like sales and brand health at the top of the integration scorecard.
- Value the target on a conservative retention scenario through integration.
- Ring-fence the acquired business's customer proposition until the back office is stable.
- Treat early churn or service-quality drops as integration failures requiring action.
- Plan for the revenue the integration will lose, not only the costs it will save.
Warning signs
- Synergies are ahead of plan while sales decline.
- Customer churn rises in the acquired base after platform changes.
- Marketing and brand spend is the first saving.
When it applies
- Mergers in consumer goods, retail, telecoms, banking and other customer-franchise businesses.
When it does not
- Pure capacity or asset consolidations with contracted customers, where revenue risk is low.
Evidence grade: Grade B
At least 6 counted supporting cases for every 100 cases in the knowledgebase (6 × cases ÷ 100, rounded to the nearest whole number), whose primary regions span at least 4 regions.
Why this grade
Grade B by schema 4.10 route: >=14 counted cases across >=4 primary regions (the case bar is 6 per 100 cases in the knowledgebase, 235 cases). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does.
Where it applies
- Transformation type
- Topic (business problem)
- Function
- Starting situation
- Industry
- Region
Supporting and counter cases
The Kraft Heinz Company CS-050
Sears Holdings Corporation CS-051
Sprint Nextel Corporation CS-083
Natura &Co Holding S.A. CS-060
Nokia Corporation CS-066
Satyam Computer Services (Mahindra Satyam), acquired by Tech Mahindra CS-118
WEG S.A. CS-128
Xero Limited (cloud accounting software, listed on the ASX) CS-135
Avast Software (Avast plc from 2018), Prague-based consumer cybersecurity company CS-229
Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026
Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.

