Why the first hundred days matter more in a carve-out
Most acquisitions underperform the case that justified them, and the reason is usually execution after completion rather than price at completion.
A carve-out raises the difficulty. The acquirer is not integrating a company that already works alone. They are standing one up: finance, payroll, identity, security and support, all while the people doing that work are also being asked to hit a plan. The transition services agreement buys time for it, and time is the only thing it buys.
Day one has to be boring
Nothing on day one should be a surprise, which means the work happens before completion.
Communications drafted and approved for employees, customers, partners and suppliers, sequenced so that nobody important hears it second-hand. Organisational decisions made rather than deferred, so that every person knows who they report to on the first morning. System access provisioned under the new structure and tested. Customer notification letters cleared by counsel. Banking, payroll and treasury arrangements live.
The test of day one readiness is whether an ordinary employee can do their ordinary job without asking anyone a question about the transaction.
The first thirty days are about not breaking anything
The instinct after completion is to start changing things. Resist it for a month.
Talk to people. Reporting lines confirmed, retention arrangements honoured on the date promised, and enough forum for questions that rumour does not fill the gap. Uncertainty is what causes resignations, not the change of ownership itself.
Talk to customers. The top twenty personally, from a named person, confirming continuity and introducing whoever now owns the relationship. Customers who learn about a change of ownership from a press release start taking competitor calls.
Watch the operational metrics daily rather than monthly. Ticket volumes, uptime, deployment frequency, sales pipeline movement. A problem caught in week two is an incident. The same problem caught in week eight is a trend, and trends show up in the numbers the buyer will be judged on.
Deliver two or three visible improvements. Something small that was blocked under the old owner and can now be done. It changes the internal story from what is being taken away to what has become possible.
Days thirty to sixty are for finding out what is true
The deal model contained assumptions. Now they can be tested.
Assess the people properly, against what the business needs going forward rather than against what they did before. Some of the assessment will contradict what the seller said, and that is normal.
Document the technology estate as it is rather than as the memorandum described it. Redundancies, licence obligations, whatever was running that nobody mentioned. For a carve-out, confirm which services are actually being consumed under the transition agreement, because it is commonly more than the schedule lists.
Consolidate reporting onto one chart of accounts. Until that exists, nobody can say whether the business is performing.
Test the synergy assumptions against operational reality and revise them in writing. A synergy case that nobody revisits becomes the standard against which the acquisition is later judged to have failed.
Days sixty to one hundred are for execution
Now change things, on a plan with dates and owners.
Migrate systems in order of risk, starting with the ones where failure is recoverable and working toward the platforms that would stop the business. Every migration completed reduces the transition services bill and the dependency that comes with it.
Harmonise the processes that need to be common and leave alone the ones that do not. Sales methodology and financial reporting usually need to converge. Engineering practice frequently does not, and forcing it is a reliable way to lose engineers.
Track everything on a dashboard the executive committee sees: integration milestones, synergy capture against the revised case, and the underlying business metrics. Integration programmes fail quietly when nobody is measuring them.
Where it goes wrong
Moving too slowly. Delay does not reduce disruption, it extends it, and the people you most want to keep are the ones with the most options while they wait.
Cutting cost before understanding what the cost was doing. The savings are visible immediately and the damage appears two quarters later in churn.
Treating culture as a soft matter to address after the systems work. In a business whose assets walk out at night, it is the systems work.
Losing people in the first ninety days. Almost always traceable to unclear communication rather than to money.
Who owns it
One named integration lead with executive authority and a cross-functional team, full time. Not a general manager doing it alongside a day job.
The office should meet weekly against a milestone plan and escalate blockers immediately rather than reporting them a month later. In a carve-out, that person also owns the relationship with the seller under the transition agreement, because the two workstreams are the same workstream viewed from either end.
Editorial Team · Published for orientation, not as advice on a specific transaction. Any figure cited is orientation, not a valuation. See market notes.