Carve-outs come with a transition clock

When a company spins off or sells a unit, the new company wakes up owning almost none of its systems. It borrows them from the parent under a transition services agreement. That agreement has an end date.

This is one of the strongest signals there is. Fixed date, real money and work the new company can't do alone.

Why carve-out work goes outside

A carve-out is a business unit separated from its parent. It becomes a standalone public company in a spin-off, or it's sold to a buyer, often private equity.

On day one, the unit runs on the parent's ERP, the parent's HR system, the parent's email, the parent's network and the parent's help desk. The transition services agreement, or TSA, lets it keep using them for a fee, usually for twelve to twenty-four months. After that, the parent turns them off.

So the new company has to stand up everything. Finance, HR, payroll, identity, infrastructure, data, security, every application the unit touched. It has to pull its data out, often untangling it from shared databases. And it has to do this with an IT team that was a small slice of the parent's, if it got any IT people at all.

That's why the work nearly always goes outside. There's no internal team big enough, and there's no time to hire one.

Where to find it

Spin-offs at public companies are loud. The parent announces the plan, often a year or more ahead. The new company files a Form 10 registration statement on SEC EDGAR, and that document describes the separation, the TSA and the systems the new company has to build. Read the sections on the separation and on agreements with the former parent.

Divestitures show up in an 8-K when they're material, and in press releases either way. The deal announcement tells you who'll own the unit. If it's a private equity firm, read private equity ownership changes the timing.

Trade press covers carve-outs in most industries. LinkedIn shows the new company's leadership team forming, usually months before close.

What to read in the documents

The TSA term is the clock. Eighteen to twenty-four months is normal. Twelve is tight. Anything shorter than a year means the new company is already behind.

Language about standalone systems, separation costs or one-time costs to establish independent infrastructure is strong. Companies often estimate those costs in the filing, and that number is the size of the opportunity.

A unit that shared a single ERP instance with the parent is a harder separation than one that ran its own. Look for that in the description of the business. Harder means more work.

A sale to a strategic buyer who'll fold the unit into its own systems is a different signal. That's integration work on the buyer's side, closer to post-merger integration and the first 100 days.

Noise is a "strategic review" with no announced outcome. That might become a carve-out. It isn't one yet.

Both sides of the table

The new company's CIO, if there is one, owns the clock and was probably hired in the last few months. The new CFO needs a working finance system and a clean close before the first quarter as a standalone company. The separation office lead, often an executive on loan from the parent, owns the plan. On the parent side, the CIO wants the TSA to end on time so their team can stop running someone else's systems.

Both sides buy. The parent pays for help to disentangle. The new company pays for help to stand up.

Say Aldren Health announces it will spin off its diagnostics unit as Clarion Diagnostics, with an 18-month TSA. Clarion names Tom Brandt as its first CIO. Here's an opener.

Clarion's Form 10 shows an 18-month TSA with Aldren. That puts every system the business runs on behind a date you didn't pick. My guess is ERP and HR are planned, and the harder part is the data still living in Aldren's shared warehouse, with no one assigned to untangle it. Is that close, or is the bigger gap somewhere else?

Hook from the filing. Trigger on his seat. Hypothesis on the part nobody planned. Exit he can answer in a line.

Timing and what stacks

The best window is between announcement and close. Decisions about the target architecture get made then, and the new leadership team is forming. After close, the clock is running and the first vendors are in. There's still work, especially as the TSA end date gets closer and things slip. Carve-outs rarely finish early.

A carve-out stacks with nearly everything. A new CIO at the spun company. Debt raised to fund the separation, which a credit facility is money with a purpose covers. Job posts for an entire IT function at once. And the signals before an ERP migration show up almost every time.

A TSA is a contract with an expiration date. Everything the new company runs on has to be rebuilt before it. Find the person holding that date and name the piece of the rebuild nobody owns yet.