The TSA clock starts at signing, and the technology separation is usually the workstream that decides whether Day 1 is calm or a scramble. If you are an operating partner or a portfolio-company CIO carving a business unit out of a parent, the IT separation consultant M&A decision sits directly on that clock: the parent wants its systems back, the buyer is paying for shared services on a meter, and every month of overrun shows up as cash out the door and a delayed clean close. This guide is for a buyer with budget who has to choose that firm and then hold it accountable, not for someone learning what a carve-out is.
The commercial stakes are concrete. Bain’s annual private equity report has tracked how much of the return in the current cycle depends on operational improvement rather than multiple expansion, and a botched separation eats into both. Below is how to scope the work, what to demand in the pitch, and how to judge delivery against actual versus plan.
1. Fix the separation problem before you shop for a firm
The first mistake buyers make is hiring capacity before they have named the boundary. You need a clear perimeter at the application and data layer before any proposal can be priced accurately, because a carve-out creates a set of dependencies between what the parent keeps, what transfers, what gets rebuilt standalone, and what the TSA covers in the interim.
Before you brief a single consultant, get the deal team to hand you three things: the perimeter (which entities, users, and systems are in scope), the TSA schedule with its exit dates, and the carve-out financials that assume a standalone IT cost base. If those do not exist yet, the work you need first is carve-out technology due diligence, not a separation build. Buying a separation team without a validated perimeter is how scope creep gets funded.
This ties back to what came out of technology due diligence during the deal. The diligence read on entanglement, shared licenses, and single-tenant systems is the input that sizes the separation. If the two were run by different people who never spoke, expect surprises in the first 30 days.
As FT Partners documented in their H1 2024 M&A research report on technology transactions, poorly scoped carve-outs regularly overshoot budgets by 30–50%, and most of that variance emerges from perimeter ambiguity that should have been resolved in diligence. Deloitte’s 2023 M&A Trends Survey found that 62% of respondents cited unclear scope definition as the top driver of separation delays, ahead of technical complexity or resource constraints.
2. Scope the four workstreams every separation actually contains
A credible firm will structure the engagement around the same handful of workstreams, and you should reject a proposal that blurs them together, because blurred workstreams hide where the risk and the cost sit.
Infrastructure and identity
Email, directory, network, endpoints, and access. This is the workstream that most often controls the Day 1 date, because users cannot function without identity and mail cutover. It is also where TSA dependency is highest.
Applications and data
The business systems, including ERP, the CRM, finance, and any industry-specific platforms. Some transfer, some clone, some get replaced. The separation of shared instances and the extraction of the divested entity’s data is the hard part, and it usually runs longer than the infrastructure work.
Security and compliance
Standalone controls, logging, and the evidence a standalone entity needs. The Harvard Law School Forum on Corporate Governance has published extensively on how governance and control gaps surface in M&A, and a separated entity that inherits none of the parent’s tooling is exposed on Day 1 unless this workstream is funded early.
Service management and the standalone operating model
Who answers the phone when a user has a problem after TSA exit. A separation that rebuilds systems but not the support model just moves the failure date later.
For the applications layer specifically, the CRM and ERP cutover deserves its own plan. The mechanics of that are covered in detail in CRM and ERP integration post merger, which applies in reverse when you are pulling a business out of a shared instance.
3. Judge the pitch on the plan, not the logos
Every firm will show you a methodology slide. The difference between firms shows up in what they commit to when you push. Ask for a work plan that maps each workstream to a named owner, a dependency on the TSA schedule, and a set of exit criteria you could actually verify. If a firm cannot tell you which TSA service they will retire in which week, they have not done the analysis, they have done the deck.
Three questions separate the operators from the presenters:
- Which TSA service exits first, and what has to be true for that to happen? The answer tells you whether they understand your cost clock.
- Where is the data separation riskiest, and what is the fallback if extraction runs long? A firm without a fallback has never done a hard one.
- What is the standalone run-rate IT cost after separation, and how does it compare to the carve-out model? If the separated cost base is higher than what the deal assumed, you need the variance quantified and explained before the first board meeting, because that gap flows through to EBITDA and the return calculation.
According to McKinsey’s 2023 private equity annual review, value leaks in integration and separation when accountability is diffuse, with portfolio companies that establish clear decision rights and named workstream owners achieving Day 1 readiness 1.4 times faster than those that do not. BCG’s 2024 principal investors report documented the same pattern, finding that separations with defined exit criteria and weekly reporting deliver TSA exit 20–30% faster than those relying on status updates. This is the same discipline described in how to buy and judge a divestiture technology separation consultant, and it is worth reading alongside this one.
4. Set the commercial terms against the TSA clock
The economics of a separation are driven by the TSA meter. The parent typically charges for shared services during the transition, and those charges often step up if you overrun the agreed exit dates. Time controls the outcome more directly than any other input, which makes it the factor you structure the engagement around.
Set the commercial terms so the firm carries some of that time risk. A pure time-and-materials contract on a fixed-scope separation gives the firm no reason to hit the TSA dates. Tie a portion of the fee to milestone exit of specific TSA services, verified by the parent’s sign-off. PitchBook and S&P Global Market Intelligence both publish deal-cost data that helps you sanity-check whether a proposed budget is in a normal range for the transaction size, so you are not negotiating in the dark.
Be explicit about what happens on overrun. If the separation slips, who pays the extended TSA charges, the firm or the portfolio company? A firm confident in its plan will accept a meaningful share of that exposure. One that will not is telling you something about its plan.
5. Track delivery on evidence, not status decks
Once the work starts, the reporting you accept determines what you actually know. A weekly deck that says “on track” is not evidence. Hold the firm to a small set of measures you can check against plan:
- TSA services exited versus scheduled, the single most important number, because it maps directly to cash.
- Users cut over versus total in scope, the leading indicator for the identity and mail workstream.
- Data migration completeness and reconciliation status, the workstream most likely to hide a problem until late.
- Open risks with owners and dates, a risk register that never changes is a register nobody maintains.
This is standard integration-management-office practice applied to a separation, and if you do not have that office in place, merger integration management office services is the function to stand up. The same reporting discipline governs the first 100 days of any deal, and the AICPA & CIMA guidance on transaction reporting and controls is a reasonable external reference for what “evidence” should mean in this context.
Harvard Business Review’s M&A coverage has repeatedly made the point that separations fail on execution, not on strategy. The strategy is usually obvious. The reason a Day 1 slips is that someone accepted a status color instead of a checkable number.
6. Where this sits in the wider portfolio program
A single carve-out is rarely the whole picture. If the thesis is a buy-and-build, the separation team you hire needs to hand off cleanly into the integration team that will fold the asset into a platform, which is why roll-up integration services and divestiture IT consulting in private equity are worth reading as two halves of the same competence. The revenue systems in particular, CRM and marketing operations, often need rebuilding on the standalone side, which connects to outsourced RevOps for a portfolio company.
Firm-level research from Preqin, Private Equity International, Buyouts, and PE Hub all track how operational execution now weighs on returns more than it did a cycle ago, and the SEC’s disclosure framework raises the bar on what a standalone entity has to be able to report from Day 1. That combination is why separation quality has moved from an IT concern to a deal-team concern.
7. Your next-step checklist
- Confirm the perimeter, the TSA schedule, and the standalone IT cost base exist before briefing any firm.
- Require a work plan structured into the four workstreams, each with a named owner and verifiable exit criteria.
- Ask the three pitch questions on TSA exit sequencing, data-separation fallback, and standalone run-rate cost.
- Tie part of the fee to milestone TSA exits verified by the parent, and settle who pays for overrun.
- Accept only checkable weekly numbers: TSA services exited, users cut over, data reconciled, risks past due.
- Plan the handoff into the integration or RevOps rebuild before separation ends, not after.
If you are choosing an IT separation consultant M&A partner for a live carve-out and want the M&A advisory and PMI sprint support to run it against the TSA clock, review the private equity program from DevriX and GrowthShuttle and bring the specific deal into the conversation.