In many companies, planning is not a document but a person. Someone knows which customer was difficult last week, which employee cannot work next to whom, which machine runs slower after maintenance, and which supplier delivers on time and which does not. That knowledge is not written down anywhere because it is used daily and therefore has never been recorded. For day-to-day operations, that works fine. For a buyer, it is a problem: there is no planning for sale, only a person who happens to have to be sold along with it.
Planning has usually grown, not been designed. In the early years, one person was needed to keep an overview, and that person kept getting better as the company grew. Systems were sometimes introduced, but as a tool alongside the head, not as a replacement for it. Exceptions, preferences and tricks remained undocumented, because the person who knew them was there every day. No one had a reason to write it down, until the moment a buyer asks what happens if that person is unavailable for a month.
A buyer does not value the planning as it currently runs, but what remains working once the current planner is no longer there. If the answer is "we don't know," that risk is factored into the price or into the terms of the transfer. This directly affects the owner dependence index: the more planning decisions rest with one person, the greater the correction a buyer applies, even if the rest of the company is in good shape. What succession readiness means for the price shows how that correction works in practice.
Planning consists of a series of decisions, and not every decision carries the same weight. Part of it is regular: who is available when, which order is logical, which combination has already worked well a hundred times. That part can already be captured and executed today by a system with AI, provided the rules have at some point been written down or can be derived from historical data. Another part still requires oversight: an exception that deviates from the pattern, a conflict between two regular customers, a decision that needs a reason the system can present but cannot decide on its own. A third part remains human work, especially where it concerns de-escalating an angry customer or assessing a new employee who does not yet have a track record.
The ratio between these three categories differs greatly per company, and that difference does not lie in the sector but in what has ever been recorded. A company where planning rules, exceptions and preferences are already in a system can have a large part of the regular work taken over and retain oversight for the rest. A company where that only exists in the planner's head must first take that step before AI can take over anything. This is not a matter of planning better or worse, but of what was ever written down and what was not.
The planner who currently knows everything is not the problem but the source of the solution. Making it transferable starts with recording what that person already does: which rules he applies, which exceptions recur, which trade-offs he makes and why. This is not a replacement of his role but a translation of his knowledge into something a system can support and a successor can read. Where AI subsequently takes over the regular work, there remains room for the planner to assess the exceptions, which tends to deepen the significance of his function rather than diminish its importance.
This approach also affects other parts of the company. Planning is often connected with how customer relationships are made transferable, because customer preferences and planning rules often sit in the same heads, and with how supplier relationships are made transferable, because delivery times and planning affect each other. The decision-making around it is also relevant: how decision-making is made transferable describes how similar dependencies arise outside of planning.
If this topic touches on personnel decisions, such as a change in tasks or staffing, separate legal requirements apply that are not covered here.
A transferable planning is more than software. Contracts with customers and suppliers must transfer along with a sale, and agreements that are currently verbal or implicit must be put in writing. Which legal matters need to be in order for a sale is described on the page which legal matters need to be in order for a sale, and is a logical next step once the planning itself has been recorded.
The question of which part of the planning in this specific company can be taken over by AI, which part still requires oversight, and which part remains human work, is answered per task with the work scan from FTE TO AI. If you would first like to know where planning and the other drivers currently stand, the free value check with eight short questions, one per driver, gives you a picture of which driver is weighing most heavily on your price today. The full value scan, with maturity scores per driver and a two-year calendar toward the exit moment, is under construction.