May 6, 2026
Merge now, cry later
How to organize 3 acquired companies into one coherent website
Four brands, one website, and a comment section ready to fight about it
TLDR: The article argues that after buying several companies, the best way to build one clear website is to organize it around what customers need to do, not around internal brand history. Commenters agreed in principle but roasted the usual merger chaos, saying the real battle is getting proud teams to stop building a site around their own turf.
A seemingly sensible guide to merging four acquired companies into one website somehow turned into group therapy for corporate turf wars in the minds of readers. The article’s main pitch is simple: stop organizing the site around which old company owns what, and start with what real people are actually trying to do. In plain English, don’t make customers learn your office politics just to figure out how to move a couch, relocate an office, ship a painting, or log into software. Fair! But the community reaction? Way more dramatic.
The strongest opinion by far was that this is less a website problem and more an ego problem. Commenters joked that every acquired company thinks its menu item deserves top billing, and several compared merger website planning to a family reunion seating chart designed by rivals. Others loved the article’s user-first approach, calling it the only sane way to avoid a homepage that reads like a corporate ransom note. The hot-take crowd was split between “yes, organize by customer goals” and “good luck getting four internal teams to stop fighting long enough to agree on what a customer even wants.”
The humor wrote itself. People mocked the usual post-merger web mess with lines about “three clicks to find a phone number and seven to discover you’re on the wrong brand entirely.” One recurring joke was that the true universal navigation tab should just be ‘What did we buy, exactly?’ Another meme-ish reaction: every merger promises “synergy,” but users just want to know who does what without needing a flowchart. Brutal, funny, and honestly? A little too real.
Key Points
- •The article recommends defining user goals before making rebranding or information architecture decisions after acquisitions.
- •It uses a sample case of four related businesses in relocation services and software to show how different offerings can create website complexity.
- •The article says internal product-focused discussions can help gather context but may reinforce divisions between acquired teams.
- •It advises organizing homepage and navigation content around user goals and ways users complete tasks, rather than around company ownership.
- •It recommends using taxonomy labels such as location, role, phase, and specialty to help users orient themselves and find relevant content quickly.