Day One Readiness
Plan it. Then close it.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Carve-out Day One readiness is the discipline of preparing Newco to operate as an independent business on the first calendar day after close. The work begins long before signing and is the single largest determinant of whether the TSA becomes a bridge or a trap. This article sits inside the broader carve-out advisory program and explains what Day One actually requires, who owns each piece, and where the work most often breaks down.
Day One is the first business day Newco operates under new ownership. Day One readiness is the set of capabilities, contracts, systems, people, and money flows that must be in place at that moment for the company to invoice customers, pay vendors, run payroll, close the books, secure the environment, and meet regulatory obligations. Anything not ready on Day One either falls back to the seller through the TSA, falls to a third party, or fails.
The trigger event is close. Close is a fixed date. The capabilities required at close are not negotiable in the way deal terms are. The customer expects an invoice. The employee expects a paycheck. The auditor expects a closing balance. The cyber posture must hold. None of these can slip a quarter while the team works through a project plan. Day One readiness is the operational version of a hard deadline.
The scope is broader than IT. Day One readiness covers finance, HR and payroll, treasury, procurement, legal entity setup, cybersecurity, customer communication, vendor communication, and regulatory filings. Each workstream has its own dependencies, its own critical path, and its own gating decisions. Coordinating all of them under one program is the work.
Most failures on Day One are not technical surprises. They are missed dependencies. A bank account opens late because a tax ID arrived late because the legal entity formed late because the corporate counsel waited on a state filing nobody owned. The remedy is sequencing and ownership, not heroics. The full sequence is covered in the carve-out 100 day plan.
Across carve-outs in every industry, the same nine workstreams recur. Legal entity setup creates the corporate shell, the registrations, and the tax IDs. IT separation establishes connectivity, identity, and access for Newco. Finance separation sets up the general ledger, the close cycle, and the audit trail. HR and payroll moves the employee population onto Newco systems and pay codes. Treasury opens bank accounts, sets up cash management, and funds payroll on Day One.
Procurement migrates vendor contracts, sets up purchase orders, and prevents service interruption with key suppliers. Cybersecurity establishes the Newco perimeter, the identity boundary, and the monitoring posture before any external traffic flows. Customer and vendor communication notifies parties of the change in legal entity, payment instructions, and operating contact. Regulatory and tax filings register Newco with the relevant authorities, transfer permits, and start the clock on new obligations.
Each workstream has a Day One target and a steady state target. The Day One target is the minimum capability required at close. The steady state target is the destination over the TSA exit ramp. The work between those two states is the bulk of the program. Underestimating either target produces predictable problems. Overbuilding for Day One slows the program. Underbuilding leaves Newco unable to operate without the seller.
The dependency map between workstreams is the most important artifact in the program. IT separation depends on legal entity for domain ownership. Treasury depends on legal entity for bank account opening. Payroll depends on treasury for funding and on HR for the employee master file. Procurement depends on IT for system access and on legal for contract assignment. The map looks simple until it does not. For deeper coverage of IT, see the IT separation playbook.
The TSA exists because Newco cannot stand up every capability on the first business day. The seller provides services across the gap. The pricing is typically cost-plus a mark-up. The duration is typically 12 to 24 months. The extension fees are typically punitive. The TSA is a commercial document, not a partnership. The buyer who treats the TSA as a continuation of seller goodwill ends up paying extension fees that exceed the cost of building the capability.
Day One readiness reduces TSA scope. Every capability that Newco can stand up by close is a service that does not appear in the TSA. Every service that does not appear in the TSA is a cost not paid, a dependency not created, and a milestone not negotiated. The program economics flip in favor of the buyer the more capability moves to Newco before close. The temptation to push everything into the TSA produces a thick TSA and a thin Newco. That combination is expensive.
The TSA also has structural risks the readiness program must address. Services not explicitly listed will not be provided. Services priced at cost-plus often carry pass-through costs the buyer did not see during diligence. Service level commitments are usually weak. Termination rights typically favor the seller. The readiness program needs to know the TSA inside and out before close, not after. The pre-signing leverage window is the only time the buyer has the seller's full attention.
The exit ramp belongs in the program from the start. Each TSA service has a planned exit milestone, a destination, and an owner. The exit milestones drive the readiness work and the TSA renegotiation rhythm. A program without a credible exit ramp drifts. A program with milestones, owners, and dates reaches steady state on the original timeline.
The Day One readiness program needs one accountable owner. The owner has authority across all nine workstreams, reports to the operating partner or the CEO, and runs a weekly cadence from signing to close. The owner does not need deep expertise in every workstream. The owner needs the ability to call escalations, resolve cross workstream conflicts, and hold dates. A program without a single owner produces nine separate plans and no integration.
Operating partners typically take the sponsor role and let an embedded program leader hold the day to day reins. The program leader can be internal or external. Either model works. The model that does not work is distributing the program across the workstream leads with no central owner. Day One readiness is integrative work. Without a single throat to choke, the integration does not happen.
The governance committee meets weekly until close and then biweekly through the TSA. The agenda is dependencies, blockers, escalations, and decisions. The committee is small. Most carve-outs benefit from a committee of five to eight, with rotating workstream leads as the agenda demands. Large committees produce theater. Small committees produce decisions.
The call rights with the seller need to be explicit. Newco needs the ability to escalate TSA issues to the seller's program management office on agreed timelines. The escalation path runs from workstream lead to TSA manager to governance committee to executive sponsor. Each level has a clock. Disputes that miss the clock without resolution move up the chain automatically. The mechanism is detailed in TSA governance best practices.
The most common failure is starting too late. Programs that begin after signing run out of calendar before they run out of work. Day One readiness should begin at the letter of intent stage, not at signing. The IT separation in particular requires lead time on identity, network, and endpoint that signing to close calendars rarely provide. Late starts produce thick TSAs and unhappy Newcos.
The second common failure is misjudging the carve-out perimeter. The deal team draws a clean perimeter on a slide. The operating reality is messier. Shared services, shared contracts, shared people, shared systems, shared physical space, and shared data create a long tail of small separations. Each one missed becomes a friction point on Day One. The perimeter audit, sometimes called the asset and contract reconciliation, takes weeks and is not optional.
The third common failure is underestimating cybersecurity. The seller's controls protect a different perimeter than Newco's. Identity systems, endpoint posture, email domain, certificate authorities, vulnerability management, incident response, and third-party risk all need a Newco footprint by Day One. The cyber workstream is often the last to be scoped and the first to surface gaps after close. The right sequence is detailed in the Day One cybersecurity article.
The fourth common failure is treating the TSA as a passive document. Buyers who do not actively manage the TSA are managed by it. The seller will execute the TSA as written. Services not explicitly requested will not be provided. SLA breaches not formally claimed will not produce credits. Extension fees not avoided will accumulate. The TSA needs an active manager on the Newco side. That role is detailed in vendor management for TSA exit.
The IT separation sequence and the dependencies that drive Day One readiness.
Read the article →The 100 day operating plan that bridges Day One readiness to early TSA exit.
Read the article →The stranded cost problem on both sides of the carve-out and how to address it.
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.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →Day One is binary: the carved-out business operates standalone or it does not. On a representative $48M-revenue carve-out, running the readiness check across all twelve functions instead of discovering the gaps at midnight removes $2.4M of avoidable Day-One remediation and emergency-extension cost.