Carve-outs: Standing Up Operations That Never Stood Alone

Rebuilding day-to-day operations has shaped how I look at a carve-out: work can belong to a business without everything needed to perform it belonging to that business. A buyer may be acquiring an operation whose payroll, reporting, purchasing, or customer administration still depends on the seller.

That distinction matters before the parties commit to a separation plan. I want to understand not only what changes hands, but what must be replaced, transferred, or temporarily supported for the business to operate independently. Otherwise, an agreed transaction boundary can leave an unresolved operating boundary.

Separate the work, not just the assets

I start with how work moves through the business. An asset list identifies what the parties intend to transfer. It doesn't, by itself, explain who approves a purchase, maintains a customer record, resolves a billing issue, or produces the information needed to manage cash.

For each essential process, I would map who performs the work, which systems and information it requires, and what authority makes it possible. Then I would identify which parts sit inside the business being sold and which remain elsewhere in the seller's organization.

The aim isn't to document every task equally. I would prioritize dependencies that could interrupt revenue, payments, customer service, or required reporting. Those dependencies deserve explicit decisions rather than assumptions that someone will keep handling them.

People and responsibilities don't always move together

A role on an organization chart isn't the same as the capacity to perform the work. I would distinguish employees dedicated to the operation from people who support it alongside other responsibilities.

For a buyer, that means identifying work that needs an owner even when no corresponding position transfers. For a seller, it means understanding what support remains necessary after employees or responsibilities move out of the retained business.

I would also separate knowledge from authority. Someone may know how a process works but lack the access or approval rights to carry it out after separation. A useful staffing plan therefore connects each responsibility to a person, the necessary permissions, and a way to handle exceptions. A list of transferring employees alone doesn't establish that connection.

Systems separation starts with business requirements

I wouldn't begin by choosing replacement software. First, I would establish what each side needs to keep doing and what information each side needs to retain or receive.

That creates a basis for reviewing access, records, licenses, reporting, and responsibility for maintaining information. Technical separation and permission to use a system or its data are different questions. I would bring qualified legal counsel and appropriate technical specialists into those reviews rather than treat operational preference as authorization.

Only then would I compare transferring a system, establishing a separate environment, or replacing the capability. The choice should follow the operating requirement — including the people and processes needed to use it — rather than the appeal of a fresh technology purchase.

Temporary support needs a defined destination

If the parties contemplate continued support from the seller, I would make the work explicit before treating that support as part of the separation plan.

The operating questions are concrete: what service is being provided, who requests it, who performs it, how costs are handled, and how problems get resolved. Equally important is the condition that allows the support to end.

I would connect each temporary service to a replacement capability and an accountable owner. Qualified transaction counsel should address the contractual terms. My operating concern is whether the buyer has a credible path away from the support and whether the seller understands the resources needed until then.

Price the independent operation, not the inherited arrangement

I would keep the cost of running the separated business distinct from the cost of separating it. Recurring staffing and system needs belong in one view; transfer work, setup, and temporary overlap belong in another.

Historical allocations are something I would examine, not automatically accept as the cost of standing alone. I would ask qualified financial and tax advisers to review the assumptions relevant to the transaction, while testing whether the operating plan actually includes the work that must be done.

For me, the decisive test is straightforward: every essential activity needs an owner, usable systems and information, and an understood cost. Where that isn't yet true, the separation plan needs to show the gap and the decision required. That's how I distinguish a defined carve-out from a business that is ready to stand alone.