A closer look at how we work with portfolio companies, drawn from real engagements across our practice.
The portfolio company had grown through a series of bolt-on acquisitions, each one bringing its own systems, its own processes, and its own version of the truth. By the time we were engaged, the business was running four separate ERP instances, three CRM platforms, and a patchwork of spreadsheet-based reporting that made group-level visibility nearly impossible. Finance could not close the books with confidence, operations teams across business units were working from different customer records, and the investment committee had no reliable single view of performance across the platform.
The risk was not just inefficiency. Every quarter the fragmentation persisted, it became more expensive to unwind, and it stood in the way of the operating leverage the platform strategy depended on.
We were brought in to lead the integration roadmap. Rather than pursue a single big-bang migration, which would have carried significant operational risk during a period when the business needed to keep performing, we sequenced consolidation in phases tied to the calendar the finance and operating teams could actually absorb. Early phases focused on establishing a unified chart of accounts and a single reporting layer, so leadership gained group-level visibility well before the underlying systems were fully merged. Later phases consolidated the ERP and CRM platforms themselves, retiring duplicate systems one business unit at a time, with clear rollback points built into each stage.
Throughout, the priority was protecting day-to-day operations. Customer-facing teams kept working without disruption, and finance kept closing the books on schedule. The integration ran alongside the business, not against it.
The result was a single source of financial and operational truth across the platform, delivered without the operational disruption that a faster, less structured consolidation would have risked. Leadership gained the visibility needed to manage the business as one platform rather than a collection of legacy entities, and the underlying systems architecture was left in a state that could support further bolt-on acquisitions without repeating the same fragmentation.
Book a call and tell us about the situation you're navigating.
Book a call