.png)
When a board asks a management team running a consolidation to report on each acquisition’s performance, it sounds like responsible governance. You spent capital. You want accountability. You want to know if Deal Seven performed as modeled.
That instinct comes from portfolio investing, where assets stay distinct, and tracking reflects how value is created. In a portfolio, that works. But in a consolidation, it’s the wrong model. Teams that apply it end up slower, more fragmented, and further from the platform value they set out to build.
Deal-level tracking in a roll-up produces friction. It tells your integration team to protect the old perimeter rather than build the new one. By the time leadership teams realize what it's costing, the damage is embedded in their systems, structure, and next acquisition.
Two Roll-Ups (and Why the Difference Matters)
Not every roll-up is a consolidation, and that distinction is where most governance mistakes start.
Sam Youssef, Founder and CEO of Valsoft Corporation, runs one of the more disciplined decentralized roll-up models in the software space (Ep. 233). Valsoft acquires vertical-market software companies and keeps them operating independently. Each acquisition is underwritten on a standalone, unlevered IRR basis. The businesses retain their management teams, identities, and operating models. The value comes from Valsoft’s ability to operate each company better than before.
In that model, separate tracking is rational. The businesses are meant to remain distinct. Measuring them individually reflects the structure of the investment.
A platform consolidation works differently. The strategy is not to own many businesses, but to build one business faster than organic growth would allow. Acquired companies are inputs to a single operating model. Their individual performance, once integration begins, isn’t the best unit of analysis. For that, we look to the platform.
As Baljit Singh, SVP and Global Head of Corporate Development at Nielsen Ventures, put it in his conversation on strategic alignment (Ep. 287): "The best way to manage capital allocation is to look at them collectively." M&A dollars in a consolidation are not business-unit bets to be optimized individually. They are investments in a single direction, and they need to be evaluated that way.
When boards import portfolio-investor logic into a platform consolidation, they create a structural conflict between the governance model and the integration strategy. And that conflict compounds with every acquisition.
What Deal-Level Tracking Really Costs
The cost of deal-level tracking in a consolidation shows up in three places. Each one gets harder to fix the longer the model stays in place.
Decision cost. When each acquired company is still being evaluated as a separate unit, integration decisions become negotiations. Which system should both companies adopt? Which sales process is better? Which operational approach should survive?
Both sides advocate for their own, because the acquired team is being measured on the performance of what they brought in. These debates can drag on, meaning decisions that should have been made in the first 30 days of integration are postponed into the first year. While teams debate, the next acquisition waits.
System cost. Delayed decisions harden into Frankenstein architecture: two CRMs running in parallel, two ERP systems, two sets of reporting standards, two customer data models. Ivan Golubic, CFO and Head of Corporate Development at FastLap Group, addressed this in his episode on executing roll-up strategy (Ep. 296):
"It's much easier to start with the right solution and then incorporate other acquisitions into it, rather than trying to synchronize everything after you already have a hundred different locations or divisions."
Every acquisition added before synchronization is complete makes the reckoning more expensive and more disruptive.
Management cost. Leadership bandwidth is finite. In a consolidation running on deal-level accountability, a significant portion of that bandwidth shifts from building the platform to defending the old perimeter. Executives are justifying deal-level metrics to investors, managing the politics over which team's system won, and explaining why the numbers for acquisition seven differ from those for acquisition three. Meanwhile, that time could have been spent on the next deal, the next customer, and making the platform more valuable.
Gwen Pope, a veteran M&A practitioner with experience at Google, Microsoft, and eBay, describes what happens when integration governance breaks down at the decision level (Ep. 340): "Once Corp Dev and the IMO wrap up their work, the deal gets tossed over the wall, and nobody owns it. No executive is tracking whether integration is succeeding. There's no escalation path for issues. And there's no decision-maker when trade-offs need to be resolved."
That’s the compounded cost of deal-level tracking. It doesn’t just slow integration; it removes the ownership structure that integration needs to succeed.
The Measurement Model That Works
The question in platform consolidation is: "What did this deal contribute to what we're building?"
Ivan Golubic describes how PE firms actually measure consolidation performance:
"They want to see the performance of the overall consolidated company. How are you doing now that we've consolidated everyone? Are you covering your extra overhead?"
Deal-level questions — what did we pay for it, what did it earn on its own — are a useful underwriting check while the acquisition is being validated. After that, it folds into the aggregate. Platform-level EBITDA growth, return on invested capital, and overall enterprise value become the signal. Deal-by-deal scorekeeping becomes the noise.
Baljit Singh makes the structural case for why aggregate measurement matters: applying isolated business-unit accountability to a consolidation creates distorted performance optics. Teams optimize for the metric they are being measured on, and if that metric is deal-level performance, they will protect deal-level assets at the expense of platform convergence.
Dan Caruso built Zayo Group through ~45 acquisitions over a decade, investing about $1B in equity and returning 8.5x at exit without relying on premium multiples. His view on deal-level tracking is simple: the moment you ask a board to track each acquisition separately, you signal that they should remain separate. And separate things don’t converge.
After Caruso stepped back, the next leadership team quickly returned to deal-level tracking, a pattern seen across consolidations. It highlights how fragile platform discipline is when it isn’t built into the company's self-measurement.
The vocabulary shift matters operationally. "How did Deal Seven perform?" is about the past. "What did Deal Seven contribute to the platform?" is about direction.
One produces a scorecard, while the other produces a building plan.
The Integration Discipline That Makes Platform-Level Measurement Possible
Platform-level economics happen because someone made an early decision about what the platform standard would be (and then held to it).
Most integrations default to negotiation. Teams compare the acquired company’s systems to the acquirer’s and try to compromise. That’s how you get Frankenstein architecture. Deal-level governance reinforces this because, as long as the acquired company is measured as its own unit, it has leverage to defend its systems.
The alternative is to set the platform standard before the first acquisition and apply it consistently, without re-litigation. As Ivan Golubic puts it: "It's essential to have your IT in order from the beginning." Get systems and reporting right on the first deal, and the second folds in cleanly. Get them wrong, and the problem compounds with every acquisition.
Gwen Pope outlines the governance that makes decisive integration possible: define a North Star before close, track decisions and ownership, and set clear escalation paths so trade-offs don’t surface as executive surprises. “The North Star should guide all integration planning,” she says. “Every decision should align with it. That way, when complexity hits, you’re not debating in a vacuum—you’re operating from clear principles.”
The sequence is simple: set the platform standard, assign decision rights, resolve trade-offs at the functional level, escalate what can’t be resolved, and integrate before exceptions multiply. Speed isn’t a style choice; it’s what prevents deal identities from hardening into structures that take years to unwind.
One Company or Many?
The teams that build durable value in a roll-up are the ones that stop managing a collection of acquisitions and start building one company with one operating model, one measurement standard, and one scoreboard.
To accomplish this, you need governance that matches your strategy. Frameworks designed for portfolio investing don’t transfer to platform consolidations. Tracking each deal isn’t irresponsible; it’s just the wrong tool. Successful operators call that mismatch early, align investors on what platform-level performance means, and build the discipline to deliver it.
If you’re running a consolidation and getting pressure to report on deals individually, check out the Intelligence Hub’s Roll-Up Integration Playbook. It’s built around the discipline of fast-close, full-synergy integration so you can capture value at the platform level.
