I have been part of several company separations.
Sometimes they called it a “spin-off.” Other times it was selling an unprofitable or unwanted part of the business.
I wasn’t always in a position to understand the dynamics or the reasoning behind the decision. Especially earlier in my career, I was simply an employee inside one of the businesses affected by it.
Sometimes removing a unit that no longer fits or no longer works can make the remaining business stronger. But the part being removed is often still connected technically and operationally to the part being kept.
But every time, the separation created a lot of attention and emotion inside the company.
In the larger enterprises where I saw these processes from the inside, one thing stood out: they moved slowly.
Not necessarily because people were indecisive.
Because they were planned to an extraordinary level of detail.
And that planning took time.
Systems were shared. Data was shared. Access was shared. Knowledge bases were shared. Infrastructure and operational processes crossed organizational boundaries.
There were many things that looked simple on an org chart but were anything but simple underneath it.
Someone had to work out what belonged where, what needed to be duplicated, what needed to move, what needed temporary support, and what could simply disappear.
When that work was planned thoroughly and executed well, the actual separation could happen without major disruption.
That is the boring outcome.
And boring is exactly what you want.
Months of preparation can result in very little drama on the day. The absence of disruption can be evidence that the planning worked.
When the deal runs ahead of the work
I have also seen — and heard about — much uglier scenarios.
Sometimes the wrong decision was made. Sometimes the right decision was made, but too late.
One particularly dangerous version is deciding how the company will technically separate only after the deal has already been done.
The transaction can be complete while the businesses still depend on the same systems to operate. A P&L can show the unit someone wants to remove without showing everything attached to it.
If somebody is about to invest a large amount of their money — or a large chunk of their life — into acquiring a business, these are the kinds of questions that should already have answers.
Systems and data
- Which applications belong to the parent and which to the separated business, NewCo?
- Which databases contain shared data?
- Which APIs and integrations cross the boundary?
- Which reports and finance workflows depend on shared systems?
Identity and ownership
- How are identities separated?
- What happens to SSO, Active Directory, Okta, or Microsoft 365?
- What cybersecurity access must disappear at separation?
- Who owns source code, repositories, domains, and cloud accounts?
Vendors and infrastructure
- Which SaaS contracts need cloning, renegotiating, or replacing?
- Which vendors support both businesses?
- What infrastructure must be duplicated?
Day 1 independence
- Can NewCo operate independently on Day 1?
- What temporary services must the parent continue supplying?
- What does the transition services agreement, or TSA, actually require technically?
- What is the minimum viable standalone stack?
- What can be killed instead of migrated?
Those answers determine how independent NewCo can actually be on Day 1 and what still needs to be supplied temporarily by the parent. Temporary support may be part of the plan. It still needs systems, access, and people capable of supplying it.
The business boundary people negotiate commercially is often very different from the boundary that exists technically and operationally.
Someone needs to investigate that difference while there is still time to change the plan.
Before closing, these are planning questions, with time to act on the answers. After closing, the unresolved questions become operational problems that have to be worked out while both businesses are trying to keep running.
When this matters
What needs to be understood technically before buying or separating a business unit?
Execution, not consulting.
If you are looking for another strategy deck, Safyron is probably not the right fit. If you need someone who will still be there when the difficult work starts, read how Safyron operates.