Building a Scalable Marketing Operating Model Across Nine Acquired Businesses
How I helped a private equity backed group begin turning nine separately acquired businesses into a more connected marketing ecosystem without removing the individual strengths that made those businesses worth acquiring
Acquisition had been an effective growth lever for this private equity-backed group. Rather than trying to build every capability organically, the business had deliberately acquired eight established companies around a flagship ninth business, selecting organisations whose services, expertise and reputations aligned with the wider direction of the group.
Commercially, the strategy made sense. Each acquisition brought something valuable into the portfolio and allowed the group to expand its overall proposition more quickly than building every capability from the ground up.
The complexity came afterwards.
Every acquired business had arrived with its own history, people, marketing structure, customer data, systems, suppliers, processes and interpretation of what good marketing looked like. Some of those differences were important because they reflected the expertise, market position and reputation that had made the businesses attractive acquisition targets in the first place. Others were simply duplication created by bringing separately operated organisations under common ownership.
The challenge was therefore not to turn nine businesses into one identical company.
It was to establish where remaining different created genuine value, where greater consistency would improve performance and where duplication was creating unnecessary cost, risk and operational complexity.
That made this substantially more than a marketing consolidation project. It became a wider exercise in post acquisition integration, marketing infrastructure, customer data, technology, governance and organisational design.
The business had grown faster than the marketing operating model underneath it
The nine businesses had not originally been designed to operate together. They had been acquired because each offered something that strengthened the wider portfolio, but naturally each organisation came with an operating model built around its own requirements before acquisition.
Marketing reflected that history.
There were multiple marketing teams operating across the group, with different levels of capability, different priorities and subtly different definitions of what successful marketing looked like. Those teams had knowledge of their individual businesses and markets that the group did not want to lose, so simply creating one large central marketing department was neither necessary nor desirable.
The larger problem sat underneath those teams.
Customer and prospect data existed across different environments. Systems had been introduced independently and, in some cases, similar functions were being performed by several different platforms. Other systems had gradually become shared across businesses in ways that had developed through necessity rather than deliberate architecture.
That meant the group could be paying for multiple solutions to substantially the same problem while simultaneously depending on individual systems more heavily than anyone initially realised.
Reporting was also more difficult than it should have been because different businesses could define customers, leads, opportunities and marketing performance differently. Even when the underlying activity was similar, the structure around it was not necessarily comparable.
The result was an organisation that had successfully expanded its commercial capability through acquisition but had inherited the marketing and technology complexity of every business it had bought.
The first question was not what could be consolidated
Before deciding what the future group structure should look like, I wanted to understand what had actually been acquired.
The programme therefore began with an audit of all nine businesses.
This was important because starting with a predetermined consolidation plan would have created a significant risk of removing things that genuinely contributed to the value of individual companies.
The audit was designed to answer a broader question:
What role should each business play within the wider ecosystem, and what needs to exist around it for that role to work properly?
That meant looking considerably further than individual campaigns or marketing performance.
Each business needed to be understood in the context of the group strategy, its proposition, its market reputation, its customers, the capability sitting within its marketing team, the technology supporting that work, the data it held and the dependencies it had developed with other businesses inside the portfolio.
The intention was not to assume that the flagship company automatically had the best answer. Acquisition should create an opportunity to identify the strongest aspects of every business and determine what the wider group could learn from them.
In some cases, the best process, capability or technology may already exist within an acquired company rather than the original platform business.
That made the audit as much about finding what should be retained as identifying what should change.
Understanding why each business belonged in the wider portfolio
An important part of the work was understanding the strategic role of each acquired company.
The eight businesses had not been bought randomly. Their offerings and reputations aligned with the longer term direction of the flagship brand and collectively allowed the group to build a broader proposition.
The marketing question was therefore not simply whether each business was performing well independently. It was whether its brand, proposition and market position still made sense within the larger ecosystem that acquisition had created.
That required considering where brands complemented one another, where capabilities overlapped, where customer audiences were shared and where maintaining clear separation remained commercially important.
This is particularly important in acquisition led growth because integration can easily become confused with standardisation. If a business has been acquired partly because of the strength of its reputation, customer relationships or specialist positioning, removing those characteristics in pursuit of organisational simplicity can destroy some of the value the acquisition was intended to create.
The work therefore began from a different principle.
Protect the differences that create value. Remove the differences that create unnecessary complexity.
That principle became increasingly important as the audit moved from brands and people into systems, technology and customer data.
Nine businesses did not need nine versions of everything
It quickly became clear that the biggest integration opportunity was not necessarily within the individual marketing teams.
The group wanted those teams to continue operating separately, allowing them to retain their own market knowledge, relationships and brand focus. What did not make sense was supporting that independence with unnecessary duplication underneath them.
Across a portfolio created through acquisition, it is easy for infrastructure to grow in layers. One business may use one CRM while another has built processes around a different platform. Separate email systems may exist. Websites may use different technology. Reporting can develop independently. Customer information may be stored in different structures, while software licences, suppliers and integrations are contracted separately.
None of those decisions necessarily looked unreasonable when each company operated independently.
The economics change once all of those businesses share common ownership.
The question becomes whether nine separate pieces of infrastructure are still delivering nine different forms of value, or whether the group is simply paying several times for capabilities that could be provided more effectively through a shared foundation.
That was one of the central questions behind the programme.
Rather than centralising marketing itself, the emerging direction was to centralise more of the infrastructure that marketing depended upon.
Centralising the foundations while protecting brand autonomy
The target model was deliberately not a traditional central marketing department controlling every brand.
The better structure was closer to a shared group foundation supporting independent brand teams.
Customer data, core systems, governance and common reporting could increasingly sit within a controlled group environment, while individual marketing teams continued making decisions appropriate to their own audiences, propositions and commercial requirements.
That created an important distinction between centralised infrastructure and centralised execution.
The group did not need every campaign conceived centrally, nor did every brand need identical messaging or customer journeys. Those decisions often benefited from the expertise sitting closest to the individual market.
What did make sense was establishing stronger common foundations underneath that work.
A single properly designed data environment could potentially support all nine businesses more effectively than several disconnected databases. Shared platforms could reduce duplicate licensing and administration. Common standards could make group reporting more reliable. Stronger access controls and governance could reduce the operational risk created when customer information was spread across multiple systems.
The objective was therefore not to make every business look and behave identically.
It was to create a group structure in which differences were deliberate rather than accidental.
Creating one governed view of customer data
Customer data became one of the most important areas of the transformation.
The long term objective was to bring relevant customer and prospect information into a more consistent environment where the underlying records could be governed centrally while remaining segmented according to the individual brands with which those people had a relationship.
That sounds straightforward until the practical implications are considered.
A person might exist within more than one acquired business. The information held about them may have been collected at different times, for different purposes and using different systems. Field structures may vary. Marketing permissions may have been captured differently. Suppression records and communication preferences may not be consistent. One business may consider the individual a customer while another considers them a prospect.
Simply combining those records into one large database would therefore have solved very little.
The aim was to create a much more considered architecture in which there could be a reliable view of the underlying person or organisation while preserving the context of their relationship with individual brands.
That meant thinking about data at more than one level.
There needed to be consistency around identity, data quality and governance at group level, but enough segmentation to understand which business owned the relationship, what that relationship consisted of, what communications were appropriate and what permissions or restrictions applied.
This approach was intended to reduce duplication without treating all group customer information as interchangeable.
That distinction was particularly important from a governance and compliance perspective. Shared ownership of businesses does not remove the need to understand why data was collected, how it can legitimately be used and which people within the organisation need access to it.
The proposed future state therefore needed to improve both commercial usefulness and control.
Reducing technology duplication required understanding dependencies first
The systems review created another layer of complexity.
At first glance, duplicated technology can look like an easy cost saving opportunity. If several businesses are paying for platforms performing similar functions, consolidating those services appears an obvious decision.
Operationally, it is rarely that simple.
Over time, systems become connected to forms, websites, reporting processes, automation, customer journeys and other platforms. A piece of software that appears redundant may be performing a small but critical task for another business somewhere else in the group.
Some platforms were also being shared across companies even though the wider architecture had never been deliberately designed around that model.
That meant rationalisation could not begin with cancelling licences.
The first requirement was to understand what each system did, who used it, what information it contained, what other technology depended on it and what would stop working if it disappeared.
Only then could platforms be meaningfully classified according to whether they should remain, be migrated, be consolidated into another solution or ultimately be retired.
This is one reason the programme became such a significant operational undertaking. Technology consolidation after several acquisitions is not simply a procurement exercise. Every system represents a combination of data, processes, people and dependencies that needs to be understood before change can take place safely.
A different view of the marketing teams
One of the more important strategic choices was what not to centralise.
It would have been possible to look at multiple marketing departments and conclude that combining them into one group team represented the easiest route to efficiency.
That was not automatically the best commercial answer.
The acquired businesses had their own market knowledge, customers, specialist capabilities and brand reputations. Their marketing teams were closer to those individual requirements and, where those teams were working effectively, their independence remained useful.
The intention was therefore to maintain separate marketing teams while creating stronger common standards and infrastructure around them.
This allowed the organisation to separate two questions that are often treated as though they are the same:
Who should make the marketing decisions for each business?
and
How many versions of the underlying infrastructure does the group really need?
Once those questions were considered independently, the target model became much clearer.
Local teams could continue owning appropriate marketing decisions while benefiting from cleaner data, stronger systems, common governance and better group visibility.
Creating common definitions of success
Technology alone would not create a joined up marketing operation.
The audit also exposed the importance of agreeing what success meant across the group.
Nine businesses can easily develop nine different reporting conventions, particularly when they have different histories and commercial models. One company may focus heavily on lead volume, another on revenue, another on pipeline and another on customer acquisition cost. Even apparently common terminology can hide different definitions underneath it.
That creates a significant problem for group leadership because comparing performance becomes difficult when the underlying measures are not constructed consistently.
The transformation therefore also required a common layer of marketing and commercial definitions.
The objective was not to force every business to report exactly the same metrics regardless of context. Individual brands still needed measures appropriate to their own objectives.
What the group did need was enough consistency to understand the portfolio as a whole.
That included knowing what constituted a meaningful opportunity, how performance should flow into group reporting and which core measures needed to be comparable across the businesses.
Without that foundation, consolidating the technology would simply have created a cleaner system containing inconsistent definitions.
Looking for value beyond software savings
Reducing duplicate software and infrastructure was an obvious opportunity, but the commercial case for the programme was much broader.
Every duplicated platform brought more than a licence cost. It created additional administration, additional supplier relationships, additional integrations, additional access controls and another environment containing customer information that had to be understood and governed.
The potential value therefore sat across several areas simultaneously.
There was an opportunity to reduce direct technology and supplier costs where multiple businesses were purchasing substantially similar capabilities. There was an opportunity to improve data quality by reducing the number of places where customer information needed to be maintained. Governance could become clearer because responsibility, permissions and retention rules could be established within a more controlled environment.
Reporting could also become considerably stronger.
Instead of trying to reconcile information from independently structured businesses, group leadership could work towards a more consistent view of customers, opportunities, marketing investment and performance while still retaining the ability to understand results by individual brand.
The work was therefore not simply about reducing what the group spent.
It was about creating an operating environment better suited to the scale the business had already reached.
Designing for acquisition number ten
Perhaps the most important long-term consideration was that the integration work should not only solve the complexity created by the acquisitions that had already happened.
The group had used acquisition strategically as a growth lever. If that approach continued, another acquisition could easily introduce another CRM, another database, another marketing technology stack, another reporting structure and another set of processes.
Without a repeatable integration model, every successful acquisition would recreate some of the same problems.
The programme therefore created an opportunity to think beyond the current nine businesses and establish a more deliberate framework for future growth.
A newly acquired business could eventually be assessed against an established group model covering its strategic role, brand position, marketing capability, customer data, systems, reporting and governance.
That would make integration a repeatable process rather than a new discovery exercise every time another business entered the portfolio.
The longer-term objective was therefore not simply to tidy up the consequences of previous acquisitions.
It was to build marketing infrastructure capable of supporting acquisition-led growth without allowing operational complexity to increase at the same rate.
An ongoing transformation rather than a cosmetic integration exercise
This remains an active programme of work.
That is important because integrating nine businesses safely and sensibly cannot be reduced to a short CRM migration or a new organisation chart.
The initial work began by auditing the nine businesses and establishing what each contributed to the larger ecosystem. From there, the programme could start identifying where brand autonomy remained valuable, where technology and data could become more consistent, where duplicated infrastructure could eventually be removed and what a more scalable group operating model should look like.
The next stages require those decisions to be converted into practical implementation.
Data needs to be understood before it can be migrated. Dependencies need to be mapped before systems can be retired. Brand relationships and permissions need to be preserved within any central customer environment. Marketing teams need sufficient autonomy to continue serving their individual markets while adapting to stronger group standards.
That work takes time because the objective is not merely to make the organisation look tidier.
It is to make it work better without accidentally removing the capability, customer relationships or reputation that the acquisition strategy was designed to secure.
What this project demonstrates
Acquisition can accelerate growth significantly, but it can also multiply complexity beneath the surface of a business.
Every company acquired brings more than additional revenue and capability. It also brings its existing marketing people, customer information, systems, suppliers, contracts, processes, reporting conventions and ways of working.
For a period, those differences can coexist without creating an obvious problem. Eventually, however, the organisation reaches a point where the cost and risk of operating several independent infrastructures begins to outweigh the value of keeping everything separate.
The answer is not necessarily complete centralisation.
In this case, the more appropriate direction was to preserve the independence of marketing teams and the individual strengths of the acquired brands while creating stronger common foundations underneath them.
That required looking at the group as a connected commercial ecosystem rather than treating each company’s marketing function as an isolated department.
The central question became:
Where does being different create value, and where does being different simply create cost, risk and unnecessary complexity?
Answering that properly requires marketing leadership that can move comfortably between brand strategy, organisational design, CRM, customer data, technology, governance and commercial decision making.
It is also why post acquisition marketing integration should begin with diagnosis rather than implementation.
Until the business understands what it has acquired, what should be protected, what should be shared and what no longer needs to exist, moving systems and restructuring teams simply makes the existing complexity look different.
Has acquisition made your marketing infrastructure more complicated than the business expected?
Businesses using acquisition as a growth strategy often inherit far more than products, customers and talented people. They inherit separate systems, databases, marketing teams, suppliers and operating models that were never designed to work together.
If that complexity is beginning to create duplicated cost, unreliable data, inconsistent reporting or uncertainty about how the brands should operate together, I can help assess the marketing function across the portfolio and define what should remain separate, what should be connected and what should be consolidated.
My Marketing Function Review, Fractional CMO services and CRM and Marketing Data Audit provide different ways to begin that process, depending on whether the immediate requirement is diagnosis, ongoing senior marketing leadership or a deeper review of the infrastructure underneath the group.