Carve-outs fail in the window between the separation blueprint and its execution, so carve-out consulting needs people who stay to do the work: migrate systems and data, stabilize operations through cutover and manage the parent through a shrinking TSA. A firm that delivers the roadmap and leaves hands the portfolio company work it has never done, on a deadline it did not negotiate.
Picture a PE firm that closes a carve-out with a 12-month TSA and, 18 months later, is still paying the parent for stranded IT. The carve-out consulting firm delivers the separation blueprint, maps the dependencies and leaves, and nobody inside the portfolio company has the technical capacity to migrate the infrastructure, renegotiate the data licensing or stabilize the customer portal after cutover. The thesis assumed operational independence by month 14; the result is a bloated cost base, delayed integration work and a CFO explaining to the investment committee why EBITDA is below the model.
Carve-outs fail in the window between diagnosis and execution. Most carve-out consulting engagements deliver analysis, separation roadmaps, and a list of dependencies. The firm exits before the hardest work begins: standing up independent systems, migrating data under time pressure, stabilizing operations during cutover, and managing the parent relationship through a shrinking TSA. The portfolio company is left holding a roadmap it cannot execute and a ticking clock it cannot stop.
Carve-out consulting that ends at the blueprint stage does not create enterprise value. It creates a handoff problem.
The structural problem with roadmap-only carve-out consulting
Most carve-out advisory follows a predictable arc. The consulting firm arrives during diligence or shortly after close, performs a separation assessment, maps dependencies, estimates costs, sequences workstreams, and delivers a 60-page roadmap. The engagement ends. The operating team is now responsible for executing work they have never done, under a TSA deadline they did not negotiate, with internal resources already stretched across integration, growth initiatives, and day-to-day operations.
The roadmap does not tell the CTO how to migrate a customer database off the parent’s Oracle instance when the parent controls the schema and the TSA renewal is €18,000 per month. It does not tell the CFO how to reconcile intercompany AR when the parent’s ERP export format changed mid-quarter and finance has three people. It does not tell the VP of Engineering how to replace a shared authentication service when half the development team is contractors who were not part of the deal and left in month two.
A separation plan is not the same as separation capacity. One is a document. The other is people, tools, and execution hours applied to the work described in the document, under time pressure, with real consequences for missing a milestone. The difference between the two is the difference between a deal that hits the value-creation plan and one that burns six months explaining why it did not.
What embedded capacity means in a carve-out context
Embedded capacity is technical and operational resource applied continuously during the separation window, accountable to milestones, integrated into the portfolio company’s operating rhythm, and measured on delivery rather than documentation. It is not a consulting firm that flies in quarterly to review progress. It is engineering, data, infrastructure, and RevOps capacity deployed inside the business, reporting to the operating partner or the portfolio company CFO, working alongside the internal team, and responsible for completing the separation work before the TSA expires.
In practice, embedded capacity during a carve-out covers:
- Migrating customer, product, and transaction data off parent systems before the TSA cutoff, including schema translation, historical reconciliation, and QA under live-transaction conditions.
- Standing up independent infrastructure for authentication, payments, reporting, and customer-facing applications where shared services agreements are ending.
- Rebuilding integrations that connected the carved-out entity to parent platforms, HubSpot to a new CRM instance, payment gateways to new merchant accounts, analytics pipelines to independent warehouses.
- Stabilizing customer-facing operations during cutover, monitoring uptime, patching failures in real time, and managing the communication layer so customers do not experience the separation as service degradation.
- Managing the parent relationship through TSA renewal negotiations, usage tracking, dispute resolution, and the final exit when the agreement terminates.
This is not advisory work. It is execution work that requires people with deployment access, working credentials, and the technical skill to make changes under time pressure without breaking production systems. A roadmap cannot do any of it.
Why TSA windows compress execution risk
A TSA is a forcing function. It creates a fixed window during which the carved-out entity must achieve operational independence or continue paying for services it no longer controls at rates it cannot negotiate. Most TSAs are structured as 12- or 18-month agreements with renewal penalties that escalate, 110% of the original rate in year two, 125% in year three. The economic logic is clear: the parent wants separation risk off its books and the buyer accepted the timeline during diligence.
The operational reality is harder. Twelve months sounds like enough time until month four, when the team discovers that the parent’s IT group has deprioritized carve-out requests, the data export they were promised is incomplete, and the shared service agreement for payment processing has a six-month termination notice no one flagged during diligence. By month eight, the portfolio company is negotiating a six-month extension at 115% of the original cost, explaining to the investment committee why separation is behind schedule, and delaying the next phase of the integration plan because engineering capacity is still tied up finishing the carve-out.
TSA deadlines do not move. The parent has its own priorities. The fund has a value-creation plan tied to a specific exit timeline. The portfolio company has limited technical capacity and competing demands from growth initiatives, product development, and customer commitments. Carve-out work that was supposed to be complete by month 12 is now consuming resources in month 18, and the opportunity cost is measurable: delayed pricing optimization, slower go-to-market execution, weaker SaaS metrics, and a portco CEO explaining to the operating partner why EBITDA growth is running 90 days behind model.
Embedded capacity solves this by removing the execution bottleneck. The work gets done on the timeline the deal requires, not on the timeline the internal team can manage between everything else they are responsible for.
The operational handoff problem no one plans for
Carve-outs create a second structural problem that most consulting engagements ignore: who owns the separated systems after the consulting firm leaves? The answer is usually the portfolio company’s IT or engineering team, a group that did not design the new architecture, was not involved in the migration, and is now responsible for maintaining infrastructure they inherited mid-project with incomplete documentation.
This handoff problem shows up as operational drag. The customer portal has intermittent timeouts and no one knows whether the issue is DNS propagation, a misconfigured load balancer, or something the consulting firm changed during cutover. The finance team cannot reconcile Q3 revenue because the intercompany allocations in the old ERP do not match the new chart of accounts and the consultant who mapped them is no longer on the project. The marketing automation platform is sending emails to the wrong segment because the HubSpot migration did not preserve list logic and no one documented the original rules.
Each of these problems is solvable. Each requires someone with context, access, and time to investigate, diagnose, and fix it. When the separation consulting engagement ends before those problems surface, the portfolio company’s internal team is debugging work they did not do, under pressure from a business that expects systems to work, with no institutional memory of why decisions were made during the carve-out.
Embedded capacity that stays through stabilization prevents this. The team that executes the separation is the same team that stabilizes it, documents it, and hands it off to internal operations with training, runbooks, and a working escalation path. The handoff is a managed transition, not an emergency.
Why most PE firms still separate advisory from execution
The standard model in private equity carve-out work separates strategy from execution. A consulting firm handles the separation assessment and roadmap. The portfolio company’s internal team, or a systems integrator hired separately, handles the build and migration work. An IT staff aug firm provides supplemental capacity if the internal team is underwater. Three vendors, three contracts, three handoffs, and no single party accountable for whether the carved-out business is operationally independent when the TSA expires.
This model exists because it mirrors how PE firms historically approached value creation: diagnose with consultants, execute with management, and escalate only when something breaks. It worked when value creation meant cost cuts and when carve-outs were simpler, fewer dependencies, less technical debt, more manual processes that could be replicated without migration risk.
It does not work now. Modern carve-outs separate entities with SaaS stacks, APIs, shared authentication services, cloud infrastructure, customer data warehouses, and integrations that span CRM, ERP, payments, support, marketing automation, and analytics. The separation roadmap is no longer a question of which invoices to split. It is a question of which systems to rebuild, which data to migrate, which integrations to replicate, and how to do all of it under a TSA deadline without destabilizing the business.
PE firms that continue separating advisory from execution pay for it in extended TSAs, delayed EBITDA ramps, and portfolio companies that cannot move to the next phase of the plan because they are still finishing the last one. The firms that treat carve-out execution as a single workstream with embedded accountability see faster separation, cleaner handoffs, and operating teams that can focus on growth instead of firefighting legacy dependencies.
What embedded carve-out capacity looks like in practice
A $240M carve-out in the healthcare SaaS space illustrates the model. The PE firm acquired the division from a Fortune 500 parent with a 15-month TSA covering payments, customer data, authentication, and reporting infrastructure. The initial separation assessment flagged 47 dependencies and estimated eight months to achieve operational independence.
Rather than hire a consulting firm to deliver the roadmap and then hire a separate implementation partner, the operating partner brought in an embedded technical team at close. The team included infrastructure engineers, a data architect, a RevOps specialist, and a project lead who reported directly to the portfolio company’s CFO. The engagement was structured as a 12-month retainer with milestone-based deliverables tied to TSA exit and three months of post-separation stabilization included.
By month six, the team had migrated the customer database, rebuilt the payment gateway integration, stood up independent authentication, and consolidated reporting into a new data warehouse. By month ten, the carved-out business was operationally independent. The TSA was terminated two months early, saving $67,000 in extension fees. The CFO had clean financials for the first board meeting post-separation. The CTO had working systems, documentation, and a trained internal team ready to take over operations.
The operating partner did not have to explain to the investment committee why separation was behind schedule. The portfolio CEO did not have to choose between finishing the carve-out and launching the pricing initiative that was part of the value-creation plan. The deal moved to the next phase on time because the carve-out execution was treated as a single accountable workstream, not a consultant-to-operator handoff.
Why this model works for portfolio-company operators
Portfolio-company operators inherit the consequences of every separation decision. If the TSA extends, they pay for it. If the data migration fails, they explain it to customers. If the cutover destabilizes the business, they manage the fallout. A carve-out consulting model that treats execution as someone else’s problem leaves the operator holding all the risk.
Embedded capacity shifts accountability. The team executing the separation is measured on whether the business achieves operational independence on the timeline the deal requires. That team works inside the portfolio company, integrated into the operating rhythm, reporting to the CFO or CTO, and responsible for delivery rather than advice. The operator has a single point of accountability for separation work, a clear escalation path when problems surface, and confidence that if a milestone slips, the embedded team owns the recovery plan.
This matters for three reasons. First, the operator’s internal team can stay focused on running the business rather than executing a separation plan they did not design. Second, when the separation work is complete, the operator has systems that work, documentation that reflects reality, and a trained team ready to maintain them. Third, the operator can make the case to the investment committee that the carve-out is complete, the TSA is terminated, and the next phase of the value-creation plan can begin.
A portfolio-company CFO evaluating carve-out support should ask one question: who is accountable if we are not operationally independent when the TSA expires? If the answer is a roadmap, a handoff, or a vendor the operator has to manage, the model is broken. If the answer is an embedded team with skin in the game, that is what execution looks like.
Conclusion
Carve-out consulting that ends at the roadmap creates a handoff problem. The portfolio company is left with a separation plan, a TSA deadline, and no one accountable for whether the work gets done on time. TSA extensions, delayed integrations, and portco operators explaining to the IC why EBITDA is behind schedule are the predictable result.
Embedded capacity solves this by treating separation as a single workstream: one team, one accountability model, and delivery measured on operational independence rather than documentation. The team that diagnoses the dependencies is the same team that migrates the data, rebuilds the infrastructure, stabilizes the cutover, and hands off working systems to the internal team. The operator has confidence that the carve-out will not stall the value-creation plan. The investment committee has confidence that the deal will hit its milestones.
A carve-out consulting engagement that leaves before the TSA expires is not a consulting engagement. It is a diagnostic service with an execution gap. Closing that gap is the difference between a separation that delivers on the deal thesis and one that explains why it did not.
If your portfolio company is entering a carve-out or divestiture and you need embedded technical capacity to execute the separation plan, not just document it, senior operators in the CEO Hangout network have managed these transitions before. Marketing and RevOps leaders can also provide insight into customer-facing stabilization during cutover. For technical execution that delivers operational independence on the timeline your deal requires, reach out directly.
Where Embedded Capacity Pays for Itself
The cost case for embedded capacity is straightforward. A TSA extension on IT services for a $100M portfolio company typically costs $50,000 to $150,000 per month, depending on the scope of shared infrastructure. A three-month extension, which is common when separation work stalls, costs $150,000 to $450,000. A six-month extension can approach $900,000. That is OpEx the deal model did not price in, coming directly out of forecast EBITDA.
Embedded separation capacity for a carve-out of this scale typically costs $30,000 to $60,000 per month, fully loaded. The team executes data migration, rebuilds infrastructure, manages vendor transitions, stabilizes cutover, and delivers operational independence on the original TSA timeline. If that engagement prevents one three-month TSA extension, it pays for itself. If it prevents two extensions or avoids a failed cutover that destabilizes revenue, the ROI is 3-5x.
The second cost is harder to quantify but larger: delayed integration. A carve-out that does not reach operational independence blocks the next phase of the value-creation plan. The portco cannot consolidate onto a shared ERP, migrate to a unified CRM, or begin cross-selling into the acquired customer base until separation is complete. Every quarter the separation drags, the deal thesis sits on hold. The investment committee sees a forecast that assumes integration synergies are flowing by Month 9. The CFO sees a TSA that is still running at Month 14. Embedded capacity closes that gap.
The third cost is credibility. When a portfolio company misses separation milestones, the IC questions whether the operator can execute the rest of the plan. A single failed carve-out does not kill a fund, but it signals execution risk across the portfolio. Operators who deliver clean separations on time build trust with the deal team. Operators who extend TSAs and blame consultants lose it.
What to Measure
A carve-out engagement should report against three milestones: separation readiness, cutover completion, and operational independence. Separation readiness means the portco has rebuilt every dependency the TSA covered, data migration is complete, and the new infrastructure is tested and stable. Cutover completion means the parent systems are disconnected, customer-facing operations are stable, and no unplanned rollbacks occurred. Operational independence means the TSA is terminated, the internal team can maintain the new systems without vendor support, and the business is ready for the next phase of integration.
Those three milestones matter more than any intermediate deliverable. Weekly reports, cutover runbooks, and dependency maps are artifacts of the work, not measures of success. The only measure that matters is whether the portfolio company achieved operational independence on the timeline the deal required. If the answer is yes, the engagement succeeded. If the answer is no, it did not.
Operators evaluating carve-out support should set the success condition before the engagement begins: operational independence by a specific date, no TSA extensions, and the value-creation plan back on track. Any consulting model that cannot commit to that outcome is selling documentation, not execution.
The Execution Model That Works
The consulting approach that delivers clean carve-outs is not complicated. The team embeds with the portfolio company’s internal operations, reports to the CFO or COO, and owns specific separation workstreams end-to-end. That means data migration, infrastructure rebuild, vendor negotiation, cutover sequencing, and post-cutover stabilization. The engagement runs from TSA signature through operational independence, typically six to twelve months depending on the complexity of the shared systems.
This is how DevriX staffs separation and integration work: embedded, reporting to the CFO or COO, against those three milestones.
The model differs from strategy consulting in three ways. First, the team is accountable for execution, not recommendations. A strategy firm delivers a separation playbook and hands it to the internal team. An embedded team builds the infrastructure, migrates the data, and manages the cutover. Second, the team operates inside the budget and timeline the deal partner approved. If the separation requires additional spend, the embedded team surfaces that decision early, with alternatives and trade-offs, not three weeks before cutover. Third, the team stays through stabilization. Cutover is not the finish line. Operational independence is.
The CFO running the separation needs to know three things at any point: whether the timeline is holding, whether unplanned cost is coming, and whether any dependency will block cutover. An embedded team can answer all three because they are doing the work, not observing it. A consulting team that parachutes in for workshops cannot.
When to Engage
The right time to engage separation capacity is before the TSA is signed. Once the TSA is in place, the timeline is set. Waiting until Month 4 to start infrastructure work means the team is building separation capability while the TSA clock is running. Engaging during diligence or immediately post-close gives the separation team time to map dependencies, sequence the work, and identify long-lead vendor transitions before the timeline compresses.
Deal partners who treat separation as a post-close operating problem consistently miss this window. The separation plan should be part of the investment thesis, not an afterthought. If the deal model assumes the portco reaches operational independence in nine months, the separation workstream needs to start in Month 1, not Month 5.
Portfolio companies that engage late typically do so because an internal leader believed the work was manageable with existing staff. That assumption holds until the first major dependency surfaces, usually a shared ERP, a consolidated data warehouse, or a parent-controlled payment gateway. By the time the CFO realizes the internal team cannot execute the separation on schedule, the TSA extension is already priced into the revised forecast.
Operators who have managed one clean carve-out engage early. Operators managing their first carve-out engage late, extend the TSA, and remember the lesson for the next deal.
