Blog · Carve-Outs

An add on TSA is a smaller deal with the same risk profile.

A private equity add on TSA is a transition services agreement entered by a portfolio company acquiring a tuck in target. The work runs inside the broader carve out advisory framework but the dynamic is different from a platform carve out. The buyer is already a sponsor backed operator, the integration runway is shorter, the operating partner has done it before, and the value creation thesis depends on how fast the add on integrates into the platform.

6
Workstreams
3 to 12 Mo.
Typical Timeline
9 min
Read Time
2026
Last Updated
Section 01

Tuck in dynamics and the integration window.

An add on acquisition runs faster than a platform carve out. The portfolio company already has working systems, working teams, and a value creation plan. The target is usually smaller, often a founder owned company or a corporate divestiture of a non core unit. The TSA is shorter, the service catalog narrower, and the exit runway tighter. The integration thesis assumes that the add on lives inside the platform within a defined window.

Three patterns appear in add on integration. Hard integration brings the add on onto the platform systems as fast as possible and retires the legacy stack. Soft integration leaves the add on on its own systems with operating overlap at the holding company level. Hybrid integration runs the add on on its own systems for a defined period before migrating onto the platform. The TSA design follows the integration pattern.

Hard integration TSAs target a 3 to 6 month exit. Soft integration TSAs may run 12 months or longer. Hybrid integration TSAs run 9 to 12 months with a planned migration milestone partway through. The TSA timeline maps to the integration approach and the operating partner approves the choice before the team writes the service catalog.

The seller in an add on deal is often a strategic seller carving out a non core unit, a private equity sponsor of a smaller fund, or a founder owner. Each seller type has a different default TSA posture. The buyer side review during pre signing adapts the negotiation playbook to the seller's typical patterns. Strategic sellers default to longer runways. Sponsor sellers default to shorter runways. Founder sellers default to almost no TSA at all.

Section 02

Platform alignment and the system mapping question.

The platform already runs on a chosen ERP, a chosen HRIS, a chosen CRM, and a chosen finance stack. The add on runs on whatever it inherited. The integration plan maps the add on systems to the platform standards and identifies which add on systems retire, which migrate to the platform, and which remain because the add on has a feature the platform does not yet support.

Master data alignment is the first integration work. Customer records, vendor records, product hierarchies, chart of accounts mappings, and employee records all map between the add on and the platform. The mapping logic gets documented before any system migration starts. Where the platform has tight reference data, the add on records get cleaned during the migration. Where the platform is loose, the add on records carry their own structure.

Reporting and consolidation come early in an add on integration. The portfolio company needs consolidated financials on the next quarterly board meeting. The TSA covers the add on accounting work until the consolidation logic moves into the platform finance stack. The work pairs with the carve out 100 day plan and runs in parallel with the broader integration plan.

Identity, security, and access management consolidate fast. The add on employees move onto platform single sign on, platform email, platform device management, and platform endpoint security in the first 30 to 60 days. The TSA carries the legacy identity stack briefly until the cutover completes. Where the platform runs a mature security program, the add on inherits the program rather than building its own.

Section 03

Reverse TSA risk and the seller dependence trap.

Reverse TSA risk is the silent killer in add on deals. The add on may continue to provide services to the seller after close, particularly when the seller carved out a single business line from a larger parent. The reverse TSA runs from the add on back to the seller, the add on receives a fee, and the operating attention sits with a small team that the portfolio company needs for the integration. The reverse TSA gets ignored in the deal sprint and becomes a drag on the value creation timeline.

The buyer side review during pre signing isolates every reverse TSA service. The reverse service catalog gets a defined end date, a defined fee, a defined service level, and a defined transition plan. Where the seller wants a longer reverse TSA, the portfolio company prices the operating cost honestly and either declines or negotiates a real margin. The default seller language often leaves the portfolio company providing services at cost while seller demands rise.

Operating distraction is the second order risk. Senior engineers in a small add on cannot integrate the company and serve a reverse TSA at the same time. The portfolio company assigns specific people to the reverse TSA, ring fences them from the integration team, and tracks their utilization weekly. Without that discipline, integration slips and the value creation thesis slips with it.

Reverse TSA exit clauses match the forward TSA exit clauses. The portfolio company should be able to walk away on reasonable notice with limited liability. Sellers will resist. The buyer side review establishes the exit terms during the deal negotiation, not during the inevitable later renegotiation.

Section 04

Sponsor coordination and the operating partner cadence.

The operating partner sits on top of the add on TSA program. The portfolio company CFO and CIO run the day to day work and the operating partner sets the cadence, the milestones, and the escalation paths. The first 30 days post close set the operating rhythm. The first 90 days demonstrate the integration progress to the deal team and the fund.

Value creation reporting on an add on uses a defined template. Cost savings capture, revenue expansion, run rate operating efficiency, system retirement milestones, and headcount alignment all roll up into the quarterly investor letter. The TSA exit milestones map to those reporting milestones. Each TSA service that retires translates directly into a value creation data point.

Working with the platform CFO matters more than working with the deal team. The platform CFO inherits the operating responsibility for the add on and lives with the integration outcomes for years. The operating partner positions the platform CFO as the owner of the TSA program from the first board meeting forward. The TSA design respects what the platform CFO can absorb.

A sponsor with multiple add ons in flight develops a portfolio TSA discipline. The same playbook, the same templates, the same governance cadence run across each add on. The work pairs with the portfolio TSA management framework. The result is a faster, more predictable, and less expensive add on program across the platform.

Section 05

Pre signing leverage and the buyer side review.

Add on TSAs are smaller than platform TSAs but the buyer side review pays back faster. The platform already has working systems and a working team. The TSA pricing should reflect the lower complexity. The buyer side review during pre signing brings a tuck in TSA checklist into the negotiation. Service scope. Service catalog. Reverse TSA exposure. Extension fee curves. Integration milestones. Each item gets a buyer estimate of cost, time, and risk.

Extension fees in add on TSAs default to seller favorable patterns even when the runway is short. The buyer side review caps the extension fees, defines the extension triggers, and negates penalty escalations for delays caused by seller readiness. The work pairs with the pre signing leverage playbook.

Service levels in add on TSAs need to anchor to the platform's existing service levels. The platform CIO already operates a CRM SLA, a finance close SLA, and a help desk SLA. The TSA SLAs should align so that the add on integration does not degrade the platform's existing performance metrics. The buyer side review imports the platform standards into the TSA service definitions.

Private equity add on TSA reviews and exit programs are delivered under a Fixed Fee or Portfolio Retainer engagement model through TSA pre signing review and the Day One readiness program. The work runs faster when the sponsor has a portfolio retainer because the template, the team, and the playbook are already in place.

Related Reading

More on industry carve outs.

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 →

An add on TSA is a smaller deal with the same risk profile.
TSA Pre-Signing Review

A buyer side TSA review. Before the deal closes.

Fixed-fee proposal 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 →
White paper

PE Value-Creation Playbook

A representative $150M-revenue platform carve-out runs a Transition Services Agreement across nine functions. For a PE owner the exit is not an IT chore — it is a value-creation workstream with an EBITDA number on it. The moves below cut the exit from a 16-month drift to a 9-month managed exit, remove $4.4M of mark-up and stranded cost, and lift recurring EBITDA enough to move enterprise value at exit multiple.

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 →