Guide

The people side of post-acquisition integration: a 100-day checklist for CEOs

Most integration plans are clear on systems and silent on how the people who must carry them out actually read the plan.

Published

Key takeaways

  • Integrations usually stall because capable leaders leave the meeting agreeing and then run different playbooks, not because the plan is wrong.
  • Words like ready, synergy and on track carry different meanings in different seats. Define them in writing before close.
  • Check incentives early. If a comp plan does not pay for the behavior the deal model assumes, the behavior will not happen.
  • Find the people the acquired business quietly depends on, and decide what you owe them, before you decide who is redundant.
  • Hearing what is not being said takes a deliberate method. Status updates will not carry it.

Why integrations stall on the people side

A deal model is a set of assumptions about how people will behave. Cross-sell assumes the acquired sales team will sell your products. Cost savings assume the right people stay and the wrong tasks stop. Speed assumes leaders in two companies will make decisions the same way. Integration is the work of turning those assumptions into habits, and it stalls when the assumptions were never shared with the people who have to live them.

Four patterns show up again and again. First, leaders agree in the meeting and then run different playbooks. Agreement in a room is cheap, and it says little about what each person understood. Second, the same words carry different meanings. Ready, synergy, on track and integrated can each describe three different situations depending on who is speaking. Third, incentives pull the other way. An acquired rep whose comp plan does not pay for selling your product will not sell it, however good the strategy sounds. Fourth, the acquired business depends on a few people nobody on your side has identified, and they are often not the ones with senior titles.

None of this is a failure of intelligence or effort. It is what happens when two organizations with different histories are asked to behave as one, under time pressure, with each side trying to look competent to the other. The rest of this guide is a way to find those gaps while they are still cheap to fix.

What to settle before close

The cheapest time to remove ambiguity is before the deal closes, when you still have time and goodwill. Treat this list as decisions to make and write down, not topics to discuss.

If you cannot yet speak to the acquired leaders freely, do the parts you can. Write the definitions, list the behavioral assumptions, and review your own incentive plans. You can then take a much shorter, better-prepared set of questions into your first conversations after signing.

  • Name one accountable integration owner who is not also running the business day to day.
  • Write one-sentence definitions of the five or six words your plan leans on, such as ready, done, on track, priority and customer.
  • List the assumptions in the deal model that depend on human behavior, and name who must act for each to come true.
  • Check whether comp plans, bonuses and targets reward the behavior those assumptions require. Decide what changes and when.
  • Ask the acquired leaders, privately, who the business really runs on, and which people they worry about losing.
  • Decide what will not change in the first 100 days, and say so plainly. Uncertainty drives more quiet departures than bad news does.
  • Agree on how disagreement travels: who hears it, how quickly, and what happens next.

Days 1 to 30: make the plan shared

The first month is for turning your plan into something both teams hold the same way. Speed matters less than clarity. A plan that two groups read differently will cost more than a plan that took an extra week.

  • Hold one-on-one conversations with every acquired leader before any large group meeting. Ask what they expect to change, what worries them, and what they think you misunderstand.
  • Ask each leader on both sides to describe, in their own words, what success looks like at day 100. Compare the answers before you publish the plan.
  • Publish the definitions you settled before close, and ask each leader to restate them.
  • Confirm decision rights: who decides what, and what escalates. Write it on one page.
  • Talk to the people the business depends on, not only the people who lead it, and tell them directly where they stand.
  • Set a rhythm of short, regular check-ins with a fixed set of questions, so you can compare answers over time.

Days 31 to 60: test the plan against reality

By now the plan has met the field. This month is for finding where it bends. Look at behavior rather than reports, because reports are written to reassure.

  • Pick three deal assumptions and trace each to the people doing the work. Is the cross-sell actually being pitched? Are the handoffs actually happening?
  • Compare what leaders say in the leadership meeting with what their direct reports say. Differences are information, not disloyalty.
  • Review early attrition and near-misses. Ask why people are staying or leaving, in their words.
  • Look at where the same issue has come up twice. A repeated issue often means two people hold different definitions of the problem.
  • Revisit the incentives. If behavior has not changed, ask first whether it is rewarded, and second whether it is understood.
  • Repeat the day-one question to each leader, on what success looks like at day 100, and note how the answers have moved.

