An acquisition does not create value when the legal entities combine. It creates value when the combined organization can do something materially better: serve more people, move capital to a real constraint, integrate a critical network, reduce decision latency, or operate a new capability with greater reliability than either party could achieve alone.
That is why M&A belongs in the operating model. The transaction joins more than assets and financial statements. It joins data, energy exposure, satellites, terrestrial networks, spectrum, suppliers, contracts, brands, talent, service commitments, regulatory obligations, and the decision rights that keep those parts coherent.
Start with the capability, not the synergy slide
We define the integration thesis before the integration plan:
- What capability is the combined enterprise trying to make possible?
- Which constraint currently prevents it: capital, energy, coverage, latency, trust, talent, service reliability, or market access?
- Which assets, permissions, relationships, and operating practices relax that constraint?
- What evidence will show that the capability is real after close?
- What would make the thesis false, and who has authority to stop or change course?
This reframes diligence. A satellite platform may be valuable because it changes coverage, resilience, or latency—not because it adds another asset to a portfolio. A telecommunications transaction may matter because it connects markets, emergency services, logistics, and financial infrastructure. A financial-services acquisition may matter because it changes the speed and quality of capital allocation across a network. A marketing or distribution combination may matter because a new operating capability can reach customers in the languages, channels, and regulatory contexts where demand actually exists.
Six integration surfaces
The diligence work should make six surfaces visible:
- Physical and energy: power, cooling, facilities, transmission, spectrum, orbit, maintenance, and supply-chain dependencies.
- Communications: terrestrial and satellite paths, network diversity, latency, availability, coverage, sovereignty, and partner exposure.
- Data and intelligence: ownership, provenance, access, quality, model evaluation, cybersecurity, and human review.
- Finance and capital: cash flows, funding gates, insurance, liquidity, capital allocation, and the value of optionality under uncertainty.
- Market and customer: the promise, brand, channel, pricing, language, regulatory boundary, and adoption friction that make the capability useful.
- Service and change: owners, incidents, problems, changes, configuration, releases, continuity, knowledge, and continual improvement.
The last surface is where ITIL practice earns its place. Service management is not bureaucratic decoration around a deal. It is the operating discipline that makes a new capability supportable: someone owns the promise, changes are assessed before release, failure is learned from, configuration is visible, and recovery is designed before the first incident.
A global scale requires local operating truth
UN DESA’s current medium projection puts the global population at about 9.6 billion in 2050. ITU reports that 6 billion people were online in 2025 while 2.2 billion remained offline, with substantial gaps in affordability, quality, skills, and rural access. The implication for a global transaction is plain: scale is not the same as reach. An integrated enterprise must know where its services work, where they fail, and which local constraints change the mechanism without changing the outcome.
The energy system sets another hard boundary. The IEA projects data-centre electricity demand to more than double to around 945 TWh by 2030 and notes that grid connection and transmission constraints can delay projects. A deal that expands digital capability without integrating power, permitting, cooling, resilience, and community legitimacy is not an infrastructure strategy. It is a deferred operating problem.
Value is a service outcome
The post-close scorecard should measure whether the combined system is becoming more capable:
- decision latency and the age of unresolved cross-functional dependencies;
- service availability, recovery time, and change failure rate;
- energy used per unit of computation or delivered service;
- connectivity reach and quality by market, region, and customer segment;
- critical data with an owner, provenance, access rule, and refresh expectation;
- retention, adoption, and service quality by channel and language;
- capital deployed against the constraint that limits growth.
Financial return remains essential. It is not sufficient. If the income statement improves while service reliability, access, energy intensity, or decision speed deteriorate, the transaction is exporting cost to customers, employees, communities, or the future.
Global Enterprise helps boards, corporate development leaders, and operating executives make the integration thesis explicit: what is being assembled, which constraints govern it, how value will be observed, and which service and change system can carry it across borders.