integrations

The Deal Is Closed. The Value Is Not.

Most acquisitions fail in the months after signing. A GE story shows how fast it can happen, and how the damage gets fixed.


The champagne moment of an acquisition is the signing. The value moment comes much later, and for many deals it never comes at all. Study after study puts the share of acquisitions that fail to deliver their expected value somewhere between half and two thirds. The striking thing is that the causes are rarely strategic. The logic of the deal was sound. The price was defensible. What breaks is the execution of the integration itself, when the integration plan meets the operating reality of two businesses that were never designed to work together.

This is not a theoretical observation. Years inside General Electric provided a front-row seat to one of the most instructive integration failures imaginable, and to its recovery.

A Reverse Acquisition in Bavaria

GE Capital Solutions in Germany, an equipment leasing business, acquired a competitor twice its size. The combined entity became a multi-billion euro business unit. On paper, a market-defining move.

In practice, it was a reverse acquisition. The CEO and most of the management team of the acquired company took control of the combined business. And with that came a culture clash that everyone saw coming and nobody managed. On one side, a GE business: process-driven, metric-driven, direct, shaped by the GE operating disciplines. On the other, a traditional company from Bavaria with its own codes and hierarchy. The symbol said everything: the GE CEO drove his own car, the new CEO was driven by a chauffeur.

Then came the GE way of extracting synergies. A social plan, and a wave of employees fired or resigning. The plan delivered its headcount number. It also delivered something the model had not priced: a massive loss of expertise, precisely in the teams that knew how the acquired portfolio actually worked.

When the Engine Breaks

The integration inherited two large vendor programs, Xerox and Ricoh, totaling 800 million euros in sales, to be migrated into the new structure. The data migration and the ERP implementation failed. What followed was the catastrophe that failed integrations produce, except at industrial scale and on a regulated clock.

Fifteen thousands leasing contracts stopped being invoiced. Customers who receive no invoice do not pay, so cash collapsed alongside revenue recognition. Ten thousand customer claims flooded a customer service organization that had just lost much of its experienced staff. Xerox, watching its own customers caught in the chaos, threatened to end its relationship with GE across Europe, turning a German operational failure into a European commercial crisis.

And because the business was a regulated bank, the failure had a fourth dimension. Customers who are not invoiced stop paying, and non-payment reads as delinquency. The delinquency ratio went through the roof, and the German banking regulator started asking questions that no integration steering committee had planned for.

One failed data and system migration. Four simultaneous crises: operational, commercial, financial, and regulatory. That is what integration risk actually looks like. It is not a synergy shortfall on a slide. It is the operating engine of the combined business seizing up in production.

The Hidden Tax: Leadership Attention

There is a fifth cost that never appears in any deal model, and it is often the largest: the leadership capacity an integration consumes.

At the peak of the German crisis, half the leadership team of an eight billion euro business was traveling to Germany once a month to review progress. The full German leadership team was in the room as well, along with the integration team. Thirty people in the room. Thirty of the most expensive, most scarce hours in the company, spent every month on one broken integration, month after month.

The arithmetic of that room is brutal. Every hour those leaders spent on Germany was an hour not spent on the other businesses: their customers, their growth plans, their own operational issues. A failed integration does not just destroy value in the acquired business. It quietly taxes the performance of everything else the leadership team is responsible for, because attention is the one resource that cannot be hired quickly. The rest of the portfolio gets managed on autopilot precisely when it deserves better.

And a thirty-person monthly review is itself a symptom, not a solution. A room that size demonstrates concern, but it does not make decisions. Real recovery governance is the opposite: a small team, clear single owners, a tight weekly cadence close to the operations, and a short escalation line to the top. Senior attention is essential in a crisis, but it must be structured to decide, not to witness.

This is a question boards should ask before any deal: if this integration goes wrong, whose time will it consume, and what will that cost the rest of the business? The answer is usually more sobering than the synergy model.

The Illusions That Set It Up

Looking back, that integration failed the way most do, through four illusions that are worth naming because they repeat everywhere.

The first illusion is that signing creates alignment. It does not. Signing creates a legal structure. The two organizations still had different processes, different systems, different data definitions, and, in this case, two management cultures actively competing for control. Alignment has to be built deliberately, decision by decision. A reverse acquisition raises the stakes further: the acquirer’s disciplines and the acquired team’s authority pull in opposite directions unless leadership reconciles them explicitly.

