Day One is the moment the Newco becomes a real company. Payroll runs. Customers are invoiced. Taxes are filed. Bank accounts work. Most of what makes that happen is buyer-side stand up work, not TSA service consumption. This pillar lays out the nine workstreams, the 90 day playbook, and the common failure modes.
Day One is the legal close. The moment the Newco becomes a separate company with its own balance sheet, its own employees, its own contracts, and its own operating responsibility. Day One readiness is the buyer-side work that makes that moment functional rather than chaotic.
Day One readiness is not about exiting the TSA. The TSA is the safety net. From Day One forward, the Newco consumes services under the TSA while it builds independent capability. Day One readiness is about the things the Newco has to do for itself, independent of the TSA, from the moment of close.
The work splits roughly into three phases. Pre-close stand up covers the legal entity, bank accounts, tax registrations, and basic operating infrastructure. Day One execution covers the cutover events that have to happen at close: customer notifications, employee transfers, system access changes, first payroll under the new entity. Post-Day One stabilisation runs the first 60 to 90 days, during which the Newco's operating cadence is established and the TSA workstreams settle into their steady state.
A working Day One readiness program is owned end to end by a single accountable lead, with named owners for each of the nine workstreams. Most failed Day Ones are failures of accountability structure, not failures of effort. The work was done. It was done by people who did not own the outcome, and the seams between workstreams went unaddressed.
Every Day One program runs across the same nine workstreams. The relative risk and complexity varies by carve-out. The list itself does not.
IT applications and infrastructure. Almost always the largest workstream by effort and risk. ERP, finance systems, identity, networks, end user computing, applications, data.
Finance and accounting. Chart of accounts, general ledger, financial close calendar, audit relationship, intercompany unwind, reporting infrastructure.
HR and payroll. Employee transfer documents, payroll cutover, benefits enrollment, HRIS data migration, employment law compliance.
Treasury and cash management. Bank accounts, cash forecasting, letters of credit, FX, insurance placements.
Procurement and vendor management. Vendor master file, purchase order systems, contract assignment or novation, supplier notifications.
Legal and corporate entities. Newco formation, board appointment, governance, subsidiaries, intellectual property assignments, customer contract assignments.
Tax. Direct and indirect tax registrations, transfer pricing, intercompany agreements, payroll tax, sales and use tax, international tax.
Cybersecurity and data protection. Identity and access management, network segmentation, security operations, data classification, regulatory compliance.
Commercial and customer operations. Customer notifications, sales operations, order to cash, customer support, marketing operations, branding transitions.
IT is almost always the largest Day One workstream by hours, dollars, and risk. The seller's ERP runs the business until the Newco stands up its own. Identity systems control who can log into what. Networks decide what can talk to what. End user computing decides whether employees can do their jobs on day one.
Day One IT readiness has four buckets. First, identity and access. New Newco accounts, MFA, single sign on, removal from seller domains where appropriate. Second, applications. ERP, CRM, HR systems, finance systems, the long tail of departmental tools. Most go onto the TSA at Day One. The Day One readiness work is making sure the Newco can authenticate into them and operate them.
Third, infrastructure. Networks, data centres, cloud accounts. Most Day One programs keep the seller's infrastructure on the TSA at close, with carve-out and migration to follow over the TSA term. The Day One work is ensuring the Newco's traffic can reach the seller's environment cleanly and securely, and the seller's traffic does not bleed into the Newco's environment.
Fourth, data. What data belongs to the Newco, where it lives, who can access it, and how it gets extracted at the end of the TSA. Data migration is often the long pole on the IT exit ramp. The Day One readiness work begins building the inventory and the extraction plan.
From Day One, the Newco has to close its books, file its taxes, manage its cash, and answer to its auditors. The seller's general ledger is no longer the source of truth. The Newco needs a chart of accounts, an accounting policy, a close calendar, an audit relationship, and a reporting cadence.
Most Day One programs run the financial close on the seller's general ledger for the first three to six months under the TSA, then migrate to a Newco system. The Day One readiness work for finance is therefore split. Pre-close, the Newco's chart of accounts, accounting policies, and reporting requirements are documented. At close, the seller's GL becomes a TSA service and the Newco's finance team learns to operate it from the buyer side. Mid-TSA, the Newco's own GL is stood up and migrated to.
Treasury is more time critical. From the moment of close, the Newco needs its own bank accounts, its own signatories, its own cash forecasting, its own letters of credit and trade finance. Most banks require six to eight weeks lead time. Day One treasury readiness starts six to eight weeks before close, not in the final week.
The intercompany unwind is often missed. The target business probably has intercompany balances, intercompany trading flows, and intercompany services with the parent. All of those have to be either terminated, novated, or converted to TSA scope at close. An unaddressed intercompany account is a future audit issue.
Day One in HR is high stakes because employees notice when payroll is wrong. The legal mechanics of transferring employees vary by jurisdiction. Some jurisdictions transfer automatically by operation of law. Some require explicit consent and documentation for each employee. Some treat the transfer as a new hire event. The Newco needs jurisdiction by jurisdiction advice from local employment counsel.
Payroll cutover is technical and unforgiving. The first payroll under the Newco entity has to net the same as the last payroll under the seller entity. Tax withholdings have to be correct. Benefits deductions have to roll over. Vacation accruals have to transfer. Year to date wage totals have to feed correctly into the Newco's W-2 or local equivalent at year end.
Benefits enrollment is similarly time critical. The Newco needs medical, dental, retirement, life, and disability plans in place at Day One. Plan terms should typically match what employees had pre-close, at least for the initial transition period, because employees evaluate the deal partly by what happens to their benefits.
The HRIS migration is usually a longer term workstream, often running ten to twenty four months. At Day One, most carve-outs keep the seller's HRIS on the TSA. The Day One work is documenting employee records, establishing data ownership, and starting the migration plan that runs across the TSA term.
Procurement Day One readiness centres on the vendor master file. The Newco needs to know who its vendors are, what contracts are in place, and which contracts assign or novate to the Newco at close. Most carve-outs have a long tail of vendor contracts that nobody on the buyer side has read. The Day One work is reading them, classifying them, and notifying vendors of the change in counterparty where required.
Tax is technical and jurisdiction-specific. The Newco needs direct tax registrations in each jurisdiction it operates, indirect tax registrations for sales tax, VAT, GST as applicable, payroll tax registrations, and any specialty registrations such as excise tax or environmental levies. Each registration has its own lead time. Most Day One programs begin tax registrations eight to twelve weeks pre-close.
Transfer pricing requires its own attention. The Newco's intercompany flows with any remaining parent affiliate need supporting documentation. Customer contracts that ran through the parent and now run through the Newco may have different VAT or sales tax treatment. The Day One tax workstream identifies these and addresses them.
Legal Day One readiness covers the Newco's corporate organisation, board composition, share register, statutory filings, contract assignments, intellectual property assignments, and the long tail of customer notifications. Most of the legal work is mechanical but has hard deadlines. Missing a corporate filing in the wrong jurisdiction can trigger penalties or dissolve a subsidiary.
Cybersecurity is the workstream most often left until last and the workstream most likely to surface a serious issue. At Day One, the Newco is exposed to identity and network risks that did not exist when it was inside the parent. Seller employees may retain access to Newco systems. Newco employees may retain access to seller systems. Network paths between the two environments may be wide open.
A Day One cyber readiness program covers four areas. Identity hygiene: a documented inventory of who has access to what, with seller leavers removed and Newco joiners provisioned. Network segmentation: defined boundaries between Newco and seller, with explicit allow lists for TSA service flows. Security operations: the Newco has its own incident response, its own security monitoring, and its own escalation paths, even if running initially on shared infrastructure under the TSA. Data classification: what data belongs to whom, what can move where, and what regulatory regimes apply.
Data protection requirements vary by jurisdiction. GDPR, CPRA, sectoral regulations all impose obligations on the Newco from Day One. The Day One readiness work includes documenting the Newco's data protection posture, identifying any breaches in the transfer process, and putting in place the records, agreements, and notifications required.
A common Day One failure pattern is treating cybersecurity as an IT subworkstream. Cyber sits across IT, legal, compliance, and operations. It deserves its own workstream owner reporting into the Day One lead, not a subteam inside the IT lead.
A standard Day One readiness program runs across roughly twelve weeks, divided into pre-close, Day One execution, and post-Day One stabilisation. The breakdown is not symmetric. Most of the work happens pre-close. Day One execution is roughly one week. The first 60 to 90 days of stabilisation are weeks of running cadence rather than weeks of net new build.
Weeks minus eight to minus four. Legal entity formation, bank account applications, tax registrations, vendor master build, employee transfer documentation, Newco governance design, board appointments. Most of this is mechanical with long lead times.
Weeks minus three to minus one. Final cutover preparation. Day One playbooks. Communication plans. Dress rehearsals. Test payrolls. Final Day One readiness assessment by workstream.
Day One week. Execution. Cutover events, system access changes, customer notifications, first day employee experience. A real time command centre handles issues as they surface.
Days one to thirty. Stabilisation. Operating cadence is established. Workstreams move from project mode to operations mode. Any Day One issues are remediated. TSA governance committee begins meeting.
Days thirty one to ninety. Steady state. The Newco is operating. The TSA is running. Mid-TSA workstreams begin: renegotiation planning, exit ramp construction, service-level baseline measurement. Day One readiness program is the firm's full twelve week package.
Six failure modes appear consistently on Day One programs that run into trouble. Each is avoidable with the right discipline.
Treating Day One as an IT project. IT is one of nine workstreams. An IT-led programme misses finance close issues, payroll cutover risks, tax registrations, and legal filings. A single Day One lead across all nine workstreams is the structural fix.
Starting too late. Bank accounts take six to eight weeks. Tax registrations take eight to twelve. Legal entity formation in some jurisdictions takes longer. A programme that starts four weeks pre-close has missed its lead times.
Conflating Day One readiness with TSA exit. Day One is operational stand up. TSA exit is the eighteen month schedule that follows. Programs that try to exit the TSA at Day One usually fail at both.
No single accountable owner. Each workstream has a lead, but no one person owns the seams between them. Issues that cross workstream boundaries fall into the gap.
Cybersecurity treated as an afterthought. Identity, network segmentation, and data protection are Day One critical. A Day One that goes live with seller employees still in Newco identity systems is a security incident waiting to happen.
No dress rehearsal. The Day One cutover is too complex to run blind. A dress rehearsal in week minus one surfaces issues that can be remediated before they cost real time on Day One.
Day One readiness means the Newco can operate as an independent legal entity from the moment of close. Payroll runs on the right entity. Bank accounts work. Customers can be invoiced. Taxes can be filed. IT systems are addressable from the Newco side. The TSA continues to provide everything that is not yet stood up independently.
A typical Day One readiness program runs roughly twelve weeks. Pre-close stand up of the legal entity, bank accounts, and operating infrastructure. Day One execution itself. And the first 60 to 90 days of stabilisation under the TSA. Complex carve-outs with shared ERP or significant headcount transfer can run longer.
A single accountable Day One lead, often a chief of staff to the CEO, a portfolio operations executive, or an interim COO. Each of the nine workstreams has a named owner who reports to the Day One lead. The Day One lead reports into the sponsor or the new entity's board.
No. Day One readiness is operational stand up. TSA exit is the schedule by which services move off the TSA over twelve to twenty four months. The Newco can be fully Day One ready while still consuming the entire TSA service catalog. Conflating the two is a common error.
Treating Day One as an IT project. Day One spans nine workstreams. IT is one of them, often the largest, but finance, HR, treasury, tax, and legal each have Day One critical deliverables that an IT-led programme will miss. A single accountable owner across all nine workstreams is the discipline that prevents this.
Signed TSA. Signed SPA. Newco legal entity formed and operating. Bank accounts opened. Tax registrations filed. Customer notification letters drafted. Employee transfer documents executed. Vendor master file populated. Insurance policies in place. Cybersecurity controls active. The Day One readiness checklist runs to roughly two hundred line items across the nine workstreams.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.