BP-053Grade B28 supporting cases (26 counted), 0 counter-examples
Buy the capabilities the new strategy lacks rather than building all of them
The practice
Where the new strategy needs capabilities the company cannot build in time, acquire them, recycle exit proceeds into those acquisitions, and leave the acquired culture intact.
Why it works
Building every new capability in-house is slow, and in a shifting market the window can close before the capability exists. Acquiring capability (software, products, creative or technical teams) shortens the path, especially when funded by exits from businesses that no longer fit. The value bought is often the people and culture, so leaving them intact, and sometimes putting acquired leaders in charge, is part of the practice (BP-008). Price discipline still applies (BP-039).
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
- Map the capabilities the strategy needs against what can be built in time.
- Buy the gaps, funded where possible by exits from non-core businesses.
- Keep the acquired team's culture and leadership intact unless the thesis requires otherwise.
- Set a walk-away price for each capability acquisition.
Warning signs
- Acquisitions are chosen for size rather than capability fit.
- Acquired teams are integrated into the old structure immediately.
When it applies
- Strategic pivots, digital transformations and portfolio reshaping.
When it does not
- When the capability is core to the culture and can be grown in time; acquired cultures may then clash.
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. 2 supporting case(s) rest only on company-reported claims and are not counted toward the grade.
Where it applies
- Transformation type
- Topic (business problem)
- Function
- Starting situation
- Industry
- Region
Supporting and counter cases
Microsoft Corporation CS-013
FUJIFILM Holdings Corporation (Fuji Photo Film Co., Ltd. until 2006) CS-090
Schneider Electric SE CS-098
Hitachi, Ltd. CS-047
The Walt Disney Company CS-032
Satyam Computer Services (Mahindra Satyam), acquired by Tech Mahindra CS-118
TOTVS S.A. CS-127
WEG S.A. CS-128
FPT Corporation (FPT), with its export subsidiary FPT Software CS-132
Hikma Pharmaceuticals PLC (established in Amman, Jordan, in 1978; listed in London from 2005) CS-140
MonotaRO Co., Ltd. (Tokyo Stock Exchange), majority-owned by W.W. Grainger, Inc. since 2009 CS-143
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.

