Post-merger integration and the first 100 days

The first 100 days after close are when the integration plan meets the systems. Plans written before close assumed things that turn out to be wrong. That gap is where outside help gets hired.

If you saw the announcement and reached out before close, this is when it pays. If you didn't, it's not too late.

What the first 100 days look like inside

Day one is mostly legal and financial. Entities merge, signatures change, people get new email addresses.

Then reality arrives. The acquired company's ERP doesn't map cleanly to the parent's. Customer records overlap and conflict. Two sales teams call on the same accounts. Board reporting has to combine numbers from systems that define revenue differently.

The integration team was sized for the plan. Now the plan is bigger than anyone thought. And the synergy targets promised to investors haven't moved.

Who feels it

The integration leader feels the timeline. They're reporting progress to the CEO and often the board, and the progress is slower than anyone wants.

The CFO feels the reporting. The first combined quarter has to close, and the numbers have to make sense.

The acquired company's technology leader feels the uncertainty. Their systems might be retired, their team folded in. They're often the most motivated person in the building to get the transition right, since their reputation rides on it.

And the parent's CIO or CTO feels the load. Their team is running the business and absorbing a second one at the same time.

Signals to watch after close

An integration leader named in a press release or on LinkedIn. That's your clearest buyer.

Job posts for integration program managers, data migration specialists or ERP consultants. Those say the team knows it's short-handed.

The first 10-Q after close. Look for integration costs, new risk factors about systems or controls, and any language about timing. A company that says integration is taking longer than planned has told you where the pressure is.

Departures. Leaders on the acquired side often leave in the first months. A champion who leaves is a signal at both companies. The one they left has a gap. The one they join has a new buyer who knows the problem.

I covered how to read the deal itself in an acquisition announcement is a services signal.

An opener for the integration leader

Say a mid-size distributor closed its acquisition of a regional competitor two months ago, and its first 10-Q since close says integration costs are running ahead of plan.

Saw the 10-Q note on integration costs, two months into combining the two businesses. That usually means the system work is bigger than the plan assumed, and it lands on you first. My guess is the hard part is customer and pricing data, since both companies sold to some of the same accounts at different prices. Is that where it's sticking, or is the bigger issue somewhere else?

Notice the opener doesn't say the integration is failing. It names what's public and guesses at the cause. The leader can correct you without admitting anything.

How to show up

Bring a narrow offer. Integration teams don't want a firm that'll rethink their strategy. They want a firm that'll fix one thing that's stuck, fast.

Respect the people. On the acquired side especially, everyone's worried about their jobs. Don't write anything that assumes consolidation or cuts. Talk about the work, not the org chart.

Write to the committee. The integration leader, the CFO and the technical lead on each side all see a different piece. Each should hear a hypothesis about their own.

When the window closes

After the first few months, the integration either finds its footing or becomes a longer program with its own budget and vendors. Both can still mean work, but the early, urgent need for help is mostly gone.

That's why timing matters more here than with most signals. The first 100 days are short. Be in them.