Days 61 to 100: lock in and close the loop

The last stretch is for making decisions stick and for showing people that what they told you changed something. If it does not, they will stop telling you.

  • Turn what you learned into a short list of decisions, each with an owner and a date.
  • Tell the teams what you heard and what you are changing. Be specific about what you are not changing and why.
  • Reset the definitions that proved to be unclear, and communicate the new wording.
  • Fix the incentive gaps you found, or say clearly that you are leaving them in place and what that means for the plan.
  • Decide which retention conversations still need to happen, and have them now.
  • Choose the next checkpoint and put it in the calendar. Alignment decays unless someone looks again.

Signs it is drifting

Drift rarely announces itself. It shows up as small mismatches that are easy to explain away individually. Watch for these.

A useful habit is to write down, at day 30, what you would expect to see by day 60 if the integration were healthy. Then compare. It is easier to notice a gap against a written expectation than against a general feeling that things are fine.

  • Status reports are green but the people closest to customers sound tired or evasive.
  • The same decision gets revisited in meeting after meeting.
  • Acquired leaders say yes quickly and ask few questions.
  • Two leaders describe the same project in ways that cannot both be true.
  • Key people become harder to reach, or start declining optional meetings.
  • Local workarounds multiply, and nobody can say who approved them.
  • Your own team stops bringing you bad news, or brings it softened.

How to hear what is not being said

People in the middle of an integration have good reasons to stay quiet. The acquired side does not want to seem resistant. The acquiring side does not want to seem to be failing. Everyone is aware that you are the person deciding who stays. Asking a direct question in a group usually produces the safe answer.

A few methods help. Talk to people one at a time and ask for reasons rather than ratings. Ask each person what they think other people on the team believe, because people often describe their own view more safely as the view of others. Ask what they would change first if the decision were theirs. Ask for definitions of the key words, then compare the answers across leaders, since the differences are often the finding. Make it clear who will and will not see what they say, and keep that promise exactly.

Closing the loop matters as much as asking. When people see their input change something, even something small, they say more the next time. When they see nothing happen, they conclude that candor has no use.

Where Halo fits

Halo, HaloVision's AI, shows you where your leaders and the acquired team are describing the integration differently, before it shows up in the numbers. It talks privately with each person and goes deeper into the reasons behind each view, which a status meeting does not reach. Every conversation is confidential. The report shares only what does not disclose sensitive information, and it stays at the level of the system. It fits around close and again at day 30 to 60, and it does not replace the checklist above. Each conversation takes about 30 minutes, and the report lands within 48 hours of the last conversation.

FAQ

Questions leaders ask

What should a CEO focus on in the first 100 days after an acquisition?
Focus on four things: a shared definition of success that every leader can state the same way, incentives that reward the behavior the deal model assumes, the identity and retention of the people the acquired business depends on, and a regular way to hear unfiltered feedback. Systems and reporting matter, but they usually follow naturally once these four are settled.
Why do post-acquisition integrations fail?
Many stall for reasons that are human rather than technical. Leaders leave a meeting in agreement and then act on different understandings of the plan. Key words are interpreted differently. Incentives point away from the intended behavior. Valuable people leave because nobody told them where they stood. Each of these is visible early if someone asks the right questions privately.
How do you retain key talent after an acquisition?
Identify who the business actually depends on, which is often not the same as who holds senior titles. Speak to them directly and early about what will and will not change. Make any retention arrangement specific and timely. Avoid headcount decisions that remove institutional knowledge before you have mapped where it sits.
How do you find out what acquired leaders really think?
Talk to each leader privately before group meetings, ask for reasons instead of ratings, and ask what they think others believe. Compare how different leaders define the same words. Make clear who sees what they say. Then show them something changed because of what they said, which is what keeps them candid.
Can an AI help with the people side of integration?
It can help with the listening. Halo, HaloVision's AI, holds confidential one-on-ones with the leaders on both sides and shows the CEO where their views differ and what to decide next. The decisions, the incentives and the conversations that follow remain the leader's job.

Related situations

See what Halo would find on your team

Talk to Halo now, in your browser, or book time with the HaloVision team. The report lands within 48 hours of your last leader's conversation.