Blog · Special Situations

In a roll-up, the TSAs multiply faster than the platform.

A roll-up TSA problem is rarely one agreement. It is a stack of them, one per acquisition, each with its own seller, term, and service catalog, accumulating faster than the platform can absorb them. Managing that portfolio as a system, not a series of isolated deals, is the discipline behind a roll-up TSA exit strategy.

N
Stacking TSAs
per deal
New Catalog
8 min
Read Time
2026
Last Updated
Section 01

Why roll-ups create a TSA portfolio

A roll-up acquires a sequence of businesses and folds them into a single platform. Each acquisition that was carved out of a larger parent arrives with its own TSA, its own seller, and its own set of services to migrate. A platform doing four deals a year can be running four to eight active TSAs at once, each on a different clock. The challenge stops being any single exit and becomes managing a portfolio of them.

The platform's advantage is that it has somewhere to migrate services to. Unlike a standalone carve-out, a roll-up has existing infrastructure that each acquisition can fold into. That should make exits faster, because the target is not a greenfield standalone but an established platform. The risk is that the platform's integration capacity does not keep pace with its deal pace, and TSAs pile up faster than they can be retired.

That mismatch is the central roll-up problem. Deals are easy to do and TSAs are easy to sign. Migrations are slow and integration resources are finite. A platform that closes deals faster than it integrates ends up paying multiple sellers for overlapping services, carrying a growing TSA cost base that the deal model never accounted for.

Section 02

Standardizing across many sellers

Every seller writes its TSA differently, so a roll-up that signs each one on the seller's paper ends up with a portfolio of inconsistent agreements. Different pricing mechanics, different SLA definitions, different exit terms, and different governance structures make the portfolio impossible to manage as a system. The platform that wins treats TSA terms as a repeatable template it brings to every deal.

Standardization starts in diligence. The platform develops a clear view of what services it actually needs from any seller, given that it has its own infrastructure to fold acquisitions into. Often a roll-up needs far less from each seller than a standalone buyer would, because the platform already runs finance, IT, and HR. Knowing that in advance lets the platform negotiate narrow, consistent TSAs rather than accepting each seller's full catalog.

Consistent exit terms matter most. The platform wants the same exit ramp, the same extension mechanics, and the same governance approach across every TSA, so its integration team can run them all the same way. A portfolio of TSAs with consistent terms can be managed by one repeatable playbook. A portfolio of bespoke ones needs constant special handling the platform cannot scale.

Section 03

Integration capacity is the binding constraint

The number that governs a roll-up's TSA exposure is not the deal count, it is the integration capacity. Each acquisition needs its services migrated off the seller and onto the platform, and that work takes finite people and time. When deal pace outruns integration pace, TSAs accumulate, extension fees mount, and the platform pays for the same function at multiple sellers at once.

The discipline is to plan integration capacity as deliberately as deal flow. Every acquisition added to the pipeline implies a migration workload, and the platform that does not resource that workload will see its TSA cost base grow with every deal. The integration team's throughput sets the real ceiling on how fast the platform can acquire without drowning in transitional cost.

Sequencing across the portfolio is its own skill. With several TSAs running, the platform decides which migrations to prioritize based on extension fee exposure, service risk, and integration efficiency. Batching similar migrations, for example moving several acquisitions onto the platform ERP together, is far more efficient than handling each as a separate project. Portfolio level governance, not deal level, is what keeps a roll-up's TSA cost under control.

Section 04

Portfolio governance and visibility

A platform running many TSAs needs a single view of all of them: which are active, when each expires, what each costs, what extension exposure each carries, and where each migration stands. Without that portfolio dashboard, TSAs expire by surprise, extension fees trigger unnoticed, and the platform discovers its transitional cost only when the invoices arrive. Visibility is the precondition for control.

Governance has to operate at the portfolio level. A weekly view that tracks every active TSA, its migration status, and its cost lets the platform allocate integration resources where they retire the most cost or risk. This is the same discipline a portfolio program brings to any acquirer running several agreements at once, and a roll-up needs it more than anyone because its TSA count only grows.

Standard records make the portfolio manageable. Each acquisition closes its TSA with the same short record: services migrated, date of exit, residual cost, and lessons for the next deal. That repeatability turns a chaotic stack of isolated transitions into an industrialized capability, which is exactly what a serial acquirer needs to keep its deal machine from being throttled by its own transitional drag.

Section 05

Turning TSA exit into a repeatable capability

The platforms that roll up well treat TSA exit as a core competence, not a per deal afterthought. They have a standard TSA template they bring to negotiations, a standard migration playbook their integration team runs, and a portfolio governance system that keeps every active agreement visible. That machinery lets them acquire at pace without accumulating runaway transitional cost.

Building that capability pays compounding returns. The fifth acquisition migrates faster than the first because the playbook is proven, the template is tested, and the team has done it before. A platform that invests in TSA exit as a repeatable process turns what is a recurring drag for most acquirers into a genuine advantage in how fast and cheaply it can absorb deals.

The investment starts at the front. Pre-signing review of each target's service dependencies, done consistently with a tool like our TSA Pre-Signing Review, feeds the standard template and the migration plan from the first day of every deal. A roll-up that scopes every TSA the same disciplined way is a roll-up whose transitional cost scales with its ambition instead of strangling it.

FAQ

Questions buyers ask.

Why do roll-ups create a TSA portfolio rather than a single TSA?

A roll-up acquires a sequence of businesses, each carved out with its own seller, term, and service catalog. A platform doing several deals a year can run multiple active TSAs at once, each on a different clock. The challenge shifts from managing one exit to managing a portfolio of them as a coordinated system.

What is the binding constraint on a roll-up's TSA cost?

Integration capacity, not deal count. Each acquisition needs its services migrated onto the platform, and that work takes finite people and time. When deal pace outruns integration pace, TSAs accumulate, extension fees mount, and the platform pays multiple sellers for overlapping services. Resource integration as deliberately as deal flow.

How should a roll-up standardize its TSAs?

Treat TSA terms as a repeatable template brought to every deal, with consistent pricing mechanics, SLA definitions, exit ramps, and governance. Because the platform already runs finance, IT, and HR, it usually needs far less from each seller than a standalone buyer. Consistent terms let one integration playbook manage the whole portfolio instead of handling each TSA bespoke.

What does portfolio level TSA governance require?

A single view of every active TSA: status, expiry, cost, extension exposure, and migration progress. That visibility lets the platform allocate integration resources where they retire the most cost or risk, batch similar migrations, and avoid TSAs expiring or extension fees triggering by surprise. Standard closeout records turn a chaotic stack into an industrialized capability.

Related Reading

More on special situations.

Free Download

Get the buyer-side TSA Exit Playbook.

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 →

In a roll-up, the TSAs multiply faster than the platform.
TSA Pre-Signing Review

Make TSA exit a repeatable capability.

Fixed-fee review in 48 hours. Senior team on day one. The first conversation is always free.

White paper

The TSA Exit Playbook

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.

Read the playbook →
The Day One Letter

Get buyer-side TSA intelligence every two weeks

One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.

Subscribe to The Day One Letter →