A merger or acquisition in the energy sector carries a weight that does not play out to the same degree in other sectors. Permits, grid connections, metering data and contracts with grid operators or regulators are not something an integration team can simply speed up on its own. Where in other sectors most of the delay sits in people and systems, here a substantial part sits with external parties that do not move at the pace of the deal. That changes the order of an integration: some steps wait on a third party before they can even begin internally.
On top of that, the sector often works with long-term contracts, capacity agreements and sometimes regulated tariffs. Two companies merging each bring their own set of ongoing obligations. Those obligations cannot simply be added up or averaged; some are legally fixed for a period that extends far beyond the integration itself.
For every part of the integration, the question applies whether it should be combined at all. In the energy sector that may hold even more strongly than elsewhere: a shared ERP system delivers something, but a shared permitting process could just as easily produce twice as much delay as gain. Metering data and billing systems are another example: merging them sounds logical, but if the underlying tariff structures differ, a technical and legal issue arises that can outweigh the synergy it was meant to deliver.
This trade-off should not be made implicitly. It belongs on the decision list, along with the reason why something is or is not combined, and who made that choice.
The synergy baseline is the starting point: a generator that records the assumptions before the integration begins. In the energy sector, that means making explicit which synergies depend on external approval, and which can be realized directly, internally. Those two categories easily blur together if they are not named separately, with the result that a synergy is already booked on paper while the underlying permit has not even been applied for.
The way a synergy is substantiated, and who is responsible for it, is not a sector-specific question. Those working from a buy-and-build strategy can read how a synergy is substantiated in a buy-and-build and who within the organization owns that synergy. Both questions recur in the energy sector, but with an extra layer: ownership of a synergy that depends on a permit differs from ownership of a synergy that can be fully realized internally.
The Day 1 plan in the energy sector must account for two speeds running side by side: the internal organization, which can act from day one, and the external dependencies, which have their own pace. A Day 1 plan that makes no distinction between what the company controls itself and what lies beyond its influence risks having internal teams wait for something that can take weeks or months, without that wait being recorded anywhere.
The Day 100 plan builds on that: which dependencies have since been resolved, which are still pending, and which parts of the integration have, based on the first few months, still been decoupled because merging cost more than it delivered. The latter is not an exception to the rule but part of the process: not every plan needs to remain standing.
The tension between internal speed and external dependency is not unique to energy. In the installation sector a similar pattern occurs around permits and certifications that delay the integration, and in construction something similar arises with ongoing projects and subcontractor agreements that cannot simply be transferred. Those working in the real estate sector will recognize a different pattern around lease agreements and valuations that force the integration into their own pace. The external party differs per sector; the structure of the problem — waiting for something the integration team cannot speed up itself — is the same.
The integration office keeps track of where each synergy stands in the process, which dependencies are still open and which decision on merging or keeping separate has already been made. In a sector where part of the process lies outside the organization itself, that overview is not just a status update but a way to see where the delay comes from, and whether that delay lies with the organization itself or with a third party.
These generators and the integration office record what needs to happen, who depends on what and which parts are or are not being merged. What they do not answer is how much of the underlying work — filling in templates, keeping track of statuses, rewriting reports for different stakeholders — actually needs to be carried out by people. FTE TO AI's work scan calculates, per task, which part of that work can be taken over by AI, so that it becomes clear where an integration team's time is genuinely needed and where it is not.
The generators for the synergy baseline, Day 1 plan and Day 100 plan, and the integration office built around them, are currently being built. Those who want to work with this once it becomes available can sign up for the waitlist.
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.