In private equity, post-close value creation is getting harder. McKinsey’s latest private equity research shows entry multiples remain elevated, leverage is contributing less to returns than it did in prior years, and firms are relying more heavily on operational improvement and EBITDA expansion to hit targets.
That is exactly why post-merger IT and telecom rationalization deserves more attention than it usually gets.
Most acquired businesses do not come into a deal with a clean infrastructure stack. They arrive with different carriers, different voice systems, different mobile contracts, different branch architectures, different firewall standards, and different support models. On day one, those inconsistencies may look like background noise. By day ninety, they become integration drag.
The combined business starts carrying unnecessary run-rate expense, duplicated vendors, uneven service levels, and preventable risk. That directly suppresses EBITDA, slows integration, and makes future scaling harder than it should be.
For PE operating partners, portfolio CIOs, and integration leaders, the question is not whether rationalization matters. The question is how quickly the combined business can move from inherited complexity to a repeatable operating model.
The cost of fragmentation usually shows up in four places.
Telecom is one of those categories where cost can hide in plain sight. CFO.com, citing Aberdeen Group research, reported that organizations using centralized telecom usage and invoice reconciliation saved an average of 26%, while Gartner analyst Eric Goodness noted that 12% to 20% of telecom charges are estimated to be in error and that most of those errors favor the carrier.
That matters in a PE environment because acquired companies often bring separate billing systems, separate contracts, and separate local buying decisions. Without centralized inventory and invoice validation, it becomes difficult to answer basic questions: What are we paying for? What is still under contract? Which circuits are inactive? Which sites are overbuilt? Which locations are under-protected?
That lack of visibility is not just an accounting nuisance. It is avoidable EBITDA leakage.
Carrier readiness has a real operational impact. AT&T’s current Dedicated Internet materials state that fiber-ready sites can be installed in as little as 10 to 20 business days, while non-fiber-ready sites may take 30 or more business days. AT&T’s product page similarly says installation at fiber-ready locations can happen in as little as 10 days.
In a roll-up strategy, that delta matters. If a business is opening locations, consolidating offices, standing up a call center, or moving a site onto a standard UCaaS platform, connectivity timing affects the entire integration sequence. A site that is not network-ready is not truly operationally ready.
Post-merger rationalization is therefore not only a cost exercise. It is a speed-to-execution exercise.
Voice platforms are not just about dial tone anymore. They also carry emergency calling obligations. According to 911.gov, Kari’s Law requires direct dialing to 911 without needing a prefix on covered multi-line telephone systems, and RAY BAUM’S Act requires dispatchable location information so responders can identify where a caller is located.
That means inconsistent voice environments across acquired companies can create compliance and safety problems. One site may have modern location-aware configuration. Another may not. One platform may be centrally governed. Another may still be managed locally. In post-merger environments, that inconsistency is exactly what needs to be rationalized.
IBM defines secure access service edge, or SASE, as a network security approach that combines wide-area networking and network security capabilities into a single, integrated, cloud-delivered service.
That definition matters because many acquired businesses bring fragmented branch and edge environments with them. One company may have legacy MPLS with separate firewalling. Another may have broadband plus SD-WAN. Another may have partially modernized around cloud-delivered security. Left alone, that sprawl leads to too many vendors, too many consoles, too many policy models, and too much operational friction.
SDxCentral, citing Gartner, reported that enterprises are increasingly consolidating around one or two SASE vendors to reduce complexity and streamline administration. That trend aligns directly with what many PE-backed businesses need after integration: fewer vendors, fewer overlapping tools, and a cleaner model for branch connectivity and security.
This is where many firms get sloppy. “IT rationalization” is a broad phrase, and it can easily drift into software estate cleanup, ERP modernization, or general application portfolio work.
That is not the right frame for NCG.
For NCG, post-merger rationalization should stay focused on five infrastructure domains.
This includes legacy PBX environments, cloud voice migrations, number management, emergency calling configuration, user provisioning, and support governance. In many post-merger environments, voice is inherited rather than designed. Rationalization means moving from a patchwork of legacy and cloud systems toward a manageable standard.
This includes dedicated internet, broadband, coax, fiber, MPLS, failover architecture, bandwidth right-sizing, and SD-WAN placement. Not every location needs the same design, but every location should fit into a deliberate operating model rather than a legacy artifact.
Mobile contracts are often overlooked during M&A integration. Yet they frequently contain unnecessary cost, fragmented plan structures, inconsistent device policies, and too many local exceptions. Mobility should be governed as part of the telecom strategy, not as a separate afterthought.
Where relevant, PE-backed platforms in logistics, field services, transportation, and distributed operations can benefit from standardizing telematics and connected-asset infrastructure. This is not theoretical. The U.S. Department of Transportation has noted that fuel can account for roughly 28% to 38% of operating costs in Class 8 trucking, which is why fleet visibility and operational efficiency can materially affect cost performance.
This is the layer where SD-WAN, firewalling, policy consistency, and SASE strategy intersect. The goal is not to buy buzzwords. The goal is to reduce sprawl and move toward a supportable, scalable edge architecture.
A lot of teams undersell this work by framing it only as “bill cleanup.” That is too narrow.
Yes, direct savings matter. Efficio notes that procurement programs can create disproportionate value in PE because even moderate savings on addressable spend can produce meaningful EBITDA growth and valuation impact at standard market multiples.
But the real business case is broader.
When site profiles, preferred vendors, and support models are standardized, future cutovers get easier. New acquisitions can be onboarded faster. New branches and facilities can be provisioned with a repeatable playbook rather than reinvented every time.
The combined business gets a cleaner inventory, clearer ownership, and better visibility into renewal dates, service levels, and active spend. This makes it easier to govern exceptions and harder for waste to hide.
A platform company that plans to grow through acquisitions cannot afford to absorb endless local variation forever. At some point, inherited complexity becomes a tax on growth. Rationalization reduces that tax.
AT&T’s current dedicated internet materials emphasize proactive monitoring, embedded security features, and uptime commitments as part of the service model. While every provider has its own specifics, the broader point is simple: when connectivity and edge architecture are standardized, it becomes easier to define the right resilience level for each site type and enforce it consistently.
The most effective teams do not start with product pitches. They start with visibility, operating discipline, and sequence.
Before standardization, the combined business needs one source of truth.
That means documenting:
If leadership cannot see the estate, leadership cannot rationalize the estate.
Not every site should be identical, but most sites can be grouped into practical categories: headquarters, branch, retail store, clinic, warehouse, service depot, and so on.
Each archetype should define the expected:
This is how rationalization becomes operational instead of theoretical.
Once the target-state model is clear, the commercial strategy changes. Instead of dozens of local decisions, the PE-backed platform can negotiate from aggregate volume and standard requirements.
This is where the real value of centralization appears. Better rate cards matter, but so do co-termination strategies, escalation paths, implementation commitments, and cleaner support terms.
Do not try to transform every site at once. Start with locations where complexity is high and business risk is manageable. Validate the design, validate the cutover motion, and validate support responsiveness.
Then scale.
This is especially important in voice, where emergency-calling configuration cannot be treated casually. 911.gov’s guidance on direct 911 dialing and dispatchable location is clear enough that this should be a formal workstream, not a footnote.
This is the step many integrations miss.
Rationalization only sticks when invoice validation, contract oversight, support governance, and change control become routine. Otherwise, local exceptions creep back in and the business slowly recreates the same fragmentation it just paid to eliminate.
A disciplined program should show progress in phases.
Leadership should have visibility into the existing estate: site inventory, vendor map, contract dates, likely overpayment areas, and obvious operational risks.
The business should have a target-state architecture: standard site profiles, preferred carrier strategy, voice direction, mobility governance, and an edge-security view.
The first migration wave should be active or complete, invoice validation should be underway, and early savings or operational improvements should be documented.
The combined business should have a repeatable model: clear standards, active governance, and a rationalized path for future acquisitions, site openings, and upgrades.
That is the difference between integration activity and integration capability.
The following is a composite example based on common post-merger scenarios, not a single client engagement.
A mid-market PE firm combines three multi-location businesses into one platform with roughly 75 sites. Each business brings different carriers, different branch architectures, different voice systems, and different support habits.
The integration team starts with inventory and quickly finds inactive services, uneven bandwidth allocation, scattered mobile contracts, and multiple voice environments with inconsistent location data. Some sites are materially overbuilt. Others are under-supported.
The team then defines standard site bundles. Critical sites move to cleaner dedicated internet or fiber-based designs with backup connectivity where needed. Voice is standardized and emergency-calling configuration is formalized. Mobility contracts are consolidated. Edge security is narrowed to a smaller number of policy models and support paths.
The result is not just lower spend. It is a cleaner operating platform: fewer vendors, fewer billing surprises, faster site turn-ups, and less friction on the internal IT team.
That is the real point of rationalization. It is not about making the stack look tidy. It is about making the platform easier to scale.
Private equity firms are under more pressure than ever to create value through execution, not just capital structure. That makes post-merger telecom and infrastructure rationalization more important than it may have looked in easier markets. McKinsey’s latest data reinforces the same broad point: as leverage contributes less and entry multiples stay high, operational improvement matters more.
For PE operating partners and portfolio CIOs, the opportunity is straightforward. Reduce duplicated vendors. Standardize voice, connectivity, mobility, and network-edge decisions. Build a repeatable model. Eliminate complexity the platform is no longer being paid to carry.
That is how infrastructure stops being inherited baggage and starts becoming an operating advantage.
For firms evaluating post-merger infrastructure complexity across portfolio companies, NCG’s role is to help rationalize voice, connectivity, mobility, IoT, and edge environments into a more scalable operating model.
.png)