I experienced that directly at AXI. The original brief assumed one or two acquisitions and was centred on strengthening the commercial engine, building a more structured inbound capability and creating better links between Salesforce, HubSpot and demand generation. The scope was manageable because the surrounding organisation was expected to remain relatively stable. Instead, the acquisition programme accelerated until ten businesses had to be absorbed into an environment whose commercial architecture was still being built. CONSOLIDATED STORIES.docxDOCX
Ten acquisitions do not simply create ten integration projects. They alter the context in which every previous integration decision was made. A CRM structure that looked sensible after the second acquisition can become inadequate after the sixth, while a brand architecture that initially appeared clear may no longer explain the portfolio once several additional capabilities have entered the group. The target state keeps moving while the organisation is trying to reach it.
That dynamic changes the nature of the work. Integration can no longer be approached as a sequence in which one business is absorbed, the new operating model settles, and management then moves to the next transaction. Decisions about customer ownership, CRM, lead generation, business units and go-to-market structure have to be made while new companies are still arriving. The commercial model therefore develops under live operating pressure rather than inside a controlled transformation programme. Business Plan 20260722 v0.9.docxDOCX
The legal and financial organisation can appear integrated well before the commercial organisation reaches the same point. Reporting lines may have been changed and revenue may already be presented at group level, yet customers can still encounter separate brands, different sales processes and propositions that overlap without an obvious relationship between them. Employees feel the same fragmentation internally when account information sits in different systems or commercial priorities depend on which part of the group they belong to.
None of this automatically means the acquired businesses should be made identical. Their differences often contain much of the value that justified buying them, including specialist knowledge, customer relationships, entrepreneurial speed or a strong position in a particular market. The integration challenge is therefore more demanding than simply imposing a central process. Management has to determine which differences are strategically useful and which differences merely reflect the fact that the businesses grew up separately.
Customer ownership is one area where that decision becomes very concrete. An account may already buy from several companies inside the group, with each commercial team knowing only part of the relationship. What appears on paper as an attractive cross-selling opportunity can create an awkward customer experience if several salespeople approach the same organisation independently or compete for control of the account. The commercial value of a broader portfolio only becomes real when the organisation can see the customer as one customer rather than as a collection of unrelated opportunities.
Achieving that requires more than merging contact records. Teams need enough shared information to understand existing relationships, enough agreement about priorities to know which opportunities should be pursued, and enough clarity about ownership to avoid turning internal boundaries into a customer problem. Without those conditions, cross-selling remains something the organisation talks about more easily than it executes.
Positioning becomes equally important as the portfolio grows. Acquisition logic is usually clear to the people involved in the deal because they understand why a capability, customer base or technology fits the wider strategy. Buyers in the market rarely have access to that reasoning. They simply see a company that is suddenly offering more things, sometimes under several brands and through several sales teams.
A broader portfolio is commercially useful only when people can understand how its parts belong together. Sales needs to know when one proposition leads naturally to another, Marketing needs a structure that allows the group to explain itself without reducing every acquired business to the same generic story, and customers need enough clarity to understand why the expanded company is more useful to them than the businesses were separately. Capability can increase while commercial clarity decreases, especially when acquisition volume outpaces the work required to organise the portfolio.
CRM integration exposes a similar tension. Moving several organisations onto one platform looks like progress because the technology becomes common, but a shared system does not automatically create shared commercial logic. One business may define an opportunity when a customer expresses initial interest, while another may not create one until budget and timing are confirmed. Pipeline stages, account ownership and even basic terminology can carry different meanings across acquired companies.
Those differences have to be resolved before consolidated reporting becomes genuinely useful. Otherwise, management receives one dashboard containing several interpretations of the commercial process, which creates the appearance of visibility without the underlying comparability. The difficult part of CRM integration is therefore not simply migration. It is deciding what the organisation collectively means by the information being entered.
Rapid acquisition also changes the role of central functions. Marketing, Sales leadership and other group functions can easily become integration bottlenecks if every question has to travel to the centre for interpretation. Too little central direction allows fragmentation to continue, while too much centralisation can strip away the speed and expertise that made the acquired businesses attractive. The workable model usually lies somewhere between those extremes, with a limited number of common commercial principles and enough autonomy for genuinely different markets or propositions.
AXI's situation made that balance especially important because the transformation was happening while the business itself continued to expand. The organisation needed inbound and outbound engines, CRM integration and a clearer go-to-market structure, but none of those could be designed around the assumption that the company had finished changing. The commercial system had to provide coherence without depending on organisational stability that did not exist. CONSOLIDATED STORIES.docxDOCX
People also experience acquisition integration differently from management. Someone who joins through an acquisition may see a strong local business, familiar customer relationships and practices that have worked for years. A central request to adopt a new CRM process, positioning structure or reporting cadence can therefore feel less like improvement and more like unnecessary interference. Resistance is not always evidence of unwillingness to integrate; sometimes it reflects a legitimate concern that the new group has not yet understood what should be preserved.
For leadership, that creates a demanding form of judgement. Standardisation is valuable when it removes duplication, improves visibility or makes it easier for teams to work together, but harmful when it replaces useful local capability with bureaucracy. Autonomy is valuable when it protects expertise and responsiveness, but harmful when it prevents the group from acting on shared customers or building a coherent market position. Acquisition integration repeatedly forces management to decide which side of that line each issue belongs on.
These choices become more difficult when acquisitions continue arriving before earlier decisions have settled. Temporary arrangements begin to accumulate because there is always another priority, while individual managers become the bridges between processes that have never been properly connected. Strong people can keep such an organisation functioning for a surprisingly long time by remembering who owns which customer, knowing which system contains the reliable data and resolving conflicts through personal relationships. Their effectiveness can hide how much integration remains unfinished.
Eventually, complexity starts showing up in commercial performance. Opportunities are missed because nobody sees the full customer relationship, propositions overlap without clear positioning, reporting becomes difficult to reconcile and Sales spends increasing amounts of time navigating the organisation itself. At that point, the issue can look like execution weakness even though the root cause lies in accumulated integration choices that were postponed while the business kept growing.
A useful measure of commercial integration is therefore not how many systems have been consolidated or how many businesses now report into the same structure. It is whether the combined organisation has become easier to understand and easier to operate. Customers should find the broader company more useful rather than more confusing, while employees should have better visibility across accounts, propositions and opportunities than they had when the businesses were separate.
That standard also changes the questions leadership should ask after a transaction. Instead of focusing only on whether the acquired company has adopted group processes, management can examine whether the combined portfolio now creates opportunities that neither business could have pursued alone. It can ask whether customers receive a clearer or more complicated experience, whether teams know when to collaborate across business-unit boundaries and whether reporting supports decisions rather than merely satisfying consolidation requirements.
Those questions matter even more in an acquisition programme because every unresolved issue compounds. A small ambiguity in account ownership is manageable across two businesses but becomes significantly harder across ten. A weak portfolio architecture becomes more confusing with every additional proposition, while inconsistent CRM definitions become less useful as more data enters the system. Acquisition velocity therefore increases the cost of commercial ambiguity at the same time as management has less time available to resolve it.
The AXI experience ultimately reinforced a lesson that is easy to underestimate when the focus is on transaction completion. Acquisitions create scale quickly, but scale does not automatically create a stronger commercial system. The value of the expanded business depends on whether customers, propositions, systems and teams can gradually be made to work together without destroying the strengths that came with the individual companies. CONSOLIDATED STORIES.docxDOCX
Revenue can enter the group on the day a transaction closes. Building an organisation that knows how to use the combined customer base, capabilities and market position takes considerably longer, particularly when the next acquisition arrives before the previous integration has finished. Commercial coherence is therefore not the administrative end of an acquisition programme. It is one of the capabilities that determines whether acquisition-led growth becomes more valuable as the organisation gets larger, or simply more complicated.
