Multi-Brand Integration Strategy
The Setup
StellarWP (part of Liquid Web) wasn’t just running one WordPress company—they were running five. The Events Calendar. LearnDash. Kadence. GiveWP. Multiple product lines, multiple communities, multiple identities. Each had loyal users who’d been with them for years. Each had its own voice, its own way of talking to creators, its own reasons for existing.
Then the acquisitions happened. And suddenly you’ve got a corporate parent asking: “How do we make this one thing?”
The instinct from the top was obvious. Slap the StellarWP logo on everything. Consolidate the messaging. Speak with one voice. Efficiency, right?
Except that’s not how communities work.
The Build
The real work was finding what these brands actually had in common—and it wasn’t their logos.
What they shared: a mission to serve WordPress creators. Not just developers, but people building their livelihoods on WordPress. People who care about their tools working well, getting support when things break, and having a say in where products go.
We started by mapping each brand’s unique position:
- The Events Calendar was the trusted event management standard. Event organizers trusted it. It had to stay authoritative, reliable, boring in the best way.
- LearnDash spoke to educators, course builders, people taking a risk on online education. Their tone had to feel like a partner, not a vendor.
- Kadence was the design tool for creators who didn’t want to code. They needed confidence, permission, inspiration.
- GiveWP served nonprofits and mission-driven organizations. The voice had to honor the work they do.
Then we built what I called the “WordPress Creator Ecosystem”—not four separate products, but four tools inside one larger story about building sustainably on WordPress. Same mission. Different angles. Each brand kept its name, its visual identity (mostly), its community.
The messaging framework became: “These are the tools you need to build, teach, design, and sustain on WordPress.” Not “we acquired these, deal with it.” Not “we’re now unified, buy everything.” Just: here’s how they work together.
The Mess
Oh, there was mess.
Internal politics first. Product teams didn’t want to be “owned.” Existing customers saw the acquisition and got nervous—would their product get deprioritized? Would support get worse? Would the thing they’d paid for and loved get killed off or absorbed into a worse version?
There was the brand loyalty problem. LearnDash customers didn’t care about Kadence. The Events Calendar users didn’t need GiveWP. You couldn’t just cross-sell everyone to everyone and hope it worked. That erases identity.
Then came the harder part: integrations had to happen. Some of them made sense (The Events Calendar + GiveWP for fundraising events). Some felt forced. Some products didn’t technically fit into the ecosystem at all, but corporate needed them to.
And throughout it all, there was the tension between what looks unified on the surface and what actually serves real people. You can’t make a brand integration work by pretending five different communities are one community. You can only make it work by respecting that they’re different and building a system where different can coexist.
The Result
We shipped a full rebrand + integration framework that:
- Kept each brand’s name and core identity intact
- Built a visual system that felt unified without being uniform
- Created shared messaging about “building on WordPress” that didn’t dilute individual product positioning
- Set up content and SEO infrastructure so that each product showed up where its own customers were looking
- Established a communication playbook for when to speak as individual brands and when to speak as StellarWP
The portfolio approach won with internal stakeholders because it was honest. “We’re one company with different products” landed better than “we’re consolidating everything into one thing.” It landed better with customers because it was true.
Cross-product adoption went up, but not because we forced it. It went up because people actually wanted to use multiple tools once they understood how they fit together. That’s the difference between integration and coercion.
The Takeaway
Most brand consolidations fail because they try to erase difference. They assume “unified” means “the same.” But unified can also mean “aligned around a shared purpose without losing what makes each part special.”
The insight that changed everything: integration isn’t about making things the same. It’s about making them work together while respecting what made them matter in the first place.
That’s harder than just changing logos. It’s also why it actually works.
What Changed Because of This
- Each brand’s messaging got clearer, not muddier
- Product positioning became easier because we had a clear framework
- Cross-product initiatives stopped feeling like forced marriages and started feeling like natural extensions
- Customer conversations shifted from defensive (“no, we’re still supporting this”) to constructive (“here’s how you can use these together”)
- Internal teams stopped fighting the consolidation because it made space for them to keep doing what they did well
- The WordPress creator community saw StellarWP as a partner with multiple tools instead of a corporate acquirer with a new logo
Ready to do this for your acquisition or rebrand?
If you’re sitting on multiple brands, products, or personalities that need to work together without losing their souls, let’s talk. Book a build session and we’ll figure out what stays, what shifts, and what actually holds everything together.