Hair Care Division Of A Consumer Products Manufacturer ยท Pe Carve-Out
Nothing came with the deal. Twelve months to stand up a company.
A private equity sponsor signed a letter of intent for the professional hair care division of a large consumer products manufacturer: three brands, a Midwest factory and warehouse, 277 people. Every system the division ran on belonged to the parent, and the parent had never done a divestiture. As lead consultant, David Day sized the entanglement, priced the separation, and wrote the plan to get the new company onto its own systems inside a twelve-month transition agreement. The deal closed.
What David walked into
- No systems of its own. The division ran on the parent's global ERP, one instance serving 40 countries in the parent's data center. Neither the license nor the hosting could transfer.
- No network of its own. No domain, directory, email tenant, file storage or firewall. The day the trust to the parent was cut, all of it would go dark.
- A warehouse system nobody could move. Shipping ran on a system the parent had used for nearly 25 years, and the vendor refused to transfer the contract.
- One person. A single network engineer was the only IT candidate to transfer, and the parent was running three carve-outs that year with no playbook.
- A transition bill built by the seller. The parent's first estimate to run the division's IT during transition was about $2.1 million a year.
The insight
A carve-out is not a migration. The question is not how to move what the parent has, it is what the new company should run on for the next decade, and in what order, against a clock that is already running. The parent had cloned an empty copy of its ERP so the division could transact on day one. The easy answer was to keep it. David argued the opposite: use the clone as a twelve-month bridge and nothing more, because a global-scale ERP was overkill for a 70-user business.
The plan david built
Enterprise resource planning
A cloud ERP sized for the business: financials, distribution and manufacturing in one system, over a hundred written requirements.
Warehouse management
Keep the incumbent product the team knew, reimplemented in the cloud: outbound first so shipping never waited on the ERP.
Infrastructure
New office, new network with a temporary trust to the parent, cloud directory, email and files, a firewall of its own. Then cut the trust.
People
Make the offer to the one engineer immediately. A small permanent team under a transitional bench, and a dedicated program manager.
Every stream ran in parallel, because the transition agreement was a meter, not a safety net.
Three decisions that mattered
Each one went against what the seller, a vendor, or the easy path was offering.
He did not keep the parent's erp
Reimplementing it for good would have run about $3,000 a seat on hardware the new company could not support. The recommended cloud ERP cost about $1,200 per user per year. The clone bought the time. It did not become the answer.
He kept the hardest system on purpose
The warehouse system was the hardest piece of the separation and the obvious move was to switch vendors. David did not. Replacing a system that had shipped every order for 25 years, during a separation, on a deadline, was the bigger risk. He also pushed back on a cloud quote priced for 110 users when the business needed 40 to 50.
He questioned every line of the transition bill
The parent's estimate was read line by line: which costs were true run costs, which were the parent's overhead, which support roles were really half a person. The revised estimate came down by about $165,000 a year before the agreement was negotiated.
What was delivered
- Technology assessment with a scored framework and an overall rating the sponsor could act on
- Carve-out strategy across all four work streams: systems, requirements, vendors, infrastructure, staffing and sequencing
- A bottoms-up IT budget for the transition year and the year after, separating one-time separation cost from run rate
- Transition service agreement detail: what to buy from the parent, for how long, and what each line should cost
- Phased timelines for the ERP, warehouse, office, network and directory cut-over inside the twelve-month window
The deal closed. This engagement delivered the assessment, strategy, budget and transition plan; program management of the separation was handled separately. Lead consultant: David Day, prior to founding Elevate Tech. Client, parent, sponsor and vendor names withheld by policy.
What this means for your company
- Pe deal teams The seller's transition estimate is a starting position, not a price. Someone on your side has to read it line by line.
- Operating partners A carve-out that arrives with one IT person and a cloned ERP is not a company yet. It is a twelve-month project.
Related service: Technology integration after an acquisition.
Not sure where to start?
Take a free three-minute score. If a conversation makes sense, it will offer one.