Most carve-out losses do not show up on Day 1. They accumulate in month four, when the transition services agreement is still running, the seller’s finance team has moved on, and the portfolio company is paying a monthly fee for services it was supposed to stand up itself. TSA exit consulting in private equity exists to close that gap: getting the acquired business off the seller’s systems, contracts, and people before the clock runs out and the penalty rates start. If you are an operating partner or a portfolio CFO staring at a signed TSA with an exit date you did not set, the decision in front of you is what to buy, how to sequence it, and how to tell whether the work is on plan.
This guide is written for a buyer with budget and an active schedule who needs to decide what to buy before engaging anyone, how to run the exit as a set of workstreams with owners, and how to judge the work while it is happening rather than at the end.
1. Decide what you are actually buying before you scope the engagement
A TSA exit is a portfolio of separations that happen to share a deadline: applications, infrastructure, data, finance processes, HR and payroll, procurement contracts, and often customer-facing systems like CRM and billing. The mistake buyers make is scoping the engagement as “TSA exit” and letting the firm decide what that includes. The scope should come from your own reading of the schedule and its exit milestones.
Before you talk to a firm, get clarity on three things. First, which services are on the TSA and what each one costs per month, including any step-ups that trigger after an initial period. Second, which of those services the portfolio company can realistically run on its own systems, and which require net-new build. Third, where the dependencies sit, because you cannot exit finance if the ERP data migration has not landed, and you cannot cut over the ERP if identity and access are still on the seller’s directory.
Bain’s annual private equity report has tracked how large a share of returns now depends on operational improvement rather than multiple expansion, which is exactly why a sloppy TSA exit quietly erodes the thesis. McKinsey’s private capital research makes a similar point about the discipline required in the ownership period. Harvard Business Review’s coverage of mergers and acquisitions and the Harvard Law School Forum on Corporate Governance both document how integration and separation execution, not the deal terms, decide whether the economics hold. PitchBook and S&P Global Market Intelligence data on carve-out and divestiture volume show these transactions are a steady share of deal flow, which means the buy-side execution discipline is a repeatable capability worth building across a portfolio rather than reinventing per deal. Preqin and Private Equity International track the fund-level pressure that makes clean exits matter, while Buyouts and PE Hub cover the transactions and BCG’s work on principal investors rounds out the operational view. Treat the exit as value creation with a hard deadline, not as an IT chore.
If the separation touches technology heavily, the earlier carve-out technology due diligence should already have flagged the dependencies. If it did not, that is the first thing to reconstruct.
2. Map every TSA service to an owner and an exit date
The single artifact that determines whether the exit stays on schedule is a service-by-service register. Each row is one TSA service. Each service carries a monthly cost, an exit milestone date, a named owner on the buy side, a named counterpart on the seller side, and the status of the replacement that will let you exit it.
Do not accept a Gantt chart in place of this register. A Gantt chart shows sequence; it does not show who has the decision right when a milestone slips. The register forces that question on every line. When a firm proposes to run your exit, the first thing to ask for is how they will build and maintain this register, and who updates it, because a stale register is worse than none.
Separate the services you can exit early from the ones that anchor the schedule
Some services can be exited quickly and cheaply once a replacement exists, email and collaboration tools, for example. Others anchor everything, usually the ERP and the core data. Exiting the cheap, easy services first buys goodwill and reduces monthly cost, but it does nothing for the critical path. Keep the two categories visibly separate so the board does not mistake early cost savings for schedule progress on the services that actually matter.
3. Sequence the exit around dependencies, not around the calendar
The exit dates written into the TSA are commercial deadlines, not a delivery plan. The delivery plan runs on dependencies. Identity and access come first, because almost every application cutover depends on knowing who logs in from where. Infrastructure and hosting come next, then the data migration, then the applications that sit on that data, then the finance and payroll processes that run through those applications, and finally the procurement contracts you need to novate or replace.
This is the same logic a divestiture technology separation consultant applies from the sell side, and it is worth understanding both sides of the transaction because the seller’s team is your dependency on every shared service. If your CRM and billing are entangled with the seller’s systems, treat that as its own workstream; the mechanics of CRM and ERP integration after a merger apply in reverse when you are separating rather than combining.
The commercial pressure runs the wrong way here. TSA fees usually rise over time to push the buyer off the seller’s systems, so the temptation is to chase the highest-cost services first. Resist that when those services sit downstream of an unfinished dependency. Paying an extra month of ERP hosting fees is cheaper than a failed cutover that corrupts finance data.
4. Staff the exit with capacity, not just advice
A firm that produces a separation plan and a weekly status deck has not exited a single service. The work that closes a TSA is execution: configuring the replacement systems, migrating and reconciling data, retraining the finance team on new processes, and standing up the vendor contracts that replace what the seller provided. Buy the engagement on the basis of embedded delivery capacity with named people, not on the basis of a methodology.
This is where the first 100 days discipline matters, because the exit clock usually starts at close and the early weeks decide whether you hit the schedule or spend the last two months in crisis. The same execution logic applies to a broader Day One readiness engagement for a carve-out, which often flows directly into the TSA exit as the next phase of the same program.
Decide where the management office sits
On a large exit with more than a handful of workstreams, you need a coordinating function that holds the register, runs the seller-side cadence, and escalates slips before they hit the milestone date. Some buyers run this internally through the portfolio company; others buy it as a merger integration management office. The decision turns on whether the portfolio company has a program manager who can hold vendors and the seller accountable. If it does not, buy the function rather than hoping it emerges.
5. Judge the work while it is running, not at the deadline
The failure mode of a TSA exit is a program that reports green until the month before the deadline and then discovers three services cannot exit on time because the work was judged on status color rather than on the underlying evidence of configuration changes, user migrations and cutover milestones.
- Services actually exited versus planned. Count closed TSA lines against the plan, cumulatively. A program that has exited two of twelve services by the halfway point is behind regardless of what the deck says.
- Monthly TSA cost trajectory. The fee run-rate should fall as services exit. A flat run-rate at the midpoint means nothing has actually come off the seller’s systems.
- Dependency slips. Track whether upstream milestones (identity, data) are moving their downstream dependents. One slipped data migration can push four application cutovers.
- Seller-side responsiveness. Log how long the seller takes to answer access and data requests. This is often the real constraint, and it is invisible unless someone measures it.
The AICPA and CIMA and the U.S. Securities and Exchange Commission set the reporting and disclosure context that finance separation has to satisfy, which is why the service register has to track exited status with the same rigor a QoE would demand.
6. What good looks like in the proposal and the contract
When you evaluate firms, the proposal itself is a diagnostic. A firm that has run buy-side TSA exits will ask for your service schedule and fee structure before quoting, will propose a register-driven approach with named owners, and will scope embedded delivery rather than advisory hours. A firm that leads with a generic separation methodology and a fixed timeline has not read your specific TSA.
Tie payment to exited services where you can, not to elapsed time or delivered documents. This aligns the firm with the only outcome that matters, which is services off the seller’s systems before the fees rise or the TSA expires. For the underlying technology risk, lean on your technology due diligence findings so the firm inherits a known baseline rather than rediscovering it on your budget.
7. The buyer’s checklist for a TSA exit engagement
- Build the service register before scoping the engagement, one row per TSA service with cost, exit date, and named owners on both sides.
- Separate quick-exit services from the ones that anchor the critical path, and report them separately to the board.
- Sequence by dependency (identity, infrastructure, data, applications, finance, contracts), not by TSA fee size or calendar date.
- Buy embedded delivery capacity with named people who own migrations, cutover windows and issue resolution, rather than advisory hours that produce status decks without accountability for completion.
- Decide explicitly whether the coordinating function sits inside the portfolio company or is bought in.
- Judge progress on services exited, fee run-rate, dependency slips, and seller response time, monthly.
- Tie payment to exited services, and hand the firm your due diligence baseline so it does not rediscover it on your budget.
If the exit is part of a wider integration or roll-up, the same register and cadence discipline carries over into roll-up integration work and into standing up RevOps in the portfolio company once it runs on its own systems.
To scope a buy-side TSA exit against your service schedule and exit dates, review the private equity M&A and PMI Sprint offering from the DevriX and GrowthShuttle PE team.