The second illusion is that synergies are a finance exercise. The social plan delivered its savings number. But synergy value is delivered in operations, and the same restructuring that produced the savings destroyed the expertise needed to run the migration. Nobody had priced the dependency between the two.

The third illusion is that the systems work can be treated as a back-office task. The ERP and data migration carried the entire commercial relationship with two major vendors and the invoicing of the whole portfolio. It was staffed and governed as an IT project. It was, in reality, the single highest-risk item in the whole deal.

The fourth illusion is that commercial integration, organizational redesign and ERP migration can all be delivered at once. Sequence the work instead: capture priority synergies, establish a unified financial model and migrate the ERP only when the business is ready. Otherwise, the migration competes for scarce resources, embeds unresolved differences at significant cost, and risks destroying value instead of creating it.

Fixing It: Sequence Beats Ambition

I joined the business to fix the situation. The most important decision we made was not any single fix. It was the method: a clear roadmap, and a strict sequence. Fix issues one after the other, in order of impact, rather than attacking everything at once and achieving nothing.

That discipline matters because a broken integration produces infinite urgent demands. Every function is on fire, every stakeholder wants their issue first, and the natural response is to launch twenty parallel initiatives. Twenty parallel initiatives in an exhausted organization deliver none. Sequencing is what turns a crisis into a queue.

The recovery logic followed the same order every failed integration requires.

Stop the bleeding first. Restore invoicing, because everything downstream, cash, delinquency, regulatory standing, customer trust, depended on invoices going out again. A contract that is invoiced correctly removes a claim, a delinquency case, and a regulatory data point at once.

Rebuild one version of the numbers. In the chaos, nobody could say precisely how many contracts were affected, what was billed, what was collectible. Trusted operational data, contract by contract, was a precondition for every other decision, including what to tell the regulator and the vendors.

Manage the critical relationships with facts. Xerox and the banking authorities did not need reassurance, they needed evidence: a credible plan, visible milestones, and weekly proof of progress. Nothing rebuilds stakeholder confidence like a commitment made in week one and demonstrably delivered in week four.

Fix the process, then the backlog. Clearing fifteen thousand claims is pointless if the engine keeps producing new ones. The permanent fix to the billing process had to come before the mass processing of the backlog, otherwise the backlog refills.

Install a cadence and hold it. Weekly operating reviews, single owners per issue, decisions made in the room, blockers escalated the same day. The rhythm was the recovery. It kept the sequence honest and made progress visible to an organization that badly needed to see some.

What This Teaches About the Next Deal

The lessons transfer to any acquirer, in any industry.

Price the operating risk, not just the synergies. The highest-risk item in this deal was never the market or the price. It was a data and system migration. Due diligence teams model synergies to the decimal, yet rarely ask the questions that predict integration outcomes: which ERP survives, who owns the migration, what happens to invoicing on day one, and how much expertise the restructuring plan is about to walk out the door.

Sequence restructuring after stabilization. Cutting the people who hold the operational knowledge before the systems are stable is a bet that nothing will go wrong at precisely the moment when things go wrong most often.

Treat culture as an execution variable. Culture clash is not soft. In this case it shaped who stayed, who left, whose processes won, and how fast problems surfaced. A reverse acquisition needs an explicit answer to whose operating model runs the combined business, before the organization answers it through attrition.

Regulated businesses have no grace period. In a bank, an insurance company, a utility, an airline, operational failure converts into regulatory exposure within weeks. Integration planning in regulated industries must treat continuity of core processes as a compliance requirement, not an operational preference.

And when it does go wrong: one roadmap, strict sequence, visible cadence. Everything at once is nothing at all.

The Deal Creates Potential. The Integration Creates Value.

A well-executed integration is recognizable within months. Leadership reviews one set of numbers. Managers can say who decides what without checking. Customers, if they notice anything, notice that service got better. None of this is conceptually difficult. All of it is hard to do while running the base business, which is exactly why integration execution deserves the same seniority, discipline, and attention as the deal itself.

The GE Germany story had deal objectives that were perfectly sound. Three times the scale, a market-leading platform, real synergies. What nearly destroyed it was execution, and what saved it was execution too: sequence, ownership, data, and cadence, applied relentlessly until the engine ran again.

Because in the end, nobody gets credit for the plan. The market pays for what the combined business actually delivers: EBITDA, cash, execution and growth.

Similar Posts