The signed carve-out on your desk gives you a target close, a transition services agreement (TSA) with a clock on it, and a diligence file that describes the parent. The target business frequently diverges from what diligence captured, because shared services, allocated costs, and entangled IT were described as they sat inside the parent rather than as they will cost once separated. That gap is where carve-out consulting private equity engagements earn or waste their fee. You are the operating partner or portfolio executive who has to decide, before Day 1, which parts of separation you run internally, which you buy, and how you will know within the first month whether the money is working. Get that decision wrong and you carry avoidable TSA cost, miss the separation milestones your lenders assumed in the model, and enter your first board meeting explaining a slip instead of reporting a plan.
This is a buyer’s guide to that decision, written for someone with budget and a deadline, not someone learning the mechanics.
1. Decide what the consultant is actually accountable for
The word “carve-out” covers three jobs that are frequently sold as one: separating the business from the parent’s systems and contracts, standing up the standalone entity, and exiting the TSA on or ahead of schedule. A firm that is strong at the first is not automatically strong at the third, and the contract you sign should name which one owns the milestone dates in your model.
Before you brief anyone, write down the outcome you are buying in financial terms. Bain’s annual private equity report, BCG’s principal investors research, and McKinsey’s private capital work have all tracked how compressed holding periods force operational timelines forward, which means every month of separation delay adds direct TSA cost, defers margin improvement, and shortens the runway to exit. Tie the engagement to a dated separation plan, a TSA exit schedule, and a run-rate cost the buyer inherits at exit, not to a deck of activities.
If your separation is technology-heavy, the accountability question sharpens further. The people judging an IT separation consultant on a carve-out should be looking for someone who owns cutover dates, not someone who documents them.
2. Build the baseline the seller’s diligence did not give you
Most carve-out diligence describes the target inside the parent’s shared services. It rarely tells you what the standalone cost base looks like once shared IT, procurement, and back office are priced at market. That baseline is the number your value-creation plan depends on, and it is the number a good consultant produces first.
Ask for a standalone cost model that separates one-time separation spend from recurring standalone operating cost, and reconcile it against the TSA schedule of services. McKinsey’s private capital research, BCG’s principal investors work, and Deloitte’s carve-out practice guides all point to entangled operating models as the recurring source of carve-out overrun, so the consultant who cannot produce this baseline in the first two weeks is the wrong choice.
This baseline is also where technology due diligence pays back. If the diligence found application sprawl, shared licenses, or data that lives in the parent’s warehouse, that finding becomes a line item and a date in the separation plan rather than a surprise in month three. For deals where the target was never technically separate, read the specifics of carve-out technology due diligence before you scope the work.
3. Judge the firm on the TSA, not the pitch
The TSA is where carve-out engagements are won or lost, because every service the parent provides during transition carries a cost, a term, and an exit condition. A consultant who treats the TSA as a legal document rather than a project plan will let it run long, and long TSAs are pure margin drag on the entity you are trying to sell later.
Test any firm on how it manages the schedule of services, the exit criteria per service, and the dependencies between exits. The detail of what to look for is covered in how to buy and judge a TSA management consultant in an M&A carve-out, and the execution discipline once you are running it is in how to run TSA exit on schedule when you are the buyer.
What a credible TSA answer sounds like
- A dated exit plan per service, not a single “TSA ends” date.
- Named owners on both the buyer and seller side for each exit dependency.
- A cost curve showing TSA spend declining as services exit, so finance can forecast it.
- A stub-cost estimate for services the buyer will replicate versus retire.
4. Separate the two-stage decision on technology and data
Technology separation is where the largest hidden costs sit, because the parent’s ERP, CRM, and identity systems were never designed to split. The buyer decision is whether to stand up a clean environment on Day 1 or run on TSA and migrate later, and that decision changes the fee, the risk, and the TSA length.
For the revenue stack specifically, the split between the parent’s CRM and the entity’s future system is rarely trivial. Customer records, pipeline history, and integrations to billing all have to move without breaking the sales motion, which is why CRM and ERP integration post merger is worth scoping as its own workstream rather than folding it into general IT.
When the technology separation is the deal-defining risk, judge the provider the way you would judge any divestiture technology separation consultant, on cutover evidence and rollback plans, and read the wider view in divestiture IT consulting in private equity.
5. Set the Day 1 and first-100-days line clearly
Day 1 readiness and the first hundred days are different scopes with different owners, and buyers routinely conflate them. Day 1 is a binary: the entity can invoice, pay, run payroll, keep the lights on, and serve customers without the parent noticing a break. The Day 1 readiness consultant you hire should be judged on a tested readiness checklist that proves every system works before the date arrives.
What comes after Day 1 is the value-creation work your thesis actually rests on, and it belongs in a structured first 100 days plan with owners, dependencies, and a risk register the board can read. If the carve-out is one of several assets you are combining, the integration office discipline in merger integration management office services and the platform view in roll-up integration services apply directly.
6. Price the engagement against enterprise value, not day rates
Day rates tell you what a firm costs. The right frame is what the engagement protects or creates: TSA cost avoided by exiting on schedule, one-time separation spend kept inside the model, and the run-rate cost base the next buyer will underwrite at exit.
PitchBook and Preqin data on holding periods and exit conditions, S&P Global Market Intelligence coverage of deal activity, and Harvard Law School Forum on Corporate Governance publications on separation risk all reinforce that a clean standalone with a documented separation is easier to sell and finance. Harvard Business Review’s M&A research documents how separation risk surfaces in diligence at the next transaction, which is where a rushed carve-out gets repriced. Fee discussions that ignore this are arguing about the wrong number.
7. A buyer’s checklist before you sign
- The engagement names an owner for the milestone dates in your model and for each of the workstreams that feeds them.
- A standalone cost baseline separating one-time from recurring cost lands inside the first two weeks.
- The TSA has a dated exit plan per service with named owners on both sides.
- The technology and data separation is scoped as its own workstream with a Day 1 versus migrate-later decision made explicitly.
- Day 1 readiness is a tested checklist; the first 100 days is a separate plan with a risk register.
- The fee is argued against TSA cost avoided and exit-ready run-rate, measured in dollars per month of dependency eliminated.
- There is a single integration management structure if this is one of several assets.
If most of these are missing from the proposal in front of you, you are buying activity and hoping it adds up to a separated business. The AICPA & CIMA guidance on carve-out financial statements, the U.S. Securities and Exchange Commission’s requirements for standalone reporting, and EY’s and PwC’s technical separation guides are all useful reminders that “separated” has a specific, auditable meaning, and your consultant should be building toward it from the first week.
Scope the IT carve-out advisory separately from the integration it enables
An IT separation and a post-merger integration are two engagements with different owners, different end states, and different clocks, and buyers who scope them as one line usually end up paying a separation firm to document work it was never going to execute. The separation advisory owns disentangling the target from the parent’s systems, licenses, and shared infrastructure so the standalone entity can run without the TSA. The integration work only begins once that standalone entity exists and you are folding it into a platform or another portfolio company.
Decide which one you are actually buying before you brief anyone, because the firms that are strong at exiting a TSA on schedule are rarely the same firms that run a clean platform integration, and the contract that names cutover dates is not the contract that names the target operating model after close.
What an IT carve-out advisory should own
Ask the firm to own the cutover dates for each entangled system, the application inventory the seller’s diligence left inside the parent, and the run-rate cost of the standalone IT estate the buyer inherits at exit. A firm that will only produce a separation plan and a RACI chart is documenting the work, and you will still need an owner for the dates your lenders assumed in the model.
When the integration should wait
If the thesis is a buy-and-build, the temptation is to start integration before separation is finished, which stacks two sets of migrations on the same team and the same quarter. Run the separation to a stable standalone first, then integrate, unless the TSA cost of staying separate for that interval exceeds the risk of running both at once. That is a cash calculation the operating partner should make deliberately, not a sequencing default the consultant chooses for you.
When the carve-out is the value-creation event and the clock is already running, route the separation and integration work to a team that manages it as a private equity operating problem with dated milestones and board-ready reporting. Take the carve-out execution scope to the DevriX PE team to pressure-test your Day 1 plan and TSA exit schedule against the dates in your model.