TSA Pre-Signing Review
Find the stranded cost before it finds you. Before you sign.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Stranded costs are the expenses that remain after a carve-out exits a transition service but the underlying cost does not disappear with it. The buyer migrates off the seller’s payroll system, stops paying the TSA charge, and then discovers a contract, a license, a headcount, or an allocation that was supposed to fall away and did not. Stranded costs are one of the most under managed risks in a separation, and surfacing them early is a core part of a disciplined TSA exit strategy.
A stranded cost is a cost that survives the thing it was meant to support. In a carve-out it shows up in two directions. The seller can be left with cost that used to be absorbed by the divested business: a data center sized for a larger organization, overhead that was allocated across more units, contracts scaled for higher volume. The buyer can be left with cost that the transition was supposed to retire but did not.
On the buyer side, the classic pattern is a service that migrates but whose cost lingers. The buyer stands up its own payroll and stops paying the TSA charge, but a third-party contract the seller signed on the business’s behalf rolls on, or a software license remains committed, or a shared facility cost keeps being allocated. The service moved. The expense did not.
Stranded costs are insidious because they are easy to miss in the relief of a completed migration. The visible TSA charge disappears from the invoice, the team marks the service exited, and the residual cost continues quietly in another line of the budget. Without a deliberate hunt for them, stranded costs accumulate into a meaningful drag on the value creation plan.
Contracts are the largest source. The divested business often relied on agreements the seller signed centrally: vendor contracts, service agreements, volume commitments. When the business leaves, those contracts may carry minimum commitments, termination penalties, or notice periods that keep cost flowing long after the service is replaced. The buyer needs to know which contracts it is assuming and what it costs to exit them.
Licenses and subscriptions are the second source. Enterprise software is frequently licensed at the parent level with terms that do not unwind cleanly. The carved out business may keep paying for seats, instances, or capacity it no longer needs, or be locked into a term that outlasts the migration. Mapping the license estate before signing reveals which commitments will strand.
People and space round out the list. Headcount that supported a function can be left without a role once the function migrates, and real estate sized for the old footprint can keep generating cost after the business consolidates. Each of these is a stranded cost in waiting, and each is far easier to plan for before close than to unwind after it. The pattern is covered further in carve-out stranded costs.
Stranded costs hide because the signal that usually flags a cost, the invoice for a service, goes away when the service is exited. The team sees the TSA charge disappear and reasonably assumes the cost is gone. The residual contract, license, or allocation that remains is in a different budget line, often owned by a different team, and nobody connects it back to the service that was supposed to take it with it.
They also hide because allocation obscures them. A cost allocated across the business as overhead does not announce itself as belonging to any one service. When the service migrates, the allocation may simply redistribute rather than disappear, leaving the buyer paying the same total with one fewer service to show for it. Untangling allocation from actual cost is essential to seeing what should strand.
Finally they hide because the transition’s attention is on standing up replacements, not on confirming that old costs fell away. The migration is judged complete when the new service works, not when the old cost is gone. That gap between operational exit and financial exit is exactly where stranded cost lives, and closing it requires deliberate financial tracking alongside the operational migration.
Time works against the buyer here. The longer a stranded cost sits unexamined, the more it looks like a normal part of the run rate, until no one remembers it was supposed to disappear. Costs that would have been obvious exit items in the first month become accepted budget lines by the sixth. Catching them requires checking for residual cost at the moment each service exits, while the link between the retired service and its supporting expense is still fresh and the contract or license is still identifiable.
Quantifying stranded cost starts with a baseline built from the service catalog and the cost behind each service. For every service in the transition, the buyer should know not just the TSA charge but the underlying contracts, licenses, headcount, and allocations that support it. That mapping is the reference against which the buyer confirms, after each exit, that the supporting cost actually fell away.
With the baseline in place, the buyer tracks cost as services retire. As each service exits, the team checks that the associated third-party cost was terminated, the license was released, the headcount was redeployed or removed, and the allocation was eliminated rather than redistributed. The difference between what should have fallen away and what actually did is the stranded cost, quantified line by line.
This is measurable work, not estimation. Each stranded cost has a contract, a license number, a role, or an allocation behind it, and each can be priced. A buyer that maintains this tracking can show exactly how much cost the transition removed and exactly how much remains stranded, which turns a vague concern into a managed elimination program.
Elimination begins before signing. The buyer should understand which contracts and licenses it is assuming, what their commitments and exit terms are, and which will strand when services migrate. Knowing this early lets the buyer negotiate exit rights, align contract terms with the migration timeline, and avoid inheriting commitments that outlast the services they support.
During the transition, elimination is a tracked workstream, not a hope. The same governance that manages the service exits should manage the cost exits, confirming that each retired service takes its supporting cost with it. Where a cost cannot be eliminated immediately because of a contract term, the buyer at least knows about it, has priced it, and has a date for when it ends.
The discipline that prevents stranded cost is the same discipline that runs a clean exit: a complete catalog, a cost baseline behind it, and a governance process that tracks financial exit alongside operational exit. Buyers who plan the cost exit as deliberately as they plan the migration recover the value the carve-out was supposed to deliver. Those who plan only the migration find the stranded cost later, in the budget, where it is hardest to remove. This is exactly the work a stranded cost elimination program addresses.
They are costs that remain after a transition service is exited but the underlying expense does not fall away with it. A buyer may migrate off a service and stop paying the TSA charge, only to find a contract, license, headcount, or allocation that was supposed to disappear still generating cost.
Because the invoice that usually flags a cost goes away when the service is exited. The team sees the TSA charge disappear and assumes the cost is gone, while the residual contract or allocation continues quietly in a different budget line owned by a different team.
By building a cost baseline from the service catalog that maps every service to the contracts, licenses, headcount, and allocations behind it, then tracking, after each exit, whether that supporting cost actually fell away. The gap between what should have ended and what did is the stranded cost.
Before signing. Knowing which contracts and licenses will strand when services migrate lets the buyer negotiate exit rights and align terms with the migration timeline, rather than discovering the residual cost after close when it is hardest to remove.
The fuller picture of where residual cost hides in a separation.
Read the article →The tracked workstream that removes residual cost as services retire.
Read the article →The inventory that becomes the cost baseline behind every service.
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.
Quantify dis-synergy before signature and build the elimination into the exit. Stranded cost is invisible until the TSA ends and the invoices keep arriving.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →