The math on add-on acquisitions makes perfect sense on paper. Buy a platform company. Use the existing credit facility to bolt on smaller companies at lower multiples. Consolidate. Grow. Exit the combined entity at a premium.
The strategy works. It has been one of the most reliable playbooks in mid-market PE for a decade.
What nobody planned for is the data.
The add-on surge
Add-on acquisitions saw a substantial increase from the beginning of 2024 through the end of 2025. GF Data’s tracking shows most fall in the $10 million to $25 million range, with many below $10 million. Sponsors are financing these off existing credit facilities from platforms acquired in 2021-2022.
The rationale is sound. Organic growth at 10-12% annually is difficult. Acquisitive growth, where you buy companies and consolidate them under a platform, can get you there faster. Each bolt-on adds revenue, potentially adds customers in adjacent markets, and can deliver procurement and operational synergies that show up in EBITDA.
GF Data launched a dedicated Small Deals report covering the $1 million to $10 million range specifically because of how much activity has migrated to this segment.
The problem is not the strategy. The problem is what each acquisition brings with it.
What every add-on actually delivers
Every bolt-on acquisition arrives with three things the deal model does not account for.
Its own ERP. The $15 million services company you just bought runs on a different accounting system than the platform. Different chart of accounts. Different revenue recognition methodology. Different fiscal year conventions. The platform runs on NetSuite. The add-on runs on QuickBooks. The second add-on runs on Sage. The third one has a custom system built by a consultant who left four years ago.
Its own definitions. Revenue means something different at each entity. Customer count means something different. “Active customer” is defined differently. Margin calculations use different methodologies. Segment reporting follows different logic. Nobody documented these differences because nobody planned for the entities to be combined.
Its own reporting cadence and quality. The platform company reports monthly with a 10-day close. The first add-on reports monthly with a 25-day close. The second add-on reports quarterly. The third add-on reports “when the controller has time.” The operating partner receives a consolidated board deck that presents these four different reporting standards as though they are one company.
The compounding data problem
Each add-on does not just add its own data complexity. It multiplies the integration challenge exponentially.
With one platform and one add-on, you have two systems to reconcile. Two definitions of revenue. Two customer databases. The reconciliation is manual and tedious but manageable.
With one platform and three add-ons, you have four systems, four definitions, four customer databases, and the cross-references between all of them. The reconciliation work does not scale linearly. It scales geometrically. And in most mid-market portfolio companies, the reconciliation is being done by one person in finance who maintains a master spreadsheet that nobody else understands.
That person is the most critical individual in the company for exit purposes. And they are usually someone the operating partner has never met.
The board deck illusion
The board deck presents consolidated metrics. Revenue growth across the combined entity. EBITDA margins. Customer count. Pipeline. The numbers look clean because someone cleaned them. But the process of cleaning them is invisible.
Behind the consolidated revenue number is a manual reconciliation that takes three days every month. Behind the customer count is a deduplication exercise that nobody is confident is accurate. Behind the margin calculation is a set of assumptions about how to allocate shared costs across entities that were never formally agreed upon.
The operating partner sees a consolidated business growing at 15% with 14% margins. What they do not see is that the 15% growth number includes acquired revenue that has not been separated from organic growth, and the 14% margin includes allocation assumptions that a buyer’s diligence team will question.
This is not a problem of bad intent. The finance team is doing the best they can with the systems they have. The issue is that nobody invested in the data infrastructure to support the consolidation. The add-on strategy assumed the data would work itself out.
It does not work itself out.
What diligence reveals
When the exit process starts, the buyer’s diligence team asks three questions that expose the integration gap immediately.
“Show me organic growth separate from acquired growth.” This requires tracking revenue by entity, by vintage, with consistent definitions. If the platform and each add-on define and recognize revenue differently, producing this analysis requires a level of data lineage that most mid-market companies do not have.
“Reconcile customer count across all entities.” A customer of the platform who is also a customer of Add-on 2 might appear twice in the consolidated count. Or they might be counted once in one system and zero times in another because the deduplication logic was never built. The buyer wants to know the real number. The company’s answer is a range.
“Walk me through the EBITDA bridge at the entity level.” The buyer wants to see how each entity contributes to the consolidated number. This requires consistent accounting treatments, documented adjustments, and a chart of accounts that maps across all systems. In a company with four ERPs and no data integration, this walk-through takes weeks to prepare and still contains gaps.
Each of these questions is reasonable. None of them is a trick. And in a company that planned for data integration alongside the add-on strategy, all of them can be answered in 48 hours.
In a company that did not, they become the reason the exit timeline extends by three months, the buyer introduces an earnout, or the deal trades at a discount.
Why nobody budgets for it
The data integration gap exists because the add-on acquisition process does not include a data integration budget.
The deal model accounts for the purchase price. It accounts for transaction costs. It accounts for integration of the sales team, the leadership overlap, and the back-office consolidation.
It does not account for the work of making the data systems talk to each other. The assumption, explicit or implicit, is that the data integration will happen as part of the general “integration” workstream. But the general integration workstream focuses on people and processes, not on systems and definitions.
The systems stay separate. The definitions stay inconsistent. The reporting stays manual. And the cost of this decision does not appear until three to five years later, when the exit process starts.
By then, the cost is not the data integration itself. It is the lost time, the discounted valuation, the extended hold, and the compounding benefit that was never captured because the foundation was never built.
What the first 100 days should include
For any add-on acquisition, the first 100 days should include five data integration steps that cost relatively little compared to the downstream risk they prevent.
Map the chart of accounts. Create a single mapping table that shows how each entity’s chart of accounts translates to the platform’s structure. This does not require system migration. It requires documentation that makes consolidation consistent and auditable.
Agree on definitions. Revenue. Customer. Active customer. Churn. Margin. For each metric the board tracks, document the definition across all entities and agree on the canonical version. If the definitions differ, decide which one the consolidated entity will use and document the bridge.
Establish reporting standards. Every entity should report on the same cadence, in the same format, with the same close timeline. If an add-on currently reports quarterly, shift it to monthly. If the close takes 25 days, invest in shortening it. Consistent reporting is not a preference. It is a requirement for consolidation.
Build the deduplication logic. Customers that span multiple entities need to be identified and reconciled. This is not an enterprise data management project. It is a focused exercise to ensure that customer count, revenue attribution, and retention metrics are accurate across the combined entity.
Separate organic from acquired. From the moment the add-on closes, track its revenue and growth separately from the platform. This is the single most important data point a buyer will ask for. And it is nearly impossible to reconstruct retroactively.
The firms getting this right
The firms that are building enterprise value through add-on strategies and exiting at premium multiples share one characteristic. They treat data integration as a deal-level investment, not as an afterthought.
The data integration budget is in the deal model alongside the transaction costs. The first 100 days post-close include specific data milestones. The operating partner reviews data integration progress the same way they review revenue integration progress.
This is not a technology project. It is an operating discipline. And in a market where the quality premium is compressing and buyers are more selective than ever, it is the discipline that separates the portfolio companies that trade from the ones that sit in the backlog.
The add-on strategy works. But the data strategy has to keep up with it. When it does not, the math that made the add-on attractive becomes the math that makes the exit painful.