Services

Six practices, staffed as one team around the question you bring us.

All services

+4.2 pts

Average revenue growth over plan, three years on

Services

Strategy & Growth

15โ€“25%

Typical reduction in addressable cost

Services

Operations & Performance

3.1x

Median return on AI use cases we have taken to production

Services

Digital & AI

92%

Of transformation milestones delivered on time across recent programs

Services

Transformation & Change

112%

Average delivery against announced cost savings

Services

Mergers & Acquisitions

-20%

Typical reduction in management layers and spans below five

Services

People & Organization

Services

Six practices, staffed as one team around the question you bring us.

All services

+4.2 pts

Average revenue growth over plan, three years on

Services

Strategy & Growth

15โ€“25%

Typical reduction in addressable cost

Services

Operations & Performance

3.1x

Median return on AI use cases we have taken to production

Services

Digital & AI

92%

Of transformation milestones delivered on time across recent programs

Services

Transformation & Change

112%

Average delivery against announced cost savings

Services

Mergers & Acquisitions

-20%

Typical reduction in management layers and spans below five

Services

People & Organization

Article

The first 100 days after a merger

The first hundred days after closing set the pace for everything that follows. What to settle before day one, what to do quickly, and what to leave alone.

Lukas Brenner and Amara Nwosu

ยท 3 min read

Share

The period between closing and the end of the first quarter is short, but most of what determines whether a merger delivers its savings is decided in it. Leaders are appointed or not, customers stay or begin to look elsewhere, and employees in both companies form a view about what the new organization will be like. That view is hard to change once it has settled.

Across the integrations we have supported, the ones that went well treated the first hundred days as a period with a small number of clear priorities. The ones that went badly tried to do everything at once, or nothing until the organization design was finished.

Settle leadership before closing

The single most useful thing an acquirer can do is announce the top layers of leadership on day one. Uncertainty about jobs is the main reason good people leave in the first year, and it spreads downward: a director who does not know who their manager will be cannot reassure their own team.

In a recent merger of two chemicals producers, the top three layers, about 140 roles, were selected and announced before closing using the same structured assessment for candidates from both sides. Retention of critical staff a year later was 94 percent. In integrations where appointments drag on for six months, we routinely see retention in the seventies.

Selecting leaders fairly matters as much as selecting them quickly. If the appointments look like a victory for one side, the other side's best people will draw their own conclusions.

Protect the customer from the integration

Customers do not care about the merger, except to the extent that it disrupts them. Competitors know this and will be calling your largest accounts in the first week.

Good practice is to leave customer-facing teams and processes alone for at least the first six months, assign a named senior executive to each of the largest accounts, and contact every major customer before they hear about the deal from someone else. Price harmonization, sales territory changes and system migrations can wait until the organization is stable.

Move first on the savings that carry least risk

Not all savings are equal. Some, such as procurement consolidation, can be captured quickly with little effect on customers or operations. Others, such as closing plants or merging core systems, carry much greater risk and should follow once the organization is settled.

A sensible sequence for most integrations looks like this:

  1. Days 1 to 30: Combine purchasing for the largest categories, freeze discretionary spending and hiring in overlapping functions, and launch the integration office.

  2. Days 31 to 60: Agree the design of the back-office functions, begin consultation where required and confirm savings targets by owner.

  3. Days 61 to 100: Start consolidating back-office functions, finalize the plan for the operating footprint and lock savings into the next budget.

Doing procurement first also builds confidence. Early, visible savings make it easier to hold the line on the harder decisions that follow.

Run the integration as a business process

An integration office should be small and senior, with members from both companies. Its job is to track decisions and savings, resolve conflicts and keep the executive team focused. It should meet weekly and report against the budget, not a parallel set of numbers.

If the integration office and the finance team disagree on how much has been saved, the finance team is right.

The office should also watch for integration fatigue. Managers running the business while integrating it are doing two jobs. Sequencing changes carefully, and being willing to delay those that are not essential, is how the business keeps performing while it changes.

What to leave alone

Not everything needs to be integrated. Brands with distinct customer bases, specialized plants and teams with unique capabilities can often be left largely intact, at least at first. The test is whether combining them creates more value than it puts at risk. Many integrations destroy value by harmonizing things that were working perfectly well on both sides.

The first hundred days will not deliver most of the savings. They will determine whether the savings arrive at all.

Have a decision on the table?

Tell us what you are weighing. A partner will reply within two working days, and the first conversation is on us.

Have a decision on the table?

Tell us what you are weighing. A partner will reply within two working days, and the first conversation is on us.

Have a decision on the table?

Tell us what you are weighing. A partner will reply within two working days, and the first conversation is on us.

Have a decision on the table?

Tell us what you are weighing. A partner will reply within two working days, and the first conversation is on us.

Buy template

Webinar: scenario planning for the 2027 board calendar

scenario-planning-2027-webinar

Event

Elena Marsh and Priya Raman

A one-hour online briefing for directors and executives on building scenarios, triggers and prepared moves into the board's regular cycle.

Scenario planning that boards will actually use

scenario-planning-for-boards

Article

Elena Marsh and Thomas Reid

Most board scenario exercises produce a thick report and no decisions. A lighter approach, tied to triggers and pre-agreed moves, makes them useful.

Making cost savings last: a breakfast roundtable for CFOs

making-cost-savings-last-roundtable

Event

David Okafor and Hannah Cole

A closed-door breakfast in London for finance leaders planning their next cost program, built on the findings of The CFO Cost Agenda 2026.

Operations AI Benchmark 2026: from pilots to the P&L

operations-ai-benchmark-2026

Report

Marcus Lindqvist and Priya Raman

How 286 operations leaders are using AI in maintenance, planning and quality, how much of it reaches production, and what the companies seeing returns do differently.

Zero-based organization design, done properly

zero-based-organization-design

Article

Hannah Cole

Designing an organization from a blank page sounds radical. Done well, it is the most practical way to remove layers and duplication without starting a political war.

The first 100 days after a merger

first-100-days-after-a-merger

Article

Lukas Brenner and Amara Nwosu

The first hundred days after closing set the pace for everything that follows. What to settle before day one, what to do quickly, and what to leave alone.

The CFO Cost Agenda 2026: why savings fade and what keeps them

cfo-cost-agenda-2026

Report

Thomas Reid and David Okafor

A survey of 412 chief financial officers on cost programs, how much of the savings survive, and the practices that separate durable results from temporary ones.

Making AI pay back in operations, not in pilots

making-ai-pay-back-in-operations

Article

Marcus Lindqvist and Kenji Watanabe

Most operations AI never leaves the pilot stage. The few use cases that pay back share a set of traits that have little to do with the model itself.

Pricing power after the inflation years

pricing-power-after-inflation

Article

Elena Marsh and Priya Raman

Companies raised prices faster than costs between 2021 and 2024. Customers remember. How to set prices now that the cover of general inflation is gone.

Why cost programs fail in year two

why-cost-programs-fail-in-year-two

Article

David Okafor and Thomas Reid

Most cost programs hit their first-year targets. The savings disappear in the second year, for reasons that are predictable and largely avoidable.

Create a free website with Framer, the website builder loved by startups, designers and agencies.