You have signed the LOI on a carve-out, and the seller’s data room describes a business that does not exist on its own. Shared ERP instances, commingled customer records, IT contracts in the parent’s name, a sales team that logs into the parent’s CRM. The gap between what you underwrote and what you can actually operate on Day 1 is where a carve-out and divestiture consultant earns or destroys their fee. Buying that help badly costs you money twice: once in fees, and again in a stranded-cost tail or a missed separation date that pushes your first synecast off plan. This guide is for the operating partner or portfolio executive deciding whether to hire one, what to scope, and how to tell competent work from a slide deck.
The commercial question is narrow. You are not buying a project manager who tracks tasks. You are buying someone who can hold a separation plan against your investment thesis and tell you which dependencies threaten value and which are noise.
1. Decide what problem you are actually buying help for
Before you shortlist anyone, name the separation you are managing. A carve-out from a strategic parent with deep shared systems is a different job than a divestiture where the target already runs semi-standalone. The scope of divestiture technology separation work depends on how entangled the entity is, and you cannot judge a proposal until you can describe that entanglement in your own words.
Write down three things: the entities and systems that are shared today, the transition services agreement (TSA) you expect to negotiate, and the date by which you need to be standalone. Everything a good consultant proposes should trace back to one of those three. If a workstream in their plan does not map to a shared dependency or a TSA exit milestone, ask why it is there.
Bain’s annual Global Private Equity Report has tracked how separation complexity and holding periods interact, and the practical lesson holds: the separation you scope loosely at signing becomes the cost you cannot control at exit.
2. Separate the two jobs most firms sell as one
Carve-out and divestiture consulting usually bundles two distinct capabilities, and buyers overpay when they cannot tell them apart. The first is separation strategy and program governance, the office that owns the plan, the risk register, and the reporting into your board. The second is functional execution, the people who actually stand up finance, IT, HR, and commercial systems on the new entity.
A firm that is strong at governance and weak at execution gives you a beautiful integration management office and a hollow delivery bench. The reverse gives you competent engineers with no one holding the cross-functional dependencies. Ask which capability sits on the proposed team, by name, and what the other half costs.
Where the CRM and revenue stack sits
For a revenue-stack owner, the commercial systems workstream is where separation gets real. If the sales team lives in the parent’s CRM, you need customer records, pipeline history, and integrations rebuilt on your own instance before the TSA on that system expires. The mechanics of CRM and ERP integration after a deal usually become the longest-pole item for the go-to-market function, because these systems hold the customer relationships and pipeline history the revenue forecast depends on.
3. Judge the diligence work before you judge the plan
A consultant who arrives with a separation plan but no independent read on the technical estate is guessing. The separation plan is only as good as the technology due diligence underneath it. Ask what they verified against the actual environment versus what they took from the seller’s representations.
Good carve-out technology due diligence produces an inventory you can act on: which systems are shared, which licenses transfer and which do not, which integrations break when the parent cuts access, and what each dependency costs to replicate. McKinsey’s and BCG’s separation research both point the same direction, that stranded costs and underscoped IT are the recurring reasons carve-outs miss their value case. You can read the underlying framing in McKinsey’s private capital research and BCG’s principal investors practice.
4. Test how they handle the TSA, not just Day 1
Day 1 readiness gets the attention because it is a visible date. The TSA is where money leaks for the next twelve to twenty-four months. A consultant who treats the TSA as a legal artifact rather than an operating and cost problem will hand you a signed agreement and a stranded-cost surprise.
Ask how they price and sequence TSA exit. The relationship between buying and judging TSA management and the separation plan is direct: every service you take from the parent has a cost, an exit date, and a migration that has to be built and tested before that date. Someone has to own the schedule that gets you off the TSA on time, and it should not be you discovering the slippage at a board meeting.
The stranded-cost question to ask in the first meeting
Ask a candidate firm to walk through a shared service, say IT support or payroll, from Day 1 to full independence. If they cannot name the exit date, the interim cost, the replacement, and who signs off that the replacement works, they are selling governance without delivery. The Harvard Law School Forum on Corporate Governance has published useful practitioner material on separation and TSA structuring, worth reading before you negotiate; see the corporate governance forum.
5. Score the people, the plan, and the reporting line
Three things separate a consultant who delivers from one who bills. Judge each explicitly. First, look at the named delivery team. Ask for the functional leads by name and their prior carve-outs, because a strong IT separation lead is worth more than a partner’s logo. Second, check whether the separation plan references the value case you are underwriting; if it reads the same as any other deal, it was not built for yours. Third, confirm the reporting line into your governance: you need weekly actual-versus-plan on milestones, cost, and risk, in a format your board already reads, because reporting that only appears when something is already late is not reporting.
This is also where Day 1 readiness and separation planning connect to the broader first 100 days plan. The separation is a subset of the operating plan, not a parallel project, and the reporting should reflect that.
6. Match the engagement to the deal, not the fee
A single-carve-out from a strategic parent, a divestiture of a semi-standalone unit, and a serial roll-up integration program need different structures. The first wants a fixed-scope separation office. The last wants a repeatable playbook you can run across add-ons without re-buying the setup each time.
The broader market context matters when you negotiate. PitchBook and S&P Global track deal volume and holding periods, and Preqin and Private Equity International cover the fundraising and exit pressure that shapes how fast you need to be standalone. Scan PitchBook, S&P Global Market Intelligence, Preqin, and Private Equity International for where separation timelines are tightening. Harvard Business Review’s M&A coverage is a useful check on the integration failure modes that recur across deals.
7. A checklist before you sign the engagement
Run every candidate through the same list. If a firm cannot answer these in the first two meetings, you are buying a deck.
- Can they describe your specific entanglement (shared systems, entities, contracts) back to you, in their words?
- Does every workstream in their plan trace to a shared dependency or a TSA exit milestone?
- Did they verify the technical estate independently, or repeat the seller’s representations?
- For each shared service, can they name the exit date, interim cost, replacement, and sign-off owner?
- Who are the named delivery leads, and what carve-outs have they actually run?
- Does the separation plan reference your value case, or is it generic?
- What does their weekly actual-versus-plan reporting look like, and does it fit your board format?
- Is the commercial systems workstream (CRM, ERP, pipeline data) scoped as a long-pole item or an afterthought?
For the standalone entity’s separation dependencies, the divestiture IT scope in a private-equity context is worth reviewing alongside this list, because IT tends to be both the most entangled function and the one most often underscoped at signing.
The engagement is a means to an enterprise-value outcome: a clean standalone business, a controlled TSA cost tail, and a separation date that holds against the operating plan. Judge every proposal against those, not against the fee. If you want a delivery team that owns the separation plan and reports actual-versus-plan into your governance, review the DevriX private equity practice and its M&A separation and PMI sprint work.