TSA Exit Acceleration
The exit is done. Now make it lean.
Fixed-fee scope to find and remove the cost the exit left behind. Senior team on day one. The first conversation is always free.
Post-TSA optimization is the work that begins the day the last service exits, when the Newco runs on its own systems for the first time and the real operating costs become visible. The exit proved the business can stand alone. Optimization proves it can run lean. This is the phase the TSA exit strategy framework treats as the second half of the deal, not an afterthought.
Most buyers treat the TSA exit as the destination. The last service migrates, the seller invoices stop, and the program declares victory. That instinct leaves money on the table. The Newco that exits the TSA is rarely the Newco that should exist at steady state. It carries the seller's process design, the seller's vendor contracts at the seller's volumes, and a cost base sized for a business that no longer exists.
The exit was scoped to replace what the seller provided, function for function. That was the right scope for the exit. It is the wrong target for the operating company. A buyer who replicated the seller's email platform, the seller's procurement process, and the seller's reporting cadence has bought continuity, which is what the exit required. The value creation plan needs more than continuity.
Post-TSA optimization is the deliberate second pass. It asks a different question than the exit asked. The exit asked whether the function works without the seller. Optimization asks whether the function is sized, priced, and designed for the business as it is now owned and operated. The two questions produce different answers, and the gap between them is the opportunity.
The operating partner who funds the exit and then redeploys the team has captured the easy half of the value. The buyers who keep a small standing team focused on the operating model for two quarters after exit capture the rest. The cost of that team is trivial against the run rate savings it finds.
The best optimization work is scoped during the TSA, not after. While the separation team documents every system, process, and contract it is replacing, it should flag each one that was replicated rather than redesigned. That flag list becomes the optimization backlog. Building it during exit costs almost nothing because the team already has the systems open.
Three categories fill the backlog. First, oversized infrastructure: cloud capacity, license counts, and support contracts provisioned to match the seller's footprint rather than the Newco's actual demand. Second, replicated process: approval chains, close cadences, and manual handoffs inherited from a larger parent. Third, premium vendor pricing: contracts signed at exit speed without the leverage that a deliberate sourcing exercise would have applied.
Each backlog item gets a rough size and a confidence level during exit. The team will not have time to act on most of them while the cutover dominates attention. The point is to capture them while the knowledge is fresh, so the optimization phase opens with a ranked list instead of a blank page. A backlog built six months after exit is a backlog built from memory.
The map also records dependencies. Some optimizations cannot start until the TSA fully closes because they touch systems still under seller control. Others can begin in parallel. Sequencing the backlog against the exit timeline turns a vague intention into a dated plan the operating partner can hold the team to.
The exit eliminates the TSA invoice. It does not eliminate stranded costs, the overhead that was sized for the separated business and never resized. A Newco that contracted a help desk for the seller's headcount, a finance team for the seller's transaction volume, and a real estate footprint for the seller's office plan is carrying capacity it does not use.
Stranded cost elimination is the highest return optimization work because the savings are pure margin. There is no revenue risk, no customer impact, and no integration to manage. The work is unglamorous: matching contracted capacity against actual demand, line by line, and renegotiating or terminating the excess. It is exactly the work that gets deferred when the team scatters after exit.
The discipline that finds stranded cost is the same one that runs the exit. Inventory everything. Measure actual consumption over a representative period, usually 60 to 90 days post exit when demand has settled. Compare against contracted capacity. Act on every gap above a threshold. The buyers who do this systematically recover one to three points of operating margin that the exit alone would never have surfaced.
A full treatment of where this overhead lives and how to remove it sits in our note on stranded cost elimination. The headline is that stranded cost is not a TSA problem. It is an operating model problem that the TSA exposed.
The exit migrated systems. Optimization redesigns the processes those systems run. A Newco that inherited a monthly close built for a parent with shared service centers can often close faster and with fewer hands once it owns the full process. The same is true of procurement approvals, vendor onboarding, and reporting. The inherited design was built for a different organization.
Process redesign is where a smaller, more focused company has a structural advantage over the parent it left. The seller's process carried the overhead of scale, of consensus across divisions, of controls sized for a large enterprise. The Newco can strip that overhead if it is willing to question the inherited design rather than preserve it out of habit.
The risk is moving too fast. A process redesign during the fragile post exit window can break things that the exit team worked hard to stabilize. The sequencing rule is simple: stabilize first, optimize second. Give each migrated function a quarter to prove it runs reliably on the new systems before you start changing how it works. Optimization on an unstable base creates more problems than it solves.
The operating partner sets the redesign priorities against the value creation plan. Not every process is worth redesigning. The ones that drive cost, slow decisions, or block growth come first. The rest can wait or stay as inherited. Discipline about what not to optimize is as valuable as the optimization itself.
Optimization needs a baseline, and the exit is where you set it. The run rate cost of the Newco in its first full quarter post exit is the number every later improvement measures against. Buyers who never capture that baseline cannot tell whether their optimization worked. They have activity without evidence.
The metrics that matter are operating, not project. Cost per transaction, infrastructure spend per unit of demand, headcount against output, vendor spend against contracted volume. These are the numbers the operating partner reports to the board and the numbers the value creation plan is judged on. The exit produced the conditions to measure them cleanly for the first time.
We treat the discipline of capturing and reporting these numbers as its own workstream, covered in our note on TSA exit retrospective metrics. The short version is that a Newco which measures its own operating efficiency from day one optimizes faster than one which waits for a problem to appear in the financials.
Post-TSA optimization is not a separate program with its own budget and governance. It is the natural continuation of the exit, run by a smaller team against a backlog the exit produced. The buyers who treat it that way turn a successful separation into a more valuable company. The buyers who declare victory at exit leave that value uncaptured.
The backlog is built during the exit while systems and contracts are open. Active optimization work starts once a function has run reliably on its own systems for a quarter. Stabilize first, optimize second. Acting before the migrated function is stable risks breaking what the exit worked to deliver.
No. It is the continuation of the exit run by a smaller standing team against a backlog the exit produced. Treating it as a separate program with its own governance adds overhead. The knowledge, the inventory, and the relationships built during exit are exactly what optimization needs.
Stranded cost elimination first, because the savings are pure margin with no revenue risk. Then oversized infrastructure and licenses provisioned to the seller's footprint. Then premium vendor pricing signed at exit speed. Process redesign delivers value too but takes longer and carries more execution risk.
Against the run rate baseline captured in the first full quarter post exit. Operating metrics like cost per transaction, infrastructure spend per unit of demand, and vendor spend against contracted volume show whether the work moved the number. Without that baseline, optimization is activity without evidence.
The operating numbers to capture at exit and report against forever after.
Read the article →Where the overhead hides after separation and the discipline that removes it.
Read the article →How the operating partner turns a separation into measurable enterprise value.
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 scope to find and remove the cost the exit left behind. 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.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →