Day One Readiness
Run the right playbook. Run it well.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Carve-out vs merger integration is the comparison that most portfolio operating teams get wrong on their first deal. The two playbooks look adjacent. The work is almost opposite. This article sits inside the broader carve-out advisory programme and explains why the playbooks differ, where the cost profiles diverge, and which one a given portfolio situation actually needs.
A merger integration takes two operating models and produces one. A carve-out takes one operating model and produces two. The shape of the work is the inverse. Merger integration combines duplicated functions, retires redundant systems, rebadges teams, and consolidates data. Carve-out replicates functions, stands up new systems, hires the missing roles, and splits data sets. The vocabulary overlaps. The execution does not.
Integration teams optimise toward consolidation. They look for the duplicate vendor contract to terminate, the duplicate role to remove, the duplicate ERP instance to retire. Carve-out teams optimise toward replication. They look for the missing vendor contract to sign, the missing role to fill, the missing ERP instance to stand up. Asking a team trained in one motion to execute the other usually produces an awkward middle that delivers neither benefit nor cost certainty.
Many PE platforms run both at the same time. A platform may have just been carved out of a strategic seller and be acquiring bolt ons in the same quarter. The carve-out workstream is closing TSAs and standing up Newco. The integration workstream is consolidating the bolt ons into Newco. The two programmes need separate leadership and separate cadence, even though they share executive sponsorship. The Day One readiness context is in carve-out Day One readiness.
The vocabulary collision is the first thing to fix. Words like Day One, integration, transition, target operating model, and migration mean different things in each programme. Programs that fail to define the terms across both workstreams generate confusion that surfaces in the wrong meeting. The discipline of a shared glossary is worth the hour it takes to write.
Merger integration creates cost savings. The business case is built on the cost to remove from the combined organisation. Headcount, software, vendors, real estate, and overhead all reduce. The savings run rate compounds quarter by quarter. The integration cost is one time and concentrated in the first year, while the savings benefit is recurring and extends across multiple years.
Carve-out creates cost increases. The standalone business has higher unit costs than the integrated version. Vendor volume discounts shrink. Shared service economies disappear. Subscale corporate functions cost more per unit. The investment thesis sometimes glosses over the cost increase. A clean carve-out with a credible 100 day plan still typically lands at 3 to 8 percent higher cost than the carve-out income statement implied, before stranded cost remediation kicks in.
The TSA fee carries the cost difference for the first year. The seller charges for the services it continues to provide, often at cost-plus rates with a mark-up. The reported P&L looks closer to the parent run rate while the TSA is active. When the TSA exits, the standalone cost shape appears. Programs that confuse the TSA period numbers with the steady state numbers misread the trajectory.
The stranded cost on both sides is the cost increase that has no offset. The seller carries the stranded cost in its retained operating model. Newco carries the stranded cost in its inherited operating model. Neither party planned for the full number in the deal model. The stranded cost remediation is therefore the closest carve-out equivalent to merger integration savings capture. The stranded cost context is in carve-out stranded costs explained.
A merger integration does not depend on a third party for ongoing service. The buyer owns both businesses and can move at its own pace. A carve-out depends on the seller for the duration of the TSA. The seller is a counterparty, often with different incentives, different timelines, and different competence levels in each service area. Newco cannot move faster than the seller is willing to support.
Seller incentives diverge from buyer incentives in predictable ways. The seller wants the TSA to be short, the services to be priced high, the change requests to be few, and the exit milestones to be flexible. The buyer wants the TSA to be priced low, the change requests to be honoured, and the exit milestones to be firm. The negotiated TSA mediates these incentives. Active TSA governance manages the relationship through the operating period. The TSA exit context is in TSA exit strategy.
The information asymmetry is severe. The seller knows its systems, its people, its vendors, and its operating norms. Newco inherits the operating reality without the institutional knowledge that ran it. The first six months are partly an information transfer exercise. The seller may not be motivated to make that transfer thorough. The carve-out work needs explicit information capture milestones in the TSA, with deliverable sign offs and quality bars.
The seller relationship can also be an asset. A well managed TSA can deliver services more cheaply than Newco could stand up alone, at least temporarily. The seller may be willing to extend services beyond the original scope where commercial terms make sense. Newco that treats the seller as a temporary supplier rather than an adversary often gets better outcomes. The risk is over reliance, where Newco fails to exit because the seller is convenient. The discipline is the exit calendar.
Merger integration starts with multiple instances of every system and ends with one. Carve-out starts with one instance shared across the seller and ends with one instance for the seller and one for Newco. The technology programme is the most expensive workstream in either case, but the deliverable looks opposite.
Data is the asymmetric problem. Integration teams converge data into a single source of truth. Carve-out teams split data, cleanse, and rehome it. Splitting data sets that were never designed to be split is harder than combining data sets that were never designed to be combined. The data work usually takes longer than the application work and is often underestimated in both programmes. The IT context is in the carve-out IT separation playbook.
Software licensing follows the same pattern. Integration buyers consolidate licences and capture volume discounts. Carve-out buyers may need to negotiate new agreements at standalone scale, often with worse unit economics. Where vendor relationships were managed by the seller's procurement team, the carve-out teams may not even know the price points until they request a quote.
Cloud platforms are particularly tricky. Integration teams may inherit multiple cloud tenants and consolidate. Carve-out teams need to split the cloud footprint, replicate the identity provider, and migrate workloads with minimum disruption to running operations. The technical complexity of the split is often higher than the consolidation, because the source environment is in active production use throughout.
The honest test is asking who owns what after close. If the buyer owns one operating model that combines two, the work is integration. If the buyer owns a new operating model that replicates a function previously shared, the work is carve-out. Many deals contain both. A PE platform built from a strategic carve-out, then growing through bolt on acquisitions, runs carve-out workstreams against the seller and integration workstreams against the bolt ons in the same quarter.
Programmes need separate ownership when both motions are active. A single programme manager juggling both workstreams will favour one and starve the other. Most platforms put the carve-out work under a Day One readiness lead reporting to the COO, and the integration work under a value creation lead reporting to the CEO or operating partner. The reporting lines stay separate even when the people are shared.
Vendor selection follows the same logic. A merger integration consultant does not automatically know how to run a carve-out. A carve-out specialist may not be best placed to run a merger integration. PE platforms that retain the same firm for both motions out of convenience usually accept slower progress on one side or the other. Specialist support on the carve-out side is the cheaper option, since carve-out mistakes are harder to reverse.
The PE carve-out playbook covers the platform level approach in detail. The Day One readiness programme covers the execution discipline. Both workstreams need a defensible 100 day plan with named owners and honest deltas. The 100 day plan context is in the carve-out 100 day plan.
The operating cadence both motions need in the first quarter.
Read the article →The cost drag that distinguishes carve-out from merger integration.
Read the article →How the deal structure shapes the separation work.
Read the article →The 90-day governance, IT, finance, HR and procurement separation plan we run on live carve-outs. Get the playbook plus the bi-weekly Day One Letter — short, signal-heavy, buyer-side.
No spam. Unsubscribe in one click. · Read the overview first →
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Seven buyer-side moves to exit a Transition Services Agreement on time and below budget. The mark-up, the extension-fee curve, exit sequencing, and the 11-month calendar.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →Set the standalone target operating model before the first cutover. Separation without a destination just rebuilds the seller's stack at the seller's cost.