Not every decision in the first hundred days carries the same weight. Some decisions can wait without anything being lost. Others cost money, people, or time for as long as they remain open — even when no one is watching. The distinction between those two categories is where an integration usually goes wrong: not because too few decisions are made, but because the ordering is missing.
A decision that stays open does not stand still. Customers who don't know which point of contact they'll be dealing with will find their own way around it. Employees who don't know whether their role will continue to exist will start job hunting before anything has been announced. Systems that aren't connected keep generating duplicate work until someone flips the switch. Uncertainty is not a neutral state waiting for attention — it works against the deal, every single day the decision is delayed.
So the question isn't only what needs to be decided, but what it costs to postpone that decision another week, another month. Those costs aren't equal across every part of the business. For your key people in the acquisition, the clock usually runs faster than for an IT migration that can wait behind the scenes. For customer contracts with a notice period, the clock runs differently than for internal reporting lines. Sorting by cost of uncertainty means: looking first at what is already deteriorating today, not at what feels biggest on paper.
The Day 1 and Day 100 generators in this tool put decisions in order based on dependencies and the consequences of delay. They make visible which dependencies are blocking the rest — a decision that doesn't seem urgent in itself, but is holding back three other decisions, deserves a different place in the planning than the order in which it arrived would suggest.
What the generator does not do is determine what carries weight for your organization. That is a choice that remains with the deal team or the operating partner. The tool lays the options side by side and shows what remains undecided if no choice is made; it does not choose on your behalf. And not every part is by definition meant to be integrated — sometimes the question isn't in what order something should happen, but whether it should happen at all. That question sits alongside every list, not as an afterthought.
An order set on day one has often already shifted by day thirty. A key person leaves, a system runs into delay, a customer asks a question no one anticipated. The cost of uncertainty is not a static figure you calculate once — it changes along with what happens in the organization, especially during the period in which people still don't know where they stand. That is precisely the phase in which people leave during the unclear months, often not because the decision was bad, but because it took too long to arrive.
Here, oversight means: someone who regularly returns to the list and checks whether the order still matches what is happening now, not what was assumed three months ago. The integration office is where that oversight lands — not as an extra layer of bureaucracy, but as the one place where benefit tracking, dependencies, and the decision list come together. Without that place, responsibility spreads across too many people, and precisely the overview needed to see which decision is most expensive to postpone today disappears. How you keep that office workable without it becoming a delaying factor itself is a question that deserves separate attention.
This is not a track record. There is no completed engagement this approach leans on, and that should not be suggested either. What exists: three generators that bring structure to the synergy baseline, Day 1 plan, and Day 100 plan, and an integration office that keeps benefit tracking, dependencies, and the decision list together. Structure, not proof of results. No percentage indicating how much faster you would be, no guarantee that the order the generator proposes is the right one for your situation.
Even when the Day 100 plan is not achieved — and that happens more often than the day-one planning predicts — there is a question that must then be asked, and that question should not be forgotten under the pressure of the next deadline.
The generators and the integration office as described here are not yet fully available. Anyone wanting to work with this can sign up for the waiting list; what is ready will be shared once it is ready, not before.
An ordering of decisions says something about what needs to happen and when. It says nothing yet about who carries out that work and whether that work should by definition rest with a human being. For the tasks that surface from a Day 1 or Day 100 plan, that is a separate question: which part of it is repetitive enough, or data-processing enough, to leave to AI. The work scan from FTE TO AI calculates per task which part of the work qualifies for that — not as a replacement for integration planning, but as a way to see where capacity frees up at the moment it's needed most.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.