Fig. 01 · Decision guide
Carve-Out vs. Full Acquisition: Technology Integration
A decision guide for choosing carve-out, full acquisition, or phased TSA structure when technology systems, teams, and customer operations must separate cleanly.
A carve-out is not a smaller acquisition. It is a separation program with a transaction attached. The integration risk is highest when the target looks independent in the model but depends on the parent for systems, data, finance, support, security, HR, or customer operations.
The core decision is whether the buyer is acquiring a standalone operating system or extracting value from a larger one.
The separation test
If the target can run independently on Day 1 with clear ownership of customers, people, systems, data, contracts, and finance, a full acquisition may be cleaner. If the target depends materially on the seller’s shared services, a carve-out or phased TSA is usually the honest answer.
What delays EBITDA capture
The model usually misses delay from user provisioning, data migration, ERP and CRM separation, cybersecurity baseline work, vendor novation, finance reporting, and unclear operating ownership.
Those are not back-office details. They decide whether the deal captures synergy in the first two quarters or spends the first two quarters building the ability to operate.
Operator rule
Do not underwrite a carve-out as if it were a normal integration. Treat every shared dependency as a draw on time, cash, and leadership attention.
How the call gets made
Inventory shared dependencies
Map systems, data, people, contracts, vendors, processes, and customer operations that the target does not control independently.
Classify dependencies by Day 1 risk
Separate dependencies that must be live on Day 1 from dependencies that can transition over the first 100 days.
Price separation work
Convert migration, security, data, licensing, and staffing work into budget, timeline, value-at-risk, and synergy delay.
Set TSA exit gates
Define the operational requirements for exiting each transition service: system cutover, data validation, support ownership, and user adoption.
Govern integration as value capture
Run integration around retained customers, retained staff, retired systems, clean data, and recognized EBITDA, not activity reports.
Questions the board asks
What makes a carve-out risky in technology companies?
The value may sit inside shared systems, shared data, shared support teams, or parent-company processes. If those dependencies are not mapped before close, the buyer inherits delay.
When should a buyer prefer a full acquisition?
A full acquisition fits when the business can transfer as a coherent operating system and inherited risk can be priced or remediated.
How should a TSA be scoped?
A TSA should list each service, owner, service level, exit criterion, cost, extension penalty, and escalation path. Without exit gates, it becomes a recurring tax.
Decision guide · Human Renaissance · First published 2026-04-29 · Research methodology
