A portfolio company does not automatically need one public brand.
Local names carry history. Customers recognize the trucks, the yard, the family, and the reputation. Flattening all of that into one corporate identity can destroy the very trust an acquisition was meant to preserve.
The better move is to separate identity from infrastructure. Let each operating company keep the language, proof, and local relevance its market understands. Share the parts customers do not need to see: analytics standards, lead tracking, reporting, campaign learning, content operations, and governance.
Give every brand a job. One may capture contractor demand. Another may own high-end access control. Another may protect a local search footprint that still produces valuable calls. The architecture should make those roles clear.
Then build cross-referral paths. A fence customer may need a gate. A gate customer may need access control. A fabrication need may begin on a different operating-company site.
The portfolio becomes stronger when the system is shared and the trust stays local.