Corporate Governance, Board Management & M&A ExitsPlaybook3 min readUpdated September 2026

The First 100 Days After an Acquisition Closes

The purchase agreement is signed, the wire has cleared, and now the actual work starts. Most of the value a buyer expects from an acquisition is created or destroyed in the first hundred days, not in the deal negotiation.

A hundred-day plan isn't a formality for large public deals. Even a founder buying a five-person competitor benefits from writing down, before closing, exactly what happens in week one, month one, and day one hundred.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Week One: Stabilize Before You Change Anything

The first week's only job is making sure nothing breaks: payroll runs on time, customers can still reach support, and every employee knows who their manager is and whether their job exists. Announce the acquisition to employees and customers on the same day, with a short, honest message, rather than letting rumors travel faster than facts.

Resist the urge to announce org changes, new product direction, or system migrations in week one. Employees are watching for signals about their own job security; unrelated big announcements read as instability even when they're not meant to.

Have a short, specific answer ready for the question every acquired employee will ask in some form: what happens to my role. "We'll figure that out together over the coming weeks" is honest but unsatisfying; naming a specific date by which reporting lines and role decisions will be communicated gives people something concrete to hold onto instead of filling the silence with their own assumptions.

Week one comes down to these stabilizing checks:

  • Payroll runs on time, with no disruption to anyone's paycheck.
  • Customers can still reach support the way they always have.
  • Every employee knows who their manager is and whether their job exists.
  • Employees and customers hear about the acquisition on the same day, in a short and honest message.

What should you merge in the first month after closing?

Not everything needs to be integrated immediately, and treating every system and process as urgent is how integration teams burn out in month one. Sort systems and processes into three categories: merge now (anything customer-facing or financial-reporting related), merge on a planned timeline (HR systems, internal tools), and leave alone for now (anything that works fine independently and isn't blocking a reporting deadline).

This is also when a transition services agreement, if the deal included one, starts getting exercised in earnest, so the integration lead should already know exactly what's covered and what isn't.

When does retention risk peak after an acquisition closes?

Key employees who were waiting to see how the acquisition actually felt before deciding whether to stay tend to make that decision around the six-to-eight-week mark, once the initial uncertainty has settled but before new equity or retention arrangements have been fully explained. This is the window to have direct conversations with the people the deal depended on, not a company-wide town hall.

Customer retention follows a similar pattern: accounts that were quietly evaluating alternatives during the transition tend to make their decision here too, which is why a structured customer outreach plan matters as much as internal communication.

A short, personal check-in from someone the customer already trusts, rather than a mass email about the acquisition's benefits, tends to do more for retention during this stretch. The message that matters to most customers isn't about the deal's strategic logic, it's whether their day-to-day service and their main point of contact are staying the same.

Days 61 to 100: Measure What the Deal Was Actually Supposed to Do

By day one hundred, the integration team should be able to answer the specific question the deal thesis was built on: did retention hold at the target rate, did the combined cost structure move the way the model assumed, did the systems that were supposed to be merged actually merge. Vague statements about things "going well" aren't a substitute for the specific metrics the deal was underwritten on.

For deals with earnout or milestone provisions, this is also when the tracking mechanism for those milestones needs to be fully operational, not something that gets built retroactively when the first payment is due.

If the numbers are off track at this checkpoint, treat it as information rather than failure. A deal that's behind on cost savings but ahead on retention is a different problem than one that's behind on both, and the response, more integration resources versus a harder look at the original deal thesis, should differ accordingly rather than defaulting to a generic "stay the course" response.

Executive Capability Standard

What Good Looks Like

A hundred-day plan is written before closing, names a single integration lead, sequences what merges immediately versus on a planned timeline, and defines the specific metrics that will tell you by day one hundred whether the deal is delivering what it was underwritten on.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Read the deal model's underlying assumptions about retention, cost savings, and timeline before closing, so the hundred-day plan is built around what actually needs to be true.
2. Do Manually:Draft the week-by-week plan and the retention conversation list yourself alongside the acquired company's leadership before closing.
3. Delegate:Appoint a dedicated integration lead whose only job for the first hundred days is running this plan and escalating blockers.
4. Automate:Track integration milestones, retention conversations, and system cutover status in a shared project tool rather than a rolling status email.
5. Buy:Bring in an interim or fractional COO to run post-close integration when the deal is large enough that day-to-day operations can't absorb the extra load.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Every

A reasonable fit for consolidating banking and treasury operations onto one back office during the systems phase of integration, rather than running two sets of accounts side by side longer than necessary.

Visit Every→

Frequently Asked Questions

Who should own the hundred-day plan, the buyer's CEO or a dedicated integration lead?

A dedicated integration lead, reporting to the CEO but not the CEO themselves. The CEO has to keep running the rest of the business, and integration work benefits from one person whose full-time job is tracking the plan, resolving conflicts between teams, and escalating only what actually needs the CEO's attention.

Should the hundred-day plan be written before or after the deal closes?

Before, ideally during the last few weeks of diligence. Writing it after closing means the first month is spent planning instead of executing, which is exactly the window where stabilization and clear communication matter most.

How much should be communicated to acquired employees on day one?

Enough to answer their two real questions: is my job safe, and does anything change about how I get paid and who I report to. Product strategy and long-term vision can wait; job security and next paycheck cannot.

What's the biggest sign an integration is going off track?

Key people from the acquired company leaving in the first ninety days, especially anyone the deal thesis specifically depended on. It's a lagging indicator of communication and retention planning failures that usually started weeks earlier.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides