Buying doors is easy; stitching networks together is not. Consolidation between MDU providers creates scale on paper. Whether it creates a better operator depends on something far less glamorous: whether the buyer can stitch the networks it acquires into a single network. This final part is about the work on the technology stack behind the hardware and the plumbing underneath, and why it determines who actually wins.
In sum – what to know:
- A door count is not an operator: a provider can cross a hundred thousand units and still be running four or five separate networks held together by four or five separate teams.
- The hardware mismatch is hard, but the harder problem is the plumbing underneath: the billing, provisioning, monitoring, and support systems that each company brings.
- The providers that win treat plumbing as a real asset; property owners should ask whether a provider’s doors run on one coherent platform or several.
Parts 1 and part 2 in this series established that consolidation is underway and mapped who is driving it. This final part is about the piece that never makes the press release: what it actually takes to turn the companies you buy into a single operator. The capital has chosen scale, customers are concentrating, and the largest operators have decided that multifamily is where their growth must come from. What none of that settles is whether a buyer can deliver on the promise of scale once the deal closes. Buying doors is the easy part. Making the acquired networks behave as one is where most roll-ups either earn their money or quietly give it back, and it is what the rest of this part is about.
The figure that drives every MSP acquisition is the door count, but the doors arrive attached to hardware and software that rarely match the buyer’s. This is where roll-up math meets operational reality. A platform can announce that it has crossed a hundred thousand units, but if those units run on four different networks, each held together by a different team, the announcement describes a billing total, not a single network.
Consider the most basic case. An MSP standardized on RUCKUS acquires an MSP built on Cambium. Overnight, the combined operator runs two access-point fleets with different controllers, firmware lifecycles, radio-frequency tuning philosophies, and entirely separate spare-parts inventories. Add a third acquisition running Meraki or Calix, or a TIP OpenWiFi deployment, and the operator is now maintaining four or five parallel hardware platforms, each with its own makes and models, its own trained technicians, its own vendor relationships, and its own upgrade path. The scale economics that justified the deal assumed one network to run, not five.
The plumbing underneath is the harder problem
The radios are the visible part that residents and owners can see. The harder problem is the plumbing behind them, the software that actually runs the business. Acquired companies bring their own network management and monitoring systems, provisioning and authentication, billing engines and resident portals, and ticketing and support tools. These are the parts a property owner never sees, and the acquirer cannot avoid.
A consolidated operator faces an unattractive choice. It can run all of these systems in parallel, which multiplies operating costs and headcount and erodes the very efficiency the acquisition was supposed to deliver, or it can undertake an expensive, multi-year migration to a single standard, which carries a real risk of service disruption in occupied buildings where residents notice every outage. Neither path is cheap, and the cost rarely shows up in the headline purchase price.
INSERT
The difficulty compounds because each system was chosen for a reason and wired into daily operations. A support team trained on one ticketing workflow does not become productive on another overnight. A billing connection tuned to one property management platform has to be rebuilt for the next. Resident-facing applications have their own brand, logins, and support history. Reworking any one of these is a project; doing all of them across several acquired companies at once, without dropping service, is the central operational challenge of building a scaled platform, and it is routinely underestimated at the point of acquisition.
“Door count is not an operational scale. In a roll-up, every acquired operator brings its own controllers, billing, monitoring, ticketing, and support. The real question is whether the buyer runs one operating model or several companies under one logo. The winners keep the hardware flexible but standardize the control layer above it, turning the integration tax into a reusable asset instead of a cost that compounds with every deal,” says Magnus Johansson, chief executive and co-founder at WiBUZ.
Why do some operators plan the merger before they buy
This is the unspoken logic behind two strategies that look like ideology but are really about keeping the merger cheap. The vendor-agnostic operators, the ones who invest in an in-house development team to run a multi-vendor back-end, are building a common layer above the hardware precisely so that absorbing whatever systems an acquisition brings incurs lower costs, but these in-house developments are very costly and prone to many delays.
The open Wi-Fi advocates are making a parallel bet that a shared, vendor-neutral control layer will make consolidation cheaper by decoupling the software from any single manufacturer. Single-vendor operators gain depth, roadmap influence, and simpler day-to-day operations, but they pay for it with a harder merge the moment they buy across vendor lines. There is no free version of this trade-off.
The conclusion is that the platforms that win consolidation will not be the ones that simply buy the most doors. They will be the ones who treat the plumbing, rather than the hardware, as the real asset, and who walk into every deal with a deliberate plan to stitch it together. MSPs who buy doors without a plan for the plumbing inherit a complexity tax that compounds with every deal, until the cost of running the patchwork cancels out the benefit of scale.
The ability to stitch acquisitions into one operation, not the appetite to make them, is the skill that separates a durable platform from an expensive collection of mismatched networks. It is also the reason that service quality, the thing property owners actually buy, is most at risk in exactly the period when an operator is growing fastest.
The implication for property owners
For owners and operators of multifamily real estate, the consolidation of the MSP segment is not a spectator event. It changes who will be on the other side of the table at the next renewal and shifts the leverage in the negotiation. The provider landscape five years from now will be less crowded, more capitalized, and more capable, but also more concentrated.
Owners who understand that shift can use it, choosing partners with the balance sheet to fund the roadmap and the scale to serve the whole portfolio, while asking the harder diligence question that most owners skip: not how many doors a provider runs, but whether those doors run on one coherent platform or on the unmerged remains of several. The provider that has done the stitching, on the hardware and on the software, is the one whose service will hold up as it grows. The managed Wi-Fi market is growing, and the owners who choose well will share in that maturity rather than be subject to it.
Maravedis sizes and tracks the MDU market in its 2026-31 market analysis, and works directly with operators, investors, and property owners via a strategy consulting practice. Contact [email protected].
