In this article
For many people involved in a transaction, signing feels like the finish line. The negotiations are over, the documents are agreed and the advisers' most intensive work is done. For the business, it is closer to a starting line. The reason for the transaction — a new market, a new capability, a stronger combined business — has to be delivered through integration, and the agreement itself often creates obligations that continue for some time.
This article explains why integration should be planned before completion rather than after it, and how to approach the first period, governance and reporting, people and culture, customers and suppliers, systems and processes, and continuing obligations. Wherever legal or regulatory obligations are involved, they must be confirmed with qualified counsel; nothing here describes what any agreement or law requires.
The work continues after signing
Two things happen after a transaction is signed. First, there may be a period before completion during which conditions are satisfied and the parties prepare to transfer ownership or control. Second, once completion happens, the business must actually operate in its new form.
Both periods need planning. Before completion, the parties typically must continue to run their businesses within the limits set by the documents and the law, without acting as if the transaction had already completed. After completion, integration begins — or, if the plan is to keep the businesses separate, the arrangements for independent operation must be put in place.
Planning integration before completion
Integration planning that starts only after completion tends to be rushed. Planning earlier allows the team to:
- turn the objective of the transaction into specific integration goals;
- identify which decisions must be made on the first day and which can wait;
- prepare communication to employees, customers and suppliers;
- line up the people, systems and advisers needed;
- spot dependencies, such as people who must relocate or systems that must be connected.
Planning before completion must respect confidentiality and the legal limits on coordination between parties that are not yet combined. Advisers can explain what information may be shared and what activities must wait. The transaction objective described in defining the transaction objective before engaging advisers is the anchor for every integration goal.
Deciding how far to integrate
Not every transaction aims at full integration. Some acquired businesses are deliberately kept largely independent; others are fully absorbed; many sit in between, with shared reporting and governance but separate operations. Being explicit about the intended approach avoids confusion and shapes every later decision.
Useful questions include:
- Which functions will be combined, which coordinated and which left separate?
- What must stay unchanged to protect the value of the acquired business — a brand, a team, a customer relationship?
- Where does combining bring a genuine benefit, and where does it only add disruption?
The first period after completion
The early period after completion sets the tone. People inside and outside the business watch closely for signals about what will change.
A practical first-period plan usually covers:
- Leadership and decision-making — who is in charge of what, and how decisions are made in the interim;
- Communication — what employees, customers and suppliers are told, by whom and when;
- Continuity — the activities that must not be interrupted, such as payroll, customer service and supply;
- Quick decisions — the small number of decisions that cannot wait;
- Listening — ways to hear concerns from employees and customers early.
Resist the temptation to change everything at once. Stability in the early period often protects more value than speed. Where a change is genuinely urgent, explain the reason for it, so that people can tell the difference between a deliberate decision and the uncertainty that naturally follows any change of ownership.
Governance and reporting
After completion, the new owner or combined group needs to understand and oversee the business. That usually means agreeing:
- how boards and management bodies are composed and how they operate;
- which decisions require approval at group level;
- what management information is reported, in what format and how often;
- how financial definitions are aligned between the businesses;
- how risks and compliance are monitored.
Aligning financial definitions deserves particular care. If the businesses measure revenue, costs or performance differently, reports may look comparable when they are not. The financial preparation described in preparing for due diligence: organising company information often provides a useful starting point.
People and culture
Most integration challenges are ultimately about people. Employees want to know what will happen to their roles, their teams and their working conditions. Different working cultures meet, sometimes across languages and countries.
Helpful practices include:
- telling people what is known and what is not yet decided, honestly and early;
- identifying key people whose departure would harm the business, and talking to them directly;
- respecting any obligations to inform or consult employees, as advised by employment lawyers;
- creating opportunities for teams from both sides to work together on real tasks;
- recognising that cultural differences are not solved by memos.
Where people need to move between countries as part of integration, their work authorisation and personal circumstances require separate planning, as described in people in a transaction: when staff may need to relocate.
Customers and suppliers
Customers and suppliers often learn about a transaction at the same time as the public. They want to know whether service, terms, contacts and quality will change. A planned approach usually includes:
- identifying the most important relationships and assigning a named person to each;
- preparing clear messages about what changes and what does not;
- checking which contracts may need notifications or consents, with legal advice;
- monitoring signs of concern, such as delayed orders or questions about terms.
Systems, processes and data
Systems integration can be one of the most complex and disruptive parts of the work. Before changing anything, understand what each business relies on, how data flows and where the risks lie. Decide which systems will be combined, which will stay separate for now and how data will be protected during any migration.
Data protection deserves particular attention. Combining customer or employee data may raise legal questions that should be answered by qualified advisers before any transfer takes place.
Continuing obligations to confirm with counsel
Transaction documents and the law may create obligations that continue after signing or completion. Depending on the transaction, these might relate to:
- conditions or undertakings given to obtain an approval;
- payments or adjustments that depend on later events;
- protections given by one party to the other, and the process for raising claims;
- restrictions on the parties' activities for a period;
- reporting, notification or registration steps in one or more jurisdictions;
- obligations towards employees.
Do not rely on memory or summaries. Ask counsel for a written list of continuing obligations, their owners and the relevant dates, and keep it with the integration plan.
Tracking integration
Integration needs the same discipline as the transaction itself. A simple tracker — goals, actions, owners, dates, status and risks — reviewed regularly by an integration lead keeps work visible. Separate measures of progress (actions completed) from measures of outcome (whether the goals of the transaction are being achieved), and review both.
Learning from the process
Every transaction teaches something about preparation, coordination and integration. A short review once the integration is under way — what worked, what took longer than expected, what would be done differently — is valuable for any future transaction and for the way the combined business works.
In short
Signing is the start of delivering a transaction, not the end. Plan integration before completion, decide how far to integrate, manage the first period carefully, put governance and reporting in place, treat people, customers and suppliers with care, approach systems and data cautiously, and keep a written list of continuing obligations confirmed by counsel. Coordinated well, integration turns the objective of the transaction into a working business.
If you would like help preparing integration planning and keeping continuing obligations organised, you can talk to Wobridge.
General information only. It is not legal or migration advice, and requirements can change — please confirm current details for your own case before acting on them.


