A carve-out needs someone who has stood up a finance function before, and later someone who will run it for five years. Those are rarely the same person. Hiring permanently on day one means selecting against a business that does not exist yet.
Who runs a carve-out on day one?
Someone who has stood up the function before. On day one the job is exiting the transitional services agreement, standing up systems, and getting to a first standalone close — a project with a defined end rather than a management role.
That work rewards pattern recognition over relationship building. Someone who has done three carve-outs knows which dependency will be discovered late, and that knowledge is worth more in the first six months than anything a permanent hire brings, whatever the day-rate comparison suggests.
| Interim on day one | Permanent from day one | |
|---|---|---|
| Best at | Standing up functions, TSA exit, stabilizing | Building a team and a three-year plan |
| Speed to start | Weeks | Months, plus notice period |
| Risk | Institutional memory leaves with them | Hired against a business that does not exist yet |
Why are the two hires different?
Because the businesses are different. The company at close is a set of dependencies on a former parent; the company at year three is a standalone operation with its own team and plan. Selecting for the second while running the first is how both get done badly.
There is also a candidate-supply argument. The people who are good at standing up functions frequently do not want the permanent role, and hiring them into it produces a departure at month eighteen.
How should you sequence them?
Interim through TSA exit and the first standalone close, then permanent. The permanent specification becomes writable once the shape of the standalone business is known, which is precisely what the interim period establishes — and what a first-hundred-days plan should be built to discover.
The sequencing also gives the permanent search something to recruit against. "Run this function" attracts a different candidate from "take this function, which now works, and grow it".
The interim's own view is worth taking on the permanent specification, since they will have spent months discovering what the role actually requires. It is the cheapest input available to that hire and it is frequently not asked for, because by then the search is already running.
What goes wrong with each?
With interim, institutional memory leaves when they do. Decisions get made, rationales do not get written down, and the permanent hire inherits a working function they cannot explain.
With a day-one permanent hire, the risk is a mismatch discovered at month twelve, by which point the person has hired a team around themselves and the correction is expensive — an outcome a sponsor pays for twice.
How should the handover work?
With overlap, and with the interim's decisions written down and rationalized. A handover meeting is not a handover; the permanent hire needs to know why things were done, not only what was done.
Documentation should be a named deliverable in the interim engagement rather than a courtesy at the end. Engagements that treat it as the latter reliably produce nothing usable.
The handover also has to include the things that were decided provisionally. Carve-outs generate a large number of temporary arrangements — a workaround for a system that was not migrated, a manual process standing in for an automated one — and each carries an expiry the permanent hire needs to know about. A list of those, with dates, is worth more than a narrative account of the period.