The TSA Countdown: Why Most Carve-Outs Underestimate Day 1 Readiness
Every carve-out comes with a Transition Services Agreement, and every TSA comes with a clock. The problem is that most organizations treat the TSA period like a safety net instead of what it actually is: a countdown with a hard deadline and real financial consequences if you miss it.
We've seen the same story play out across enough carve-outs to recognize the pattern. The deal closes. There's a collective exhale. And then the TSA, which felt like generous runway during negotiation, starts to feel uncomfortably short by month three.
The Day 1 illusion
"Day 1 readiness" sounds like it means the carved-out entity can function independently starting on close date. In practice, it almost never does. What Day 1 readiness actually means is: the entity can limp along on the parent company's systems and services while a real standalone operation gets built underneath it, inside a window that's shorter than anyone budgeted for.
The gap between those two definitions is where carve-outs get into trouble. Deal teams negotiate TSA length based on what looks reasonable at signing. Operating teams then discover, once they're inside the actual systems, that "reasonable" didn't account for:
ERP and financial systems separation. Standing up a new instance, migrating clean data, and reconciling chart-of-accounts differences takes longer than IT estimates suggest - especially when the parent's systems were never built with separation in mind.
Payroll, benefits, and HR infrastructure. These carry hard compliance deadlines. You can't quietly run six weeks over on payroll continuity the way you might on a reporting dashboard.
IT and cybersecurity dependencies. Network access, email domains, security tooling, and data governance are frequently more entangled with the parent than anyone mapped out pre-close, and untangling them touches almost every other workstream.
Vendor and customer contract novation. Contracts that need to be reassigned to the new entity often move at the speed of the counterparty's legal department, not yours - and that's rarely factored into the internal TSA timeline.
None of these are exotic risks. They're well-known categories. What's underestimated isn't the category of risk, it's the time each one actually consumes once you're inside the details.
Why the underestimate happens
Three recurring reasons:
The TSA gets negotiated by deal teams, not operators. The people setting the TSA duration are optimizing for a clean deal structure and a defensible number to negotiate against. The people who will actually live inside the TSA countdown often aren't in the room yet.
Standalone readiness work doesn't start until after close. Legal and diligence work happens pre-close. Operational separation work, the actual system builds, the actual process design, often can't meaningfully start until the deal is signed, which means the TSA clock and the standalone-build clock start at the same moment, with no head start.
Nobody owns the full picture. IT owns systems. Finance owns the ledger. HR owns people systems. Without a single integration management office tracking dependencies across all of them, each function reports "on track" in isolation while the interdependencies between functions quietly slip.
What actually works
The carve-outs that hit their TSA deadlines cleanly tend to share a few disciplines:
Standalone cost and system mapping starts in diligence. Even a rough map of what needs to be separated - systems, contracts, people, IP - gives the operating team a running start instead of a cold one.
A single integration owner tracks cross-functional dependencies from day one. Not a steering committee that meets monthly — someone whose full-time job is knowing which of the twenty workstreams is actually the pacing item.
The TSA timeline gets stress-tested against the slowest dependency, not the average one. Payroll, ERP, and contract novation are usually the long poles. If those aren't done, the TSA isn't done, regardless of how everything else is tracking.
A contingency plan exists before it's needed. Whether that's a TSA extension negotiated in advance or a bridge solution for the slowest workstream, the option should be on the table in month two — not improvised in month eleven.
The cost of getting this wrong
TSA overruns aren't just an operational headache - they're a direct cost. Extended TSAs typically come with escalating fees, and every month spent still dependent on the seller's infrastructure is a month the new standalone entity isn't fully capturing the value the deal was underwritten on. For a PE sponsor, that shows up directly in the return math.
The fix isn't a longer TSA. It's treating Day 1 readiness as what it really is — the start of a sprint with a fixed finish line - and building the standalone operation with that finish line in view from the moment the deal is signed, not the moment it closes.
